The category
Product integrity is what keeps a product's decisions together.
Product integrity is what keeps a product’s decisions from coming apart.
It’s the state where the direction feels real, the evidence is still current, the plans actually reflect what was learned, shipped work gets checked against the original intent, and the outcomes feed back into the strategy that started them. When it holds, you can pull on any bet and find a clear reason it exists.
This page just defines the term. Shorter Loop is the system we built to keep that integrity intact.
THE DRIFT
We have never lacked documents.
Strategies. Research repos. Roadmaps. PRDs. Backlogs. Dashboards. Quarterly reviews. Every artifact can look perfectly reasonable on its own.
Then something happens between them. The connections fray. Six months later nobody can reconstruct why a major bet was made, or whether the original evidence still holds.
The product drifts.
HOW IT COMES APART
- Research says one thing.
- The roadmap reflects another.
- Engineering ships something slightly different.
- The original reason gets lost.
- The outcome is measured against a new story nobody started with.
We call the thing that prevents that drift Product Integrity.
THE DEFINITION
Product integrity is the ability to pull on any meaningful bet and still find the evidence, claims, decisions, and outcomes that justify it — with their actual standing intact.
- Why are we building this?Because we made this decision.
- Why did we make that decision?Because we believed these claims.
- Why did we believe those claims?Because this evidence supported them.
- Is that evidence still true?Here is what we know now.
- Did the thing we shipped actually work?Here is what happened.
You will still ship the wrong thing sometimes. Customers will still surprise you.
Integrity means you can still see what you believed, why you believed it, what you built because of it, and what reality did to that belief.
WHY "INTEGRITY"
The word has dual meanings here.
A product needs both.
STRUCTURAL INTEGRITY
It holds together under load.
Pull on a roadmap item and its reasoning is still attached.
Trace a decision backwards and you find the claims and evidence underneath.
Trace it forward and you see what shipped and what actually happened.
Those links hold through handoffs, reorganizations, plan changes, and time.
INTELLECTUAL INTEGRITY
The organization tells itself the truth.
A claim stays labeled as a claim until evidence moves it.
Evidence is carried with its standing: claimed, corroborated, unsupported, or contradicted.
Weak signals do not harden into fact because they appeared in enough decks.
When reality contradicts the bet, the record changes.
Structural without intellectual: every decision is beautifully documented and the reasoning is still wrong.
Intellectual without structural: people are honest and thoughtful, and six months later nobody can reconstruct why anything happened.
You need both.
WHERE THE TOOLS STOP
Product management tools have optimized the parts.
Each tool tells you something true about its slice of the process. Product integrity lives in the gaps between those slices.
THREE TESTS
For an important decision to have integrity, three things must be true.
1
The decision can be traced to the claims it depends on.
Pick something meaningful on the roadmap. You should be able to retrieve the actual reasoning beneath it — retrieve, not remember.
NOT AN ANSWER TO “WHY IS THIS HERE?”
- “Sarah wanted it.”
- “The enterprise team asked for it.”
- “We discussed this last quarter.”
2
The claims can be traced to evidence — and represented honestly.
A claim is not evidence merely because somebody wrote it down. The system should preserve what supports a claim and how strongly.
WHAT MUST STAY TRUE
- An assumption still looks like an assumption.
- Limited evidence does not quietly become “proven.”
- Contradicted claims do not survive on roadmap inertia.
3
The evidence is still current.
Evidence has a half-life. Customers change, markets change, competitors move, usage changes, technology changes, the product changes.
WHAT THAT MEANS
- A decision made from sound evidence six months ago can be a bad decision today.
- New evidence can challenge old reasoning.
- Decisions depending on that reasoning can be revisited.
CHECK FOR YOURSELF
Follow one bet through the product.
The same team, the same evidence, the same feature, the same result. On the left, the reasoning stays attached. On the right, it does not. Nothing in the second column is anyone's mistake — it is what happens by default.
WITH PRODUCT INTEGRITY
The reasoning stays attached.
| CLAIM | Mid-market customers abandon onboarding because integration setup takes too long. |
| EVIDENCE | Interviews repeatedly mention setup complexity. Analytics show a significant drop during integration configuration. Support tickets contain repeated requests for implementation help. |
| STANDING | Not proven. But well supported — and recorded as exactly that. |
| DECISION | Reduce the time required for customers to complete their first integration. |
| BET | Guided Integration Setup, expected to increase successful onboarding and improve 30-day retention. |
| OUTCOME | Integration completion improves 18%. Retention barely moves. |
| READING | The solution worked. The original causal belief did not. |
| RETURN | The evidence changes. The claim changes. The understanding of the problem changes. Eventually the strategy may change. |
The evidence changes. The claim changes. The understanding of the problem changes. Eventually the strategy may change.
WITHOUT IT
The same bet, in a normal product stack.
| RESEARCH | Integration setup is identified as the problem. A presentation summarizes the research. |
| ROADMAP | The research becomes an “Onboarding Improvements” initiative. |
| DRIFT | Three months later the initiative has become a Guided Setup Wizard. |
| HANDOFF | Engineering receives requirements for the wizard, not the original evidence. |
| SCOPE | Scope changes during implementation. Nobody checks whether those changes affect the hypothesis. |
| SHIP | The wizard ships. The delivery ticket closes. |
| SIGNAL | Analytics show more users completing integration. The team celebrates. |
| SILENCE | Retention remains unchanged. Nobody goes back to the original claim. |
| MEMORY | Six months later, somebody says: “We already fixed onboarding.” |
The organization has accumulated information. It has lost the reasoning.
WHERE IT HAS TO HOLD
Integrity is not a box you tick
It has to survive across the product lifecycle — in five places, and then in a sixth that no single tool owns.
What the team believes about customers and problems remains attached to the evidence behind it.
- Claims are distinguishable from assumptions.
- Contradictions remain visible.
- Weak signals do not become facts through repetition.
AND THEN THERE IS THE SIXTH
Loop integrity.
Each phase can work well while the product as a whole loses integrity. A team can conduct excellent discovery and build a roadmap unrelated to it. Make a sound strategic decision and hand engineering requirements that no longer reflect it. Execute beautifully and never check whether the thing worked.
The damage happens in the seams.
No individual point tool can see that chain on its own. Most product stacks were designed to manage artifacts. They were not designed to preserve the relationships between them.
The seams
Loop integrity is whether the reasoning survives those handoffs.
THE SYMPTOMS
How you notice it is broken.
None of these look like a crisis. That is what makes them expensive.
The roadmap has no visible reason behind it.
Ask why an initiative exists and you get a person's name, a meeting, or an old presentation instead of evidence.
Research finishes and nothing changes.
The study gets written up. Insights get shared. Everyone agrees they are interesting. The roadmap remains exactly the same.
Assumptions quietly become facts.
Someone says “customers need this.” Three months later the roadmap says “customers need this.” Six months later the strategy says “our customers require this.
”Nobody can find the evidence that originally justified the statement.
Strategy and roadmap silently diverge.
Both are current. Both look reasonable.
They describe different companies.
Scope changes alter the bet.
What engineering ships is materially different from what discovery validated.
Nobody notices, because the requirement changed but the reasoning did not.
“Done” means shipped.
The work reaches production. The ticket closes.
Nobody returns to ask whether the expected outcome occurred.
New evidence contradicts an old decision.
The new evidence gets filed. The old decision remains untouched.
The same decisions get re-litigated.
Teams repeatedly reopen arguments because the reasoning behind the original decision was never preserved somewhere people can retrieve it.
Leadership changes and product memory disappears.
A new leader arrives. The organization remembers what it is building.
It cannot explain why.
WHAT THIS IS NOT
Product integrity adds almost no process.
Product teams work under uncertainty. They make bets. Some of those bets fail. That is the job.
Integrity keeps uncertainty from being dressed up as certainty, and keeps the original reasoning available when reality forces an update.
- Another stage gate or review ceremony.
- Forcing teams to document every conversation.
- Chasing a perfect single source of truth.
- Requiring certainty before anyone can make a decision.Trying to stop people from being wrong.
- Knowing which claims are actually carrying a decision.
- Preserving why a bet was made so the organization can revisit it.
- Letting new evidence change the organization's mind.
THE SYSTEM
Shorter Loop is a Product Integrity System.
Most product software stores artifacts. We store the relationships between them.
| 01 | EVIDENCE → CLAIMS | Evidence stays connected to the claims it supports. |
| 02 | CLAIMS → DECISIONS | Claims stay connected to the decisions that depend on them. |
| 03 | DECISIONS → BETS | Decisions stay connected to roadmap bets. |
| 04 | BETS → WORK | Roadmap bets stay connected to the work that implements them. |
| 05 | WORK → OUTCOME | Delivered work stays connected to its intended outcome. |
| 06 | OUTCOME → BELIEF | Outcomes return to the beliefs and strategy that created the bet in the first place. |
That creates something most product organizations do not have today: a living record of why the product is becoming what it is becoming.
So when new evidence appears, you can see what it challenges.
When a roadmap changes, you can see what reasoning changed with it.
When something ships, you can see what outcome it was supposed to create.
And when reality disagrees with the original bet, the learning can travel all the way back through the system.
Product integrity does not make you right.
It makes it harder to stay wrong.
You will still make bad bets. Customers will still surprise you. Markets will move. Experiments will fail. Assumptions will turn out to be false. That is product development.
The difference is whether the organization learns from those failures — or simply piles the next roadmap on top of them. Product integrity keeps the reasoning attached long enough for the organization to learn.
See where your product loses integrity.
Trace a real product decision from evidence to outcome and find where the chain breaks.
- Pick one committed roadmap item and name the decision behind it.
- Retrieve the claims that decision depends on — retrieve, not remember.
- Find the evidence beneath each claim and check whether it is still current.
- Wherever you cannot get to the next link, that is where integrity breaks.