How to Optimize Team Performance in a Founder-Led Business

Most founders think they have a hiring problem.

They don't.

A founder at $8.5 million ARR came to us convinced his business had a sales problem. Sales was stuck. Operations was drowning. Every meeting felt like the team was moving through mud. His instinct: hire more people.

After a two-week audit, the team ran a different play. They moved a high-initiative problem-solver into fixing inventory forecasting. Shifted their two best sellers off weak product lines. Exited one consistent blocker.

Forty-five days later: sales cycle time down 38%, close rate up 26%, and the founder got his Fridays back.

Same team. Better seats.

That's what figuring out how to optimize team performance actually looks like in a small business. A clearer picture of who's multiplying value and who's draining it, then acting on what you find.

To optimize team performance in a founder-led business, score every team member on Impact (1-5) and Energy (-2 to +2), classify them as Builders, Stabilizers, or Blockers, and make role decisions based on net contribution, not activity, tenure, or gut feel. The ROE scan takes about 60 minutes. What you do with it takes longer.

How to optimize team performance: why it starts with seats, not headcount

There's a pattern in founder-led businesses that shows up around $1 million to $5 million in revenue.

The founder has built something real. The team is larger than it was. Revenue is growing, or was growing, until it hit something. And the first instinct when growth slows: hire more.

Sometimes that's right. Often it isn't.

What's more common is that growth has outrun the formation. Your best initiative-takers are buried in work a lower-energy person could handle. Your reliable executors are working with ambiguous priorities because no one has documented the process. Somewhere in the mix, there's at least one person generating motion without progress.

Gallup's 2023 research puts numbers to it: only 23% of employees are actively engaged at work. The cost of disengagement to the global economy is $8.8 trillion annually. For a 12-person team, that's not abstract. That's two or three people showing up every day and doing roughly enough to not get fired.

The fix isn't always an exit. Sometimes it's a re-seat. Sometimes it's a process change that gives a capable person the clarity they've been missing for months. You can't make those moves without an honest picture of what you're actually working with.

The ROE scan provides that picture.

What militaries have known about team classification for decades

Before the scoring system, consider what German General Kurt von Hammerstein-Equord figured out nearly a century ago.

He classified officers on two axes: clever versus stupid, industrious versus lazy.

The clever and industrious make excellent staff officers. Reliable, detail-oriented, capable of executing complex tasks when given clear inputs.

The clever and lazy make the best commanders. They find the most efficient path to the objective, delegate everything they can, and don't waste energy on motion that doesn't generate progress. Strategic leadership runs on that instinct.

The stupid and lazy are functional in routine duties. They follow instructions, don't cause problems.

The stupid and industrious are dangerous. Energy without judgment doesn't underperform quietly. It causes collateral damage. They sprint in the wrong direction and often take part of the team with them.

Business owners have all four types on their roster. The question is whether you know which is which, and whether each person is matched to a role that fits them.

Hammerstein's framework isn't meant to be cruel. It's meant to be honest. Honesty is what good personnel decisions require.

The three types on every team: Builders, Stabilizers, and Blockers

Every team has three types of people. Which category someone falls into depends on two things: what they deliver, and how they affect the people around them while delivering it.

Builders: your growth engine

Builders take initiative without being asked. They spot problems before anyone else sees them and propose solutions before you've finished describing the issue. They think in outcomes, not tasks.

Give a Builder a well-defined problem and the authority to solve it. That's their environment. They don't need oversight. They need a mandate and the confidence that you'll back them up when they make a call.

The mistake founders make with Builders: keeping them in comfortable, familiar work because they're good at it. A Builder who's mastered their current role is coasting. And a Builder who's coasting is eventually leaving.

If you have Builders doing Stabilizer work, restructure before you wonder why your best people are looking elsewhere.

Stabilizers: your operational backbone

Stabilizers keep the trains running.

They aren't generating the breakthrough ideas. They're making sure the breakthrough ideas ship on time, in full, without errors. That's a different kind of value, and it's one founders underestimate until a Stabilizer leaves.

