Cagan's advice for teams fighting to be treated as empowered rather than as feature teams: accept the stakeholder's framing of the problem rather than re-litigating whether the problem is real, and put the energy into solution discovery instead. The reason is a hidden constraint — leadership's patience for Discovery (Product Discovery Process) before demanding a shipped solution is a "clock" that's always running, even when nobody names it. Spending that limited time contesting the problem statement burns the same runway that solution exploration would need, so it's the worse use of it. See Three Conditions for Empowerment, Believers vs. Doubters (Transformation Stakeholder Split).
A specific, non-obvious version of this trap: an empowered team that spends its early runway proving a stakeholder's problem is real — rather than moving to solve it — has good intentions but has, in Cagan's words, 'totally messed up politically.' The leadership-tolerance clock keeps running regardless of whether the team's activity is validation or solving.
Once a team is confident a problem is real, shift visibly toward solving it — don't let validation work read as stalling to a leadership audience that is already watching the clock.
Из тем: The Product Operating Model