The difference between high-agency and low-agency people is not immediately obvious from their resumes, their titles, or even their stated attitudes. It shows up in behavior — specifically, in what they do when the situation is unclear.
The same situation, different responses
Imagine this: a product team is preparing for a launch and realizes two weeks out that the external API they depend on has been deprecated without notice. The team that depends on it has no alternative in place.
A high-agency person on that team does several things in rapid sequence. They assess the scope of the problem. They identify what alternatives exist. They start building a workaround or engaging vendors before being asked. They flag the risk to stakeholders with a clear status and a proposed path forward, not just a problem statement.
A low-agency person on that team documents the issue in a ticket, sends a message noting the API is deprecated, and waits for someone to tell them what to do. They may be entirely competent at their job. They may complete their tasks promptly and correctly. But in this moment, the gap between them and the high-agency version is not about skill — it's about the willingness to act without a brief.
The behavioral markers
High-agency people share a cluster of behaviors that are recognizable once you've seen them — and the behaviors are consistent enough that they're visible even without knowing the person's background or confidence level:
They frame problems as their problems. Not in a martyrish "I'll do everything myself" sense, but in the practical sense that they don't wait for a problem to be formally assigned to them before engaging with it. When they encounter something broken, their first instinct is to ask "can I fix this?" rather than "who owns this?"
They close the loop. When they take on a task or identify a gap, they see it through to resolution or explicit handoff. They don't leave a conversation with a decision unmade or a problem partially addressed without a clear owner.
They give context, not just status. When they escalate or report, they include what they've already tried, what they think the tradeoffs are, and what they're asking for. They don't just surface problems — they come with considered options or a recommended path.
They operate in the white space. High-agency people are drawn to the gaps between functions, the processes nobody owns, the risks that fall between teams. They're comfortable working without a job description that explicitly covers what they're doing.
They don't confuse motion with progress. This is the important distinction. High-agency people are not necessarily the most active or the loudest. They are the ones who produce outcomes that matter. There's a difference between someone who sends 50 messages a day and someone who quietly resolves the bottleneck that's been blocking three teams for a week.
What low agency looks like
Low agency is harder to see because it's often well-disguised by compliance. A low-agency person will complete their assigned tasks, attend their required meetings, and respond to direct requests promptly. None of this is bad. But when something falls outside their defined scope — when the right action is obvious but nobody told them to do it — they wait.
The tell is this: they orient toward the source of the instruction rather than toward the work itself. When given a task, they focus on satisfying the person who gave it, not on whether the task actually accomplishes what it was meant to accomplish. They do what they were asked to do, with the exact specification they were given, and consider it complete.
This is not laziness or incompetence. Many low-agency people are talented and hardworking. The issue is a mental model that treats "being assigned" as a prerequisite for action. Without that assignment, they experience a kind of decision paralysis — not because they can't figure out what to do, but because something in their operating system treats initiative as presumptuous.
Why this matters for organizations
The cost of low agency is most visible during chaos — during a launch crisis, a key departure, a sudden market shift. But it's present constantly at lower intensity: in the meeting where three people discuss a problem that one person could have solved on their own. In the project that takes three weeks longer than necessary because nobody felt authorized to make a call. In the decision that gets escalated six levels when it should have been made at the first level that had enough context to make it.
High-agency organizations are not ones where everyone is a founder. They're ones where the default answer to "should I act?" is weighted correctly — where people have the judgment to know when to act and the permission to act without asking.