Stabilizers need clear inputs and a consistent rhythm. Give them documented processes, measurable outputs, and visibility into how their work connects to company goals. When they have that, they're among the most reliable people on your team.

When they don't have it, they look like underperformers. Often, they're not. They're working with incomplete information in an environment that was never designed for them.

This is where documentation compounds. A good AI SOP generator or a properly maintained process library isn't overhead. It's what lets your Stabilizers operate at full capacity instead of filling in gaps with guesswork.

Blockers: the drag you're probably not measuring

Blockers create drag. Not always loudly.

Sometimes a Blocker looks productive. High meeting attendance, lots of visible activity, opinions about everything. But the output doesn't match the energy spent. Decisions that should take a day take a week. Your best people start routing around them.

Blockers typically resist change because change threatens their position. Their value is often built around institutional knowledge that was never documented, which makes them feel necessary even when their net contribution is negative.

Track how the team performs when this person is and isn't in the room. That data is usually available. Founders usually haven't looked at it through that lens.

The ROE scoring method

ROE stands for Return on Energy. It measures what someone delivers against how they affect the people around them while delivering it.

Two dimensions:

Impact (I), scored 1 to 5. Shipped outcomes tied to revenue, margin, or risk reduction. What they delivered, in measurable terms.

• 1-2: Minimal or inconsistent output relative to their role

• 3: Meets expectations, reliable within defined scope

• 4-5: Exceeds expectations, drives results beyond their defined role

Energy (E), scored -2 to +2. How they affect the team's clarity, speed, and morale.

• +2: Elevates the people around them; the team moves faster when they're involved

• +1: Positive; they help more than they hinder

• 0: Neutral

• -1: Creates friction, confusion, or rework others have to manage

• -2: Actively damages team function; their involvement typically makes things harder

One case worth naming separately: high Impact, negative Energy. This is one of the most expensive configurations in a small business, because the output creates dependency while the presence taxes everyone around it. High individual contribution doesn't always mean net positive contribution. Run the full math before you protect someone from accountability.

How to run a 60-minute ROE scan

One hour. The roster. Honest answers to three questions per person.

Step 1: List everyone on the team.

Step 2: Score Impact (1-5) and Energy (-2 to +2) for each person. Anchor the score on these questions:

• What do they actually produce? Measure outcomes, not effort.

• How do others perform after working with them?

• Would you hire them again for their current seat?

Step 3: Tag each person as Builder, Stabilizer, or Blocker.

Step 4: Before you close the scan, document three things:

• Impact and Energy scores for everyone

• Role clarity gaps: any person whose score surprised you probably has a process or clarity problem worth investigating

• Your top three multipliers: the people currently generating the most forward momentum

The scan doesn't make the decisions. It gives you an honest picture to make decisions from. That's the hard part, because the picture will surface things you've been avoiding.

What to do with the results: the three-track response

Track 1: Builders, expand the mandate

Builders need more scope, not more oversight.

Look at your top two or three Builders and ask: what's the highest-value problem in this company right now that they could own? If they're not pointed at it, restructure before you hire anything.

Having the right people in the wrong seats is one of the most common and most expensive problems in founder-led businesses. The longer it continues, the more likely those people look elsewhere.

Autonomy isn't a perk for Builders. It's the working condition they require to perform.

Track 2: Stabilizers, build the environment they deserve

Stabilizers don't need inspiration. They need infrastructure.

Documented processes. Clear decision rights. Defined output metrics they can track themselves. Regular visibility into whether their work connects to what the company is trying to do.

When Stabilizers operate in a well-engineered environment, their performance is predictable in the best way. When they operate in chaos, they look like underperformers, and founders sometimes exit people who were never given the conditions to succeed.

A business operating system isn't just for the founder. It's the infrastructure that lets your Stabilizers run reliably at scale. That investment compounds.

Track 3: Blockers, coach, decide, and execute

