Explaining the Why Reduces Manager Overhead

One near universal experience in the digital age of work is the moment a senior leader sends a quick message asking for information or an update without explanation. Another near universal experience is the staggering amount of time we waste trying to figure out how this information will be used before responding. I’ll save writing about the times we didn’t figure it out and its unintended consequences for another post.

Moments where leaders don’t take the time to explain the “why” create overhead.

One of the most common examples on my teams that highlights the impact of sharing the why is urgency without context versus urgency with context. Asking an engineer to do a task urgently can go a lot of different ways. The engineer may re-triage mentally, second-guess the interruption cost to their current work, ask follow-ups, delay slightly. Asking an engineer to do a task urgently hits differently when I explain to them that it’s a security issue. Armed with the “why” they reprioritize immediately, act confidently, and stop needing confirmation from me about what they need to do next. They already know what to do and as their manager I need to show them I trust that they do.

That’s the first concrete demonstration of overhead reduction. I know that the work will be handled on the timeline I need it to be. I don’t need to follow up or check back in.

Taking this one step further, providing context enables autonomy. Autonomy replaces approvals.

By explaining why, I’m empowering my engineers to make decisions on their own and act in alignment with the goal we’re solving for. Context lets engineers make aligned decisions without waiting for me. If they understand why, they don’t need me in every room and every decision. That’s when context becomes a scalability mechanism. I have more bandwidth to do the work that only I can do.

I’ve seen managers try to solve for alignment with increased structure. They had specific actions they wanted their team to take, and they were doing everything they could to make it as easy as possible for them to just get on board with the plan. Templates, nudges, reminders, and structure often look like leadership, but they’re usually substitutes for alignment. Usually when I ask them, “But did you ever explain why?” I get a similar response. They had never explained to their direct reports why they wanted the specific actions they had asked for. Everything else they had done was just a lot of extra work on their part to supply crutches to the team. Followed by a lot of frustration that their teams didn’t seem to want to do the work. When teams don’t understand intent, managers compensate with scaffolding. When teams understand intent, alignment stops needing scaffolding.

This was the progression that surprised me most. Someone made a decision I hadn’t explicitly authorized — but it was the right one. That’s the moment overhead disappears. I was able to set the direction and have engineers execute inside it.

I’ve seen what happens to teams who don’t understand the why, either because it wasn’t explained to them at all or because it wasn’t explained to them in a way that was accessible. There is a high emotional cost to missing context around the work we do. Without context, changes feel like they’re happening to people. 

A classic example is changes to the engineering roadmap or changes in prioritization. Lack of context creates resistance overhead. Engineers without context hesitate, disengage, escalate more, and even question the legitimacy of the changes. Slowing down to explain the why replaces all of that with ownership, and that’s a cultural overhead reduction. 

A lot of times explaining the why feels like overkill — maybe the engineer doesn’t care deeply — but I’d rather give them insight into how I’m thinking about something. It lets them know it’s not just random, that there is a plan and a strategy. It helps them understand the direction we’re driving in long term. Without context priority changes feel chaotic, but with context priority changes feel intentional. Context turns resistance into ownership.

I understood the value of explaining the why early on, but it took me longer to feel what it changed on a team I managed. When I was a new manager, I used to think back a lot to my own former managers as a litmus test of how I was doing. One of my former managers I always describe as playing 3D chess. He always had multiple variations of a plan, and was always really open about sharing his vision and what he was building for his teams long-term. It made me feel really good, like I was trusted with that insight and like I was building something with him and my peers. It made the road in front of me feel exciting instead of like a dark path through the woods where I couldn’t see the end. That’s the feeling I want to imbue on the teams I manage.

Explaining the why makes people feel included in direction, not controlled by it.

There’s an important caveat around explaining the why: it does not make my decisions as a manager optional. I don’t want it to sound like what I’m suggesting is that if you just explain things more then everyone around you will suddenly agree.

Alignment and consensus are not the same thing.

Sometimes I can’t share the why with total transparency — like team personnel changes or blunt operational truths — but part of management is navigating that storytelling. Giving people enough insight to feel empowered without burdening them with information they don’t need or can’t have is an important skill that takes time to hone as a manager. 

Managers, myself included, often have to explain organizational decisions we don’t necessarily agree with. But that’s not the point. The point is finding integrity and value aligning with that direction. Okay, we’re going this way now — how are we as a team showing up for that?

Providing teams with context looks like communication work, but it’s really scaling work. When teams understand intent, they stop waiting for instructions. They stop second-guessing priorities. They stop escalating decisions that were already implied by direction.

Over time, the role of the manager shifts from answering questions to setting direction.

Explaining the why doesn’t just help your team move faster. It changes the shape of your job.​​​​​​​​​​​​​​​​