High Agency, High Accountability
Pair the freedom to solve problems your own way with clear ownership of the hypothesis and the outcome.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 88%
Fiona Fung's operating culture on Claude Code and Cowork holds agency as a core value, but always couples it with accountability. Everyone is free to propose how to address a problem (freedom to cook), but that freedom comes with owning a clear hypothesis of what they are trying to solve and being accountable for the result. The two are treated as two sides of the same coin: initiative without accountability produces motion, accountability without agency produces bottlenecks.
Origin
Fiona Fung, connecting it to the broader 'initiative/agency' theme (she references Tyler Cowen's framing of initiative) as the trait distinguishing people thriving in the AI era.
Core principles
- 01Give people genuine freedom to decide how to solve a problem
- 02Every unit of agency carries a matching unit of accountability
- 03Frame each effort around an explicit hypothesis of what you're trying to solve
- 04The people doing best take the most initiative and proactivity
How to run it
- 1
State the problem, not the solution
Present the team with a problem and the priorities, and let each person propose how they think it should be addressed.
- 2
Grant freedom to cook
Give people real latitude to choose their approach rather than prescribing the implementation.
- 3
Attach an explicit hypothesis
Require each initiative to name the hypothesis of what it is trying to solve, so freedom is anchored to a testable intent.
Pro tip Use the hypothesis as the accountability handle: did the shipped work move the thing it claimed it would?
- 4
Hold accountability for the outcome
Follow up on what was actually accomplished, not just activity — 'what have you done?' is the accountability half.
Watch out Agency without this step degenerates into busy motion with no verifiable progress.
In the wild
The team shares out the highest priorities, and then each person owns their item for how they think it addresses those priorities, giving agency inside a bounded set of accountabilities.
→ People retain freedom of approach while staying aligned to a small shared set of priorities.
Common mistakes
Granting agency without accountability
Freedom to cook with no ownership of a hypothesis or outcome produces lots of activity but no way to know if anything was actually solved.
Prescribing solutions instead of problems
Handing people the implementation removes the initiative and proactivity that distinguish the highest performers in this era.
Is it for you?
Best for
Managers of fast-moving, high-autonomy technical teams who want initiative without losing accountability
Not ideal for
Environments requiring tightly controlled, compliance-driven execution where individual latitude is a risk
From the transcript
“we say with high agency is also high accountability. So it's all about like making sure folks have that freedom to cook.”
“it goes back to like what's the hypothesis of what you're you know like trying to solve.”
“the people that seem to be doing best are taking the most initiative, getting the most proactive, have the most agency.”
From the episode
What happens after coding is solved?
Fiona Fung (Manager of the Claude Code and Cowork Teams)