Can you diagnose your own business honestly from the inside?

Partly. You can usually feel where the problem is, and most founders are further along than they give themselves credit for. What's hard from the inside is naming it plainly and then acting on it, because the thing you've stopped noticing is precisely the thing you built the business around.

What is a framework hoarder?

Somebody who has read everything and changed nothing.

Solopreneurs are famous for this and I say that with real affection, because I've been that person. You read all the books, you go to the workshops, you follow the latest thinking, and your business at the end of the year looks remarkably like it did at the start.

And the material is good. You can read Patrick Lencioni on teams and John Maxwell on leadership. You can read Seth Godin and Perry Marshall on marketing, Alex Hormozi on offers, Donald Miller on story. Nearly all of it will work, probably, if you can adapt it to your business. I'm not interested in the cynical take that says it's all noise, because it isn't.

The trouble starts when you're looking for a shortcut, and it gets worse when you assume you can apply the thing directly. Framework hoarders who never see anything change in their business tend to fail in one of two places. They don't know how to adapt rather than adopt, so they install someone else's answer into a business it was never built for. Or they're simply bad at execution, and a shelf full of frameworks sits there unimplemented. You can own every framework in the world. If none of them get put in place and shaped to your actual situation, they do nothing at all.

Inaction does a lot of the damage here, and it's rarely laziness. It's usually the reasonable-sounding decision to read one more thing before starting.

Why does the framework feel clearer than it turns out to be?

Because following a competent explanation feels almost identical to being able to do the thing.

Robert Bjork has spent a career on this. The conditions that make learning feel easy in the moment, like re-reading or watching a clear explanation, tend to produce the weakest retention and transfer. Learners consistently prefer the fluent method and consistently mistake that fluency for having learned. He calls the version that actually works "desirable difficulties," which is a generous way of saying the useful stuff feels worse while you're doing it.

Leonid Rozenblit and Frank Keil found something related about explanations specifically. Ask people how well they understand a mechanism and they rate themselves confidently, then ask them to write out how it works step by step and the confidence collapses. The illusion is strongest for exactly the kind of knowledge a good business framework appears to hand you.

None of which means stop reading. It means the reading was never the part that was going to change anything. Watching someone competent take apart a business you don't own is a fine way to find a better question. It was never going to produce an answer about yours, because nobody in those forty minutes looked at you.

What does having part of the picture look like?

This is most of the founders I work with, and it's worth describing properly because it doesn't feel like being stuck.

Take someone genuinely good at sales. They close well, they've read the sales people, they can hold a room. Everything about that looks like a solved problem. Then ask whether there's a sales process written down anywhere, one you could hand to somebody else and train them on. Usually there isn't. The founder is the process.

Which is fine right up until the day you don't want to do the sales anymore, or can't, or shouldn't. Then you find out that the strongest part of the business was also the least transferable part, and that all the sales content you consumed was helping you personally get better at a thing only you can do.

That's what part of the picture means. Not ignorance. A real strength with a structural gap underneath it that nobody has looked at, because from the inside it reads as the thing that's working.

What happens when nobody names it in time?

I had a discovery call a while back with the managing partner of a consulting firm. Around twenty independent contractors, all working under one brand. Very good consultants, most of them, and like a lot of very good consultants they weren't strong at sales. That was fine, because the managing partner was excellent at it. He'd built the whole thing on his own network.

He was approaching retirement and wanted to step back.

It took about twenty minutes. I said, you have a problem, because if you leave you take your network with you. Nobody else here can generate the work that's feeding twenty households.

He said: exactly.

That's the part I keep thinking about. He knew. He'd known for a while. He didn't need me to find anything, he needed someone from outside to say it out loud so it stopped being a background worry and became a thing on the table. I love that part of the work, calling something out and naming it, because people are usually smart and usually most of the way there already. Occasionally you meet someone who genuinely doesn't know how marketing works and needs an expert to come in, and that's fine too. More often the diagnosis is fast because the person has been circling it for a year.

