Why Your Best Hires Turn Passive in 6 Months
Why modern organizations accidentally breed passivity, and the 5-part operating model that unlocks high agency.
Let’s be honest about an uncomfortable pattern in growth-stage companies.
You spend months hunting down a high-agency operator. You look for the former founder, the scrappy growth marketer, the sharp BizOps generalist who moves mountains. You pay top of market. You bring them on board and tell them: "Treat this like your own company."
Then, month six rolls around.
That same operator is sitting silently on a 14-person cross-functional "alignment" sync. They wait for someone else to build the Notion agenda. When a key partnership stalls or an enterprise rollout drags, they don’t kick down doors to fix it; they write a polished 5-page memo detailing which external dependency slipped.
They stopped taking swings. They started playing defense.
I see founders make the same two mistakes every single time:
- They blame the talent: "We need hungrier people."
- They add bureaucratic scaffolding: "We need tighter OKRs and another weekly pipeline sync."
Both are dead wrong.
You didn't hire the wrong person. Your operating environment did exactly what it was designed to do: it trained them into compliance.
For the past two years at Wharton (working closely with high schoolers launching real ventures in Global Youth, full-time MBAs spending a semester embedded in the San Francisco tech ecosystem, and battle-tested senior leaders in the Executive MBA program), I watched this exact dynamic play out across hundreds of operators at every career stage.
High agency isn’t an innate personality trait you filter for on an interview loop. It is an engineered response to the operating environment.
If your team is suffering from execution drag, here is the behavioral system to kill passivity and run high-agency teams outside of engineering.
1. Connect the work to a human
In traditional corporate hierarchies, work is routed through layers of translation: executive sponsor to VP, VP to director, director to product manager, product manager to engineer or designer.
By the time the work lands on an individual contributor's desk, it has been stripped of every trace of humanity. It is reduced to a Jira ticket, a brief, or a Slack message.
Adam Grant’s landmark research on task significance at Wharton shows what happens when you bridge that distance. In a study of university call center fundraisers, Grant introduced a simple operational shift: one group spent just five minutes speaking face-to-face with an actual scholarship recipient who benefited from the funds they raised.
The result? A month later, those callers spent 142% more time on the phone and brought in 171% more revenue. The script didn’t change. The compensation didn't change. What changed was the proximity to the beneficiary. When you understand whose life gets easier or harder based on your craft, passivity dissolves.
The Workplace TranslationDoorDash’s WeDash & Airbnb’s Host Immersion
At DoorDash, every employee, from engineering leads to executive VPs, is required to participate in WeDash, performing deliveries or shadowing merchant support calls quarterly. When an engineer watches a merchant struggle with a broken tablet interface in real time during a dinner rush, fixing that UI bug stops being an abstract backlog task; it becomes an urgent operational fix.
Brian Chesky instituted a similar forcing function at Airbnb, requiring product designers and engineers to live in Airbnb listings and host guests themselves. Experiencing the real-world friction of a broken check-in message eliminates the need for managers to push teams to care.
- Mandate direct customer contact rituals. Require every product manager, engineer, and marketer to spend a minimum of two hours per month sitting in on live customer support calls, user onboarding sessions, or churn interviews.
- Attach the face to the ticket. Ban abstract problem statements. Every sprint ticket or project brief should link directly to the unedited user quote, call snippet, or screen recording showing the real friction being eliminated.
2. Give them a fence, not a cage
Whenever an org says, 'Take 20% of your time to go build whatever you want,' most people end up tinkering with trivial side experiments or get completely stuck staring at a blank page, which is why even at Google, only ~10% of people ever actively used it.
Angela Duckworth’s foundational work on grit at Penn explains why: genuine persistence isn't aimless passion. Grit is curiosity anchored in an explicit purpose hierarchy: the deliberate intent to solve a high-stakes problem for someone else. Autonomy without strategic boundaries breeds drift, not velocity.
High agency requires ruthless clarity on the problem boundary, paired with total freedom on execution.
The Workplace TranslationRed Bull's Field Boundaries & Ritz-Carlton’s Discretion Budget
Red Bull’s global field marketing teams operate with tremendous local autonomy, but under an ironclad brand boundary: every execution must embody sports performance, adrenaline, or youth culture. They don't dictate how a field manager in Berlin activates an event, but the strategic envelope is absolute.
Similarly, the Ritz-Carlton gives every employee the autonomous discretion to spend up to $2,000 per guest to resolve an issue or create an exceptional experience, without seeking managerial approval. The purpose hierarchy is explicit: guest loyalty and service recovery outrank internal cost controls on every single shift.
- Draw the box, then get out of the way. If you remember one thing from this post, let it be this: high agency requires clarity on the frontier, not on the path. Leadership’s job is to define the exact problem and the strategic boundaries, then completely step back from dictating to smart people how to execute.
- Filter for the "Why This Matters" test. Before anyone kicks off a new project or sprint, make them answer three simple questions: Who actually benefits? What real friction disappears for them? And is this genuinely the highest-leverage thing we could be doing right now (does it tie back to the org's goals/mission)?
3. Build for an audience, not a boss
Most deadlines fail because they are set for an evaluator instead of an audience.
When you build something solely to satisfy a manager, you optimize for downside protection and box-checking. But when you build for an authentic audience of your peers and customers, human psychology flips: you optimize for craft, pride, and the reputation of putting your name on shipped work.
Katy Milkman’s behavioral research shows why this works: human willpower collapses under present bias whenever we work in isolation. The single most reliable counterweight to inaction is a voluntary public commitment device. When people put their reputation on the line in front of a community they respect, accountability stops being a managerial chore and becomes a matter of ownership.
The Workplace TranslationMorning Star’s CLOUs & Basecamp's Fixed 6-Week Cycles
Look at Morning Star, the world's largest tomato processor. There are zero vertical managers. Every operator signs a Colleague Letter of Understanding (CLOU), a public, written contract with their peers stating exactly what deliverables they are accountable for producing. The social contract does the heavy lifting.
Basecamp runs on 6-week product cycles with fixed deadlines and variable scope. If an initiative isn't shippable by week six, the project isn't quietly extended behind closed doors; it gets cut. The unmovable public delivery deadline prevents feature bloat and forces rapid trade-offs.
- Kill the weekly status decks. At Stripe, individual builders, not managers, wrote direct dispatches to the entire company detailing the exact friction they resolved, why it mattered, and what existed today that didn’t yesterday. Create an open, company-wide channel (
#shippedor a weekly all-hands demo) where operators present finished work directly to their peers.
4. Fight the idea, not the person
Most corporate feedback loops are broken in one of two directions:
- Aggressive fault-finding: A culture of top-down critique that encourages defensive play and risk aversion.
- Artificial politeness: A culture of uncritical consensus where mediocre ideas pass without rigorous interrogation because no one wants to step on toes.
Neither environment produces excellence. Philip Tetlock and Adam Grant emphasize that top performers depend on a Challenge Network: a group of trusted peers who offer radical candor within an environment of absolute psychological safety.
In a great challenge network, pushback isn't seen as an attack on your competence. It’s treated as an essential stress test: poking holes in the idea with peers before the real world does it for you.
The Workplace TranslationBridgewater’s Challenge Culture & Pixar’s Braintrust
In Bridgewater’s investment and operational arms, consensus is explicitly treated as a hazard. Junior operators are evaluated on their willingness to challenge senior partners' operational assumptions in open forums. If a proposal passes without disagreement, it is sent back for deeper stress-testing.
Ed Catmull structured Pixar’s Braintrust as an assembly of veteran directors, screenwriters, and storytellers who conduct unvarnished, scene-by-scene post-mortems on rough film cuts. The critical rule: the Braintrust has zero executive authority to mandate script changes, and the director cannot be fired over the session. Stripping away executive consequence removes personal defensiveness, turning critique into pure problem-solving.
- Borrow Booking.com’s test criteria: critique the rigor, not the opinion. At Booking.com, anyone can launch an experiment without managerial sign-off. When peers review an initiative, they aren't allowed to debate whether they personally like the idea. They scrutinize two concrete things: Is the hypothesis genuinely falsifiable? and Are the guardrail metrics safe? If the answer to both is yes, stop debating opinions in committee and let them run the test.
- Run Duolingo-style test audits focused on learning velocity. Instead of sitting through quarterly roadmap reviews where teams defend original plans, hold weekly test post-mortems. Celebrate what lost, why it failed, and what counterintuitive user behavior the test uncovered. When your team's badge of honor is how fast you invalidated a flawed assumption, the fear of running bold experiments disappears.
5. Reward the swing, not the safety
What an organization rewards defines how its people actually behave, not whatever values are painted on the office wall.
B.F. Skinner’s foundational work on reinforcement schedules showed that behavior is an exact function of its consequences. If you want people to take massive swings, you can't just reward compliance with a safe quarterly plan. In most companies, a mediocre project delivered safely on time gets an "Exceeds Expectations" rating, while an ambitious, high-upside initiative that ran into an unexpected wall gets a quiet reprimand.
Operators quickly learn the real game: play it safe, protect downside, and never touch anything that could explode. If you punish smart failures, you aren’t running an innovation culture; you're running a risk-mitigation bureaucracy.
The Workplace TranslationTata’s "Dare to Try" & Supercell’s Champagne Post-Mortems
Tata Group instituted the "Dare to Try" award, celebrating operational and business failures that represented intelligent, well-executed risks. The award removed the social stigma of failure across a massive conglomerate.
Supercell famously celebrates cancelled games by popping champagne with the entire studio. When a game team realizes a title will not become a top-tier hit, they kill the project and share their learnings openly. Recognizing failure quickly is treated as a strategic win, redirecting top engineering and design talent to the next high-potential opportunity.
- Reward the swing, not just the hit. If someone runs a smart, rigorous experiment that fails, celebrate the speed of learning and the discipline to pull the plug. If the only people getting promoted are the ones who hit safe, sandbagged targets, your best operators will stop taking risks.
- Audit for the "Safe 100%." In performance reviews, treat a spotless track record with suspicion. If an operator didn't fail at anything over the last twelve months, call it what it is: they aimed too low.
At the end of the day, high agency is more than a trait you find in a person. It's also defined by the room you put them in.
When you look across the most effective teams (whether they are high schoolers building their first app, MBAs running venture sprints in San Francisco, or elite product orgs), the core lesson never changes.
High agency doesn’t come from a tighter rubric, a heavier process, or more micromanagement.
Give them a real human at the end of their work. Build them a fence, not a cage. Give them an audience that matters, and a room full of peers who refuse to let them think small.
Build a culture of owners, not occupants.