The Coaching Standard: How to Turn Your Team Into CoFounders

Most founders think they have a delegation problem. They don't. They have a coaching problem. Delegation hands someone a task. Coaching builds someone who no longer needs the task handed to them. If you want to know how to coach your team, start with an uncomfortable admission: the way you're helping them right now is probably the thing keeping them small.

You built the company by being the best person in the room. Best at the product, best at the sales call, best at the hard decision at midnight. That mastery got you here. Past about 15 people, it starts working against you. Every answer you give trains your team to come back for the next one. You become the most expensive answer machine in the building.

There is another way to run a team. I've spent 18 years and more than 10,000 coaching hours watching what happens when leaders learn it. This piece is the strategic case for it. The full method lives in The Coaching Standard, free in the Source Code library.

How to coach your team: the short answer

Coaching your team means replacing answers with questions, opinions with feedback contracts, and vague expectations with accountability that has teeth. You stop being the person who solves problems and become the person who builds problem-solvers. The goal is a team of CoFounders: people who think and act like owners, not employees.

That's the whole move, compressed. The rest of this piece is why it's worth doing, what actually changes when you do it, and where to start. Because the summary sounds simple and the practice is not. Asking a question when you already know the answer feels slower, riskier and less satisfying than just telling someone what to do. It is slower. For about six weeks. Then it starts compounding, and it never stops.

The answer machine is the bottleneck

Picture a founder I've seen a hundred times, in a hundred versions. Call him the composite. Thirty-eight people in the company. He's brilliant, generous, fast. His calendar is a wall of 30-minute blocks and every one of them is someone bringing him a decision. Pricing question. Hiring question. Should we push the release. He answers all of them, well, and goes home proud of how much he helped.

Six months later his head of product resigns. In the exit conversation she says something that lands like a punch: "I never got to make a real decision. You always had a better answer."

He wasn't hoarding power. He was being helpful. That's what makes this pattern so hard to see. Every time you give a great answer, two things happen. The immediate problem gets solved, which feels good. And the person learns that the fastest route to a solved problem runs through your office, which is quietly catastrophic. You are training your best people to outsource their judgment to you. The better your answers, the faster they learn it.

Run that forward three years. The company has doubled, your judgment hasn't, and every decision still queues for your attention. Growth doesn't free you. It buries you. The business becomes a single point of failure with your name on it.

The fix is not "delegate more." Delegation without development just moves tasks onto people who haven't been built up to carry them, and when they wobble, you grab the wheel back and confirm everyone's suspicion that the real decisions live with you. The fix is learning how to coach your team so the judgment itself transfers. Not the task. The thinking.

What a CoFounder actually is

I use the word CoFounder deliberately, one word, capital C, capital F. Not a job title and not equity. A way of operating.

A CoFounder is someone who treats the company's problems as their problems. They don't bring you issues, they bring you options with a recommendation attached. They make the call inside their lane without checking, and they tell you afterwards what they decided and why. When something breaks on a weekend, they don't wait for Monday's meeting to mention it. When they disagree with you, they say so in the room instead of in the corridor afterwards.

You cannot hire this off the shelf. I've watched founders try, paying top of market for senior people and then wondering why the ownership mindset didn't arrive with the laptop. Ownership isn't a trait people carry between companies like a skill. It's a response to the environment they're standing in. Put an owner-minded person into a company where the founder answers everything, and within a quarter they're queueing outside the office like everyone else. Put an average performer into a team where judgment is expected, coached and backed, and they grow into the expectation more often than you'd believe.

Culture is what people do when you're not in the room. A team of employees does what you told them. A team of CoFounders does what you would have wanted, and sometimes something better, because they were closer to the problem than you were. The distance between those two teams is not talent. It's coaching.

Why coaching your team is the highest-return work you can do

