Agency shows up everywhere once you know what to look for. In the engineer who spots a broken process and fixes it before being asked. In the operator who notices a deal slipping and mobilizes resources without waiting for an escalation. In the manager who, when handed an ambiguous problem, comes back with options instead of reasons it can't be done.
It also shows up in its absence. In the person who does exactly what they were asked and nothing more, even when the context clearly calls for more. In the team that waits for instructions in situations where any reasonable observer would conclude the instructions should be obvious. In the organization where the response to a new problem is always a meeting to discuss who owns it.
What the word actually refers to
Agency is used loosely in organizational contexts. Sometimes it means ownership. Sometimes it means initiative. Sometimes it means the willingness to make decisions under uncertainty. All of these are related, but they're not identical. Agency as a whole is the integration of all three: you see what needs to happen, you decide you're the one responsible for making it happen, and you act without waiting to be told.
The recurring pattern
Across startups, scale-ups, and established companies, the same pattern keeps surfacing: high-agency people are disproportionately valuable regardless of their role or seniority. This isn't a soft observation — it's one that operators and investors repeatedly confirm from different angles.
Patrick Collison has written about how Stripe's early culture was defined by people who didn't wait for direction. Rather than waiting for someone to assign them a problem, high-agency individuals identified problems worth solving and worked on them. The result was a company that moved faster than its stage would suggest possible.
The pattern shows up in other contexts too. The Prussian military documented it as "mission command" — subordinate units understand the goal and are empowered to make decisions in service of that goal, even when communication breaks down. They observed directly that rigid top-down control failed in the fog of war, and the organizations that lost were the ones where nobody could act without being told. In software organizations, high-agency engineers are the ones who debug a production issue on their own initiative, write the documentation that was missing, or refactor the component that everyone knows is technical debt but nobody owns. They're valuable not because they work more hours, but because they close the gap between what should be done and what actually gets done.
Why it keeps being mentioned
Agency comes up constantly in conversations about hiring, culture, and organizational design for a simple reason: it's scarce and it's essential. Most organizations are structurally designed to suppress agency. Job descriptions define narrow scopes. Approval processes require sign-offs. Performance reviews reward compliance. Promotion criteria favor people who don't make waves.
High-agency people survive and sometimes thrive in these environments, but they often do so despite the system rather than because of it. The organizations that perform best tend to be the ones that either protect high-agency individuals from institutional antibodies, or — better — actively build systems that cultivate agency rather than suppress it.
This series is about what agency actually is, what it looks like in practice, why it's frequently confused with confidence or autonomy, and how individuals and organizations can develop it deliberately rather than hoping for it to emerge on its own.
