Product, process or business model: what is changing?

Product, process and business-model innovation describe different aspects of change. Product innovation concerns what is offered. Process innovation concerns how work is carried out. Business-model innovation concerns the logic connecting the offer, its delivery and how the organisation sustains itself. One initiative can involve all three.

These categories are useful when they clarify responsibilities and evidence needs. They are less useful when a team spends more time arguing about the label than investigating the change. Begin with “What is different, for whom, compared with what?” Then choose the vocabulary that helps you explain it.

Start with a reference point

Imagine a fictional lighting company that sells desk lamps to small offices. It is considering a lamp with replaceable high-wear parts, a new repair workflow and a service in which it supplies and maintains lighting rather than simply selling individual lamps. The three proposals overlap, but they do not ask the same questions.

Before classifying anything, state the baseline. What does the company offer now? How are repairs handled? Who owns the lamps and pays for maintenance? Without that baseline, words such as “new” and “radical” become claims with no clear comparison.

The Oslo Manual’s definitions distinguish product and business-process innovation, allow combinations, and require implementation. An unlaunched concept is therefore an innovation activity or proposal, not automatically an implemented innovation. The manual is a measurement reference; everyday management vocabulary is sometimes broader.

The same chapter treats goods and services as products. That is why a service innovation need not sit outside product innovation. Different classification systems can be useful, but say which one you are using rather than mixing their categories silently.

Product innovation: what changes for the user?

For the lighting company, a lamp designed so that damaged parts can be replaced could change the customer offering. The relevant questions concern usefulness, performance, reliability, maintenance and the experience of obtaining a replacement. A different colour alone does not necessarily establish a significant change.

Describe the proposed difference in observable terms. “More sustainable lighting” is an ambition. “The shade and support joint can be replaced without replacing the whole lamp” is a characteristic that can be examined. Whether the design actually reduces environmental impact would need separate evidence about materials, lifetime, transport and use.

Do not assume that technical novelty equals customer value. A sophisticated component may be hard to repair, difficult to source or irrelevant to the customer’s main concern. Use concept development to connect the feature with a particular situation and benefit.

The Design Council’s Double Diamond links understanding a challenge with developing and testing responses. Applied here, first explore why office customers replace lamps. The answer might favour a better repair service over a redesigned object.

Process innovation: what changes in the work?

Now consider a new repair workflow. The company introduces a shared intake record, a diagnostic sequence and a parts-identification routine so that returned lamps do not repeatedly wait for missing information. The object of change is the way the business performs work.

A process change can be significant without being visible to the end customer. It may affect production, delivery, maintenance, information flows or supporting activities. Its value still needs evidence. A new system that records more data but creates longer queues is not useful merely because it is digital.

For the fictional company, compare the previous and proposed workflow. Who receives the lamp? Who diagnoses it? Where does the part identifier come from? What happens when the model is unfamiliar? These questions reveal dependencies that a simple “process improvement” label can conceal.

Bring in the people who do the work. They can explain exceptions, workarounds and the cost of incomplete information. This connects the proposal with change readiness, because a technically coherent workflow can still lack time, authority or support.

Business-model innovation: what changes in the arrangement?

The third proposal is a maintained-lighting service. Instead of buying lamps and arranging repairs separately, an office would receive an agreed service with responsibilities for replacement, maintenance and returns. This changes more than the invoice schedule.

Strategyzer’s Business Model Canvas makes connections between customers, value propositions, delivery activities, resources, costs and revenue visible. Use that perspective to ask what must change together. A recurring payment added to the same offer may be a pricing change; a different system of ownership, service obligations and delivery may have broader implications.

In our example, the company would need to know where lamps are installed, how service requests arrive, what response it can promise and what happens when an office moves. It would also need to understand replacement demand and the working capital tied up in equipment. None of those questions is solved by calling the proposal a subscription.

Avoid declaring the model superior before examining its consequences for customers and the business. Some customers may prefer ownership and occasional repairs. Others may value predictable support. The model is a hypothesis about a workable arrangement, not a more advanced category of innovation.

Compare the same initiative across several dimensions

A compact comparison helps distinguish the questions without forcing every proposal into one exclusive box.

Proposal	Main object of change	Important evidence	Organisational implication
Replaceable lamp components	Customer offering	Usefulness, safe performance, maintainability	Design and parts support
Shared repair intake and diagnosis	Business process	Handoffs, errors, turnaround and workload	New routines and responsibilities
Maintained-lighting service	Business-model arrangement, potentially combining product and process changes	Customer choice, delivery reliability and economics	Ongoing service ownership and coordination

The categories do not rank importance. A process innovation could be more consequential for this company than a new product. Nor does a business-model proposal necessarily require inventing new technology. The useful distinction is the nature of the change and the evidence it calls for.

Record multiple classifications when necessary. Forcing the maintained-lighting service into only “product” can hide its operating model. Calling it only “business model” can hide the engineering work needed to make repairs dependable.

Novelty is a separate question

The object of change tells you what is changing; novelty asks how different it is from a reference point. Something can be familiar in a market and new to a particular company. Conversely, a technically unusual feature may leave the customer’s experience largely unchanged.

Use terms such as incremental and radical with an explanation. Incremental compared with which existing design or practice? Radical in technology, customer behaviour, capabilities or market arrangement? There is no benefit in allowing the adjective to do all the analytical work.

Also distinguish novelty from organisational impact. A familiar repair-management system may require major changes in roles and information sharing. A highly novel component might be introduced by a specialist team with little effect on other work. These dimensions sometimes move together, but they are not interchangeable.

Our innovation versus invention guide covers the distinction between developing something new and bringing it into use. Keep that distinction when reporting a portfolio: ideas, prototypes, pilots and operating offers should not all be counted as the same kind of achievement.

Use the classification to choose the next test

Once the dimensions are clear, choose the uncertainty that matters for the next commitment. A component may need technical evaluation. A repair workflow may need a realistic handoff rehearsal. A maintained-service concept may need research into customer choice before a larger operational trial.

GOV.UK’s alpha guidance focuses on testing consequential assumptions rather than building a complete service immediately. That is a useful discipline across these categories. The test should follow the risk, not the glamour of the innovation label.

For electrical products, qualified safety and compliance work is essential; this management comparison is not technical design guidance. Similarly, a service-model discussion does not replace accounting, contractual or operational assessment. Classification helps identify expertise needed, not bypass it.

Where the labels stop helping

The limitations of any typology include ambiguous boundaries, changing baselines and mixed initiatives. Statistical reporting may require a specific definition that differs from a team’s working language. Preserve the reporting definition where it matters and explain any local shorthand.

Avoid treating “radical” as a compliment or “incremental” as an insult. Neither describes evidence of usefulness. A clear account of the change, its dependencies and its current stage is more informative than a dramatic category.

The lighting company can now hold a better discussion: not “Which proposal is most innovative?” but “Which combination of offer, workflow and service arrangement is worth investigating, and what would we need to learn before committing?” That is the practical purpose of the distinction.