Seven People or Forty-Four: Servant Leadership, Intensity and Focus

I have built and led teams of every size. Seven people in a room, forty-four spread across five continents, and most sizes in between. Twenty years of running teams across time zones that never quite line up, across cultures that define respect differently, and across languages where the real meaning lives in what does not translate cleanly.

That teaches you something no management book does: what actually holds a team together when the pressure is real. My approach rests on three things most people treat as opposites — servant leadership, intensity, and focus. They are not opposites. They are the same discipline seen from three angles.

I write this on a partner advisory site for a specific reason. When Optimus embeds an operator into a client's organisation, that person is not delivering a framework. They are leading, usually inside someone else's culture, often with no formal authority. How they do that determines whether the engagement produces anything.

Servant leadership is an operating decision

The phrase has been repeated into meaninglessness, so let me be specific about what I mean.

When someone brings me a problem they cannot solve — a partner relationship gone sideways, a deal stalled on misaligned incentives, a launch slipping — my first question is what do you need from me to move this forward. Not what happened.

That difference sounds small. It is not. The first question puts a person in a defensive posture; the second puts them in a problem-solving one. A team living in a problem-solving posture builds completely different muscle. Over a year, it compounds into a team that runs toward hard problems rather than hiding them from you.

The most useful thing I ever did as a manager was run development conversations with nothing to do with performance reviews. No ratings, no compensation. Three questions: where do you want to be in three years, what are you learning right now, and what is the single most important gap we should close together.

Serving your people is not the soft part of the job you get to after the real work. It is the mechanism that produces the real work.

Intensity is a gift, not a tax

I run intense teams and I am not going to pretend otherwise. Standing up channel motions, turning around underperforming regions, launching an organisation from zero — none of that happens at a leisurely pace.

But there is a version of intensity that builds teams and a version that destroys them, and the line is precise.

Destructive intensity is manufactured. It is the manager creating artificial fire drills, treating every task as a five-alarm emergency, confusing their own anxiety with everyone else's priorities. It burns the most conscientious people first, because they are the ones who cannot bring themselves to ignore it.

Productive intensity is honest. It comes from a shared, legible understanding of what actually matters and why this deserves everything right now. When a team genuinely sees the stakes, intensity stops being imposed and starts being generated. My job is not to crank pressure. It is to make the stakes legible and then get out of the way of people who care.

The test I use on myself is simple. If I am the only source of urgency in the room, I have failed.

Focus is how you protect people from the work

You cannot ask a team for real intensity across twenty priorities. It is not physically possible, and pretending otherwise is how you burn people out. Intensity is only humane when it is focused.

The leader's actual job — the unglamorous daily one — is saying no to the ninety percent so the team can pour themselves into the ten that determines whether you win. Every priority added to a team's plate is time pulled from something else and, eventually, from their lives.

This is where servant leadership and intensity finally connect. You get to run an intense team without burning it out only if you are ruthless about focus. High output and a sustainable pace are not in tension. They are both downstream of the same decision: do fewer things, and do them with everything you have.

Why this matters when the team is not yours

An embedded operator inherits a team they did not hire, inside a culture they did not build, with a number they did not set. None of the three disciplines require formal authority. That is precisely why they travel.

A version of this piece first appeared on LinkedIn as “Seven People or Forty-Four: What 20+ Years Taught Me About Building High-Performance Teams”.