Scaling Selves

The startup playbooks will take you a long way. Here is what I keep noticing they leave out.

I have sat in rooms where a leadership team had done everything right — the right framework, the right structure, the right quarterly rhythm — and something still wasn't working. The scorecard looked fine. The rocks were set. The accountability chart made perfect sense on paper.

And yet. The same issue kept appearing. In different clothes, with different names, in different meetings. And nobody could quite explain why.

If I am honest, I could not see it at the time. I was in those rooms thinking about the frameworks, the tools, the structure. It was only later — running my own business, training as a coach, watching the same patterns show up in my own leadership — that I understood what had actually been going on.

And the view keeps sharpening. I navigate this in real time in my own company. My husband runs his own business too, so I see it there as well — close up, in someone whose thinking I know well. There is something about watching the people nearest to you wrestle with the same questions that makes everything clearer. You stop being theoretical about it.

That particular kind of humbling is useful. I am glad of it, even when it was uncomfortable. It means that when I sit with a founder who is stuck in a version of themselves the company has outgrown, I am not looking in from the outside. I have been in that room as the person who needed to change. That is a different kind of knowing.

That is the gap this post is about.

And I want to be specific about what I mean. Not inner work in the abstract, therapy-adjacent sense. Something more concrete than that. The capacity to hear something uncomfortable without immediately defending against it. The ability to say in the room what you actually think — not what you think you should think. Letting go of the work that used to make you feel capable, so someone else can own it properly. Having the conversation that has been postponed for three months because the timing never feels right.

The tools are good. Most of them are excellent. What they need to run on is a leader — and a team — who are not quietly working against themselves. That is the tangible thing. Not a personality overhaul. Just enough honesty, enough trust, and enough willingness to look at what is actually happening.

---

The Books

What the startup canon gives you — and what it quietly assumes

Most founders and leadership teams develop a shelf. Traction. Scaling Up. Good to Great. High Output Management. The Hard Thing About Hard Things. From Startup to Grown-Up. Good books. Some genuinely important ones. I recommend most of them and use their ideas in sessions regularly.

What they share — and this is not a criticism, it is an observation — is a quiet assumption that the people holding the framework are ready to use it honestly. That the leadership team has enough trust to hold each other to account. That the founder has done enough inner work to step into the leader the company now needs. That the values on the wall are the values that actually govern decisions under pressure.

The frameworks are necessary. They are just not sufficient. And the gap between the two is where most of the real problems live.

---

Identity First

The shift from founder to leader is not a promotion — it is a transformation

Alisa Cohn's From Startup to Grown-Up comes closest to naming this directly: the founder must grow from the person who started the company into the leader the company now needs. Michael Gerber said something similar in The E-Myth — that most people who start businesses are technicians who had an entrepreneurial seizure, and the technician eventually becomes the obstacle when the company needs the CEO.

Both are right. And both stop just short of the thing that makes it hard.

It is not that founders do not understand the logic. They do. Most can articulate exactly what needs to change. The difficulty is that the work they are being asked to let go of is threaded through their identity. The product they shaped. The client they won at 11pm because nobody else knew who to call. The culture that exists because of how they walked into rooms. Letting go of that is not a strategic reallocation. It is a loss. And losses tend to need acknowledging before they can be moved through.

Andy Grove's framing in High Output Management is useful here: a manager's output is the output of their team, not their own individual work. The principle is clean. Applying it requires something that principle alone cannot provide — a willingness to find your authority in something more diffuse and harder to measure than the thing you built.

A practical place to start

The still-doing audit. Make a list of everything you did last week. Against each item, ask: could someone else do this — or be developed to do this? If the answer is yes, ask the harder question: why are you still doing it? Not as a judgement. As genuine curiosity. The answer is usually more interesting than "I haven't had time to delegate it."

---

Founding Cracks

The team that built it is not always the team that can grow it

Jim Collins established in Good to Great that the discipline is first who, then what — get the right people on the bus before deciding where it goes. Reid Hoffman adds something Collins could not have fully anticipated: the people who thrive at ten people are often different from those who thrive at a hundred. The chaos-tolerant, ambiguity-loving early employee can become genuinely harmful at scale — not because they have changed, but because the company has.

