Stop Being the Bottleneck Your Team Won’t Talk About
A reflection from Software in 30 Days by Ken Schwaber and Jeff Sutherland
Hej! It’s William!
This is part of the "Meller Highlights" series with reflections and learnings from my personal book highlights. As mentioned here, this series is now something I’m keeping special for the people who support this channel as paid subscribers.
If you’ve been following along and enjoying the ideas I share, I’d love to have you join them. Becoming a subscriber not only gives you full access, but it also helps me keep creating and going deeper with the work I do.
How do these highlights work? Every day I pick one idea from my reading and think about how to apply it in real life. Most stay as private notes, but once a week, I choose one that feels special.
That’s the one I share here, a highlight that turns into a deeper reflection on how it can change the way we do something.
Today’s highlight: Software in 30 Days by Ken Schwaber and Jeff Sutherland
“The role of the manager with this approach is to set goals, facilitate, and remove obstacles. The manager empowers the people on the team.”
Let’s reflect on that…
Ken Schwaber and Jeff Sutherland created Scrum, a framework that changed how modern teams deliver work.
But more than a process, Scrum revealed something deeper: a new way to lead. I know many people disagree with that, and I can understand some of the reasons they say that.
But it is a fact. The shared leadership in Scrum was a great change that the software world will carry forever.
But, sometimes we forget that management is about managing the system around them so the work can actually move.
This quote puts that into words clearly.
A manager who still believes their job is to tell people what to do, review every decision, and be the bottleneck for every approval is not managing. They’re slowing things down.
Let me explain it the way I’ve seen it happen.
Great work doesn’t need constant pushing. It needs space. It needs clarity. It needs a rhythm where the team knows what matters, where they’re heading, and how to move without stepping into walls all the time.
The best managers I’ve worked with had one thing in common: they knew when to step back.
But stepping back doesn’t mean disappearing. It means being intentional. Setting clear goals. Creating structure. Protecting time. Removing noise.
And when blockers appear (and they always do), they’re the first to ask, “What’s getting in your way? How can I clear it?”
These managers normally have “freedom” with the team (what I attribute to Psychological Safety) to even push when required, because their credibility builds trust for that.
This role is more about flow than control.
More about creating space than filling it.
And when done well, it creates an environment where people actually enjoy working. Because things move. People grow. Problems get solved without drama.
And something else happens too. People stop waiting for permission. They start owning the outcomes. That’s when the culture shifts. That’s when speed and quality go up without burning anyone out.
But here’s the challenge: this kind of leadership feels invisible.
It doesn’t always show up in status updates or loud meetings. It shows up in what’s not broken. In what doesn’t get delayed. In how light the work starts to feel. In how often the team reaches the goal without late-night rescue missions.
If you’re leading today, maybe the most useful question isn’t “What should we do next?” Maybe it’s “Where is the work getting stuck?”
Because your real job might not be to push the team harder. It might be to get out of the way and take the obstacles with you.
Have you ever worked in a team where the flow was smooth and natural, where the manager didn’t micromanage, but you always felt supported?
Or maybe the opposite, where small blockers piled up and no one cleared the path? I’d love to hear what that experience taught you.
If you want to keep getting reflections like this one in your inbox, subscribe to Meller Notes.





Great advice.
A manager who goes away on holiday and isn’t missed is a good one.
Sadly in the corporate world we tend to promote managers who get noticed for fixing problems that shouldn’t have happened in the first place.
I once worked with a manager who would deliberately put errors in his team’s code and then he would be called out at 2:00am to fix the problem. I noticed that and asked him why, he replied that without the error he, and his team wouldn’t be noticed by the senior players.