Why Frontline Managers Feel Powerless (And What Actually Changes It) Quick Bridge: Frontline leadership means running two systems at once, one you can steer and one you cannot. Once you see the split clearly, you stop spending energy on the half that was never yours, and you get sharper about the half that is. You can get better at every part of this job and still never get your hands on a wheel that was never connected to yours in the first place. Being a front line manager is like trying to get everyone on a bumper car ride to go the same direction and not run into each other. Except the ride is bolted to the back of a truck driving around the city, and you don't know where the next turn is. I spent most of a quarter building a buffer. A new intake process, a review step, a way to filter decisions from above before they hit my team directly. I thought I was protecting people. It did not work. The decisions still landed. My team still felt them. All I had actually built was ...

Validating AI Output Is Real Work: How to Get Credit Quick Bridge: You are the person who reads the thing all the way through before it goes anywhere. When that goes well, no one can tell you did anything at all. Validating AI output is some of the most useful work on an engineering team right now, and it is also some of the hardest to point to. I found out what that looks like in a contract review. I was reading the statements of work, the whole thing, because I had some extra unallocated moments. A teammate had not read them and had produced an AI summary instead. That summary had hallucinations and errors that would have set back our negotiations. Because I had read the source, they were not set back. There was no crisis and no recovery plan. From the outside, nothing had happened. The catch is real, and it leaves no trace. Why Validating AI Output Never Shows Up on a Dashboard Every dashboard your team reports from counts what got built. Pull requests merged, features ...

Why Pushing Harder Is Sometimes the Problem: The Engineering Manager's Pacing Framework Quick Bridge: If you manage a team that feels slow and your first instinct is to add more meetings, more deadlines, or more urgency, this post will challenge that reflex. You will get a concrete decision framework for when to push and when to let it run, plus a practical signal checklist to read your team before you act. If the answer turns out to be yes, there is also a guide to what effective urgency actually looks like. There is a move that looks exactly like leadership from the outside. You see a gap, you respond. You see slowness, you apply pressure. You fill dead air with new asks. You follow up before anyone falls behind. And it is exhausting everyone, including you. The managers I work with who burn their teams out the fastest are not the ones who are disengaged. They are the most driven people in the room. They believe that constant forward motion is what the role requires. N...

AI Notetakers in 1-on-1s: What They're Actually Costing Your Team's Honesty Quick Bridge: Somewhere on your team right now, a direct report is choosing a smaller answer than the one they actually have, because a recording tool is sitting in the meeting and nobody has said out loud what happens to it afterward. Getting consent is the legal minimum, not the fix. A signature does not make someone forget there is a second audience. The next version of this is already happening. I have seen it come up often enough now that it stopped feeling like an edge case. Some managers have started using AI to score the sentiment of 1-on-1 conversations. Not what was discussed, not action items, but whether the person on the other side sounded positive or negative. No conversation about it beforehand, no explanation of who sees the score or what it gets used for. Just a running record of how someone came across, building quietly in the background of a meeting that used to be theirs. O...

What Happens to the Work After You Delegate It (And Why You Rarely Find Out) Quick Bridge: You delegated the work. Someone accepted it. But do you know where it actually landed, and what got dropped to make room for it? This post explains the organizational physics behind every delegation cascade, why this almost never gets caught until it is too late, and how technical leaders can use skip-level conversations to surface what the chain hid. The work didn't disappear when you handed it off. It just moved somewhere you stopped watching. Something always falls out the bottom of a delegation chain. It is not a skills problem. It is not a planning problem. It is the basic physics of how capacity works inside an organization. When you hand work to someone who is already busy, they drop something lower-priority or pass it further down. That chain continues until it hits someone with no one to pass to. At that point, the work gets absorbed or something else gives way. Not many...

  Quick Bridge: Your engineers adopted AI and got measurably faster. The velocity chart looks great, and a few of your best people seem strangely flat next to it. Nothing in the sprint data explains the gap. One of my strongest engineers asked if she could go back to writing a chunk of our test coverage by hand. Not all of it. Just the part she used to like. She had been running three or four AI agents at once for a couple of months, shipping more than she ever had, and she told me the days felt like air traffic control. It was all watching and deciding, with nothing at the end she could hold up and say she made. I did not have a good answer for her in the moment. The velocity chart said she was having her best quarter. She was asking to be slower on purpose. Why Agentic Work Feels Like a New Kind of Engineering Burnout Making something gives you a finish line you can see. A test that was red goes green. A design problem you have been circling for an hour finally gives way. You po...