The Plan That Removes Something From Your Manager's Plate Gets Approved. The One That Only Adds to Yours Doesn't.

Josh, who manages my DevOps team, needed no permission to solve a problem that had been sitting on my plate for weeks. I needed my devops and development teams to become genuinely AI-proficient, and I had no time to plan out how to get them there. Josh brought me a plan for rolling AI adoption out across both teams, his own and one that was not his to plan for, already built, already sequenced, ready to run. He did not ask if he could help. He removed the actual planning burden, the part I genuinely had no time for, and executed against it.

What I felt in that moment was relief, not evaluation, the specific kind that comes from watching something come off your plate instead of something new landing on it. This is not the only time it has happened on my team. Another engineer, Ethan, did something similar with our environment setup during onboarding, a story I have told elsewhere. The pattern is the same both times: someone saw a real gap, built a plan for closing it, and executed instead of waiting to be asked. Neither of them asked me first whether they were allowed to try.

The standard advice technical leaders get is the opposite of what Josh did. Wait until your role formally expands before acting like it has. Ask permission first, go through the proper channel, build trust and let buy-in accumulate over time. Taking on responsibility outside your current scope without being asked risks looking presumptuous, or like you are overstepping.

Here is what that advice misses. Waiting for permission means waiting for someone else, usually the manager, to notice the gap, design a plan, and formally grant authority to close it. But the manager is often the actual bottleneck: they do not have the bandwidth to drive the fix themselves, which is exactly why the gap exists in the first place. The person best positioned to see and close it, the one already inside the problem, sits waiting for permission from someone who has no spare capacity to design and grant it. When that person instead brings a ready-made action plan that already assumes the answer is yes, they are not asking the manager to do more work. They are removing the actual constraint, the manager's bandwidth, rather than adding to it, which is exactly why the plan tends to get approved instead of rejected. Meanwhile, the gap keeps costing something every week it sits open, even if nobody is tracking what that cost actually is.

This does depend on a baseline level of reasonableness in the relationship and the organization. Some environments are genuinely unhealthy, and no amount of plan quality changes that. What follows assumes you are not in one of those.

The move that works is specific, not general. Bring a plan that already assumes the answer is yes, and make sure the plan names exactly what it removes from your manager's plate, not just what it adds to yours. Josh did not ask permission to help with AI adoption. He removed the actual planning burden, the part I had no time to do myself, and executed against it. That is the difference between initiative that reads as ambition and initiative that reads as relief. The first asks the manager to evaluate you. The second asks nothing of them at all.

Think of the responsibility you want more authority over right now. Have you brought your manager a plan that names exactly what it removes from their plate, or have you been waiting for them to notice the gap and offer it to you?

This is the individual playbook while you wait for the structural fix. The organizational version, naming authority in writing so it survives whoever currently holds the role, is in The Staff Engineer Role Doesn't Fail on Skill. It Fails on Authority Nobody Wrote Down. If you want this kind of depth every month in print, the LeadershipOS™ Inner Circle ships the first of every month.

---

I write about structural leadership for technical leaders in high-stakes operating environments. If you want this depth every month in print, the LeadershipOS™ Inner Circle ships the first of every month. Reply “maybe” and I’ll send you details.