They didn't hire me, by the way. One conversation and a few emails and that was that. I'm telling you the story anyway, because the useful part isn't that I was clever. It's that a man got to within sight of retirement with twenty people's livelihoods resting on a network he was about to take with him, and nothing in all the good business thinking he'd absorbed over thirty years had made him do anything about it.

I think people are generally good. I also think there's something irresponsible in leaving that unaddressed for as long as he did, because other people were relying on him. Both of those are true at once, and I'd rather say so than pretend it's only the first one.

So can you diagnose your own business?

Some of it. The bit you'll struggle with is the bit that's load-bearing.

It's hard to read the label when you're inside the jar. The assumptions that built your business are the same ones doing the looking, and they've usually been right for years, which is exactly what makes them impossible to inspect. That's why a lead-generation complaint so often turns out to be a positioning problem one layer up, and why "we need to hire" is frequently a question about what seat the hire would even sit in.

Diagnosis also goes quickly when the problem sits in someone's wheelhouse. Growth frameworks are mine, so it doesn't take me long to see where things are likely to be broken, the same way a good electrician walks into a room and knows something's wrong with the panel. That isn't magic and I'd rather not dress it up as insight. It's just what pattern recognition looks like from the outside.

Which is the argument for bringing someone in earlier than feels necessary. Not when the business is in trouble. While it's working, so the structural gap under the thing that's working gets named while there's still time to build something.

The architecture every business needs is the same four domains for everybody. The version you build is yours alone, and it's never a formula. Learn from everyone. Adopt from nobody. We wrote about how to run that test in how to know if business advice applies to your business.

Putting it to work

Pick the strongest part of your business. The thing you'd name if someone asked what you're good at.

Now ask whether it exists anywhere outside your head. Could you hand it to a competent person and have them run it in six weeks? Is there a document, a sequence, a set of criteria? Or is the answer that you just do it well?

If it's the second one, you've found a structural gap under your best asset, and you found it in about four minutes without reading anything.

Then do the harder version. Say the answer out loud to somebody who doesn't work for you and has no stake in flattering you. A peer in another industry works. Your spouse works surprisingly well. Rozenblit and Keil's finding was that confidence collapses exactly at the point where you have to produce the mechanism rather than nod at it, so if your explanation wobbles under one follow-up question, that wobble is the finding.

Do that once with the thing you're proudest of. It's a short exercise and it tends to be uncomfortable in a useful way.

Sources

Frequently asked

Are you saying I should stop reading business books?

No. The material is mostly good and I read a lot of it. The change I'd suggest is what you expect from it. Treat it as a source of better questions about your own business rather than answers, and treat any framework as something to adapt rather than install. The reading was never the part that produces change.

How do I know whether I've found the real problem or a symptom?

Ask what would have to be true for the problem to disappear, then ask why that isn't true yet, three or four times over. Real constraints usually sit a layer or two above where the pain shows up, which is why "we need more leads" so often resolves into a positioning question nobody had asked.

Does this mean I have to hire a consultant?

No. Outside perspective is the requirement and a paid engagement is one way to get it. A peer group, an experienced operator in another industry, or a client willing to be blunt can all do it. What matters is that the person has no stake in your existing story about the business.

Why does this happen more to experienced founders?

Because the assumptions have been right for longer. If you built something real over fifteen years, the judgment that built it has an excellent track record, which makes it very hard to question. Newer owners often see their own business more clearly for the simple reason that they haven't yet stopped noticing it.

When is the right time to bring someone in?

Earlier than most people do. The instinct is to wait until something is visibly wrong, but the gaps worth finding usually sit underneath the parts that are working, and those are the cheapest to fix while there's no pressure. Waiting until it hurts means fixing it while it hurts.

Ready to look at the architecture honestly?

If you've read the books, know the frameworks better than most consultants, and the business still hasn't moved, information probably isn't what's missing. Book the conversation. We'll tell you what we actually see, and whether the work we do fits where you are.

Book the conversation →