Business Communication
Purpose
This programme is designed to help a technical leader become someone who can:
- Turn complex information into clear decisions
- Communicate confidently with executives and clients
- Explain technical subjects in business language
- Listen with empathy and emotional intelligence
- Influence people without relying on formal authority
- Handle resistance, conflict and difficult questions
- Facilitate productive meetings
- Give feedback and develop team members
- Communicate effectively in writing and speaking
- Maintain composure in high-pressure situations
- Build trust, alignment and accountability
The aim is not simply to become a better speaker.
The aim is to become a leader who helps people:
- Understand the situation
- See why it matters
- Trust the direction
- Contribute meaningfully
- Make decisions
- Take action
Part 1: The Complete Leadership Communication Model
Leadership communication can be organised into twelve capabilities.
Capability 1: Clear thinking
The ability to understand a situation before communicating it.
You should be able to identify:
- The problem
- The relevant facts
- The assumptions
- The business impact
- The available options
- The trade-offs
- Your recommendation
- The risks
- The decision required
- The immediate next step
A communication problem is often a thinking problem.
When you do not understand your own position clearly, you may:
- Speak for too long
- Repeat yourself
- Add unnecessary detail
- Avoid making a recommendation
- Use technical language as protection
- Give information without direction
Clear-thinking exercise
Before an important conversation, complete:
- The current situation is...
- The real problem is...
- This matters because...
- The options are...
- The main trade-off is...
- My recommendation is...
- The evidence is...
- The risk is...
- The decision required is...
- The next step is...
Capability 2: Articulation
Articulation is the ability to express an idea precisely and fluently.
It requires:
- Clear sentence construction
- Appropriate vocabulary
- Logical sequencing
- Concise explanations
- Confident delivery
- Strong transitions
- Relevant examples
- Controlled pace
Articulation is not about using sophisticated vocabulary.
A highly articulate leader can explain a difficult idea using simple language without losing accuracy.
Articulation principles
One idea per sentence
Instead of:
We have reviewed the platform and there are several possible solutions, but there are security concerns and some integration challenges, and we may need additional time.
Say:
We have completed the platform assessment. The preferred solution is technically viable. However, two security dependencies must be resolved before deployment. I recommend extending the pilot by two weeks.
Use verbal signposting
Examples:
- “There are three issues to consider.”
- “The first point concerns business value.”
- “The second concerns delivery risk.”
- “The final point is the decision we need today.”
- “Let me separate the immediate problem from the longer-term opportunity.”
- “The key distinction is...”
- “The implication for the client is...”
- “My recommendation is based on two factors.”
Use precise uncertainty
Do not pretend to know more than you do.
Say:
We have high confidence in the architecture, moderate confidence in user adoption and low confidence in the current cost estimate.
This sounds stronger than:
We are not really sure, but it should probably work.
Capability 3: Audience adaptation
Different audiences need different information.
| Audience | Focus on |
|---|---|
| Executive | Strategic value, financial impact, competitive advantage, organisational risk, options and trade-offs, decisions required |
| CFO or finance | Investment, total cost of ownership, return on investment, unit economics, cost uncertainty, financial risk, benefits realisation |
| CTO or architecture | Technical feasibility, architecture, scalability, security, integration, reliability, operational support |
| Risk and compliance | Accountability, controls, evidence, traceability, legal obligations, residual risk, monitoring, incident management |
| Product or business leader | Customer problem, process improvement, user experience, adoption, operational impact, ownership, measurable outcomes |
| Delivery team | Purpose, scope, priorities, dependencies, responsibilities, deadlines, support |
| Team member | Expectations, development, feedback, recognition, psychological safety, support, ownership |
Audience adaptation exercise
Take one topic and explain it to:
- A CEO
- A CFO
- A CTO
- A risk director
- A project manager
- A junior engineer
The facts should remain consistent, but the emphasis should change.
Capability 4: Vocal delivery
A strong message can lose impact if the delivery sounds rushed, uncertain or monotonous.
Train:
- Pace
- Volume
- Pausing
- Tone
- Emphasis
- Pronunciation
- Energy
- Breathing
- Vocal variety
Pace
Speak slowly enough to be understood.
A useful speaking pace for leadership communication is controlled and conversational. Avoid racing through important points.
Pausing
Pause:
- Before answering a difficult question
- After stating your recommendation
- Before presenting evidence
- Before delivering an important conclusion
- When interrupted
- When emotions are rising
Pausing helps you appear composed and gives the audience time to process.
Emphasis
Emphasise the words that carry meaning.
For example:
The main risk is not the technology. It is user adoption.
Filler-word reduction
Common filler words include: um, like, basically, actually, you know, sort of, kind of, just, maybe, probably.
Do not try to remove every filler word immediately.
First:
- Record yourself
- Count recurring filler words
- Select one filler word
- Replace it with a pause
AI voice-practice prompt
Listen to my spoken response and identify: where I spoke too quickly, where I needed to pause, words I overused, sentences that sounded uncertain, and places where vocal emphasis would improve meaning. Give me only three corrections, then ask me to repeat the answer.
Capability 5: Non-verbal communication
Leadership communication includes how you appear while speaking.
Develop:
- Eye contact
- Facial expression
- Posture
- Hand gestures
- Physical stillness
- Camera positioning
- Attention
- Responsiveness
In-person communication
Aim to:
- Maintain natural eye contact
- Keep an open posture
- Avoid repetitive movements
- Use gestures to reinforce meaning
- Turn towards the person speaking
- Avoid checking devices
- Show attention through facial expression
Virtual communication
Check:
- Camera at eye level
- Face clearly visible
- Appropriate lighting
- Minimal background distractions
- Stable audio
- Looking into the camera during key points
- Avoiding constant self-view monitoring
Self-review exercise
Record a two-minute video and review it once without sound.
Ask:
- Do I look confident?
- Do I look engaged?
- Do my gestures support the message?
- Do I appear tense?
- Do I make distracting movements?
- Does my facial expression match the subject?
Then listen without watching.
Finally, review the complete video.
This separates visual and vocal problems.
Capability 6: Listening and strategic questioning
Strong leaders do not simply speak well. They discover what needs to be said.
Listening has four levels.
| Level | Focus | Question |
|---|---|---|
| 1 | Facts | What happened? |
| 2 | Meaning | What does the person believe the situation means? |
| 3 | Emotion | What are they worried, frustrated or excited about? |
| 4 | Unstated issue | What are they avoiding saying directly? |
Types of leadership questions
| Type | Example |
|---|---|
| Clarifying | What do you mean by “the solution is not ready”? |
| Diagnostic | Which part of the process is creating the delay? |
| Evidence | What evidence supports that assumption? |
| Impact | What happens if we do not resolve this by Friday? |
| Perspective | How does the operations team see this issue? |
| Trade-off | Which is more important in this phase: speed or risk reduction? |
| Ownership | Who is accountable for making this decision? |
| Reflective | What would you do differently if you were starting again? |
| Commitment | What can you commit to completing by the next checkpoint? |
The five-question rule
In discovery, coaching or difficult conversations, ask at least five useful questions before presenting a solution.
This prevents premature problem-solving.
AI listening practice
Act as a client with an unclear business problem. Reveal information gradually. Do not allow me to recommend a solution until I have asked enough questions to understand: the problem, the affected users, the business impact, the existing process, constraints, risks, success measures and decision ownership. At the end, assess the quality of my questions.
Capability 7: Empathy and emotional intelligence
Empathy is understanding another person’s position, emotions and needs.
It does not require agreement.
Use:
Listen → Reflect → Validate → Explore → Respond → Align
| Step | Example |
|---|---|
| Listen | Allow the person to finish. |
| Reflect | It sounds as though the changing priorities have made it difficult for you to plan your work. |
| Validate | That concern is understandable. The scope has changed twice without an adjustment to the timeline. |
| Explore | Which change has had the greatest impact? |
| Respond | We need a stronger change-control process. |
| Align | Let us freeze the scope until Friday and review future changes together. |
Emotional self-management
When triggered, use:
Pause → Label → Separate → Choose → Respond
| Step | Example |
|---|---|
| Pause | Do not react immediately. |
| Label | Identify the emotion: “I am feeling defensive.” |
| Separate | Separate fact from interpretation. The fact is that my proposal was challenged. My interpretation is that they do not trust my judgement. |
| Choose | Decide the outcome you want: “I want to understand the risk they see and maintain a productive discussion.” |
| Respond | Can you explain which assumption concerns you most? |
Emotional trigger journal
| Situation | Emotion | Automatic response | Impact | Better response |
|---|---|---|---|---|
| My design is challenged | Defensive | Over-explain | Audience loses trust | Ask what risk they see |
| Deadline is missed | Frustrated | Focus on blame | Team becomes guarded | Diagnose dependency |
| Executive interrupts | Anxious | Rush answer | Message becomes unclear | Pause and answer directly |
Capability 8: Storytelling
Facts create understanding. Stories create meaning and memory.
Leadership storytelling should be concise and purposeful.
Use:
Context → Tension → Decision → Action → Result → Lesson
Example:
The customer-service team was handling thousands of repetitive requests every week. Response times were increasing and employees were spending less time on complex cases. We introduced a controlled AI assistant that handled routine enquiries and escalated uncertain cases to people. Within the pilot, handling time improved while human oversight was maintained. The important lesson was that workflow integration mattered more than model sophistication.
Types of leadership stories
- Customer story
- Transformation story
- Failure and learning story
- Vision story
- Values story
- Team-recognition story
- Risk story
- Innovation story
- Change story
Storytelling rules
- Use one central message
- Avoid unnecessary background
- Include a meaningful tension
- Explain the decision
- Show the outcome
- End with the lesson
- Do not exaggerate
- Protect confidential information
AI storytelling exercise
Give me a leadership topic and ask me to tell a two-minute story using context, tension, decision, action, result and lesson. Identify unnecessary detail, missing tension and whether the final lesson is clear.
Capability 9: Data storytelling
Leaders often need to turn data into decisions.
Use:
Observation → Meaning → Cause → Implication → Recommendation
| Step | Example |
|---|---|
| Observation | Customer-service handling time increased by 18%. |
| Meaning | The team is becoming less efficient as demand grows. |
| Cause | Most of the increase comes from repetitive identity and account queries. |
| Implication | Without process intervention, service levels will continue to decline. |
| Recommendation | Automate the high-volume repetitive queries while maintaining human escalation for complex cases. |
Avoid presenting data without interpretation
Weak:
The chart shows an 18% increase, 12% decrease and a 7% variation.
Stronger:
The main message is that demand is growing faster than team capacity. Most of the pressure comes from three repetitive enquiry types. Addressing those could remove approximately half of the avoidable workload.
Data presentation questions
Before presenting data, ask:
- What is the main message?
- Why does it matter?
- What caused it?
- What decision should it influence?
- What uncertainty exists?
- What should happen next?
Capability 10: Influence and persuasion
Influence is not manipulation.
It is helping people evaluate a recommendation and commit to action.
Use:
Stakeholder concern → Shared objective → Evidence → Trade-off → Recommendation → Commitment
Example:
I understand your concern about increasing the pilot budget. We both want to prove value before committing to production. The additional cost comes from security testing and evaluation, which are required to establish whether deployment is responsible. We could reduce the initial cost by narrowing the use-case scope rather than removing those controls. My recommendation is to preserve the controls and reduce the number of workflows in the pilot. Can we agree that approach today?
Principles of ethical persuasion
- Understand the stakeholder’s interests
- Use evidence honestly
- Make uncertainty visible
- Explain trade-offs
- Avoid artificial urgency
- Do not hide material risk
- Give stakeholders meaningful choice
- Seek durable agreement rather than temporary compliance
Influence without authority
When you cannot command action, build:
- Credibility
- Relationships
- Shared goals
- Evidence
- Reciprocity
- Coalition support
- Clear benefits
- Low-friction next steps
Stakeholder influence map
| Stakeholder | Interest | Influence | Main concern | Desired outcome | Communication approach |
|---|---|---|---|---|---|
| CFO | Cost and value | High | Uncertain return | Pilot approval | Quantify cost and benefits |
| Risk director | Compliance | High | Data exposure | Control agreement | Show safeguards and evidence |
| Product owner | Adoption | Medium | Workflow disruption | Operational ownership | Focus on user experience |
| Engineering lead | Feasibility | Medium | Integration complexity | Technical support | Clarify architecture and dependencies |
Capability 11: Negotiation and conflict management
Conflict often comes from:
- Different objectives
- Competing priorities
- Unclear ownership
- Limited resources
- Different risk tolerances
- Poor information
- Past relationship problems
- Misunderstood intentions
Conflict-resolution framework
Position → Interest → Evidence → Options → Trade-off → Agreement
| Step | Question |
|---|---|
| Position | What is each person asking for? |
| Interest | Why do they want it? |
| Evidence | What facts matter? |
| Options | What alternatives exist? |
| Trade-off | What does each option gain or sacrifice? |
| Agreement | What will happen, who owns it and when? |
Example:
You are requesting production deployment this month. I am recommending an extended pilot. It appears that your main concern is the commercial deadline, while mine is the unresolved safety threshold. Let us separate the launch date from the full production scope. We could launch with a smaller user group while completing the remaining evaluation. That protects the market commitment while reducing exposure.
De-escalation language
- “Let us slow this down and separate the issues.”
- “I think we agree on the objective but differ on the risk.”
- “Can we identify the assumption behind each position?”
- “What evidence would change your view?”
- “Let us focus on the decision rather than the person.”
- “I may be missing something. Help me understand your concern.”
- “We do not need complete agreement, but we do need a workable decision.”
AI conflict practice
Act as a senior stakeholder who disagrees strongly with my recommendation. Make the disagreement realistic but professional. Evaluate whether I: remain calm, understand the underlying interest, avoid becoming defensive, use evidence, offer alternatives and establish a clear agreement.
Capability 12: Leadership presence
Leadership presence is the combined effect of:
- Clarity
- Calmness
- Credibility
- Confidence
- Consistency
- Judgement
- Empathy
- Accountability
It does not mean being loud, dominant or always certain.
Behaviours that strengthen presence
- Leading with the main point
- Speaking at a controlled pace
- Holding pauses
- Making clear recommendations
- Admitting uncertainty precisely
- Listening without becoming passive
- Staying calm when challenged
- Taking accountability
- Giving credit to others
- Making decisions
- Following through
Behaviours that weaken presence
- Speaking without structure
- Over-explaining
- Apologising unnecessarily
- Avoiding recommendations
- Becoming defensive
- Blaming others
- Using excessive jargon
- Interrupting
- Changing position without explanation
- Failing to close discussions with action
Part 2: Core Leadership Communication Frameworks
Do not use frameworks mechanically. Use them to organise thinking.
Framework 1: Executive update
Position → Impact → Recommendation → Risk → Decision
The programme is two weeks behind because identity integration remains unresolved. The delay affects the pilot start date but not the overall business case. I recommend moving the training and evaluation work forward while the identity issue is resolved. The principal risk is compressed testing time. We need agreement today on the revised sequencing.
Framework 2: Recommendation
Recommendation → Reasons → Evidence → Trade-off → Action
I recommend option B. It offers the best balance of implementation speed, security and operating cost. The main trade-off is reduced flexibility during the pilot. We need approval to begin detailed design.
Framework 3: Technical explanation
Problem → Concept → Mechanism → Value → Limitation → Example
The problem is that a general language model does not automatically know the company’s current policies. Retrieval-augmented generation solves this by finding relevant approved documents and providing them to the model before it responds. This improves accuracy and traceability. It does not eliminate hallucination, so evaluation and output controls remain necessary.
Framework 4: Difficult feedback
Situation → Behaviour → Impact → Expectation → Support
In Tuesday’s client meeting, the estimate was presented as confirmed before the assumptions were validated. This reduced confidence in the plan. In future, I need confirmed estimates and assumptions to be clearly separated. I will help review the next update before the meeting.
Framework 5: Empathetic conversation
Acknowledge → Clarify → Explore → Respond → Align
I understand that the repeated changes have been frustrating. Which change has affected your work most? What would help stabilise the plan? I agree that we need clearer scope control. Let us review all new requests together until the current sprint is complete.
Framework 6: Objection handling
Acknowledge → Answer → Evidence → Trade-off → Recommendation
I understand the concern about cost. The additional expense comes from the production security controls. Removing them would lower the initial cost but increase regulatory and operational exposure. My recommendation is to retain the controls and reduce the pilot scope.
Framework 7: Crisis update
Incident → Impact → Containment → Investigation → Recovery → Accountability
A data-processing error affected a limited number of pilot transactions. The process has been stopped and access has been restricted. We are determining the root cause and validating the affected records. No production systems are involved. The next update will confirm impact, corrective action and restart criteria.
Framework 8: Meeting facilitation
Purpose → Outcome → Agenda → Discussion → Decision → Owner → Deadline
The purpose of today’s meeting is to choose the use case for the pilot. By the end, we need one prioritised use case, an accountable business owner and agreement on the discovery plan.
Part 3: Meeting Leadership and Facilitation
A strong leader does not only contribute to meetings. They shape the quality of the discussion.
Before the meeting
Define:
- Why the meeting is required
- What outcome is needed
- Which decisions must be made
- Who needs to attend
- What preparation is required
- What information should be shared beforehand
- What could block the discussion
Opening the meeting
State:
- Purpose
- Required outcome
- Agenda
- Time available
- Decision method
Example:
The purpose of today’s session is to agree whether the finance-document use case should proceed to pilot. By the end, we need a decision, named owners and agreement on the first two weeks of work. We have 45 minutes. I suggest we confirm the business case, review risk and feasibility, and then make the decision.
During the meeting
Practise:
- Summarising
- Redirecting
- Inviting quieter voices
- Managing dominant speakers
- Separating facts from opinions
- Identifying disagreement
- Testing assumptions
- Clarifying decisions
- Protecting time
Useful facilitation language
- We have heard two different positions. Let me summarise them.
- I would like to hear from people who have not spoken yet.
- Is that a confirmed fact or an assumption we need to validate?
- We are discussing implementation detail before agreeing the decision.
- What would need to be true for us to support this option?
- We have ten minutes remaining. Which issue must we resolve today?
Closing the meeting
Confirm:
- Decisions
- Actions
- Owners
- Deadlines
- Dependencies
- Open questions
- Next checkpoint
Example:
We have agreed to proceed with the pilot. Sarah owns business requirements, Ahmed owns security assessment and I will coordinate the solution design. The first checkpoint is Thursday. The only open issue is confirmation of data access.
Part 4: Written Leadership Communication
Leaders must also communicate clearly through:
- Chat
- Proposals
- Decision papers
- Executive summaries
- Risk updates
- Meeting notes
- Status reports
- Presentations
The BLUF method
BLUF means “Bottom Line Up Front.”
Put the main point first.
Weak:
Over the past few weeks, the team has been reviewing the data, and there have been several discussions with security and operations...
Stronger:
I recommend delaying the pilot by one week because the data-access approval remains unresolved.
Then provide:
- Reason
- Impact
- Options
- Risk
- Action
Leadership email structure
| Section | Purpose |
|---|---|
| Opening | State the purpose. |
| Context | Provide only what the recipient needs. |
| Recommendation or request | Make the required action explicit. |
| Deadline | State when it is needed. |
| Supporting detail | Include concise evidence. |
Example:
I recommend approving the revised pilot scope by Wednesday. The original scope depends on two data sources that are not yet cleared for use. Reducing the pilot to the approved data will preserve the launch date and allow evaluation to begin. Please confirm whether you support the revised scope.
Writing-quality checklist
Before sending, ask:
- Is the purpose clear in the first two sentences?
- Is the requested action explicit?
- Is the message appropriate for the recipient?
- Is any detail unnecessary?
- Are risks presented accurately?
- Are dates and ownership clear?
- Could the tone be misinterpreted?
- Is there confidential information that should be removed?
- Does the message create clarity or additional discussion?
Part 5: Cross-Cultural and Inclusive Communication
In global organisations, communication styles differ.
Differences may include:
- Direct versus indirect communication
- Hierarchical versus informal interaction
- Comfort with disagreement
- Use of silence
- Decision-making speed
- Written versus verbal preference
- Attitudes towards risk
- Use of humour
- Expectations around feedback
Inclusive communication principles
- Avoid assuming silence means agreement
- Explain unfamiliar terminology
- Do not rely heavily on idioms
- Provide written summaries
- Invite input in multiple ways
- Avoid interrupting people who need more processing time
- Clarify decisions explicitly
- Pronounce names correctly
- Give credit accurately
- Avoid interpreting communication style as capability
Inclusive meeting questions
- We have heard several views. Is there a perspective we are missing?
- Would anyone prefer to add comments after the meeting in writing?
- Before we decide, can each workstream confirm its main concern?
Part 6: Crisis and High-Pressure Communication
During a crisis, people need:
- Accuracy
- Calmness
- Transparency
- Direction
- Accountability
- Regular updates
Crisis principles
- State what is known
- State what is unknown
- Avoid speculation
- Explain immediate containment
- Define ownership
- Set the next update point
- Protect confidentiality
- Correct misinformation quickly
- Do not minimise the impact
- Do not assign blame before investigation
Crisis update template
At 10:15, we identified an issue affecting the pilot data-processing workflow. The workflow has been paused and access restricted. We are currently validating the scope and root cause. There is no evidence at this stage that production data is affected. The incident lead is Sarah. The next confirmed update will cover impact, corrective action and restart criteria.
Part 7: The 16-Week Communication Development Roadmap
Week 1: Clear thinking
Focus: Main point, problem definition, recommendation, decision clarity
Daily practice: Convert one work situation into a six-line executive summary; separate fact, assumption and opinion; state the decision required
Success measure: You can explain a situation in under one minute without losing the main point.
Week 2: Structure
Focus: Logical sequencing, signposting, grouping ideas, clear openings and endings
Daily practice: Use Situation → Impact → Recommendation → Risk → Action
Success measure: Listeners can repeat your main message accurately.
Week 3: Conciseness
Focus: Shorter sentences, reduced repetition, fewer filler words, answer-first communication
Daily practice: Deliver the same message in three minutes, ninety seconds, forty-five seconds, twenty seconds and one sentence
Success measure: You retain meaning while reducing length.
Week 4: Vocal delivery
Focus: Pace, pausing, tone, emphasis, breathing, filler reduction
Daily practice: Record one two-minute response. Review pace, pauses, filler words, energy, clarity and emphasis
Success measure: You sound controlled and confident rather than rushed.
Week 5: Non-verbal communication
Focus: Eye contact, posture, gestures, facial expression, camera presence
Daily practice: Record a video explanation and review it without audio
Success measure: Your physical delivery supports rather than distracts from your message.
Week 6: Audience adaptation
Focus: Executive, commercial, technical, risk and team language
Daily practice: Explain one issue to three different stakeholders
Success measure: Each explanation focuses on the audience’s concerns.
Week 7: Listening
Focus: Clarifying, summarising, reflecting, identifying unstated concerns
Daily practice: Complete one AI scenario where you cannot recommend a solution until you summarise the problem accurately
Success measure: The other person confirms that you understand their position.
Week 8: Questioning and discovery
Focus: Diagnostic, evidence, impact, trade-off and ownership questions
Daily practice: Run one client-discovery simulation
Success measure: You uncover the business problem before discussing technology.
Week 9: Empathy and emotional intelligence
Focus: Emotional awareness, validation, self-management, perspective-taking
Daily practice: Role-play one frustrated stakeholder conversation
Success measure: You acknowledge concerns without losing direction.
Week 10: Storytelling
Focus: Context, tension, decision, result, lesson
Daily practice: Tell one two-minute business story
Success measure: The audience remembers the message and lesson.
Week 11: Data storytelling
Focus: Insight, meaning, implication, recommendation
Daily practice: Choose one chart or metric and explain what decision it should influence
Success measure: You move beyond describing numbers to interpreting them.
Week 12: Influence
Focus: Stakeholder concerns, shared objectives, evidence, trade-offs, commitment
Daily practice: Present one recommendation to a sceptical AI stakeholder
Success measure: You secure a specific commitment or identify the true barrier.
Week 13: Negotiation and conflict
Focus: Interests, options, trade-offs, de-escalation, agreement
Daily practice: Run one disagreement scenario
Success measure: You remain calm and produce a workable next step.
Week 14: Feedback and coaching
Focus: Specific feedback, behaviour and impact, development questions, accountability, support
Daily practice: Give one simulated feedback conversation using Situation → Behaviour → Impact → Expectation → Support
Success measure: The feedback is clear, fair and actionable.
Week 15: Meeting facilitation
Focus: Purpose, outcomes, participation, time management, decisions, follow-up
Daily practice: Facilitate a simulated steering meeting
Success measure: The meeting produces decisions, owners and deadlines.
Week 16: Integrated leadership communication
Focus: Executive update, empathy, influence, risk, conflict, decision-making
Run simulations involving:
- A delayed programme
- A budget challenge
- A client escalation
- A team-performance issue
- A security incident
- A disagreement between business and technology
Success measure: You maintain clarity, composure and empathy while moving the situation forward.
Part 8: Weekly Practice Structure
| Day | Focus | Practise |
|---|---|---|
| Monday | Clarity | Executive updates, recommendations, decision requests |
| Tuesday | Explanation | Technical-to-business translation, data storytelling, examples and analogies |
| Wednesday | Listening and empathy | Discovery, coaching, difficult team conversations |
| Thursday | Influence and challenge | Objections, negotiation, conflict, sceptical stakeholders |
| Friday | Integrated simulation | Steering committees, client presentations, crisis updates, decision meetings |
Part 9: Daily Practice Routine
Full 30-minute version
| Block | Duration | Activity |
|---|---|---|
| Preparation | 5 minutes | Choose scenario, audience, objective, skill and time limit |
| First attempt | 3 minutes | Respond without AI assistance |
| Feedback | 5 minutes | Ask AI for main strength, highest-leverage weakness, audience interpretation and specific correction |
| Targeted drill | 5 minutes | Practise only the weakness |
| Second attempt | 3 minutes | Repeat the full response |
| Challenge | 3 minutes | Handle one objection or interruption |
| Compression | 3 minutes | Deliver a 30-second version |
| Reflection | 3 minutes | Record what improved, what remains difficult and where to apply the lesson |
Ten-minute minimum version
- Choose one scenario
- Give a one-minute response
- Ask AI for one weakness
- Repeat the response
- Give a 20-second summary
Part 10: AI Practice Modes
Use AI in different modes to avoid repetitive practice.
| Mode | Role |
|---|---|
| 1. Coach | AI evaluates your communication |
| 2. Stakeholder | AI plays a specific audience |
| 3. Interrupter | AI interrupts when you become unclear or too technical |
| 4. Challenger | AI raises objections |
| 5. Listener | AI summarises what it understood from your explanation — reveals whether your message was actually clear |
| 6. Simplifier | AI identifies jargon and complexity |
| 7. Question coach | AI evaluates the quality of your questions |
| 8. Meeting simulator | AI creates several stakeholders with conflicting interests |
| 9. Writing editor | AI assesses emails, proposals and executive summaries |
| 10. Progress tracker | AI records recurring weaknesses and revisits them later |
Part 11: Master AI Communication Coach Prompt
Copy and use this prompt at the start of a practice session:
You are my leadership communication, articulation and executive-presence coach.
I am developing as an AI Solution Engineering Manager. I need to communicate effectively with executives, clients, business leaders, technical teams, risk stakeholders and delivery teams.
Train me through realistic deliberate practice rather than lectures.
At the beginning of each session, define:
- The scenario
- My role
- The audience
- The objective
- The communication skill being tested
- The time limit
Ask me to respond without preparation.
After my response:
- Summarise what you understood from my message.
- Score me from 1 to 5 on: Main point, Structure, Conciseness, Audience relevance, Business value, Evidence, Risk judgement, Confidence, Empathy, Listening, Action orientation, Vocal delivery, Executive presence
- Identify the single highest-leverage weakness.
- Explain: the behaviour, how the audience may interpret it, and the specific correction.
- Give me one short drill targeting that weakness.
- Ask me to repeat the response immediately.
- Challenge me with one realistic objection.
- Ask me to provide a 30-second executive version.
Do not write the ideal answer until I have attempted the scenario twice.
Do not provide generic praise.
Make the feedback behavioural, specific and demanding.
Track recurring weaknesses during the conversation.
Increase the difficulty as my performance improves.
Vary scenarios across:
- Executive updates
- Client discovery
- Commercial recommendations
- Technical explanations
- Risk escalation
- Difficult feedback
- Team conflict
- Negotiation
- Crisis communication
- Steering committees
- Storytelling
- Data presentations
- Written communication
Part 12: Communication Measurement System
Daily scorecard
Rate each area from 1 to 5.
| Capability | Question |
|---|---|
| Main point | Did I state the conclusion early? |
| Structure | Was the message easy to follow? |
| Conciseness | Did I remove unnecessary detail? |
| Audience relevance | Did I address stakeholder priorities? |
| Confidence | Did I communicate a clear position? |
| Evidence | Did I support my recommendation? |
| Risk judgement | Did I explain risks and controls? |
| Empathy | Did I acknowledge concerns? |
| Listening | Did I respond to the real question? |
| Questioning | Did I ask useful questions? |
| Action orientation | Was the next step clear? |
| Vocal delivery | Was my pace and tone controlled? |
| Non-verbal delivery | Did my physical presence support the message? |
| Executive presence | Did I create confidence and direction? |
Weekly indicators
Track:
- Number of AI practice sessions
- Number of repeated attempts
- Average score
- Most common weakness
- Strongest improvement
- Number of real-world applications
- Human feedback received
- Meetings where decisions were clarified
- Situations where you handled disagreement calmly
Monthly review
Ask:
- Which communication situations still make me uncomfortable?
- Which audience is hardest for me?
- Do I speak too much or too little?
- Do I present recommendations clearly?
- Do I avoid difficult conversations?
- Do I listen before solving?
- Do I adapt language appropriately?
- Do people understand what action is required?
- Am I becoming more concise?
- Am I creating more trust?
Part 13: The Communication Practice Journal
| Date | Scenario | Audience | Skill | First score | Second score | Main weakness | Correction | Real use |
|---|---|---|---|---|---|---|---|---|
| Monday | Project delay | Partner | Clarity | 3 | 4 | Recommendation came late | Lead with answer | Weekly review |
| Tuesday | AI investment | CFO | Commercial language | 2 | 4 | Too technical | Translate to cost and value | Budget meeting |
| Wednesday | Team overload | Engineer | Empathy | 3 | 4 | Solved too quickly | Ask two questions first | One-to-one |
| Thursday | Security objection | Risk director | Influence | 3 | 4 | Did not explain trade-off | Compare options clearly | Design review |
Part 14: Real-World Transfer
AI practice only matters if it improves real behaviour.
Before an important interaction
Prepare:
- What is my main point?
- Why does it matter to this audience?
- What evidence supports it?
- What is the likely objection?
- What emotion may be present?
- What decision or action do I need?
- What should my final sentence be?
During the interaction
Remember:
- Lead with the conclusion
- Pause
- Listen
- Ask questions
- Acknowledge concerns
- Use simple language
- Clarify trade-offs
- Define action
After the interaction
Review:
- What did the audience understand?
- Where did I lose clarity?
- What objection surprised me?
- Did I listen properly?
- Did I appear defensive?
- Was a decision made?
- Were ownership and deadlines clear?
- What will I change next time?
Part 15: Human Feedback System
AI should support, not replace, human feedback.
Every two weeks, ask a trusted colleague:
- What is one communication behaviour I should continue?
- What is one behaviour I should change?
- In which situations am I least clear?
- Do I give enough context or too much detail?
- Do I listen before responding?
- How do I come across when challenged?
Every month, ask someone senior:
- What would make my communication appear more credible and leadership-ready?
Record the answers and test them during AI practice.
Part 16: The Most Important Rules
- Speak before asking AI for an ideal answer.
- Practise realistic leadership situations.
- Focus on one weakness at a time.
- Repeat immediately after feedback.
- Practise both speaking and listening.
- Train verbal and non-verbal delivery.
- Practise written communication.
- Adapt messages to different audiences.
- Increase difficulty gradually.
- Use human feedback alongside AI.
- Apply at least one lesson in real work every week.
- Track recurring patterns.
- Practise difficult situations, not only comfortable ones.
- Do not confuse confidence with certainty.
- Do not use empathy as a way to avoid accountability.
- Do not finish a session after feedback; always perform the correction.
- Do not memorise scripts; memorise structures.
- Do not aim to sound impressive; aim to create understanding and action.
Final Leadership Communication Standard
Before finishing any important message, check whether you have answered:
- What is happening?
- Why does it matter?
- What do I recommend?
- What evidence supports it?
- What are the risks and trade-offs?
- What does the audience care about?
- What decision or action is required?
- Who owns the next step?
- When will it happen?
Your communication is successful when people leave with:
- Greater clarity
- Greater trust
- A shared understanding
- A responsible decision
- Clear ownership
- Commitment to action
Practice checklist
- I completed one clear-thinking exercise before a real conversation
- I practised one framework from Part 2 aloud
- I ran at least one AI practice mode this week
- I logged scores in the daily scorecard
- I applied one lesson in a real meeting or email
Discussion
Comments
Share feedback or questions about this page. No account required.
Loading comments…