Why leadership teams of fixers struggle to own growth

Most leadership teams we meet are full of capable people. They're the ones who got promoted because they could fix things: the late shipment, the unhappy client, the broken process, the key hire who quit. Put them in a room with an Issues List and they'll work it down.

That's a real strength. It's also why growth can stall in companies that run on EOS® well.

Growth doesn't show up as an issue

Problems announce themselves. A client complains, a number turns red, someone raises a hand. Growth is quieter. It shows up as revenue that's a little behind plan, month after month, never bad enough to feel urgent. Fixers respond to what's broken, and nothing looks broken.

The weekly rhythm favors this week

The weekly meeting is designed to keep the business running: Scorecard, Rock updates, headlines, then the Issues List. It does that very well. But the questions that drive growth, like which customers to pursue or what to stop doing, take longer to answer than one meeting allows. They're easy to push to next week.

Growth has no natural owner in the weekly rhythm. That's not anyone's failure. It's a gap in how the time gets spent.

Rocks get picked from problems

At the quarterly, Rocks often come from the Issues List: things that are broken and need more than a week. Those Rocks are worthwhile, and finishing them makes the business better. But if every Rock fixes something, none of them is aimed at the gap to plan.

What helps

Make the gap visible

Fixers act on what they can see. Put actuals against the Growth Plan in front of the team every month, with the gap in dollars. A gap that's visible becomes an issue, and fixers know what to do with issues.

Give each driver an owner

Break the plan into a few drivers and assign each to one person. Now growth has owners, the same way every Scorecard number does.

Pick at least one Rock from the gap

Before choosing Rocks, ask: if we finish all of these, will we be on plan? If not, add one that moves a driver.

Protect time for the long questions

Set aside part of a monthly review for one growth question at a time. Not every week, but every month.

None of this changes how EOS works. It points the strengths your team already has at the plan. To see where your team leans, take the self-assessment in Built to Fix, Not to Grow.