"When managers mistake speed for progress"

It’s easy to celebrate output when it looks good on the surface. A developer ships features quickly, closes tickets, keeps things moving. On the face of it, that looks like progress.

But managers play a role here too. If we reward speed alone, we send the message that questioning isn’t valued. Over time, a culture forms where developers just “do” instead of asking why. That’s how we end up with complex systems nobody needs, propped up by workarounds and hidden costs.

The hard part of leadership is resisting the comfort of visible busyness. Progress isn’t how much got done this week, it’s whether we’re building the right thing in the right way.

As managers, we’re accountable for more than delivery. We’re accountable for the environment. One where it’s safe — even expected — to pause and ask, “Is this the right problem to solve?”

Are you rewarding output, or creating space for outcomes?

✉️ Enjoying The Messy Middle?​
If this sparked something useful, consider forwarding it to a colleague or friend, it might help them too.

If someone sent this email your way and you’d like to get it direct, you can sign up here.