unknown

Engineering managers who spend their days chasing ticket updates and following up on PRs are dealing with a clarity problem, not a discipline problem. When a manager becomes the primary mechanism for keeping work moving, it signals a broken system rather than a broken team. Engineers deprioritize process updates because they've learned the tracking system doesn't reflect reality. The fix involves making priorities ruthlessly narrow (top two, not top ten), connecting work to outcomes, designing accountability into workflows via automation and visibility tools, reformatting standups to surface surprises rather than status, and investing in context-sharing over control. The litmus test: take a real week off and see if the team self-directs. The goal is building systems that sustain themselves so managers can focus on growing people, shaping strategy, and organizational impact.

Stop chasing your team

Dedicated to developers who want to learn and share how they git gud at their craft 🦾. Is there a mindset you think is currently hurting developers growth? What tools do you love? 