The founder who hired these people — who owes them something real, who built something together with them — now has to hold the loyalty and the judgement simultaneously. Most oscillate between denial and overcorrection. Neither is the answer.

Ben Horowitz writes honestly in The Hard Thing About Hard Things about the loneliness that accompanies this: being the person who cannot show the fear, who must project certainty while privately uncertain. I have given that book to founders who felt entirely alone in what they were carrying. The relief when they read it is something I recognise.

But naming the loneliness is not the same as working with it. Acknowledgement is the beginning, not the end.

A practical place to start

The founding team conversation. Most founding teams have never explicitly discussed three things: what each person needs from the company as it grows, who defers to whom and on what, and what would happen if one of them was no longer the right fit for the next stage. Have that conversation now — before there is a crisis forcing it. It is far easier when nobody's job is immediately on the line.

---

Values Gap

The values on the wall are the ones you aspire to. The values in the room are another matter.

I have worked with enough leadership teams to know that the values exercise happens at some point in almost every scaling company. A workshop, a facilitated session, a set of words that end up on the website. The words are usually reasonable. "Integrity. Innovation. People first. Curiosity."

The problem is not the words. It is the gap between them and what actually governs decisions under pressure. I have seen companies where "people first" was a stated value and a key person was let go by text message. Where "integrity" was in the onboarding deck and commercial decisions were routinely made that everyone in the room knew were wrong.

The questions that matter are not "what do we value?" They are: what do we do when our stated values conflict with a commercial decision? Who is allowed to name when we are violating them — and what actually happens to that person?

A practical place to start

The decision test. Take your three most difficult decisions from the last six months. For each one, ask: did our stated values help us make that decision? Were they even in the room? If the answer is no, the values are aspirational — which is fine, but it means you are running on a different operating system than you think. Naming that gap honestly is more useful than adding a new value to the list.

---

Real Accountability

The tools work when the relationships underneath them work

Wickman's EOS tools — the scorecard, rocks, L10 meetings, the issues list — are well designed. The scorecard gives a weekly pulse on the business. Rocks set 90-day priorities. The L10 provides a disciplined rhythm. The issues list surfaces problems so they can be solved, not just discussed.

They work when there is enough trust in the room to actually tell the truth. They become theatre when they do not.

A conflict-averse team produces a scorecard full of greens nobody believes. A team where one person dominates produces rocks that reflect their priorities, quietly framed as the company's. An issues list that recycles the same three items every week is not a tool problem. It is telling you something about what the team cannot yet say to each other.

When the framework stops working, most people's instinct is to fix the framework. My instinct is to look at what is happening between the people using it.

A practical place to start

The red question. In your next scorecard review, pick one number that is green — and ask: if this were actually red, what would it be telling us? Not as a challenge to the person who owns it. As genuine collective curiosity. You will learn more from that question than from three months of accurate reporting. The scorecard is not just a dashboard. It is a mirror. The question is whether you are willing to look in it.

---

"Every framework works when the people using it have done enough inner work to use it honestly. Most companies invest in the framework. Fewer invest in the people holding it."

---

Questions to Sit With

• What version of yourself built this company — and is that still the right version for the next stage?

• What are you still doing that you know, honestly, should have been delegated six months ago? What is actually stopping you?

• What is the founding team conversation everyone knows needs to happen — and keeps not happening?

• When your stated values and a commercial decision collide, which one tends to win — and is that what you want?

• If your tools stopped working tomorrow — the scorecard, the rocks, the L10 — where would you look first?

• What would be different about how you lead if you had genuine support for the work the books don't cover?

---

Each section of this post deserves its own conversation — and probably its own post. Identity. Founding team dynamics. Values and vision. Accountability and trust. I will be writing about each of them separately. If one of them resonated, it might be worth knowing which one — and why.

If something in here landed — I would love to talk. Not a pitch. Just a proper conversation about what is actually going on.

calendly.com/katrin-kbccoaching/time-to-connect