Product Is Not Strategy. And It Is Breaking Engineering

A quiet dysfunction spreads across engineering organisations.

It rarely starts with code or with people. It starts with decisions. More precisely, with how product is practised.

Somewhere along the way, product management drifted from its core responsibility. It stopped making hard decisions and started managing ideas. That shift does not trigger alarms, yet it steadily degrades the system.

No Real Prioritisation, Only Accumulation

Most product teams no longer prioritise. They accumulate.

Everything appears important, everything carries urgency, and everything demands attention. What emerges is not a roadmap but a narrative designed to avoid conflict.

Reality does not respond to narratives, and engineering does not scale on intention.

When everything matters, nothing truly does. Teams start ten initiatives, complete three, and stabilise none. Delivery loses predictability, not because engineers fail to execute, but because the system feeds them noise.

Daily Slack pings replace actual prioritisation, roadmaps get rewritten every two weeks without acknowledging the cost, and teams get pushed to accelerate work that should never have started.

True prioritisation does not organise work. It eliminates it.

Product Outside the Flow

Product is not a control tower. It is part of a flow.

That flow connects marketing, sales, customer behaviour, and engineering constraints, and it requires negotiation rather than dictation.

Yet many product teams operate above the system rather than within it. They define direction without grounding, push priorities without negotiation, and expect execution to adapt.

It does not.

Engineering builds features that marketing struggles to position, sales works around the product instead of with it, and the organisation accumulates output while losing leverage.

Flow requires negotiation, while dictation creates rework, and most organisations now run on that rework.

Nudging, Capacity Control, and Organisational Damage

Another pattern has become increasingly visible.

Product acts as a permanent pusher.

“Can we move faster?” “Where are we on this?” “Can we accelerate?”

And now, more frequently: “We need more capacity”, “We should hire here”, or “This team needs to change”.

This is not leadership, but unnecessary pressure without ownership.

Product does not own system capacity, does not manage hiring, and does not carry the operational consequences of those decisions, yet it increasingly attempts to dictate them. Often without stable priorities, measurable outcomes, or a clear direction.

Teams get reshaped around moving targets: people join without clarity, leave without understanding what failed, and teams get resized to compensate for poor prioritisation.

If a team requires constant nudging, clarity failed upstream. If capacity changes every quarter, prioritisation failed even earlier.

Good product work creates alignment that pulls execution forward, while poor product work creates ambiguity that demands constant pressure and endless organisational churn.

Engineering absorbs the cost every time.

No Accountability for Decisions

In most organisations, engineers carry consequences.

They remain on call, stabilise production, and handle failure directly, while product defines what gets built yet rarely carries the outcome when those decisions miss the mark.

Poor prioritisation produces real damage: missed opportunities, wasted effort, degraded systems, and exhausted teams, yet ownership rarely follows the decision.

A simple rule should apply: if you decide, you own the consequences, including staying close enough to reality to understand the impact.

When was the last time a bad prioritisation decision was owned, measured, and corrected?

The Myth of Intuition

A convenient narrative persists: great product comes from vision, instinct, and a handful of iconic figures.

The reference often surfaces, Steve Jobs, yet what rarely gets mentioned is the number of failed bets, discarded ideas, and course corrections behind that narrative.

Intuition never replaced reality. it collided with it.

Today, many product organisations use “vision” as a shield against discipline. Decisions lean on opinion, internal narratives, stakeholder pressure, or trends, while data becomes decorative rather than confrontational.

Data exists to challenge decisions, not to confirm them. Without that tension, product shifts from strategy to speculation, and engineering executes guesses at scale.

Engineering as the Shock Absorber

When these patterns combine, engineering becomes the buffer.

It absorbs unclear direction, shifting priorities, unrealistic expectations, and commercial misalignment. The breakdown rarely appears suddenly. It settles in over time.

Delivery slows until deadlines lose meaning, quality drops until incidents become routine, and ownership disappears because nothing stays stable long enough to own.

Then comes the familiar question: why does engineering underperform?

It does not. It compensates for upstream instability.

Executive Enablement and Structural Confusion

This situation does not emerge by chance. It persists because leadership allows it.

Executives avoid hard trade-offs, accountability blurs, and necessary tension disappears in favour of artificial alignment.

Product and engineering are meant to challenge each other, and when that tension disappears, bad decisions accelerate.

The rise of combined roles such as CPTO often reinforces this pattern. On paper, it promises unity. In practice, it removes the friction required to keep decisions grounded in reality.

Direction and constraint collapse into a single voice, and one dimension dominates, usually the one that speaks more, not the one that understands limits. So the system drifts while believing it aligns.

What Product Should Do

A strong product function reduces work rather than generating it.

It enforces prioritisation, stays anchored in revenue and customer behaviour, uses data to challenge decisions, creates clarity that removes the need for constant follow-up, and owns outcomes.

That responsibility demands discipline.

The Uncomfortable Truth

Most organisations do not face a product problem. They face a decision problem disguised as product, and a leadership problem that refuses to enforce clarity.

Until prioritisation becomes real, accountability becomes shared, and collaboration replaces dictation, nothing improves. Teams remain busy, systems remain fragile, and progress remains an illusion.

If engineering looks broken, stop trying to fix engineers and start fixing the decisions that put them there.