From Technical Detail to Executive Clarity: How to Communicate Upward

One of the greatest pieces of advice I ever received from a supervisor was about communicating with executives.

It was simple.

When an executive opens your email, they should be able to understand within a few seconds:

• What are you asking for?
• How much will it cost?
• What is the benefit?

And when you are communicating a problem, they should be able to quickly see:

• What is the problem?
• What is the current status?
• What action are you proposing?
• What outcome do you expect?

They should not have to dig through five paragraphs and three attachments to work this out.

That advice has stayed with me. I still use it, and I find myself passing it on to others.

It sounds almost too simple. And yet, it becomes even more important in an age where AI can produce several paragraphs saying essentially the same thing in slightly different ways.

More words do not necessarily mean more clarity.

Sometimes, they simply make the reader work harder.

The shift from technical detail to executive clarity

As technical professionals, we are trained to value detail.

We want to explain the context. We want to show our workings. We want to make sure nobody misunderstands the technical issue. We want to demonstrate that we have considered all the angles.

And then we get promoted.

Suddenly, the people we communicate with may not have the time, technical background or interest to work through all those details.

Their question is often much simpler:

What do you need me to know, decide or approve?

Think about it from their perspective.

Your manager has dozens of things competing for their attention. There are decisions waiting for approval, people asking for resources, risks that need managing, budgets to review and problems that need resolving.

Why should they spend ten minutes trying to work out what you need from them?

This is where communicating upward becomes a leadership skill.

I sometimes think of it like a TikTok video.

You have a very short window to get someone’s attention. You need to deliver the why, what and how quickly and clearly.

The supporting detail can come afterwards.

This does not mean becoming superficial.

It means doing the thinking before you communicate.

And that distinction matters.

Executive clarity is not about giving executives less information because they cannot handle detail. It is about giving them the right information first, so they can quickly understand the issue and decide what they need to do next.

Core principles of communicating upward

1. Be decision- or solution-centred

Before you write the email, prepare the presentation or walk into the meeting, ask yourself:

What decision needs to be made?

Or:

What action do I want from this person?

This sounds obvious, but it is surprisingly easy to lose sight of.

A technical professional might spend several paragraphs explaining why a particular issue has arisen, only for the executive to reach the end and wonder:

“So what exactly do you want me to do?”

Do not make them guess.

If you need approval, say so.

If you need a decision, identify the decision.

If you are recommending an action, state the recommendation.

If you are escalating a risk, explain what you need the executive to do about it.

The more senior the audience, the more important this becomes.

2. Start with the recommendation or conclusion

One of the biggest changes you can make to your communication is simply changing the order.

Technical professionals often communicate like this:

Background → analysis → technical details → options → conclusion

Try this instead:

Conclusion → why → supporting evidence → detail

Put the destination at the beginning.

For example, instead of writing:

“Following the recent discussions regarding the proposed change to the construction methodology, and after reviewing the contractor’s submission and considering the potential implications…”

You could start with:

“I recommend approving the proposed methodology change at an estimated additional cost of KES X, because it will reduce the programme risk by approximately X weeks.”

Now the reader knows exactly what you are recommending.

And then, if they want to understand how you reached that recommendation, the supporting information is there.

This is not about hiding the detail.

It is about putting the detail in the right place.

3. Keep it concise and scannable

Executives often scan before they read.

Make it easy for them.

Use headings, short paragraphs, bullet points and tables where appropriate. Put the important numbers where they can be seen quickly.

A useful test is this:

If someone only reads the first 20 seconds of your email, will they understand the issue and what you need from them?

If the answer is no, your communication probably needs another edit.

And here is where AI can be both helpful and dangerous.

AI can make your writing sound polished. It can also turn one simple point into six beautifully written paragraphs.

Do not confuse polished writing with effective communication.

After using AI, ask yourself:

Can I remove 30% of this without losing the meaning?

Then try removing another 10%.

Your executive may thank you for it.

4. Translate technical information into business or project impact

This is one of the most important shifts for a technical professional moving into leadership.

You understand the technical issue.

Your executive may be thinking about cost, time, risk, quality, reputation, resources, compliance or strategic objectives.

Connect the two.

Don’t simply say:

“The existing system has reached its design capacity.”

Explain what that means:

“The existing system has reached its design capacity, which creates a risk of a three-week programme delay unless additional capacity is approved.”

Now you have translated technical information into a business impact.

You are no longer simply reporting.

You are helping someone make a decision.

Four pitfalls to avoid when communicating upward

1. Technical language

Technical language can create distance very quickly.

As technical professionals, we sometimes forget that the terminology that feels completely normal to us may be unfamiliar to the person reading our email.

Ask yourself:

Could someone outside my technical discipline understand this?

If not, translate it.

You do not need to remove the technical accuracy. You simply need to explain it in language that connects with the audience.

Your job is not to prove that you know the technical terminology.

Your job is to make sure the other person understands what matters.

2. Too much detail about the process

