How we communicate complex work, and earn the trust to lead through it
There is a particular moment that shows up in every major technology program. Something has to be decided. Maybe the original plan no longer fits the reality on the ground. Maybe two paths forward exist and both carry risk. Maybe a deadline is slipping, a vendor relationship is strained, or a design assumption from months ago no longer holds. Whatever the trigger, the team has done the hard work of understanding the problem. Now the work shifts, and it shifts to communication.
How we tell the story surrounding that decision matters more than most people realize. Not because the truth needs to be dressed up or spun. But because leadership, the people with the authority and accountability to act, can only make good decisions when they clearly understand what they are deciding and why.
This is one of the most important skills a director can build. Not just for escalation moments, but every week, in every written update, status report, and hallway conversation. Much of the job is translating complex work into something that makes sense to people who are not living inside it every day — the same translation work that makes a slow-feeling transformation legible to the people funding it.
The team that can explain what it is doing, and why it matters, earns the credibility to keep doing it.
If anything, complexity is the reason we have to be more intentional about it. The more complex the work, the more important it is that the people responsible for the organization’s success can understand what is happening and why it matters.
Where updates usually go wrong
There is a version of this that goes wrong often enough to name directly. A team gets so close to a problem that it forgets what it sounded like before it understood it. The update comes out dense with acronyms and caveats, technically accurate and functionally useless to the person reading it. That person then makes a decision based on a headline instead of the substance, because the substance was never made available to them in a form they could use.
Three questions worth answering before the meeting
The fix is not to simplify the truth. It is to do the translation work before the meeting instead of during it:
- What is the decision, in one sentence?
- What are the real options, in plain terms?
- What happens if we choose wrong?
A leader who can answer those three questions clearly has usually already done the hardest part of the job. It is the same discipline behind naming a process gap plainly instead of burying it — the gaps a team finds are the point, not something to explain away.
We have an obligation to meet people where they are. To translate. To simplify without being condescending. To tell the story around the decision, not just the decision itself. When we do that well, we do not just get better outcomes on the immediate issue. We build the kind of credibility that makes everything else easier.
More essays like this one live on the Between Mondays articles page.
Further reading: Harvard Business Review and the Project Management Institute both write regularly on communicating decisions under uncertainty.