Herminia Ibarra and Anne Scoular made the case in Harvard Business Review that the leader-as-coach is now a core requirement of the job, not a nice-to-have. The command-and-answer model of management was built for work that was predictable and repeatable. Yours isn't. In a startup, the person closest to the customer usually knows something you don't, and a leadership model where information flows up and answers flow down wastes most of what your team knows.

But the strategic case goes past efficiency. It's about what kind of company you're building under pressure.

Nassim Taleb drew the distinction in Antifragile: fragile things break under stress, robust things withstand it, and antifragile things get stronger because of it. Most founders build fragile companies without realising it, because fragility looks like strength while conditions are good. The founder-dependent company runs beautifully until the founder is sick, fundraising, burnt out or just wrong. Then every deferred decision, every underdeveloped leader, every "I'll just handle it myself" comes due at once.

A coached team is antifragile. Every hard problem that lands on it makes it stronger, because the problem becomes a rep. Someone stretched. Someone made a call under pressure and reviewed it honestly afterwards. Someone got feedback that stung and used it. The team that has been coached through fifty hard calls handles the fifty-first without you. Chaos stops being a threat to the business and starts being the training programme.

Here's the maths that should get your attention. If you coach one leader from "brings me problems" to "brings me decisions," you haven't saved an hour a week. You've removed yourself from an entire category of the company's future problems. Do that with five leaders and you've changed what the business is. Pound for pound, nothing else on your calendar returns like it.

If you want help building this into your leadership, that's exactly the work I do with founders. Book a Discovery Call.

The three shifts that turn a manager into a coach

Knowing coaching matters and knowing how to coach your team are different things. Every leader I've worked with who made the shift did three things differently. Not ten. Three.

Shift one: ask before you tell

When someone brings you a problem, your answer is sitting right there, loaded. Don't fire it. Ask instead: "What do you think we should do?" Then the harder one: "What's stopping you from doing it?"

The first few times, expect a blank look. Your team has been trained by every manager they've ever had, including you, to expect the answer. Hold the silence. When they offer something, work with what they offered, even if your version is 20 per cent better. Their 80 per cent solution that they own and execute beats your 100 per cent solution that they carry out on your behalf, because theirs comes with judgment attached and yours comes with dependence attached.

You don't need to do this with everything. Some decisions are one-way doors, the kind you can't walk back, and those deserve your direct involvement. Most decisions are two-way doors. You can walk back through them if they turn out wrong. Jeff Bezos built this distinction into how Amazon operates: treat reversible decisions lightly and move fast, save the heavyweight process for the irreversible ones. Two-way doors are your coaching ground. Let people make those calls, let some of them be wrong, and review the thinking rather than grabbing the wheel.

Shift two: put a feedback contract in place

Most teams run on vague, occasional, sugar-coated feedback, which means most people are navigating their own performance blind. Coaching runs on the opposite: a standing agreement that truth flows in both directions, regularly, without anyone needing to build up courage first.

This only works on a foundation of safety. Amy Edmondson's research on psychological safety at Harvard has shown for over two decades that teams learn and perform better when people can speak up without fear of humiliation. Not comfort. Safety. The distinction matters, because a feedback culture without safety is just a licence for the loudest person, and safety without feedback is just a pleasant place to stagnate.

Trust like that isn't built in an offsite. It's built in tiny, repeated moments: you said you'd do the thing and you did it, you asked for their view and actually used it, you admitted you got one wrong. Small deposits, made consistently. If you want the mechanics, The Micro-Trust Protocol covers the deposits, and The Effective Feedback Protocol covers how to deliver truth so it lands as investment rather than attack. Start with a simple habit: after any significant piece of work, ask "What worked? What would you do differently?" and answer the same questions about yourself, out loud, first. You go first because the leader's vulnerability sets the ceiling for everyone else's.

Shift three: accountability with teeth

The near enemy of coaching is a nice chat. In Buddhist teaching, the near enemy is the counterfeit that looks like the real thing, which makes it more dangerous than the obvious opposite. The far enemy of coaching is command and control. Easy to spot, easy to avoid. The near enemy is the warm, supportive one-on-one where everyone feels heard and nothing changes. It photographs exactly like coaching. It produces nothing.

