Why your team performs like employees (and how to coach them to think like CoFounders)

Your team performs like employees because you built a job that rewards employee thinking. That stings, and it should, because it also means you can fix it. You can coach your team to think like owners, and you do it the same way you build any skill: reps, feedback, and a standard everyone can see. Not a speech at the offsite. Not an equity grant and a hope. A coaching practice, run weekly, by you.

I call people who think this way CoFounders. Not a job title. A way of operating. A CoFounder sees a problem and owns it to the end. An employee sees a problem and reports it. Same talent. Same intentions. Completely different company.

Nobody washes a rental car. If your team treats the business like a rental, the first question is not "what's wrong with them?" It's "what have I done that makes it feel rented?"

You hired owners. Then you trained them to be employees.

Think back to the interviews. You hired smart, hungry people. In week one they brought you ideas. In week six they brought you questions. By month six they brought you problems and waited.

What happened in between is you. Every time someone brought you a decision and you made it for them, you taught them a lesson: decisions live with the founder. You were faster, so it felt efficient. You were usually right, so it felt safe. And every single time, you collected a little more of the thinking that should have stayed with them.

Gallup's global workplace research has tracked this for years: only around a quarter of employees are truly engaged at work. Most people are not lazy. They are switched off, and people switch off when nothing is truly theirs. Ownership is not a personality trait you hire for and hope. It is a behaviour that grows where decisions, information and stakes actually live with the person.

Culture is what people do when you're not in the room. If what they do is wait for you to get back, you don't have a culture problem. You have an ownership problem, and it started at your desk.

What "think like an owner" actually means

Cut through the poster version. An owner does three things an employee doesn't.

First, they make decisions instead of escalating them. Second, they act on the outcome, not the task. "I sent the proposal" is a task. "The client hasn't signed, so I called them" is an outcome. Third, they volunteer the bad news early, because they care about the result more than about looking good this week.

None of those need equity. All of them need three conditions: real decisions to make, the information to make them well, and the safety to get some of them wrong. Most founders offer none of the three, then wonder why the team plays it safe.

How to coach your team to think like owners

This is a coaching job, not an announcing job. You cannot tell people to think like owners. You have to hand them the thinking, over and over, until it is theirs. Four moves, all learnable. I've spent 10,000+ hours in coaching rooms watching what actually shifts behaviour, and it is these, run consistently, not any of them run once.

Move one: answer questions with questions

The next time someone brings you a decision, don't make it. Ask: "What would you do?" Then be quiet.

The first few times, they'll be thrown. They came for an answer and got a mirror. Hold the silence. Nine times out of ten the answer they give you is the one you'd have given, and now it's theirs. If it's not quite right, don't correct it. Ask another question: "What happens to the customer if we do that?" Let them find the gap themselves. A conclusion someone reaches in their own head beats an instruction from yours every time, because they'll defend it, refine it, and repeat it when you're not there.

This will feel slow. It is slow, for about a month. Then it compounds, because every decision they learn to make is a decision that never hits your desk again.

Move two: teach one-way and two-way doors

Owners take risks. Employees avoid them. The difference is usually not courage, it's that nobody has given the team a way to size a risk.

Jeff Bezos gave Amazon one in his 2015 letter to shareholders: one-way doors and two-way doors. A one-way door is a decision you can't walk back. Signing a three-year lease. Firing someone. A two-way door swings both ways: if it doesn't work, you walk back through and try something else. Changing the onboarding email. Testing a price on ten customers.

Hand this to your team and set the rule: two-way doors, you decide and tell me after. One-way doors, we decide together. Suddenly "am I allowed to?" has an answer they can work out themselves. Most decisions in a company of 15 to 60 people are two-way doors being treated like one-way doors, which is exactly why everything queues at the founder.

Move three: give them the real numbers

You cannot think like an owner about a business you can't see. If your team doesn't know the revenue number, the runway, the margin on what they build, then asking them to act like owners is asking them to drive with the windscreen painted over.

Founders hold numbers back to protect people, or to protect themselves. Both instincts cost you. The team already senses when things are tight. What they lack is the detail that would let them do something useful about it. Share the number that their work actually moves, every week, and watch the questions change. "What do you want me to do?" becomes "if we lift onboarding completion, that renewal number moves, right?" That sentence is an owner talking.

This is also where a North Star earns its keep. A North Star is the one thing the whole team is trying to move, named plainly, so anyone can test their own call against it without asking you. It becomes the barometer in the room: "Does this get us closer or not?" The full version is in The North Star Protocol.

If you want help installing this in your own team, Book a Discovery Call.

Move four: make bad news cheap and hiding it expensive

Owners surface problems early. But nobody volunteers bad news to a founder who flinches. If your last three reactions to a miss were sighs, silences or a quiet takeover of the project, your team has learned the real rule: only bring the founder good news.

Watch yourself in the next miss. Your first sentence decides whether you get the truth early next time. "What do we know, and what do we do now?" keeps them in the problem as its owner. "How did this happen?" puts them in the dock, and people in the dock defend, they don't own. Amy Edmondson's research on psychological safety, explained well by Harvard Business Review, has shown for decades that teams who can speak up about mistakes learn faster and perform better. This is that finding, applied at the exact moment it's hardest: when the miss is yours to react to.

Clear is kind. Hold the standard hard, and hold the person safe. Those are not opposites. They are the whole job.

The part most founders skip: hold the standard

Coaching without a standard turns into cheerleading, and cheerleading changes nothing. Ownership has to be inspected, warmly and relentlessly.

The mechanics are simple. When someone commits to an outcome, write it down where both of you can see it. Next week, ask about it. Not as a report card, as a real question: "Where did you land on the pricing test?" If it moved, name the win out loud. If it didn't, get curious before you get direct: "What got in the way?" Once is life. Twice is a pattern, and a pattern gets a straighter conversation.

Here's a composite of a founder I've coached, details changed. Ops lead, genuinely capable, escalating everything. The founder's old pattern: answer fast, feel useful, complain to me about the bottleneck. The new pattern took one question, asked with a straight face: "If I was on a plane with no wifi for two weeks, what would you do?" The ops lead laid out a complete plan in about ninety seconds. It had been in there the whole time. The founder just said "do that, and next time skip the part where you ask me." Six months later that ops lead was running a function, and the founder had his Thursdays back. The capability was never missing. The permission was.

The full engagement structure, cadence, accountability and all, is in The Coaching Standard: How to Turn Your Team Into CoFounders. And if the deeper issue is that the whole company still routes through you, start with The Founder-to-Leader Transition: How to Build a Team That Runs Without You, because coaching a team to own things only works if you're genuinely willing to let go of them.

What to expect when it starts working

The first month feels worse. Decisions slow down. People make calls you'd have made differently, and some of them are wrong. This is the moment most founders quit and take the wheel back, and taking it back once undoes months of coaching, because the team learns the ownership was on loan.

Hold on through that dip and the shape of your weeks changes. Fewer questions, more updates. Problems arrive with proposed answers stapled to them. Someone challenges one of your calls with the North Star as their argument, and it's a better argument than yours. The first time that happens it stings for about four seconds, and then you realise it's the whole point.

That's antifragility in a team. Not a team that survives without you. A team that gets sharper every time something breaks, because the people closest to the break own the fix.

Start this week

Pick one person. Not the whole team, one person with the most obvious gap between what they're capable of and what they currently own. This week, refuse to answer their next escalation. Ask what they'd do. Teach them the two doors. Show them one real number. Then hold the standard next week, and the week after.

You built the company by owning everything. You'll scale it by coaching everyone else to. If you want a partner in the room while you make that shift, Book a Discovery Call.