Founder dependency

Why your leadership team still looks to you.

A leadership team stays in name only when senior hires get titles without authority, the leadership meeting exists to update the founder and every leader’s main relationship is with the founder rather than each other. It becomes a real team when its members own decisions, run the meeting and sort things out between themselves.

By Simon Wakeman, Principal Consultant & Fractional COO
· 5 minute read

Your head of operations has been in post for six months. Your finance lead, a year. The commercial director came highly recommended. On paper you have a leadership team. Yet the Monday meeting still ends with everyone looking at you.

This is one of the most common forms of founder dependency. What you have is a set of capable direct reports, each with a strong line to you and a weak line to each other. A team in more than name looks different on three counts. They are what each leader was given when they started, how the leadership meeting runs and who the leaders turn to when something cuts across their areas.

What was your senior hire actually given when they started?

Think back to the first fortnight. There was probably a warm welcome, an introduction to the team, a handover of tasks and a general sense that they’d “own” their area. What there almost certainly wasn’t was a written list of the decisions that were now theirs.

That gap matters more than any other part of onboarding. A new leader who doesn’t know whether they can change pricing on a renewal, restructure their team or say no to a client will ask. Asking is the sensible move for someone new, and within a few weeks it becomes their habit.

A useful first-month pack for any senior hire covers three things:

  • The decisions they own outright, written down and shared with the rest of the leadership team.
  • The outcomes they’re accountable for, with one owner per outcome.
  • The peers they depend on, and what each needs from the other.

On that second point, Simon Wakeman makes a distinction in his Build newsletter that’s worth holding onto: accountability can be nested but not shared. A leader can break an outcome down and have others own the parts, but two directors “jointly owning” something usually means nobody owns it – and it drifts back to you.

How does your leadership meeting actually run?

Look at the last three agendas. If most items are someone reporting what happened while everyone waits for your reaction, you’re running a briefing session for the founder, not a leadership meeting.

The shape of the meeting teaches people what the team is for. A meeting built around updates tells leaders their job is to keep you informed. A meeting built around decisions tells them their job is to lead.

Three changes make a big difference:

  1. Move updates out of the room. Written, short and read beforehand.
  2. Let the owner run their item. The leader who owns a decision frames it, hears views and makes the call. You’re one voice, not the closing one.
  3. Put cross-team problems at the top. These are the issues no single leader can solve alone, and they’re where a team earns its keep.

It also helps if someone other than you chairs. It sounds cosmetic. In practice it changes who people look at when there’s a pause.

Who do your leaders look to when something crosses their area?

Watch what happens when sales and delivery disagree about a handover, or operations and finance clash on a hire. In a team in name only, both leaders bring it to you separately. You hear two versions, make the call and the leaders never have to work it out together.

That’s the hub-and-spoke pattern: each leader has a line to the founder and almost none to each other. It’s the natural result of hiring people one at a time into roles that report to you. As Simon puts it, the result is usually all gaps and overlaps – two directors both think they own something, and nobody thinks they own the bit in between.

The shift you want is from spokes to a web. When a cross-team issue reaches you, send it back with a question: “Have you two talked about this?” Then expect them to bring you a joint proposal, or better still a decision.

Why does a team need time to become a team?

Because trust between leaders grows through decisions they’ve made together and lived with. A group of people who meet weekly to update the founder never builds it.

Expect it to feel slower for a while. Leaders who are used to taking things to you will find it awkward to negotiate with each other. Some decisions will take longer. A few will land differently from how you’d have made them. That’s the cost of building something that doesn’t need you in the middle.

How do you check it’s working with a new hire?

Not just by asking them. Simon’s view, from hiring a senior person who interviewed brilliantly and then lost two of his team within four months, is that the interview can’t tell you how someone actually leads. Build a real check at around three months: a proper conversation with two or three of the people now reporting to the new leader, before they’ve learnt what to say and what to keep quiet. It tells you far more about whether the leader has taken hold than a probation tick-box ever will.

What to try at your next leadership meeting

These are all about the team, not the individual leaders:

  1. Tally the last three agendas. Mark each item as update, discussion or decision, and note who made each decision. If most are yours, you’ve found the pattern.
  2. Ask someone else to chair. Rotate it monthly.
  3. Publish each leader’s decision list to the whole team. Everyone should know who owns what, including what you’ve kept.
  4. Bounce one cross-team issue back. Next time two leaders bring you the same problem separately, ask them to come back together with a proposal.
  5. Book the three-month conversation. For your most recent senior hire, arrange a check with their direct reports now.

If the decisions themselves still feel hard to hand over, delegation that hands over decisions rather than permission covers how.

Where does Mallard fit in?

Often the hardest part is seeing the pattern from inside it. You see capable people being cautious. Your leaders see a founder who still has the final word. Both are right, and neither can fix it alone.

Mallard’s half day Reflect workshop brings you and your leadership team together, up to eight people, to build your own shared view of what’s holding the business back. It’s often the first time the team has worked on a problem as a team rather than as a set of reports to the founder.

Some commonly asked questions from founders…

Why does my leadership team still bring every decision to me?

Usually because each leader was hired into a relationship with the founder rather than into a team. Without a clear list of decisions they own, a meeting where they decide things together and the habit of resolving issues with each other, the founder remains the hub every decision passes through.

What should a new senior hire be given in their first month?

A senior hire needs a short written list of the decisions that are now theirs, the outcomes they’re accountable for and the people they need to work with to get things done. A handover of tasks and a warm welcome aren’t enough. Without named decisions, a new leader’s safest move is to check with the founder.

How should a leadership team meeting run?

A leadership meeting works best when most of its time goes on decisions and cross-team problems rather than updates to the founder. Updates can be written and read beforehand. The leader who owns an item should run that part of the meeting, with the founder as one voice rather than the final word.

How do I know if my leadership team is in name only?

Watch who people look at when a decision is needed. If leadership meetings are mostly updates for the founder, if leaders take cross-team problems to the founder rather than to each other, or if decisions get revisited once the founder hears about them, the team has titles without authority.

Can two leaders share accountability for one outcome?

Not really. One outcome needs one owner. A leader can break their outcome into parts and have others own those parts, but splitting the top-level accountability between two people usually means neither of them truly holds it, and the founder ends up holding it by default.

How can Mallard help a founder build a real leadership team?

Mallard’s half day Reflect workshop brings the founder and leadership team together, up to eight people, to build a shared view of what’s holding the business back. For a deeper picture, the 14 day Find diagnostic looks at 262 operational data points across people, practices and technology.

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call