The Blocker conversation is the one founders delay the longest.

The framework: 30 to 60 days of structured coaching with specific behavioral targets and defined success criteria.

Examples of what specific looks like:

• "In every meeting you attend, document and share your concerns within the meeting, not after it."

• "When you disagree with a decision, surface it in the relevant channel within 24 hours with a specific alternative."

• "Your assigned deliverable ships on the agreed date. If there's a blocker, raise it before the deadline, not on it."

Hold regular check-ins against these targets. Set a clear decision point in advance: if the targets aren't met by a specific date, the path changes.

If the behavior doesn't shift, let them go. Keeping a Blocker costs more than replacing one, in performance, in morale, and in the time your best people spend working around them.

Why small businesses get this wrong

Four patterns show up consistently.

Confusing activity with output. High meeting attendance and visible energy is not performance. What they deliver in measurable terms is performance.

Letting loyalty cloud the evaluation. The person you've known the longest and feel the strongest connection to is still subject to the same scoring. Personal relationships are real. They're not a performance metric.

Waiting for undeniable evidence before acting. By the time a Blocker's impact is undeniable to everyone, you've already paid the cost. The ROE scan gives you a leading indicator. Use it early.

Protecting high-Impact, negative-Energy people indefinitely. Set the behavioral expectation. Give them a defined window. If the Energy score doesn't move, the calculation changes.

The buy back your time conversation usually focuses on what the founder stops doing. This is the version about who the founder stops carrying.

FAQ

How often should I run a ROE scan?

Quarterly is a reasonable starting cadence. Also run it after any significant company change: a major hire, a key departure, a product pivot, or any period where the operating rhythm has felt off. Treat it like a quarterly financial review. The numbers only matter if you look at them regularly.

What do I do with someone who has high Impact but negative Energy?

Set specific behavioral expectations and a clear timeline, the same as any Blocker track. The difference is that the stakes are higher on both sides: their output is real, and so is the cost to the team around them. If the Energy doesn't shift after a coached window, be honest about the net calculation. Individual output isn't the whole ledger.

How do I have the Blocker conversation?

Be specific about behavior, not about the label. "You have a pattern of agreeing in meetings and then raising concerns through back channels afterward" is actionable. "You're creating drag" is not. State what changed, what needs to change, and by when. Give them a real window to demonstrate something different. Then close the loop on the agreed date.

Can a Stabilizer move toward Builder performance?

Yes, though what happens more often is that a Stabilizer placed in a well-engineered environment starts performing closer to the Builder range, because they're no longer burning energy compensating for structural chaos. Fix the environment before you draw conclusions about ceiling. A lot of apparent B players are A players who were never given what they needed.

What if the Blocker is a long-tenured employee or a personal friend?

The scoring still applies. What changes is how you handle the conversation. Tenure and relationship earn a clearer, more private, more honest conversation, not a different standard. If you hold a different standard for people you're close to, you corrupt the entire framework, and your team will know it.

How to optimize team performance: building the full system

The ROE scan is the starting point.

After you have a clear picture, the sequence looks like this:

Re-seat your top 20%. Map your Builders against the highest-value problems in the company. If they're not aligned, restructure before you hire.

Systematize your Stabilizers. Living SOPs, clear role ownership, visible metrics, documented exception handling. The right operating rhythm gives your Stabilizers the consistency they need to perform. Design meetings for output, not convenience.

Execute the Blocker track. Specific targets, defined timeline, clear decision point. Run it all the way through. Partial execution creates ambiguity, and ambiguity is the Blocker's natural habitat.

Identify small bets for Builders. Give them a defined mission with guardrails and incentives. Watch what they build. That's often where the next growth phase comes from.

This is the arc from a business that runs on the founder's energy to one that runs on its own structure.

The original newsletter that built this framework is here: Optimize Your Team for Rapid Growth and Sustainable ROI.

If you want to build the operating system that makes all of it stick, that's what CompanyOS is built for.