Key takeaways
  • A product is four layers: the artefact, the experience, the promise and the whole business.
  • Every decision is a product decision, whether the org chart says so or not.
  • Widen the definition and you change what you measure and who owns it.

Ask ten people in your office to define product and you'll get ten variations on the same answer. The thing we ship. The app. The platform. What's behind the login screen. Each of those answers is correct in the way a postcode is correct. It gets you to the right building but tells you nothing about the building. The thing we actually mean when we say "product" is much, much bigger, and the gap between the postcode answer and the real answer is where most product disagreements live.

This piece is a thought experiment. I'll walk you out from the smallest, sharpest definition (the one you'd give a graduate on their first day) through four expanding layers, until we arrive at the definition I actually use in client work. It's a definition that annoys some teams, because if you accept it, suddenly half the company is doing product work whether they have the title or not. Stick with it, because the implications are useful.

Layer 1: The artefact.

The narrowest definition: a product is the thing the company makes. The mobile app. The web platform. The piece of hardware. The API. The screen the user sees, the code that runs underneath it, the data model that feeds it. This is what most people gesture at when they say "the product". It's also what most product managers spend most of their time inside.

It's a useful definition for a lot of practical purposes. It draws a clean line around what the engineering team owns. It tells the designer what to mock up. It tells the PM what the next sprint is for. Most agile rituals (backlog, sprint, release) are built around this artefact-level definition, and so are most product-management training programmes.

But it's the narrowest definition for a reason. If the only product you cared about was the artefact, you could ship a perfectly-built app that nobody downloads, nobody pays for, and nobody loves. That's a successful artefact and a failed product. So we have to widen out.

Diagram · The four-layer product: concentric definitions, widest is the real one
The four-layer product — four expanding definitions of what a product is A diagram showing four concentric rounded rectangles representing expanding definitions of a product. The innermost layer 1 — The Artefact — is the app, the screen, the code, the API, shown in marigold to mark where most teams stop. Layer 2 — The Experience — wraps it, covering onboarding, support, packaging and the moment of value. Layer 3 — The Promise — wraps that, covering brand, the contract with the user, what the company stands for. The outermost layer 4 — The Business — contains all of it, covering operating model, pricing, team and every decision made every day in every department. Three inward-pointing chevrons on the left indicate the "contained within" relationship. A vertical marigold annotation on the right reads "EVERY DECISION IS A PRODUCT DECISION." Most teams optimise inside the marigold core, but the leverage sits in the outer layers. LAYER 04 · OUTER The Business operating model · pricing · team · every decision, every day LAYER 03 The Promise brand · contract with the user · what you stand for LAYER 02 The Experience onboarding · support · packaging · the moment of value LAYER 01 · CORE The Artefact the app · the screen · the code · the API EVERY DECISION IS A PRODUCT DECISION Most teams optimise inside the marigold core. The leverage sits in every layer outside it.
Four expanding definitions of a product. The artefact (the app) is the smallest. The business is the real product. Every decision made anywhere in it is a product decision, whether the org chart agrees or not.

Layer 2: The experience.

Widen out one ring. The product isn't just the artefact. It's everything the user touches between learning you exist and getting their job done. The onboarding email. The first-run tutorial. The empty state when they haven't loaded any data yet. The error message at 11pm when something's broken. The support reply that arrives the next morning. The way the bill arrives.

None of that lives inside the artefact, but all of it shapes whether the artefact lands. Marty Cagan has been making this point for decades — the discovery work of figuring out what to build is product work, the moment of first value is product work, the way you communicate change to your users is product work. The PM who only owns what's behind the login screen is owning the smallest possible slice.

The experience layer is where most teams that are doing real product thinking spend their time. It's also where the wins compound. Improve the onboarding by 10% and you've improved every downstream metric. Improve a screen inside the artefact by 10% and you've improved one funnel step. The leverage difference is enormous.

Layer 3: The promise.

Wider still. Before a user touches your onboarding, they have a belief about what you'll be like, formed by your brand, your reviews, the way your category gets talked about, the half-remembered moment a friend mentioned you. That belief is a contract. They show up expecting this, and the experience either matches or doesn't. The product isn't just what you deliver. It's the gap between what they expected and what they got.

