Earned, Not Declared

There's a pattern I keep running into, maybe you've seen it too. It doesn’t belong to any one industry, any one type of leader, or even this particular moment in tech. But it’s getting harder to ignore.

A team is early stage. The runway is real. The questions are genuinely hard. And the leader — usually smart, usually well-intentioned — responds by building the system, instead of proving the bet.

I’ve seen it show up as a deck with six proprietary frameworks, a four-column glossary, and a 500-person vision for a twelve-person team. I’ve seen it as a RACI matrix drafted before anyone’s closed a single client. I’ve seen it as a carefully articulated operating model for a product that hasn’t found its first real user yet.

Similar thing happens at large enterprises. Even when deliberately addressing a portion of the audience, a pilot or smaller test, the instinct is to start building the cathedral. Teams will be drawn. New cadences will pop up. Roles and responsibilities discussed followed (or proceeded by) seasoned individuals teaching their way of doing things to each other. Usually includes some kind of intake! All before any validation of the concept.

None of it is stupid. Most of it is genuinely thoughtful. That’s what makes it so hard to name.

What’s actually happening, I think, is that designing a system feels like progress when you’re not sure how to move forward. Ambiguity is uncomfortable. Frameworks are tangible. A comprehensive deck signals mastery. And mastery feels safer than admitting you’re still in the unknown-unknown phase of the work.

But here’s the cost: when leaders declare the system before they’ve earned it, they don’t just waste time. They consume the thing the team needs most — which isn’t more context. It’s agency.

What people actually need to move is simple: what is the current bet we’re making, who is driving it, and how do I help when they ask. That’s it. Everything else, the org design, the ceremonies, the defined workflows… gets earned through iteration, not announced in advance.

Structure is a byproduct of momentum, not a precondition for it.

This isn’t an argument against norms or working relationships, those are the soil. But soil isn’t a floor plan. I keep thinking about how this intersects with the current enthusiasm around agentic AI. There’s a lot of excitement about building systems that can act autonomously; that can sense, decide, and move without waiting for a human to authorize every step. Which is interesting, because many of the same organizations championing autonomous software haven’t yet figured out how to give their human teams that same permission.

You can’t architect your way to trust. And you can’t grant agency through a framework.

The workers who are skeptical right now — and there are a lot of them, with good reason — aren’t just reacting to AI. They’re reacting to a longer pattern. Leaders who say they want owners, then hand people instruction manuals. Organizations that declare direction without creating conditions. Systems that are comprehensive, internally consistent, and largely hypothetical.

Teams have seen the deck. They’ve read the glossary. They know the difference between a system that was earned and one that was announced.

The antidote isn’t better communication. It’s restraint. Point at the distant horizon. Name the current bet. Hand ownership to the people closest to the problem. And resist, genuinely resist, the urge to describe the whole cathedral before you’ve laid a single stone.

The structure will come. But only after you’ve done the work to deserve it.

❖ ❖ ❖

Thanks for following me down another trail of navel-gazing. If this pattern sounds familiar from where you sit, I’d genuinely like to hear about it.