> For the complete documentation index, see [llms.txt](https://cafebedouin.gitbook.io/potm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cafebedouin.gitbook.io/potm/section-1-the-crisis-of-expertise/1-the-mullahs-map/005_why_organizations_cant_learn.md).

# Why Organizations Destroy Their Own Capability

> "The problem with the world is that the intelligent people are full of doubts and the stupid ones are full of confidence."

A major consulting firm recently eliminated their junior analyst program. The reasoning was straightforward: AI can now do the work those analysts used to do—market research, data synthesis, presentation creation. Why pay entry-level salaries for work that can be automated?

The decision makes perfect economic sense if you're looking at this quarter's numbers. Junior analysts produce reports. AI produces reports faster and cheaper. Replace humans with machines. Simple.

But those junior analyst roles weren't just about producing reports. They were where people learned to develop judgment. Where they made mistakes with low stakes. Where they built the pattern recognition that, years later, would let them sense when a client was about to walk away or spot the flaw in a seemingly perfect strategy.

The firm didn't eliminate a cost center. They eliminated their pipeline to senior expertise. They're eating their seed corn.

And they're not alone. Across industries, organizations are making the same mistake: optimizing for smooth output today at the cost of capability tomorrow. Not because leaders are stupid, but because **the work that builds capability is invisible to how organizations measure value**.

### What Organizations Can't See

Remember the three stages from Essay 4:

**Stage 1: Understanding** - You know what to do\
**Stage 2: Awkward Practice** - You're learning to do it, making mistakes\
**Stage 3: Integrated Skill** - You do it automatically

Organizations can measure Stage 1 output and Stage 3 execution. Stage 2 looks like waste.

When a junior analyst spends three days wrestling with an analysis a senior person could do in three hours, that looks inefficient.

When someone makes mistakes while learning a new skill, that looks like poor performance.

When people need time to practice and integrate new capabilities, that looks like slack that should be filled with productive work.

So organizations systematically eliminate Stage 2 work. They structure roles to minimize "learning time" and maximize "productive output." They reward smooth execution and penalize visible struggle.

In doing so, they destroy their capacity to build new capabilities.

### The Measurement Trap

Imagine two employees:

**Employee A** is learning a new system. They're in Stage 2—struggling, asking questions, making mistakes, taking longer than they "should." To management, they look like underperformers.

**Employee B** is executing a familiar process. They're in Stage 3—smooth, fast, confident. To management, they look excellent.

Now the organization needs to adapt to a major market shift. They need people who can learn new skills quickly, who have practice navigating uncertainty, who have built the meta-skill of learning itself.

Employee A has been building exactly that capacity. Employee B has been executing the same process efficiently for years without building anything new.

But the organization has no way to see this. Their metrics capture output quality and speed. They can measure Stage 1 work product and Stage 3 execution. The capability Employee A has been building is invisible—until the moment they need it, at which point it's too late to develop.

When the organization needs to adapt, they discover that all their "high performers" are people excellent at executing processes that are now obsolete. And the people who would have been capable of navigating the transition weren't rewarded for building that capability—they were penalized for looking inefficient while doing it.

### When Slack Becomes Heresy

Every organization claims to value learning and development. They have training budgets, professional development programs, learning systems.

But watch what happens to unscheduled time.

A team finishes a project early. They have a week before the next major deadline. This is, theoretically, perfect time for Stage 2 work—trying new approaches, practicing unfamiliar skills, exploring improvements.

What actually happens? The capacity gets immediately filled. Someone notices the team has availability and assigns them to another project. Or they're expected to start the next project early. Or they're pulled into meetings to help other teams.

The message is clear: **unscheduled capacity is waste. If you have time to learn, you have time to produce.**

This creates a problem. Organizations want their people to develop new capabilities. But they structure work so that any time that could be used for development is immediately colonized by operational demands.

The result: people only learn new skills during crises, when old approaches have failed and they're forced to figure out something different under maximum pressure. Which is the worst possible condition for skill development—high stakes, no room for mistakes, no time for integration.

### The Pipeline Problem

Tech companies face a particularly visible version of this.

For years, the career path was clear: start as a junior developer, work on smaller features, gradually take on more complex problems, eventually become a senior engineer who can architect systems and make high-level decisions.

Junior developers were, objectively, less productive than senior developers. They wrote slower, needed more code review, asked more questions, made more mistakes. If you measured purely on output, they were inefficient.

But they were also the pipeline. The only way to create senior developers was to hire junior developers and give them years of practice.

Then coding assistants got good. AI can now generate code for routine features faster than a junior developer. The economic logic is compelling: why pay someone $80,000 to do work AI can do instantly?

Some companies are following that logic. Reduce junior headcount. Use AI for routine work. Hire only senior engineers for complex problems.

The short-term economics are sound. The long-term problem is obvious: **where do the senior engineers come from in five years?**

You can't hire people directly into senior roles at scale. Seniority requires years of practice—making mistakes, encountering edge cases, building the judgment that lets you know when the elegant solution is wrong and the ugly hack is right.

If no one is hiring junior developers, no one is building the pipeline to senior capability. The industry is collectively optimizing for today's output at the cost of tomorrow's capability.

And individual companies can't easily fix this alone. The company that invests in training junior developers when competitors don't is at a short-term competitive disadvantage—higher costs, slower output. The benefits only show up years later, and by then the developers they trained might be working elsewhere.

**This is structural.** The work that builds capability is invisible to quarterly metrics. The time required for skill formation looks like slack. And the market rewards eliminating slack.

### Transformation Without Formation Time

Here's another pattern: organizations announce major transformations. New systems, new processes, new ways of working. They expect people to adapt quickly.

But transformation requires Stage 2 work—awkward, effortful practice of new approaches. People need time to struggle with the new system, make mistakes, integrate the new patterns. They need reduced operational load while they're learning.

Instead, organizations demand transformation while maintaining full operational tempo. People are expected to learn the new system while hitting the same productivity targets they had with the old one.

This is asking for Stage 3 performance (smooth execution) while people are in Stage 2 (awkward practice). It doesn't work.

People get exhausted trying to maintain output while learning. They develop workarounds to the new system so they can keep performing. The transformation fails or produces only surface compliance.

Then the organization concludes people "resisted change" or "weren't committed." But the real problem was structural: no protected formation time, no acceptance that capability-building requires temporary performance reduction, no recognition that transformation is itself work that requires capacity.

### The Collective Action Problem

Individual organizations struggle to fix this because the incentives push toward short-term optimization.

If your company protects 20% of capacity for skill formation while your competitors don't, you have higher costs and slower output. In the short term, you're at a competitive disadvantage. The benefits—a workforce that can adapt when market conditions change—only show up years later.

This is a classic collective action problem. Everyone would be better off if everyone invested in capability-building. But any organization that does it alone pays the cost while competitors free-ride.

The result: a race to the bottom. Organizations that protect formation time lose market share to organizations that don't. The market rewards eating seed corn. Until the crisis hits and everyone discovers they have no capability to adapt.

### How This Connects to the Broken Environment

Remember from Essay 3: the environment systematically rewards performance over capability. This creates specific organizational problems:

**Credentials over consequences**: Organizations hire based on degrees and certifications (Stage 1 signals) rather than demonstrated capability (Stage 3 evidence). This means they can't distinguish people who can explain from people who can execute.

**Frameworks over judgment**: Organizations promote people who can present well using standard models rather than people who have developed discernment through consequences. This means leadership lacks the judgment to recognize when their models don't match reality.

**Complexity over clarity**: Organizations create elaborate processes and systems that are hard to evaluate, making it easier to hide the absence of real capability behind sophisticated-sounding explanations.

**Simulation over reality-checking**: Organizations make decisions based on analyses and projections (maps) without requiring evidence that previous analyses actually matched outcomes (territory-checking). This means they never get the feedback that would reveal when simulation is failing.

These dynamics compound at the organizational level because **no individual is responsible for long-term capability**. The executive who eliminates junior roles gets credited for cost savings this quarter. Someone else, years later, deals with the capability shortage. The person making the decision doesn't face the consequences.

### What Would Have to Change

Making capability-building visible and valuable requires structural changes:

**Protected capacity that can't be raided**: Not "20% time if you can find it" but "20% of capacity is reserved for Stage 2 work, period." Management cannot colonize this time for operational demands.

**Metrics that capture capability growth**: Track not just output but whether people are building new skills, expanding their range, increasing their ability to handle novel situations. Make these metrics as important as productivity metrics.

**Mandated integration periods**: After any major change, a required period of reduced operational tempo while people integrate new practices. Recognition that transformation is work that requires capacity.

**Career paths that value formation**: Promote people who build capability in others, not just people who execute well individually. Reward mentoring, teaching, and developing others as much as personal performance.

**Formal pathways for ground-level learning**: Ways for people doing the work to surface what they're learning and have it inform strategy. The people doing the work encounter reality first. Organizations need mechanisms to capture that learning.

None of this is easy. All of it goes against powerful economic incentives. Organizations that try to do it alone face competitive disadvantages in the short term.

But the alternative—organizations that can only execute existing processes and have no capability to learn new ones—is ultimately unsustainable.

### The Seed Corn Problem

This is what economists call "eating your seed corn"—consuming the resources you need for future production because you're optimizing for consumption today.

Organizations are eating their seed corn by eliminating the roles and the time where people build capability. They're getting more output today at the cost of capability tomorrow.

The question isn't whether organizations will need to adapt. The question is whether they'll build the capacity to adapt before they need it, or discover they lack it in the middle of a crisis.

That capability has to be built through the messy, invisible, inefficient work of Stage 2 formation. The work that organizations are currently optimizing away.

### What This Means For You

If you're in an organization, you can at least see what's happening:

When unscheduled capacity gets immediately filled, that's not just bad management—**it's a structural feature of how organizations value visible output over invisible capability-building**.

When junior roles are eliminated because AI can do that work, recognize: **this isn't just about cost savings, it's about destroying the pipeline to expertise**.

When you experience transformation fatigue, you can name it: **the organization is demanding constant Stage 2 effort without providing integration time to reach Stage 3**.

If you're in a position to influence organizational design, you can advocate for structural changes that would make capability-building visible and valuable.

But understand the forces working against this. Short-term metrics reward eliminating formation time. Individual managers who protect learning capacity look inefficient compared to those who maximize output. And the benefits of capability-building show up years later, usually on someone else's watch.

The invisible work isn't optional. It's the foundation of everything else. Organizations that can't see it, value it, and protect it will keep wondering why their high performers can't perform when the world changes.

The seed corn doesn't plant itself.

*"You cannot change people or organizations. They can only be made anew."*

***

### Questions

**How much of your work week is Stage 2 practice?**\
Track a typical week honestly: Stage 1 (synthesizing information), Stage 2 (struggling with new skills, making mistakes, deliberate practice), Stage 3 (smooth execution of familiar work). What percentage is actually building new capability? If it's under 20%, what's preventing you from protecting formation time?

**Where is your organization eating seed corn?**\
Identify one place where your organization is optimizing for immediate output at the cost of future capability. Is it eliminating junior roles? Filling all slack with operational demands? Punishing visible struggle? What pipeline to expertise is being destroyed? What will the consequences be in 3-5 years?

**What capability do you need but have no time to build?**\
Name a skill you know you need to develop but keep deferring because "there's no time." What would it take to protect 10% of your capacity for deliberate practice? What would you need to stop doing? Who would you need to negotiate with? What language would make this non-negotiable rather than "nice to have"?

### Practice

**The Stewardship Check**\
Ask yourself: Am I freely choosing this, and does it help me (or us) flourish?

*Use when*: You feel bound by duty, guilt, or inertia in a group, project, or habit.\
\&#xNAN;*Remember*: Stewardship is chosen and fruitful. If not, it's enabling—time to step back or step out.

***

## Footnotes

\[^1]: