Scaling Selves

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 was not 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, becoming a coach, watching the same patterns surface in my own leadership - that I understood what was actually going on. The view keeps sharpening still. My husband runs his own business, so I see it there too - close up, in someone whose thinking I know well. You stop being theoretical about something when you are genuinely living inside it.

That is the gap this post is about.

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. Not a deep philosophical detour. Just enough honesty, enough trust, and enough willingness to look at what is actually happening.

Here is what that looks like in practice. In coaching I work with leaders to set goals and action points. When those goals are not achieved - and sometimes they are not - the useful question is never simply why did you not do it. It is: what actually got in the way? Was this the right goal, or did it sound right when we set it? Did we stretch further than the current conditions allowed? Has something shifted and made this goal less relevant than it was? That process of honestly examining what happened - without judgement, with real curiosity - is the inner work made practical. It is what allows the next set of goals to actually land rather than just look good on a page.

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.

I want to explore what they open up. Not to critique the books - to name the gap they share.

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 made a similar point in The E-Myth. Most people start a business because they are exceptional at a craft, not because they set out to build and run an organisation. That same brilliance is precisely what makes the next stage hard - the skill that built the company is not automatically the skill that scales it.

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 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 have not 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. It is one of the most quoted principles in business. And it is right.

What it does not prepare you for is the specific problem of the founding team. The people who were exactly right at ten people are not always the right people at a hundred. Not because they are not talented. Because the company has moved into a stage that requires different things. Reid Hoffman is direct about this in Blitzscaling: the skills that make someone exceptional in chaos - the tolerance for ambiguity, the personal heroics, the ability to hold fifteen things at once without a system - can actively get in the way once the company needs structure and scale. This is not a failure of the individual. It is a law of growth.

Most founding teams contain both types, mixed together. It worked brilliantly early. The friction comes later. And nobody thought to have a conversation about it before the friction arrived.

This is one of the most common dynamics in any scaling company - and one of the least talked about.

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.

I think values work is some of the most important work a leadership team can do. But most values exercises are designed to produce a deliverable - when what they should produce is a conversation.

There is also a step most teams skip entirely: not just agreeing on the words, but agreeing on what those words actually mean in practice. Integrity meaning we do what we say we will do is not the same as integrity meaning we will never make a commercial decision we could not explain publicly. Both sound like integrity. They produce very different decisions under pressure. The work of defining what a value actually means - specifically enough to use it in a hard moment - is unglamorous and takes longer than anyone wants. It is also what separates a values framework that governs real decisions from one that sits on a slide deck.

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 telling you something about what the team cannot yet say to each other.

I ran OKR training for a while. John Doerr's Measure What Matters is a genuinely good book - the framework is clean, the case studies are compelling, the logic holds. And I watched the same thing happen. A team that could not be honest with each other about progress would set ambitious objectives and then quietly adjust the key results as the quarter went on. Not dishonestly exactly. Just carefully. The tool was fine. The conditions for using it honestly were not.

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.

The conversation that has been postponed for eight months. The co-founder relationship fraying at the edges. The executive everyone knows is not performing, but whom nobody has spoken to directly. These are the real issues. Almost always more resolvable than the team has convinced itself they are.

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.

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 do not 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.

One more thing: I put together a cheat sheet covering all the frameworks and tools from the books mentioned here - the key ideas, what each one gives you, and where the gaps are. The kind of reference you actually want open on your desk when you are working with a leadership team or thinking through a growth stage. Message me and I will share it.

A Few Sources That Shaped This Thinking

Gino Wickman - Traction (2011) and Rocket Fuel with Mark C. Winters (2015)

Verne Harnish - Scaling Up (2014)

Alisa Cohn - From Startup to Grown-Up (2022)

Andy Grove - High Output Management (1983)

Jim Collins - Good to Great (2001)

Ben Horowitz - The Hard Thing About Hard Things (2014)

Michael Gerber - The E-Myth Revisited (1995)

Reid Hoffman and Chris Yeh - Blitzscaling (2018)

John Doerr - Measure What Matters (2018)

Work With Me

I work with founders, C-suite executives, and leadership teams in finance, technology, and growth-stage businesses who are navigating exactly what this post describes - the identity shift, the founding team conversation, the values that need to actually mean something, the accountability that keeps quietly breaking down.

If you recognised your team in any of this - or you are the leader who knows something needs to shift but has not yet found the space to work through it properly - I would like to hear what is going on for you. No pitch. A proper conversation, and we will both know quickly whether it is useful to continue.

calendly.com/katrin-7/time-to-connect-3