Field reference
What is product coherence?
Product coherence is the degree to which every part of a product, from its positioning down to its pixels, expresses one intent, so the whole feels like it was made by a single mind.
You feel it within thirty seconds of using something good, and you feel its absence even faster. Nothing has to be broken. The pieces just don’t know each other. This page is the working definition we use at MaxQ: what product coherence is, how it differs from consistency, where it breaks, and how to audit it.
The definition, unpacked
One intent, everywhere.
Product coherence is a property of the whole, not of any part. Every screen can pass review on its own and the product can still feel scattered, because coherence lives in the relationships: whether the pricing page and the settings page believe the same things, whether the error message and the homepage were written by the same hand, whether the tenth screen keeps the promise the first one made.
The idea is older than the term. Fred Brooks called it conceptual integrity in The Mythical Man-Month in 1975 and argued it is the most important consideration in system design. Dieter Rams put “thorough down to the last detail” in his ten principles of good design. Product coherence is the same instinct, widened to cover everything a product says and does: the positioning, the words, the patterns, and the pixels, all expressing one intent.
When a product has it, users call the product simple, even when it is not. When a product loses it, users almost never name the problem. They say it feels off, and then they leave quietly. A coherent product feels like somebody loves it. An incoherent one feels made by strangers.
Coherence vs consistency
Consistency is sameness. Coherence is unity.
Consistency is sameness of parts: the same button, the same blue, the same voice rules applied everywhere. It is a property you can write down, enforce with a design system, and check with a linter. Jakob Nielsen put consistency and standards in his ten usability heuristics in 1994, and it earned the spot. Inconsistency taxes every user, every time.
Product coherence is unity of intent. It includes consistency, but it is bigger: whether the product’s positioning, language, patterns, and surfaces all describe the same thing. A product can be perfectly consistent and still incoherent. Every button identical, every hex code accounted for, and the product still cannot tell you what it is.
The asymmetry is the useful part. Consistency breaks with any exception. Coherence can survive an exception when the exception serves the intent, and that judgment call, when to break your own rule, is exactly the part no linter will ever make for you.
Consistency
- A property of the parts
- Written down as rules and tokens
- A linter can check it
- Breaks loudly, one screen at a time
Coherence
- A property of the whole
- Held as judgment
- Only a whole-product read can check it
- Breaks quietly, everywhere at once
The framework
The coherence stack.
MaxQ audits coherence with a four-layer model called the coherence stack. Each layer is a place where a product either expresses its intent or contradicts it, ordered from the deepest layer to the most visible. The deeper the layer, the quieter the break and the more expensive the fix.
Intent
One sentence that says what this is, who it is for, and what it refuses to be. Every layer above inherits from it, which is why a crack here shows up everywhere else.
How it breaksThree teammates describe the product three different ways.
Language
Names, voice, and copy. A coherent product describes itself the same way on the marketing page, in onboarding, and in the error message nobody proofread.
How it breaksThe homepage sounds like a confident friend and the onboarding sounds like a tax form.
Pattern
The recurring structural decisions: navigation logic, interaction patterns, the concepts the data model exposes. The same problem solved the same way everywhere it appears.
How it breaksTwo screens solve the same problem two different ways, and both feel right to whoever built them.
Surface
Type, spacing, color, motion, radii. The visible layer, the one users point at, and the only one most audits ever reach.
How it breaksThe button is rounded to four pixels on the hero and eight pixels three screens deep.
The rule that makes the stack useful: incoherence travels upward. A crack in intent surfaces as scattered language, mismatched patterns, and a surface that never settles no matter how much you polish it. So you audit from the surface down, and you repair from the intent up. Polishing the surface of a product that has not decided what it is: that is the most expensive way to stay incoherent.
The failure mode
Nobody decides to lose it.
No team votes to make the product feel scattered. Coherence erodes one reasonable decision at a time, made by different people on different days, with nobody holding the thread. Every individual call survives review. The sum does not.
The classic cause is a seam between teams: a brand team that owns the marketing site, a product team that owns everything past signup, and a relationship that amounts to one shared holiday party. Both groups are good at their jobs. The product still ends up speaking two languages.
AI made all of this faster. Generation is per-prompt, and coherence lives across prompts and across time, so the more fluently a team produces parts, the faster the parts drift apart. That argument is the spine of Coherence is the bottleneck and Why AI Makes It Worse: output stopped being the constraint, and holding the whole together became the job.
The audit
Surface down. Intent up.
A product coherence audit does not require software. It requires a free afternoon, a cold eye, and the willingness to write down what you find.
Write the intent sentence
One sentence: what this is, who it is for, what it refuses to be. If the team cannot produce it in under a minute, stop. That is the finding.
Walk the product cold
Marketing page, signup, onboarding, first real task, an error, settings. One sitting, no shortcuts, and read every word out loud. The mouth catches what the eye forgives.
Collect the seams
Screenshot every moment where the voice, the pattern, or the surface disagrees with what came before. Do not fix anything yet. Just collect.
Trace each seam down the stack
A four-versus-eight pixel radius is a surface note. Two screens solving the same problem differently is a pattern break. A homepage and an onboarding flow describing two different products is an intent crack wearing a surface costume.
Repair from the deepest layer up, and name a steward
Fixes stick when one person owns the thread. Coherence assigned to everyone belongs to no one.
If you want the cold eye without recruiting one, MaxQ built a free diagnostic that runs this read on a concept and returns a field report: where it holds, where it strains, what to fix first. No email, no sales call attached.
Written by
MaxQ Partners
Operators who have taken products from napkin to acquisition, writing down what holds them together.
Published Jul 02, 2026
FAQ
Product coherence questions
The short answers, self-contained enough to steal.
Product coherence is the degree to which every part of a product, from its positioning down to its pixels, expresses one intent, so the whole feels like it was made by a single mind. A coherent product feels designed rather than aggregated: the marketing page, the onboarding, the error states, and the settings screen all sound and behave like the same product.
Consistency is sameness of parts: the same button, the same blue, the same voice rules applied everywhere. Coherence is unity of intent: every part, even the ones that differ, expressing one idea of what the product is. A product can be perfectly consistent and still incoherent, and a coherent product can survive a deliberate inconsistency when the exception serves the intent. Consistency can be enforced with a design system and checked by a linter. Coherence requires judgment.
Products lose coherence one reasonable decision at a time: different people, different days, nobody holding the thread. The most common causes are seams between teams (a brand team owning the marketing site while a product team owns everything past signup), speed outrunning judgment, and AI generation, which produces each part fluently while knowing nothing about the whole.
Audit from the surface down and repair from the intent up. Walk the whole product in one sitting, from the marketing page through onboarding to the error states, collect every seam where the voice, patterns, or surfaces disagree, then trace each seam to the deepest layer of the coherence stack it comes from. MaxQ offers a free diagnostic at gomaxq.com/diagnostic that runs this read on a product concept and returns a structured field report.
Yes. AI collapses the cost of producing parts without producing any sense of the whole. Each generation answers the last prompt, not the product's intent, so the faster a team generates, the faster the pieces drift apart. Coherence lives across screens and across time, which is exactly what a single prompt cannot hold.
One person has to hold the thread. Call it a steward: a founder, a design lead, or an embedded partner whose actual job is to keep every decision expressing the same intent. Coherence assigned to everyone belongs to no one.
Name the drift before your users do.
Run the free diagnostic and get a field report on where your product is leaking coherence. Or bring us the seams you already know about.