Tag Engineering Management
A Manager's Guide to Claude, Six Months Later
Six months of evolving my workflow with Claude: feature flags that clean up after themselves, an early warning system, and a snarky tabloid.
Back in February I described Slack as my command center, generating automated briefings and team summaries, as well as a wish list that was mostly limitations. Some of my wishes came true, some didn’t, and some of my automations were sunsetted. In other words, my usage is evolving and this blog post is to document the evolution.
A Manager's Guide to Working with Claude
Engineering management on autopilot: Claude automates team summaries, release plans, and engineering metrics—surfacing risks and bottlenecks before I start my day.
I start most mornings with my coffee and two (sometimes three) automated summaries waiting in Slack. One tells me what my team did yesterday—tickets moved, PRs opened, potential bottlenecks. The second checks upcoming releases and cross-examines those with our JIRA board, flagging changes stuck in QA or review. The third is a recap of my team’s weekly performance in terms of velocity and defects. By the time I’m at my desk, I have a good idea of where to put my focus and what to follow up on. These automations let me spend more time diving into PRs and resolving risks and less time pulling data to understand where the risks might be.