Designing a solution starts by recognizing what people receive, what work is required to deliver it, and what must continue working after the first handoff.

A solution to a problem may involve an object, an app, human assistance, a procedure, or several coordinated components. It does not always fit a single label: a physical device may include software and maintenance; a website may be delivered as a project and then evolve through an ongoing content and SEO service. Classification helps when it changes a design decision; a label alone does not establish demand or value.

Product, service, process, and solution do not mean exactly the same thing

In everyday speech, we call something delivered a product and something performed a service. This is a practical distinction, but not a universal one. The OECD's Oslo Manual uses “product” in an economic sense to include both goods and services and recognizes that the boundary can blur [R01]. For design purposes, separate the questions instead of arguing about a label:

Concept Design question Example
Good or physical product What object will the person receive or use? A replaceable water filter
Digital product What capability does a digital system provide? A reservation-management app
Service What activity or outcome is provided to someone? Installing the filter or managing bookings by phone
Process What sequence of work enables delivery? Check orders, prepare them, and confirm delivery
Solution What coordinated set of elements addresses a particular need? Filter, installation, replacement, and support when something fails

An internal process does not automatically become a product purchased by the customer. It may be essential to fulfilling the promise while remaining invisible. Likewise, an app is not the whole solution when it depends on people handling incidents, suppliers, or operating decisions.

Recognizing whether an offering is a product, service, or combination only starts the conversation: design approaches help determine which perspectives to involve based on affected people, systems, and constraints.

1. Classify products without mixing different criteria

By medium, distinguish physical goods, digital products, and physical–digital combinations. A physical product calls for attention to materials, manufacturing, storage, shipping, repair, and end-of-life handling. A digital product calls for access, compatibility, information security, availability, updates, and support. A connected product combines both sets of concerns: updating an app does not fix a faulty part, and replacing a part does not resolve a synchronization error.

By economic purpose, a good may serve final consumption, be a production input, or become part of another product. The same component can be classified differently depending on who buys it and why: a printer used at home does not pose the same availability and maintenance requirements as one used to fulfill a business's daily orders.

By length of use, it helps to distinguish durable goods from consumables or replaceable components. A filter requiring periodic replacement needs instructions, supply, and perhaps reminders; equipment meant to last for years needs suitable strength, repairability, and warranty considerations for its context. These categories are not mutually exclusive: a durable machine may contain consumables.

By access model, a digital product might be installed, accessed through a browser, or used as a provider-hosted service. Do not confuse “digital” with “SaaS”: a company website delivered for a client and a multi-tenant subscription application are different offerings, even if both rely on software.

The useful question is not “Which box does this belong in forever?” but “Which features of this offering force us to design, test, deliver, or maintain something differently?”

2. Classify services by how they are delivered

Services also have multiple classification dimensions:

Dimension Common options Decision affected
Duration One-off, project-based, recurring, or continuous How completion is defined and what follows
Interaction In person, remote, or hybrid Which channels and evidence the user needs
Execution Human, automated, or assisted Who handles exceptions and how capacity expands
Standardization Repeatable procedure or highly customized work What can be documented and what requires expert judgment
Beneficiary Individual, team, or organization How experience, purchaser, and user are identified

Consulting may be a project with a deliverable and a completion date; cleaning may recur every week; a support service may be continuously available even when each intervention is short. Recurring does not automatically mean subscription-based: work frequency and pricing structure are different decisions.

Nor is every digital service automated. A form can be digital while analysis and response depend on people. If an interface promises immediate confirmation but staff review requests only once a day, that service constraint needs to be explicit.

3. Recognize hybrid solutions

Many useful offerings are systems of components rather than pure categories:

  • Product with an associated service: equipment with installation, maintenance, and replacement parts.
  • Software-supported service: consulting that uses a portal to collect information and deliver results.
  • Digital product with human operations: reservation platform with staff handling unusual changes.
  • In-person and digital experience: a restaurant with a kitchen, point of sale, web ordering, and delivery.
  • Process offered as a service: a standardized procedure a company performs for others with verifiable outcomes.

Identify which element directly creates value, which enables delivery, and which sustains continuity. Technology may be essential without being the benefit customers seek. A restaurant does not buy a schedule just to store time slots; it wants fewer lost reservations, fewer conflicts, and less coordination work.

4. Distinguish a product, a project, and an ongoing service

A product is what people use or receive; a project is a temporary effort to produce a defined outcome; an ongoing service is continuing delivery, support, or improvement work. They can coexist without becoming synonyms.

For example, building a website under an agreed scope is a project. The working website is a digital product. Later maintenance, content optimization, and SEO are recurring services. Such a service generates new product versions: titles, copy, links, or site architecture may change, while the hypothesis, date, and expected outcome are recorded.

Not every change is an experiment. To call it an experiment, at minimum there should be a testable question, an appropriate measure, and consideration of plausible alternative explanations. If search rankings change after an update, timing alone does not establish causation: competitors, seasonality, or search-engine changes may also matter. Experimental design and evidence analysis belong to the Atlas's validation articles; here the point is that the product evolves while the service supports that evolution.

