Issue #10 - Insight or Infrastructure?
Subscribers Edition
An insight lives in your head. Infrastructure lives in the world. The distinction determines whether your work compounds when you walk away or collapses the moment you do.
Field Note
G. Mick Smith left a comment on one of my posts Tuesday afternoon. Seven words.
"You've already crossed the line from insight into infrastructure."
He has a doctorate, runs a podcast that's been going thirteen years with over seven hundred episodes, and works in authority architecture. The comment wasn't a compliment in the social media sense. It was a diagnostic. A peer in an adjacent category noticing something about the work and naming it specifically.
He followed it up with a direct message. "How expertise itself becomes structured, portable, reusable, and persistent across people and systems. That is a much more interesting conversation."
I sat with that for a while.
The distinction he named isn't academic. It's the difference between work that compounds and work that doesn't. Between expertise that survives your absence and expertise that requires your continuous attention. Between knowing something and having something. Most knowledge workers I talk to never make this distinction. The cost of not making it is enormous.
The Deep Dive
An insight is a thought. A useful one, sometimes a brilliant one. It changes how you see something. You write it down, you talk about it, you build a presentation around it, you put it in a book.
But an insight is dependent on the person holding it. If you stop showing up, the insight stops being available. If you forget it, it's gone. If you can't articulate it on a given day, no one else can pick it up and use it. Insights live inside heads. They die when heads stop working.
Infrastructure is what happens when an insight has been converted into a structure that operates without you. A system, a process, a framework, a piece of writing specific enough that someone else can follow it. Infrastructure is portable. It's reusable. It's persistent. It continues to operate whether you are present or not.
The shift from insight to infrastructure is conversion, not effort. You can spend years generating insights and never produce a single piece of infrastructure. The variable isn't how hard you're working. The variable is whether you've taken the thing in your head and turned it into a thing in the world that can be operated by someone other than you.
Most knowledge workers stay on the insight side because the insight side feels productive. You're thinking. You're learning. You're saying interesting things. You're getting reactions. The feedback loop is fast and the dopamine is consistent. The infrastructure side is slower. Converting an insight into a structure that someone else can use requires you to name what you actually do, in what order, with what inputs, against what success criteria. It requires you to find the parts of your thinking that are repeatable and separate them from the parts that are intuition or context-dependent. It requires you to write things down with enough specificity that another person could replicate the work without you in the room.
The work isn't glamorous. It's also, in my experience, the only kind of work that compounds.
Case Slice Teardown
Role: Independent strategy consultant, ten-plus years of practice, strong reputation, consistent client demand
Situation: Consultant wanted to take a real vacation for the first time in years. Every previous "vacation" had been interrupted by client calls because the work could not continue without them. The client portfolio was healthy. The bank account was healthy. The thing that was missing was the ability to step away.
Constraint: No team to delegate to. Solo practice. Client engagements ranged from two-week sprints to multi-month strategic projects. Each one had been built around the consultant's personal involvement.
Intervention: Audit of the work using a single question: "What would happen to this engagement if I disappeared for a week?" Applied to every active client. The answer was the same in every case: the work would stop. Not because the clients couldn't survive a week without strategy support, but because the consultant had never converted their methodology into a form that anyone, including themselves with notes, could continue without their continuous presence.
Outcome: Six months of deliberate conversion work. The consultant documented their five most-repeated engagement patterns as structured frameworks with inputs, decision points, success criteria, and failure modes. The frameworks didn't replace the consultant's judgment. They captured enough of the judgment that engagements could continue through brief absences. The first vacation in three years happened that summer. Clients didn't notice.
What's notable here: The consultant didn't add knowledge during those six months. They converted existing knowledge. The expertise was already there. What was missing was the conversion. The consultant had been operating entirely on the insight side for a decade. The conversion to infrastructure took six months. The compounding from that point forward was immediate. Engagements could be partially run by junior people. Methodologies could be taught instead of demonstrated. The practice stopped depending on the practitioner being in the room.
The Infrastructure Test
1. Pick one thing you do regularly that you would say you're good at.
Not a hobby. Not a side interest. Something that drives outcomes that matter to you. Client work. A decision pattern. A creative practice. A management approach. Whatever you'd put on a résumé if you were trying to win business in your strongest area.
2. Could someone else do that thing if you walked away for a week?
Be honest. The answer is almost always no for most knowledge workers. Not because the work is impossible to learn, but because it has never been converted into a form that someone else could pick up. The knowledge of how to do it lives inside you. Your absence is total absence.
3. If the answer is no, you have an insight.
A useful, valuable, hard-won insight. It changes how you see your work. It produces good outcomes. It compounds in your head. It does not yet compound in the world.
4. If the answer is yes, you have infrastructure.
The system holds in your absence. The work continues. The expertise has been converted into something that operates whether you're present or not. Whatever follows from here builds on what's already operating.
5. There's no half-credit.
Either someone could continue the work in your absence or they couldn't. Either the system holds when you remove yourself or it collapses. "I have some notes" is not infrastructure. "I've written it up once" is not infrastructure. Infrastructure is what actually continues running when you walk away.
Apply the test to three or four things you do. The results will surprise you. Things that felt systematic turn out to be intuition. Things that felt simple turn out to depend on twenty small judgment calls you make without thinking. The first time someone tries to do your work without you, they will discover all the places where your intuition was doing the load-bearing work, and you didn't know it.
That's the gap between insight and infrastructure. Closing the gap is the work.
Convert one insight into one piece of infrastructure
Pick something you do well that lives only in your head.
A judgment call you make consistently. A creative process. A way of running a meeting. A pattern in how you handle a specific kind of problem. Something where your outcomes are better than average and your method has never been written down.
Name the decisions you make during the work.
Not the steps. The decisions. Where do you pause to weigh something? What signals do you look for? What would tell you to switch approaches? The decisions are the parts that hide your intuition. Write them down.
Write the success criteria.
How do you know the work is done correctly? What does the output look like? What does it not look like? If a junior version of you handed in the work, what would tell you they nailed it versus missed it?
Hand the document to someone and ask them to try it.
Not theoretical. Actual. Watch where they get stuck. Every stall is a piece of intuition you didn't capture. Patch the document. Hand it back. Repeat.
That's the conversion. It's not glamorous. It's the only thing that takes work out of your head and into the world.
What's something you do well that someone else couldn't continue if you stepped away tomorrow?
Reply with the work and what's missing from making it transferable. The most useful examples (anonymized) will appear in a future issue.
Most expertise stays trapped on the insight side because nobody teaches the conversion. The methodology for systematic conversion is teachable. The compounding starts the day you stop adding insights and start converting them.
Explore Strategic Thinking AcademyOr learn to build your own frameworks, a step-by-step methodology course.
or
Subscribe for a new framework every week
Subscribe - $17/mo
Strategic Thinking Weekly - Published every week
Unsubscribe anytime - Tampa, FL