Explaining the Why Reduces Manager Overhead
Moments where leaders don’t take the time to explain the “why” create overhead.
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 think of my teams there’s one scenario that I think highlights the impact of sharing the why, which 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 or second-guess the interruption cost to their current work or ask follow-ups or 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 because we’ve pre-aligned on how to handle security issues and as their manager I need to show them I trust that they know how to handle the situation accordingly.
This was the progression that surprised me most. 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. Someone made a decision I hadn’t explicitly authorized — but it was the right one. I was able to set the direction and have engineers execute inside it. That's when I realized context had replaced approval.
Managers often 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. I've watched managers build templates, checklists, recurring reminders, and dashboards to encourage behavior they never explained in the first place. They never explained to their direct reports why they wanted the specific actions they had asked for. They had created an entire system to compensate for missing context.
There is a high emotional cost to missing context around the work we do. Without context, changes feel like they’re happening to people.
Lack of context creates resistance overhead on the team. It can feel like whiplash to have a plan laid out in front of you only to have it swapped out for something else with no idea why that change was made. On a healthy team engineers can and should feel a strong sense of ownership over their team’s roadmap. Making changes without context can be incredibly destabilizing. 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 why can feel like overkill. Do the engineers even care? Am I wasting my breath taking the time to go over the same details across all of my direct reports’ one on ones? But I always come back to the same conclusion: I’d rather give my engineers insight into how I’m thinking about something basically every single time. It lets them know that what’s happening around them isn’t random, that there is a plan and a strategy. It helps them understand the direction we’re driving in the long term. Explaining why makes people feel included in direction, not controlled by it.
Explaining why 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?
One of my former managers who I learned a lot from 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 beyond the day to day tactical moves. 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.
Providing teams with context looks like communication work, but it’s really scaling work. When teams understand intent, they stop waiting for instructions. 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.