5. Identify all relevant actors

The person paying is not always the person using the solution; the user is not always the operator. Instead of making decisions about an abstract “customer,” record the roles that actually exist:

Actor Necessary question Restaurant reservation example
Buyer or contracting client Who decides and pays? Restaurant owner
Direct user Who performs everyday tasks? Manager changing bookings
Beneficiary Who receives the result? Diner receiving a reliable confirmation
Operator or service provider Who performs and sustains delivery? Team handling exceptions
Acceptance owner Who verifies agreed fulfillment? Person appointed by the restaurant
Essential third party Who controls a service dependency? Messaging or connectivity provider

One person may hold several roles. Do not invent stakeholders to fill a chart; distinguish the roles whose needs or constraints genuinely affect design. A user might enjoy the interface while an operator is overloaded by manual notifications the buyer never sees.

6. Map what people see and what enables delivery

A customer journey shows what the person experiences. To understand how that experience is produced, add a service-oriented view with customer actions, visible provider actions, internal work, and supporting systems or third parties. This separation is characteristic of service blueprints [R02][R03], although a simple table may be enough to start.

Moment What the customer sees or does Required internal work Critical dependency
Requests a booking Completes a form Check availability Accurate schedule
Receives confirmation Reads a message Record booking and send notification Messaging service
Changes time Requests a modification Resolve conflict and update schedule Available responsible staff
Arrives at the venue Presents booking Retrieve correct record Synchronized data

Mark what happens when something fails: if messaging is unavailable, does the booking still exist? If nobody is available, is a realistic response time communicated? Drawing only the happy path is not enough. Internal steps and exceptions may determine whether the promised value reaches the customer.

To investigate what each actor experiences before detailing internal processes, see how to map the customer journey. An experience map and a delivery-component map answer different, complementary questions.

7. Solution type changes delivery and quality decisions

Primary type Typical design focus Initial delivery evidence
Physical product Materials, tolerances, safety, replacement Inspected sample and conditions of use
Digital product Flows, compatibility, data, availability Tasks and functions verified in the intended environment
Human-delivered service Capacity, training, time, consistency Observed delivery under representative conditions
Hybrid solution Handoffs, interfaces, and failures between components End-to-end journey, including exceptions

These are areas of focus, not universal checklists or certifications. Actual quality criteria depend on requirements, risks, and applicable obligations; a separate Pillar 5 article will cover them.

That classification also informs how to incorporate real constraints into design: unavailable material, an unstable integration, or limited support capacity require different decisions depending on the solution type.

Complete exercise: a website that evolves through an SEO service

Hypothetical case. A small business commissions a website to receive contact requests. It subsequently retains a monthly content and SEO service. No actual outcomes or ranking promises are implied.

Step 1. Identify the offering. Digital product: public website. Initial project: design and implementation. Recurring service: editorial reviews, technical improvements, and monitoring. Internal components: CMS, hosting, analytics, approval process, and backups.

Step 2. Identify whom it serves. Contracting client: business management. Users: visitors seeking information and making contact. Operators: content and maintenance staff. Indirect beneficiary: sales staff receiving useful inquiries.

Step 3. Draw the minimum journey. Seek information → reach a relevant page → understand the offering → make contact → receive a response. The form is only one component; a submission that never reaches staff is not a complete experience.

Step 4. Separate versions from the service. V1: initial structure and content. V2: changes to pages and links based on an explicit hypothesis. V3: content or interface changes informed by findings. Every change records date, scope, prior evidence, and anticipated effect.

Step 5. Decide what to observe. Potential signals include search queries, clicks, completed contact events, and actual receipt of inquiries. Define comparability and limitations before attributing effects: concurrent changes and low volume may preclude causal conclusions.

Step 6. Record dependencies. If the mail system that receives forms fails, a critical part of the solution fails even when the website looks fine. If content requires client sign-off, that dependency shapes the schedule for future versions.

Case conclusion: not every SEO activity needs to be labeled a “product.” The website is a digital product; optimization is an ongoing service; versions are product changes that must be explainable and verifiable.

Common mistakes and limitations

Confusing monthly billing with having a SaaS product; describing only what users see and ignoring those who sustain the experience; treating an internal process as the final customer benefit; classifying offerings along incompatible dimensions; assuming every new version improves outcomes; assuming repeatable services have no exceptions; designing only for the person signing the contract.

This article's categories are teaching tools, not a legal, tax, or accounting classification. The contractual nature of an offering and its obligations must be assessed in context. Nor does this replace demand research or evaluation of business viability.

What you should have when you finish

A solution architecture worksheet containing: (1) expected outcome; (2) goods, digital products, services, and processes; (3) actors and responsibilities; (4) visible and internal moments; (5) dependencies and exceptions; (6) delivery and update model; and (7) key unanswered design questions. If you cannot explain how the outcome is produced from beginning to end, the solution is not yet fully scoped.

References