The classic Jobs To Be Done work from Clayton Christensen lives at this layer. People don't buy products, they hire them to do a job. The "product" they're hiring is the whole bundle of what it promises to do for them. A coffee shop isn't selling coffee. It's selling fifteen minutes of headspace before the meeting, or the social proof of being seen working out of a particular café, or the small ritual that anchors the start of the day. The cup of coffee is the artefact. The job is the product.

If you treat brand as the marketing team's problem and product as the engineering team's problem, you've drawn the wrong line. The brand is the product, because the brand is the promise the artefact has to keep. The two teams are working on the same thing.

If your brand promises one thing and your product delivers another, you don't have two problems. You have one product problem.

Layer 4: The business.

This is the answer that annoys people, so I'll say it plainly. Your business is your product. The pricing model is a product decision. The hiring plan is a product decision. The SLAs the support team operates under are a product decision. How fast finance closes the books (if your customers care, and in B2B they do) is a product decision. The shape of the org chart shapes the shape of what gets built (Conway's Law isn't a curiosity, it's the rule). Every decision made in every department contributes to or detracts from the product the customer actually experiences.

Peter Drucker got there sixty years ago: "the purpose of a business is to create a customer." Not to ship features. To create, and keep, a customer. Everything in the business either contributes to that or doesn't. Reframe every decision in the company as a product decision and a lot of false fights end. Sales vs. product about which features to push? Both are arguing about the product. Finance vs. product about discount levels? Both are arguing about the product. Legal vs. product about terms of service? Both are arguing about the product.

The reason this annoys people is that it implies the product function isn't a department. It's a perspective. You can have a hundred product managers and still not have product thinking in the business, because product thinking is the discipline of looking at every decision through the lens of "what does this do to the customer's experience of us?" That's not a department. That's a culture.

So what changes?

Three practical things change when you accept the four-layer view:

  • What you optimise for shifts. If the product is just the artefact, you optimise for feature velocity. If the product is the experience, you optimise for time-to-first-value. If the product is the promise, you optimise for the consistency of what you say and what you do. If the product is the business, you optimise for whether the whole machine creates and keeps customers — which is a CEO question, not a PM question.
  • Who's in the room changes. Product decisions stop being something the PM team makes alone. Pricing changes need product input. Hiring plans need product input. The shape of how support is staffed needs product input. The product seat in the senior team is no longer optional. It's the seat that integrates every other seat into a coherent customer experience. This is the case I keep making in the CPO Piece.
  • The definition of "shipping" widens. Shipping a feature is one thing. Shipping a change to your pricing page, a change to your refund policy, a change to your onboarding email. All of those are product launches that deserve the same care. Most teams launch features with rigour and launch the rest with a Slack message at 4pm on a Friday. That's a gap.

The provocation.

Here's the test I run with leadership teams. Pick the last ten significant decisions your business made. Not just feature decisions — all of them. Pricing change. A new hire. Office move. A change to the contract template. A reorganisation of customer success. A new partner deal.

For each one, ask: was the product team in the room? If the answer is no for most of them, you're not running a product business. You're running a feature factory wrapped in a brand wrapper, and the disconnect will show up in your retention numbers about two quarters later.

The fix isn't to make the product team bigger. It's to widen the definition of product until the leadership team understands that every meeting they sit in is a product meeting. Some will be about the artefact. Some will be about the experience, or the promise, or the business. All of them are product.

Where this lands at Product Pieces.

The whole Pieces model is built on the four-layer view. The CPO Piece exists because someone has to sit at Layer 4 and integrate the others. The PM Piece works across Layers 1–3. The PO Piece turns Layer 2 and 3 intent into Layer 1 reality. The Quality Piece guards the gap between what Layer 3 promised and what Layer 1 actually delivered. The Coaching Piece teaches your team to see all four layers at once.

That's why fractional senior product works, because the leverage isn't in writing more tickets. It's in widening the definition of product inside the business until every decision is made with the customer in the room. You don't need that perspective forty hours a week. But you need it in the room when the right decisions are being made.

So next time someone asks you what your product is, resist the urge to point at the app. Point at the whole company.

Next issue: N°01, coming late July. Subscribe via the contact form for the next read.