The art of shooting yourself in the knee

 

There’s a persistent myth in product development: that what you ship is the roadmap. In reality, what you ship is the organisation that built the roadmap.

The phrase “you always ship your org chart” is a practical extension of Melvin Conway’s observation, often called Conway’s Law, that systems mirror the communication structures of the organisations that produce them. But beyond architecture, the same applies to decision velocity, UX consistency, technical debt, customer empathy, and ultimately business performance.

If your product feels fragmented, slow-moving, or misaligned with users, chances are the root cause sits in culture.

When Org Culture Gets in the Way of Good Work

Organisations rarely intend to produce bad outcomes. Dysfunction usually emerges as a side-effect of scaling, risk management, or legacy habits that stopped evolving.

Here are the most common cultural patterns that degrade product quality.

Overly Complicated Processes

Process exists to reduce uncertainty. But when process becomes the default response to uncertainty, teams stop solving problems and start routing paperwork.

Typical symptoms:

• approval chains replacing ownership
• roadmap changes requiring multiple steering committees
• compliance theatre substituting real risk mitigation
• release gates optimised for auditability instead of customer value

The result: slower iteration cycles and diluted accountability.

Eventually, teams optimise for serving process instead of serving users.

Silos That Fragment the Product Experience

Silos create invisible boundaries inside the product.

You’ll recognise them when:

• different surfaces follow different UX principles
• teams optimise local metrics at the expense of system outcomes
• APIs reflect team ownership rather than user workflows
• duplicate infrastructure appears across domains

Customers don’t experience silos. They experience inconsistency.

And inconsistency erodes trust faster than missing features.

Unclear Responsibilities

Ambiguity in ownership produces one of two outcomes:

• nobody makes decisions

or

• everyone makes decisions

Both are expensive.

Signals include:

• repeated re-litigation of previously “closed” topics
• roadmap items drifting between teams and timelines
• shadow ownership emerging informally
• escalation becoming the primary coordination mechanism

In these environments, execution slows not because teams lack talent, but because authority is unclear and accountability is nonexistent.

Declared Culture vs Real Culture

Every organisation has two cultures:

Declared culture - what leadership says matters
Operational (real) culture - what actually gets rewarded

The second one always wins.

How to Spot the Gap

Look at these mismatches:

• (Declared value) “We move fast” - (Observable behaviour) Releases require multiple approvals
• (Declared value) “Customer first” - (Observable behaviour) Roadmap driven by internal stakeholders
• (Declared value) “Ownership culture” - (Observable behaviour)  Decisions escalate upwards
• (Declared value) “Data-driven” - (Observable behaviour) Opinions override experiments
• (Declared value) “One team” - (Observable behaviour)  Budgets allocated competitively

Culture isn’t what appears in onboarding decks.

Culture is what happens when priorities conflict. When people disagree. When things break. 

A key diagnostic question:

What behaviour gets promoted here?

An honest answer defines your real culture.

How Dysfunctional Culture Quietly Reaches the Product

Culture shapes products through predictable mechanisms:

• (Cultural issue) Fear culture - (Product-level symptoms) Missing escalation signals, everyone quiet on calls
• (Cultural issue) Siloed teams - (Product-level symptoms)  fragmented UX, missed dependencies 
• (Cultural issue) Weak ownership - (Product-level symptoms) roadmap drift, foundational issues ignored
• (Cultural issue) Incentive misalignment - (Product-level symptoms) debt accumulation, finger-pointing 
• (Cultural issue) Process overload - (Product-level symptoms) slow experimentation, slow everything 
• (Cultural issue) Stakeholder politics - (Product-level symptoms) inconsistent prioritisation, HiPPO galore 

Products rarely fail randomly.

They fail structurally.

Practical Thinking Tools to Avoid Shipping Your Org Chart

You can’t eliminate organisational influence on products. But you can shape it deliberately.

Here are interventions that consistently help.

Map Decision Ownership Explicitly

Every roadmap item should answer:

1. who decides?
2. who contributes?
3. who executes?
4. who approves?

Ambiguity compounds across releases.

Clarity compounds across organisations.

Align Incentives With System Outcomes

Reward:

• measurable customer impact
• cross-team delivery
• shared platform adoption
• reduced duplication

Avoid rewarding:

• artefacts instead of a working product
• local optimisation
• team-level velocity metrics
• roadmap volume instead of value

People optimise what gets measured and rewarded fairly. 

Collapse Communication Distance

If your product architecture mirrors org boundaries too closely, consider:

• platform interfaces
• shared standards
• developer experience layers
• integration ownership roles

Architecture and org design co-evolve whether planned or not.
Better to plan it.

Treat Escalation as a Feature, Not a Failure

Healthy organisations surface problems early.

Warning signals include:

• engineers hesitant to challenge strategy
• PMs avoiding stakeholder disagreement
• roadmap assumptions rarely questioned
• opinions valued over insights 
• doers don't understand 'why'
• mistakes repeated with no reflection

Silence scales faster than insight.

Audit Your Real Culture Quarterly

Ask:

• What behaviour actually gets rewarded?
• What decisions take too long?
• Where do dependencies accumulate?
• Which teams duplicate work?
• What problems never get escalated?

These answers predict your next product outcome with surprising accuracy.

Culture Eats Strategy For Breakfast

Strategy defines direction. Roadmaps define intent. But culture defines what actually gets shipped.

If your organisation produces fragmented systems, slow releases, or misaligned priorities, the solution is rarely another process layer.

It’s structural alignment.

Because whether you design it intentionally or not:

You always ship your org chart.