> 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-2-the-cost-and-architecture-of-formation/2-the-mullahs-fixed-cup/waiting-with-unskillfulness.md).

# Waiting With Unskillfulness

Real growth demands one cruel capability: staying bad at something after you already know how to be good.

Not permanent incompetence—that's just giving up. But the deliberate choice to remain in not-knowing when you could reach for an answer. To sit with awkwardness when you could smooth it over. To let confusion persist when you could force premature clarity.

This goes against every instinct. Incompetence feels like failure. Not-knowing feels like weakness. You can feel it in your shoulders tightening, your breath shortening, the almost-physical itch to fill the silence before it becomes unbearable. We're trained to resolve discomfort as quickly as possible, to have answers ready, to appear competent even when we're not.

But real formation often requires the opposite: staying with unskillfulness long enough for something deeper to emerge.

### The J-Curve of Formation

Most people visualize learning as a staircase—steady steps upward. In reality, formation often follows a J-curve: to move from one peak to a higher one, you must descend into the valley between them.

You have a way of doing things that works. It's Stage 1 competence—functional, fluent enough to get results. Then you encounter something that reveals the limits of that approach. To develop real mastery, you can't just add skills on top of what you have. You have to temporarily break what's working.

A runner with decent form decides to work with a coach to prevent injury. For weeks, everything feels wrong. Their natural stride pattern has to be dismantled. They're slower, more self-conscious, less fluid. They've gotten worse at something they used to do automatically. The temptation is overwhelming: go back to what worked, even if it was causing problems.

Or someone learning to have difficult conversations. They've developed a functional pattern: avoid direct conflict, smooth things over, keep the peace. It sort of works. Then they realize it's preventing real connection. Learning to be direct requires deliberately choosing awkwardness, sitting with the discomfort of potential conflict, tolerating the sensation of doing it wrong. Their old approach was at least comfortable. The new approach feels like constant failure.

This is the valley. You're not incompetent because you lack knowledge. You're incompetent because you're breaking an old pattern before the new one has integrated. The knowledge is there. The body hasn't caught up yet.

The danger: most people never complete the crossing. They descend into the valley, feel the spike of incompetence, and retreat. Better to be functional at the lower peak than fumbling in the valley.

### The AI Shortcut Problem

AI offers what looks like a bridge over the valley. Why tolerate confusion when you can generate clarity? Why sit with not-knowing when the answer can appear in seconds?

The problem isn't that AI answers are wrong. It's that they arrive at zero latency—no gap between question and response, no space where integration can occur.

Formation requires what you might call a latent period: the interval between stimulus and response where something metabolizes. Reflexes have near-zero latency. Complex thinking requires high latency. Wisdom requires even more.

AI trains you to reduce latency to zero. Question arises, answer appears. Discomfort surfaces, resolution generates. The gap collapses. And with it, the formation that only happens in the gap.

This is particularly insidious because the outputs look good. The essay AI drafts might be better than what you'd write if you struggled through it yourself. The solution it generates might be more elegant than what you'd arrive at through confused exploration.

But you haven't developed the capacity to generate that quality yourself. You've coordinated a better output without undergoing the formation that makes you capable of producing it independently.

The valley is where formation happens. The discomfort, the fumbling, the extended period of producing worse results than you know are possible—that's not a bug in the process. That's the process.

AI doesn't just offer to help you cross the valley faster. It offers to build a bridge so you never have to descend at all. But then you never reach the higher peak. You stay at your current level of capability, just with better tools to compensate for it.

### What Waiting Actually Feels Like

Staying with unskillfulness has a specific texture. It's not the same as being lost or giving up. It's active patience with discomfort.

You're in a conversation that's starting to get tense. Your usual move would be to defuse it—make a joke, change the subject, smooth things over. Instead, you stay with the tension. You can feel your throat tightening, your mind scrambling for an exit. But you don't take it. You let the awkwardness sit there, unresolved.

What happens next isn't guaranteed. Sometimes nothing does—the other person changes the subject, the moment passes. But sometimes, if you can tolerate the discomfort long enough, something shifts. A deeper honesty becomes possible. The conversation goes somewhere it couldn't have reached if you'd reflexively smoothed things over.

Or you're learning a physical skill—instrument, sport, craft. You know the movement you're trying to make, but your body won't cooperate. The old way was automatic. The new way feels mechanical, forced, wrong. Every repetition is a small failure. The temptation is to either quit or revert to what worked before.