What separates real coaching from the counterfeit is accountability. Commitments get made specifically, written down, and reviewed next session. When a commitment gets missed once, you diagnose the system together: was the commitment too big, the priority wrong, the week genuinely mad? When it gets missed repeatedly, you have the direct conversation about what's actually in the way. No shame in it. But no pretending, either. A standard that carries no consequence for being missed isn't a standard. It's a suggestion with good branding.

Your team will test this. Not because they're difficult, but because every team calibrates to what actually gets followed up versus what merely gets said. Hold the line early and the line becomes culture.

Above the line: the check before every coaching conversation

One more tool, because it decides whether everything above works or wastes an hour.

At any moment, you're either above the line or below it. Above the line means open, curious, committed to learning. Below the line means closed, defensive, committed to being right. The frame comes from The 15 Commitments of Conscious Leadership, and it's the first thing I check in any coaching conversation, starting with myself.

Everyday example: your head of sales tells you the new pricing you designed is confusing customers. Below the line, you defend the pricing, cite the three customers who liked it, and the conversation dies right there. Above the line, you get curious: "Tell me what they're saying. What are we missing?" Same information, opposite outcome. And your team learns from which version of you shows up far more than from anything you say about openness.

You cannot coach from below the line, and you cannot coach someone who's below it either. When either of you drops, and you will, the move is to name it and reset, not to push through. The full diagnostic is in The Location of Leadership. Most leaders I work with find that the label alone changes things. What used to be "I was stressed" becomes "I was below the line, and here's what pulled me there." Once you can name it, you can move.

Where to start this week

Don't announce a coaching transformation. Announcements are how initiatives die politely. Start small and let the results do the announcing.

This week. Pick your three most frequent answer-seekers. Next time each of them brings you a problem, ask "What do you think we should do?" before you offer anything. That's it. One question, three people.

This month. Choose one direct report with obvious potential and start coaching them properly: a regular session, real commitments, real review, both of the questions after significant work. One person done well beats a team-wide rollout done thinly, and the change in that one person becomes your proof.

This quarter. Adopt the full standard. The Coaching Standard is the complete protocol, published free: the mental models underneath it, the feedback contract, the deep work standard, the accountability clause, all of it. Take it, run it, adapt it. It's built to be used without me.

A steer on order: don't lead with the accountability clause. Teeth without trust reads as threat. Build the trust deposits and the feedback habit first, then introduce the standard. Trust is built going up the stairs. It comes down in a lift.

And expect the wobble. Around week three, coaching will feel slower than answering, because it is. Someone will make a call you'd have made differently. The pull to grab the wheel back will be enormous. That moment is the whole game. Grab it and you've taught the team the coaching was theatre. Hold, review the thinking together, and you've taught them the judgment is genuinely theirs now. Teams remember which one you did.

The team that coaches itself

Something happens a few months into this that nobody expects. The questions start travelling without you.

You overhear your head of ops asking a junior "What do you think we should do?" instead of dishing out the answer. Two of your leads run a what-worked review on a launch you weren't part of. Someone names "I think we're below the line" in a heated meeting and the room actually resets. The standard you practised has become the standard they practise on each other, and on the people they lead.

That's the real destination. Not a founder who coaches well, but a company where coaching is how leadership works at every level. Where the biggest breakthroughs don't need you in the room, because the thinking you used to be the sole supplier of is now the water everyone swims in. A company like that doesn't just survive your absence. It gets stronger under pressure, with or without you. That's antifragility, built one question at a time.

You built the company by being the best in the room. You'll scale it by building a room full of people who don't need you to be.

If you want a partner in that work, this is what I do. Eighteen years, more than a thousand founders and leaders, and a standard that's published free so you can hold me to it. Book a Discovery Call.