There is a difference between showing your thinking and showing every step of your thinking.

Your manager probably does not need a chronological account of every conversation, meeting and email that led to the current situation.

They need to understand the relevant facts.

What happened?

Why does it matter?

What have you done?

What remains to be decided?

What do you recommend?

Keep the supporting detail available. Put it in an attachment, appendix or supporting document where appropriate.

That way, the information is available when it is needed without forcing everyone to read it upfront.

3. Problems without solutions or recommendations

One of the easiest ways to frustrate a manager is to bring them a problem and then expect them to do all the thinking.

There will, of course, be situations where you genuinely need direction.

But before escalating a problem, ask yourself:

What would I do if I were making the decision?

Then bring that thinking with you.

Instead of:

“We have a delay because the contractor has not mobilised the required resources.”

Try:

“The contractor’s current mobilisation is insufficient to maintain the programme. I recommend issuing a formal notice requiring additional supervision resources within seven days. This should reduce the risk of further programme slippage.”

Now you are not simply escalating a problem.

You are demonstrating judgement.

And that is one of the biggest shifts from being a technical expert to being a leader.

4. Unflagged high risks

Do not assume that everyone sees the risk in the same way you do.

You might think something is obviously a major risk because you have been immersed in the technical details for weeks.

Your executive has not.

Make the risk visible.

If there is a significant cost, programme, safety, quality, contractual or reputational risk, say so clearly.

And then explain what you are doing about it.

For example:

Key risk: If the decision is delayed beyond 15 October, the project may incur additional programme and mobilisation costs.

Mitigation: We recommend approving the proposed approach by 10 October.

This gives the decision-maker the information they need to act.

A simple framework for communicating upward

When you have a significant issue, decision or recommendation to communicate, use this simple structure.

1. Do the prework

For a major decision or high-risk issue, do not wait until the decision-making meeting to introduce the entire story.

Share a brief with the key stakeholders beforehand.

Give people time to understand the issue, ask questions and consider the implications.

Nobody enjoys being handed 30 pages of information five minutes before they are expected to make a significant decision.

Good communication starts before the meeting.

2. Start with the decision

Begin with the end in mind.

Ask yourself:

What do I want to achieve from this conversation?

Then make it clear.

Decision required: Approval of the revised project budget of KES X million.

Or:

Recommendation: Proceed with Option B to avoid an anticipated six-week programme delay.

Now everyone knows why they are having the conversation.

3. Explain why the decision matters

Connect the decision to the bigger picture.

What happens if we do nothing?

What does this mean for the project, business, client or team?

This is where you move from technical communication to leadership communication.

4. Present the key evidence

Now provide the information that supports your recommendation.

Not every piece of information.

The key information.

Think:

• Cost
• Programme
• Risk
• Quality
• Resources
• Compliance
• Business impact

The evidence should help the decision-maker understand and challenge the recommendation.

5. Present the options, risks and recommendation

If there are multiple options, make them easy to compare.

A simple table can often do more work than several paragraphs.

Option	Cost	Programme Impact	Key Risk	Recommendation
Option A	KES X	+4 weeks	Medium	—
Option B	KES Y	+1 week	Low	Recommended
Option C	KES Z	No delay	High	—

The point is not to make the decision for your executive.

It is to make the decision easier to make.

6. End with the ask and next steps

Do not finish with:

“Please let me know your thoughts.”

Be specific.

What do you need?

By when?

And what happens afterwards?

For example:

Decision required: Approval to proceed with Option B by Friday, 25 September. Following approval, the team will issue the instruction and commence implementation on Monday.

Now the communication has a clear beginning and a clear end.

Your next communication is your practice ground

You do not need to wait for a major board presentation to practise communicating upward.

Start with your next email.

Before pressing send, ask yourself:

What is the decision or action I need?

Have I put it near the top?

Have I explained why it matters?

Have I translated the technical issue into project or business impact?

Have I clearly flagged the biggest risk?

Have I made my recommendation?

Can the reader understand the key message in 20 seconds?

And then, if the answer to any of these is no, edit.

This is one of those leadership skills that improves through repetition.

The goal is not to become less technical.

It is to become better at deciding which technical information matters to which audience, and when.

That is executive clarity.

Final thoughts

As technical professionals, our expertise is often what gets us noticed and promoted.

But as we move into leadership, technical expertise alone is no longer enough.

We have to learn how to turn complexity into clarity.

That means starting with the decision. Leading with the recommendation. Translating technical detail into cost, time, risk and business impact. Making risks visible. And bringing solutions, not just problems.

Most importantly, it means respecting the attention of the people we communicate with.

Your manager should not have to excavate your email like an archaeological site to find the decision you need them to make.

Give them the headline first.

Give them the evidence next.

And keep the supporting detail available when they need it.

The next time you are about to send a long technical email, pause before you hit send and ask yourself:

“If they only read the first three lines, would they know what I need, why it matters and what I recommend?”

If the answer is yes, you are already communicating like a leader.