Waiting with unskillfulness means continuing the repetition while it still feels wrong. Not grinding through mindlessly—that just reinforces the wrong pattern. But staying present with the wrongness, noticing where it catches, letting your nervous system slowly adjust.

This is qualitatively different from confusion where you have no idea what you're doing. You know what good looks like. You can see the gap between where you are and where you're trying to get. The waiting is in not forcing the gap closed prematurely—not grabbing a technique that bypasses the development, not settling for the old pattern because at least it works.

### Depth Inquiry as Structured Waiting

One way to practice waiting is through depth inquiry: the discipline of asking "why" or "what's underneath this" and actually waiting for an answer instead of grabbing the first plausible explanation.

Someone asks about your work and you feel defensive. The quick answer: "They're being critical and I don't like it." Probably true, but shallow.

What's underneath the defensiveness? "I'm worried they'll think I don't know what I'm doing."

Why does that worry you? "Because I'm not sure I do know what I'm doing."

What's underneath that uncertainty? "I'm using competence as proof of worth. If I can't demonstrate competence, I lose value."

Where did that pattern come from? And now you're into territory that matters—the deep structure that's been shaping behavior for years, invisible until you stayed with the question long enough to let something real surface.

This isn't the corporate "five whys" root-cause analysis. That's often intellectualization—more thinking instead of deeper feeling. This is closer to dropping a sounding line into deep water. You're not looking for an answer to fix the problem. You're looking for the bottom.

The practice is staying with "I don't know" instead of filling it. The first answer that arrives is usually protective—plausible enough to end the inquiry, shallow enough to avoid real contact with what's underneath.

Real answers have a different quality. They land with a small shock of recognition. Not "that's interesting," but "oh, that's true." Often uncomfortable. Usually something you already half-knew but hadn't let yourself fully see.

You can't force this. You can't rush it. The only move is waiting—holding the question open long enough for something beyond the first defensive answer to emerge.

### Productive Waiting vs. Avoidance

But there's a shadow here: not all waiting is productive. Sometimes staying with discomfort is just avoiding action you know you need to take.

How do you tell the difference?

**Productive waiting generates signal**—you notice things you hadn't noticed before. Patterns become visible. The discomfort has texture, variation, information. Even if you don't know what to do yet, you're learning something about the terrain.

**Avoidance accumulates noise**—it's the same discomfort on repeat, no new information, just spinning. The waiting isn't teaching you anything because you're not actually in contact with what's there. You're just keeping it at arm's length while pretending to engage.

Productive waiting feels oriented even when it's uncomfortable. Like something is digesting even though you can't see it yet. There's a sense of movement below conscious awareness—not progress exactly, but metabolic activity.

Avoidance feels stuck. Circular. The same thought loops, the same defensive postures, no actual movement. You're not waiting with the discomfort—you're hiding from it while calling it patience.

Another distinction: productive waiting has limits. At some point the integration either happens or it doesn't, and you move on. Avoidance is infinite—there's always a reason to wait one more day, gather one more piece of information, think about it a little longer.

The test: can you name what you're waiting for? Not a specific answer, but the kind of clarity or shift that would indicate the waiting has done its work? If yes, you're probably in productive waiting. If the waiting has become its own justification, you've likely slipped into avoidance.

### The Lattice Makes Waiting Sustainable

This connects back to "Hold the Slot": the regular practice creates the container where waiting becomes possible instead of just drift.

Without structure, waiting feels like you're floating in open water. No landmarks, no sense of whether you're making progress, just this endless uncomfortable suspension.

With structure—the scheduled slot, the returning practice, the gravitational center—waiting has context. You're not just enduring discomfort indefinitely. You're inhabiting it within a known rhythm.

Monday you sit with the confusion. It doesn't resolve. Thursday you return to it. Still murky, but maybe a shade clearer. Next week you're back again. The regularity creates the sense that even though nothing has visibly progressed, the process is intact.

This is why the slot matters for human formation in ways AI can't replicate. AI can give you the answer now. But it can't give you the capacity to generate answers through sustained contact with difficulty over time.

The lattice—the regular practice, the protected time, the rhythm of return—is what makes the valley crossable. It doesn't eliminate the discomfort of descending. But it creates the structure where you can stay with unskillfulness long enough for integration to occur.

Not forever. Just long enough. The slot doesn't just hold space for surprise. It holds space for the long, ugly incompetence that eventually becomes mastery.