When I first wrote about the nine things a program manager does, I didn’t dwell on what the job actually feels like first thing on a Monday. The hardest part was always the scramble: a dozen threads that moved over the weekend, a risk or two that quietly materialized, and a critical deliverable whose scope someone changed in a comment buried three levels deep. All of it has to be synthesized into a coherent picture before the leadership sync, and the clock doesn’t care how many tabs you have open. That scramble hasn’t gone away. But increasingly, I’m not doing it alone. From async to AI-augmented# I The evolution makes sense in hindsight. I’ve argued that teams should default to async communication — written, durable, discoverable artifacts over synchronous meetings. That managers should use the same tools engineers use — issues, pull requests, project boards — to plan and track their own work. And most recently, that AI agents are extending the same patterns of transparency and code…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.