n o ren
Building & Strategy

Who Actually Owns a Strategic Trade-Off?

Adobe’s 2010 Flash pivot wasn’t the CEO’s call—it was the engineers’ fight.

2026-07-152 min read

Strategic decisions are rarely owned by the person who declares them. The real owner is the team that must enforce the trade-off. When Adobe announced its 2010 pivot from Flash to HTML5, CEO Shantanu Narayen signed the memo, but the actual decision was made by the product and engineering teams. They saw Apple’s iOS 4 blocking Flash, evaluated the long-term cost of maintaining a dying platform, and argued for reallocating resources to HTML5. The CEO’s role was to legitimize the shift; the engineers’ was to make it happen.

Why does ownership rest there? Because strategic trade-offs are logistical, not symbolic. The pivot from Flash required cutting Flash R&D headcount, deprioritizing customer requests for Flash features, and rewriting internal tooling—all decisions that only the product team could execute. The CEO could declare a direction, but the engineers controlled the “implementation bottleneck”: the codebase and roadmap. This pattern repeats in every major strategic shift: ownership sits where the trade-off is enforced, not where it’s announced.

The deeper problem is that leaders often mistake visibility for authority. When Adobe’s board pushed for the HTML5 pivot, executives debated market share and revenue risks. The engineers, meanwhile, fought internally to protect their HTML5 experiments from being killed by legacy Flash stakeholders. This “ownership inversion” explains why 70% of strategy pivots fail—leaders assume authority exists in their domain, but it’s buried in the team that can actually make the trade-off.

The twist? The most critical trade-offs are invisible to senior leadership. When a team resists a strategic move, it’s rarely about the goal itself—it’s about the specific costs they must absorb. At Adobe, the HTML5 shift succeeded only after the engineering team secured control over Flash’s sunset timeline, ensuring they could phase it out without customer backlash. This hidden locus of power is why “strategy follow architecture” isn’t advice—it’s a rule: the unit that owns the architecture owns the trade-off.

Key insights
Ownership is where the trade-off is enforced, not declared.
The unit that controls implementation constraints owns the decision.
Senior leaders legitimate strategy—they don’t execute it.
Resistance always reflects unacknowledged implementation costs.
Why it matters

Ignoring this leads to strategies built on wishful thinking, not the gritty trade-offs that define execution.

It creates false confidence in alignment, masking internal resistance until a strategy collapses under operational friction.

Use this tomorrow
1
For your next strategic meeting, identify the team that will execute the main trade-off. Have someone from that team present their constraints.
2
Audit a recent strategic failure: Which group resisted? Was the trade-off actually their responsibility to enforce?
Go deeper

This dynamic explains why “product-led growth” strategies stall when marketing owns the roadmap. The product team holds the actual trade-off: whether to build features that accelerate virality or maintain core functionality. If they aren’t aligned, the vision crumbles.

The mechanism is similar to “incentive misalignment in bonuses” but more granular—it’s not about financial motives but systemic control over the execution levers.