(Why the projects that go smoothly are the ones nobody appreciates)

Calm delivery is not the absence of leadership. It is the result of it.

My favourite anime is One Punch Man. Its hero, Saitama, defeats every opponent with a single punch. That is exactly why he is underrated. If the fight ended after one punch, people assume the opponent must have been weak and the whole thing was easy.

It is the same in our work. When a project runs without problems nobody notices it. When a project is full of chaos and needs many people to save it, the leader who saved it gets the credit.

One captain or 135 captains

Our leadership reading circle read Turn the Ship Around by L. David Marquet. What caught my attention most was the leader-leader model. I especially like that it moves responsibility, authority and decisions to the places in the organization where they are actually needed, which reduces delays and makes the work more effective. Listening to an interview with the author I liked his line that the model turned one captain into 135 captains.

I have often said that the best leader is the one who does not stand out. When a project ends the team should be able to say "we did it ourselves". For me the model was not a revolution but an evolution of something I already believed.

A leader who leaves and everything keeps working has done the job well.

What it looked like in my team

Let's be honest. Not so long ago I was still heavily involved in executing tasks myself as an engineering owner.

Then the largest initiative I led grew into several parallel work streams. Managing that alone was not sustainable. So each stream got its own engineering owner and we held weekly syncs to review the current tasks, discuss release plans and agree on how we manage the plan. My role moved from doing the work to coaching the people who owned it.

During that period we delivered the planned work and nobody left the team. I no longer had to be in every room.

Silhouettes of people jumping with raised arms on a hill at sunset
Photo by Val Vesa on Unsplash

Quiet is the result, not the exception

I have the feeling most of my projects go this way. A good example is the goal we were given to reduce KTLO (keep the lights on) work.

At first it looked unrealistic. The teams had worked together for years, so it seemed hard to get anything more out of them. We set the goal anyway, started thinking about what to change and introduced small improvements. Within two to three months we saw a significant improvement.

The improvement came from focus, not from heroics. We stopped spending time on things that did not matter, set priorities more carefully, reduced the number of topics we worked on at the same time and invested our time in what counts.

The invisible success problem

Organizations rarely reward this kind of work. We tend to reward leaders who are visible and irreplaceable, sometimes the ones who manage through chaos and solve crises they partly caused themselves.

A good example is the race to the South Pole. Roald Amundsen reached the Pole first and brought his whole team home safely. Robert Falcon Scott arrived five weeks later and his polar party died on the way back. Yet in Britain it was Scott who became the national hero, while Amundsen stayed in his shadow for decades. We remember the dramatic story and forget the quiet one that ended well.

Calm work does not fail. It simply stays invisible unless somebody shows it. I call it the invisible success problem.

If a project runs smoothly nobody notices. If it is saved at the last minute somebody becomes a hero.

A red icebreaker ship cutting through sea ice
Photo by Nick Brice on Unsplash

Make the team's work visible

Simon Sinek describes this kind of leadership well in an essay about leading without recognition. "If everything goes right, you give away all the credit."

So the answer is not to create drama. The answer is to make calm progress visible on purpose. It should be the team's progress and not the leader's.

In my teams this means a few simple habits. We present our work at all-hands meetings and celebrate milestones together. We share achievements on Slack. We hold regular syncs to watch the progress and I share that progress with leadership. I have also organized a demo of the work delivered each quarter.

These habits do more than build visibility. They tell everyone what we are working on and where we are, they keep the team aligned and they give people a reason to celebrate what they did themselves. They also motivate people to keep going.

What I've learned

  • Build teams that do not need saving. A leader is measured by what keeps working when they are not in the room.
  • Move decisions to the people with the information. Decisions made where the information is cut delays and make the work more effective.
  • Build competence before you hand over responsibility. Ownership given to people who are not ready yet leads to mistakes, so the two have to grow together.
  • Make the team's progress visible. Share milestones, demos and wins on purpose, because calm work will not announce itself.

Final Thought

Saitama will probably never get the recognition he deserves. Leaders can do better than that by making the work behind the quiet result visible. We can build teams that win with one punch and then make sure everybody sees how much work went into that one punch.