Posts

Why Teams Fall Behind When Leaders Scale Up (And What Most Miss)

Image
Quick Bridge: When a leader steps up, teams often stall. Not because the people are weak. Because the context behind the critical work left with the leader. Most delegation conversations are about tasks. Almost none are about the reason those tasks exist. Here is what actually happens when that gap meets team growth — and how to close it before you need to. The Pattern No One Talks About Leaders get promoted. Teams get bigger. And somewhere in the transition, a quiet kind of failure starts. It does not show up in performance reviews. It does not show up in the first quarterly report. But over time, something shifts. The team that was humming before the change starts losing ground. Visibility fades. Internal relationships that used to matter stop getting attention. The work that kept the team on the map slowly goes dark. The reason is almost never the quality of the work. The reason is what the departing or scaling leader was carrying in their head that never made it into anyon...

What Your Engineering Manager Job Description Left Out

Image
My boss's boss called me into his office two months after I became a first-level manager. My manager was there too. He walked me through it cleanly: which projects my team would own, who would be assigned to each, how often they would report status directly to him. When he finished, he asked for my input. I said: "If that is how you are going to manage me, you hired the wrong person for this job." The room went quiet. My manager looked at the floor. What came next was better than I expected. We actually talked about what I was there to do, what visibility he needed and was not getting, and whether I was there to make real decisions or serve as a human relay between my team and senior leadership. I asked to be fired or demoted if it was the latter. It was not. What came out of that conversation was simple. He needed information flow. I had been hoarding it instead of creating it. Once we named the real problem, we fixed it fast. But what surprised me was how close ...

The Megamanager Trap: How Doubling Your Team Size Hollows Out Your 1-on-1s

Image
Quick Bridge: When a company grows a manager's team by half or more, the assumption is that the manager just needs a better system. What actually happens is a slower problem: the real conversations that made you an effective leader stop occurring before you notice they've stopped. This post covers what research says is driving the megamanager era, what specifically breaks first, and how to think about protecting the leadership that actually matters when your headcount grows. The average American manager now oversees 12.1 direct reports, up from 8.2 in 2013, a 47% increase in twelve years, according to Gallup's latest workplace research. Fortune's coverage this spring called it the "megamanager era," tracing it to a deliberate corporate strategy: three years of middle-management flattening, accelerated by AI cost-cutting and a relentless push to rationalize headcount. The result is that managers who once had eight reports now have fifteen or twenty. Coache...

What Engineering Leaders Actually Need to Get Promoted When AI Handles the Technical Work

Image
Quick Bridge: Most engineering leaders are still optimizing for the skills that got them their last promotion. AI has quietly changed which skills are scarce. Execution depth is becoming a baseline. Here are four diagnostic questions to tell you whether you are already in the trap, and four moves for getting out. The engineering team structure most of us grew up in is actively inverting. For decades, the standard ratio in software companies was roughly six engineers for every one product manager. In early 2026, Andrew Ng publicly described teams proposing a ratio of one product manager to every 0.5 engineers. He called it the product management bottleneck. [1] AI has made coding approximately 10x faster. The constraint is no longer how to build. It is deciding what to build. For engineering leaders, that shift is not abstract. It is a direct career signal. The Technical Leader Promotion Gap AI Is Widening Most engineering leaders were promoted because they were the best te...

Managing Someone Who Was Once Above You in the Org Chart: Why Your Feedback Gets Complicated Before You Notice

Image
Quick Bridge: When someone who was once your organizational superior ends up reporting to you, most managers focus on the relationship. The feedback gets overlooked. This post explains why the seniority history creates two opposing distortions that look exactly like real management, and what to do before your next hard feedback conversation to give feedback that is actually about the work. Something happens to feedback when the hierarchy inverts. You cannot always name it. The feedback arrives on time. The words are professional. But something about it does not quite fit the work. It lands softer than the situation called for, or harder than the output warranted. And the person receiving it cannot explain why their manager is not quite giving them what they need. Most of the time, the manager cannot explain it either. I have been on both sides of this. I know what it feels like to receive feedback from someone whose sense of who I am was formed when they were above me in the o...

Why Your Team Keeps Waiting for You (And How to Fix It)

Image
Quick Bridge: If your team keeps escalating decisions you think they should handle, the fix is not more trust. It is better design. This guide breaks down what distributed team ownership actually requires and what most leaders skip, so your team can operate without you at the center of every call. The Delegation Trap Most Managers Fall Into There is a difference between telling someone they own something and actually giving them ownership. Most managers do the first and wonder why the second never happens. Here is the pattern: a leader feels overwhelmed. They decide to delegate more. They hand off responsibilities, announce new accountabilities, maybe even set up a new meeting structure. Two months later, they are back at the center of every decision, fielding the same escalations, doing the same work. The team did not fail to step up. The system failed to exist. Distributed leadership requires more than good intentions. The version that actually works, where people act in...

Why Your Brain Won't Let You Stop Thinking About Work (And What Neuroscience Says to Do About It)

Image
Quick Bridge: If you wake up at 2am thinking about something from work, your brain is not broken. It is doing exactly what it is supposed to do. The problem is not focus or discipline. The problem is that you have not given your brain permission to stop. This post explains the mechanism, what the research confirms, and one simple practice that lets you actually close the laptop and leave. I used to think the 2am brain was just part of the job. The things that surfaced in the middle of the night were never the big projects. They were the small unresolved items. A message I had not replied to. A conversation I had been putting off. A decision I had not fully made. Small things. But they would surface because my brain had been trying to surface them all day, and I had not been writing them down. When I started capturing open items before closing the laptop, the 2am wake-ups stopped within two weeks. Not because I was getting more organized. Because I had finally given my brain so...