Formation vs Extraction: The Choice You're Already Making
Hook: Every organization is either growing developers or consuming them. There is no neutral position. Which curve are you on?
Here's a story that happens everywhere.
A talented developer joins your company. They're enthusiastic, skilled, eager to grow. Year one, they ship great work. Year two, they're a bit more cynical but still productive. Year three, they're tired, cutting corners, talking about "how things work around here" with a weary resignation.
Year four, they leave. Or worse, they stay—burned out, going through the motions, a shell of who they could have been.
What happened?
Extraction happened.
The Two Models
Every organization operates on one of two models, whether they've consciously chosen it or not.
The Extraction Model:
- Maximize output from current workforce
- Push hard, ship fast, worry about sustainability later
- When people burn out, hire replacements
- Treat developers as resources to be consumed
The Formation Model:
- Develop developers who develop
- Invest in growth, retain over decades
- Build capacity that compounds over time
- Treat developers as practitioners to be formed
These aren't endpoints on a spectrum. They're different games with different rules and different outcomes. Most organizations default to extraction because it's easier to measure and produces faster initial results.
The Math of Extraction
Extraction seems to work at first. Push hard, get more output. Simple math.
But the second-order effects are brutal:
Year 0: 100% capacity, full velocity Year 1: Burned-out people leave. Knowledge walks out the door. 80% velocity (20% lost to turnover drag). Year 2: More burnout. Remaining people cut corners to keep up. Technical debt accumulates. 60% velocity. Year 3: Debt compounds. New hires onboard into chaos. Firefighting becomes the norm. 40% velocity. Year 4: Crisis mode. The best people have left. Those who remain are exhausted. 20% velocity. Year 5: Collapse. Rewrites are discussed. "We need to start over."
The curve is: 100 → 80 → 60 → 40 → 20 → collapse.
Extraction burns through capacity faster than it can be replaced. It's strip mining applied to people.
The Math of Formation
Formation looks slower at first. Investment in people means less immediate output.
But the second-order effects compound positively:
Year 0: 70% velocity (30% invested in development) Year 1: People are growing, not burning out. Retention is high. Still 70% velocity, but capacity is building. Year 2: Investment starts paying off. Developers are more skilled. Better judgment means less rework. 90% velocity. Year 3: Masters emerging. Teaching newcomers. Systems getting more stable. 110% velocity. Year 4: Sustainable excellence. Knowledge compounds. Culture is strong. 130% velocity. Year 5: Best developers want to work here. Word has spread. 150% velocity.
The curve is: 70 → 70 → 90 → 110 → 130 → sustainable excellence.
Formation builds capacity faster than it depletes. It's cultivation, not extraction.
Why Extraction Wins (Short-Term)
If formation is better, why does extraction dominate?
1. Immediate visibility. Extraction produces output now. Formation produces capacity later. Quarterly thinking rewards extraction.
2. Easier measurement. Velocity is measurable. Skill growth is fuzzy. What gets measured gets managed.
3. Exit before the bill. Extraction works if you leave before consequences arrive. Founders who flip, managers who job-hop, investors who exit—all avoid the long-term costs.
4. Misattribution. When extraction fails, blame goes to individuals ("we hired wrong") not the model ("we burned them out"). The system escapes accountability.
5. Cultural celebration. "Move fast and break things" sounds bold. "Work sustainably for decades" sounds boring.
The Real-World Test
Want to know which model you're running? Look at these signals:
Extraction signals:
- Chronic overtime is normal (not exceptional)
- "Crunch" happens multiple times per year
- High turnover among strong performers
- Institutional knowledge keeps leaving
- Developers describe the job as "exhausting"
- Technical debt is growing faster than it's being paid down
Formation signals:
- Sustainable pace is actual practice (not aspiration)
- Crunch is rare and followed by recovery
- Strong performers stay for years
- Knowledge accumulates and spreads
- Developers describe the job as "challenging but sustainable"
- Technical debt is stable or decreasing
Be honest. Which list describes your organization?
The Basecamp Test
DHH and Jason Fried at Basecamp have run the formation model for over 20 years. 40-hour weeks. No growth targets. "Workaholics aren't heroes."
They've been profitable the entire time.
Meanwhile, extraction-model companies have burned through billions in VC funding, churned through thousands of developers, and collapsed or been acquired at fire-sale prices.
The "calm company" model works. It just requires patience and long-term thinking—qualities in short supply in tech.
The Choice Is Made Daily
Here's the uncomfortable truth: you're not choosing between formation and extraction once. You're choosing every day, in small decisions.
- Do you protect focus time, or schedule another meeting?
- Do you invest in onboarding, or throw new hires into the fire?
- Do you maintain sustainable pace, or push for one more sprint?
- Do you let the build stay slow, or invest in speeding it up?
- Do you skip mentorship "until things calm down," or prioritize it?
Every decision either invests in capacity or extracts from it. The model emerges from accumulated choices.
The Question
You're already on a curve. Either:
- 100 → 80 → 60 → 40 → 20 → collapse
- 70 → 70 → 90 → 110 → 130 → sustained excellence
Which curve are you on?
Which curve do you want to be on?
The answer isn't in your values statement. It's in your daily decisions.
Next in series: "Your DX Team Isn't a Service Desk (And That's the Problem)"