Transformation functions face a distinctive communication problem: they often bring executives an issue that has not yet become one of their top priorities.
The CEO already has customers, earnings, capital, people and risk. The plant director has output, quality, equipment and staffing. Then the team arrives and says:
We would like to discuss the development of our operating system.
The topic may matter, but it has already lost the competition for attention. The executive must first become interested in the method and then connect it to the business.
The transformation team's first question should be different:
Why should this executive give the issue the next 30 seconds?
Start with the business, not the tool
Weak:
We propose implementing Lean Daily Management.
Stronger:
Plant leaders discover a significant share of performance deviations two to three days after they occur—when recovering the lost output is no longer possible.
The first message describes the transformation team's product. The second identifies a mechanism through which the business loses results.
Lean, Agile, process mining, artificial intelligence or a new operating model may sit inside the solution. The name of a method is rarely the reason an issue deserves executive time.
Two passes into the conversation
To keep an executive listening, the team must quickly earn two forms of trust:
- Relevance: the issue affects my result, customer, risk or ability to manage the system.
- Credibility: the team understands the real operation, has evidence and is not merely selling a methodology.
Without relevance, the conversation does not start. Without credibility, it does not progress toward a decision.
The communication sequence
The diagram is a left-to-right sequence: establish business tension, explain why the issue matters now, state the mechanism hypothesis, compare change options, recommend, request a leadership action and make evidence accessible.
Business tension
What is happening in the business or management system? Use an observable fact, not the evaluative word “inefficient.”
Why now
What changed? What is the cost of delay? Is there an opportunity window? Urgency should follow from evidence, not drama.
Mechanism hypothesis
What does the team believe is producing the observed outcome? Explicitly label a hypothesis as a hypothesis.
Change options
What real actions are available, including a limited pilot, a staged decision and a deliberate wait-and-learn option?
Team position
What do you recommend and why? An executive should not have to infer your position from twenty slides.
Leadership action
What specifically should the recipient do within their authority?
30 seconds → 3 minutes → 30 minutes
The amount of information should grow with the executive's readiness to engage. Each level reveals more evidence while preserving the same decision logic.
30 seconds: earn the continuation
Answer three questions:
- What is happening?
- Why does it matter?
- Why now?
Example:
OTIF has fallen from 94% to 87%, and delays now affect our three largest customers. In 68% of reviewed cases, orders lose time at two cross-functional handoffs with no common owner. We would like to show options for testing that mechanism.
The objective is not to win a budget in 30 seconds. It is to hear: “Show me.”
3 minutes: show the decision architecture
The executive needs:
- a decision question;
- two to four material facts;
- a mechanism hypothesis;
- real alternatives;
- a recommendation and its main risk;
- a specific request.
Example:
We reviewed 120 delayed orders. In 68% of cases, the largest loss occurs at two cross-functional handoffs. We considered a local fix, a cross-functional pilot, an enterprise redesign and a wait-and-learn option. We recommend a two-month pilot because it tests the mechanism with limited risk. We need a business owner and participation from three functions.
30 minutes: enable scrutiny
This level includes source data and sample quality, alternative explanations, causal logic, option economics, sensitivity to assumptions, constraints, organisational change capacity, milestones and stop conditions.
Progressive disclosure does not hide complexity. It creates sequential access to the same logic.
Information may be absent from the first screen. A fact capable of changing the decision must be accessible before the choice is made.
One initiative, four conversations
The same presentation for every level will almost inevitably be weak for at least three of them.
| Audience | Primary question |
|---|---|
| CEO / owner | Why does this matter to enterprise performance and risk? |
| Functional executive | How will this change my management system and accountabilities? |
| Business-unit leader | What will my team need to do differently? |
| Front-line leader | What changes in tomorrow morning's work? |
The facts and decision logic remain consistent. Depth, language, the recipient's action and the link to their responsibility change.
Three synthetic examples
Equipment performance
Weak:
We propose implementing OEE meetings, visual management and standard work.
Stronger:
Over 12 weeks, the company lost 430 hours of equipment availability. Sixty-one per cent of repeated losses relate to causes recorded before. The management cycle is not converting failure information into system change. Repeated losses declined at one area after the review cycle changed. We recommend testing whether that mechanism transfers to three other areas.
A concrete sponsorship request
Weak:
We need your support for the project.
Stronger:
Appoint the end-to-end process owner; review metric X personally every two weeks for three months; accept escalation when two functions cannot agree within 48 hours.
Support stops being a sentiment and becomes observable management behaviour.
Disagreement as a good outcome
The team recommends scaling a practice. The CEO responds:
The evidence is not sufficient. Run a second pilot under different conditions.
If the executive understood the question, saw the alternatives, assessed uncertainty and can explain the decision, the communication worked—even though the author's recommendation was rejected.
The objective of executive communication is not agreement with the author. It is decision quality.
Team diagnostic
Score each statement: 0 — no, 1 — sometimes, 2 — consistently. This scale is intended for reflection, not formal certification.
- The first 30 seconds start with a business problem, not a method.
- We can describe the scale with one or two numbers.
- Urgency is evidence-based.
- The problem mechanism is framed as a testable hypothesis.
- We distinguish facts, forecasts, assumptions and recommendations.
- The request is a specific leadership action.
- Alternatives remain visible.
- We show the main risk of our own option.
- The message changes for the audience level.
- The short version leads to source evidence.
Indicative interpretation:
- 17–20: the team operates as an executive decision partner;
- 12–16: strong content, inconsistent executive communication;
- 7–11: the team explains transformation instead of connecting it to the business;
- 0–6: the executive must find the answer to “why should I care?” without the team's help.
Practise the tension
Use the Decision Room simulation to build a 30-second entry, present four options, respond to executive challenge and discover which material facts were lost under time pressure.
Before the simulation, review Clarity Without Manipulation. Use the Executive Communication Toolkit when preparing a real committee submission.