Effective communication
Stop interpreting, start asking
Most communication problems do not come from saying too little. They come from assuming too much. And interpretation becomes certainty. Certainty without verification becomes friction.
If something matters, do not guess. Ask. Effective communication starts with three things: Ask. Clarify. Confirm.
Communication is not about expressing yourself. It is about creating shared understanding. Instead of assuming, ‘They clearly don’t support this,’ ask: ‘What is your concern about this approach?’
Instead of assuming, ‘They must be unhappy with my work,’ ask: ‘Is there anything in the result you’d like me to adjust?’
Interpretation fills gaps with assumptions. Questions fill gaps with information.
Separate facts from interpretation
A fact can be checked. An interpretation is the meaning you attach to it. Fact: The deadline moved from Tuesday to Thursday.
Interpretation: They don’t take the project seriously. Problems begin when interpretations are treated as facts. Before reacting, ask: What do I actually know?
What am I assuming?
This prevents unnecessary conflict.
Be responsive, not responsible for everything
Responsiveness is valuable: acknowledge, clarify, act where appropriate. Feeling responsible for everything is harmful:
• absorbing problems that aren’t yours
• owning other people’s emotions
• stepping into decisions that aren’t yours
• trying to solve every loose end
That blurs boundaries.
Strong professionals respond, they don’t automatically take over.
Define roles before communication becomes political
Many ‘communication problems’ are actually role problems.
Conflicts arise when:
• two people think they own the same decision
• no one knows who has final responsibility
• many contribute but no one is accountable
• one person thinks they advise, another thinks they decide
Clear roles answer:
• Who owns the outcome?
• Who decides?
• Who contributes?
• Who needs to know?
When roles are clear, communication becomes easier.
Make ownership explicit
Avoid vague endings like: ‘We’ll take care of it.’ Who is we?
Better: ‘I’ll update the proposal by Wednesday. You review it Thursday morning. We decide Thursday afternoon.’
Clear communication needs: Action → Owner → Deadline
Structure the message
Complex information becomes easier when structured. For experience-based communication: Situation → Action → Result
For communicating a problem upward: Situation → Impact → Recommendation
Example:
• Situation: Customer onboarding is slower than expected.
• Impact: Delays affect activation and increase support requests.
• Recommendation: Move technical setup earlier and assign one clear owner.
Senior communication works best when the listener quickly understands:
What is happening?
Why does it matter?
What should happen next?
Match the information to the audience
More information is not always better. Different roles need different detail.
• Developer → technical dependency
• Recruiter → candidate journey impact
• CTO → architectural risk and resources
• CEO → business consequence and decision required
Good communication adapts the message to the audience.
Say what you need
Vague requests create vague outcomes.
‘Can you look at this?’
vs.
‘Please review the pricing section and tell me by Thursday whether you approve it or want changes.’
Before sending something important, check:
What exactly am I asking for?
From whom?
By when?
Disagree with the issue, not the person
Disagreement is normal. Personalising it is optional.
‘You’re wrong.’
vs.
‘I see a different risk here.’
Strong communication makes disagreement specific:
• the assumption
• the evidence
• the priority
• the proposed action
Attach disagreement to the issue, not the person.
Close the feedback loop
Sending information ≠ communicating it.
For important topics, confirm: ‘Does that match your understanding?’ or ‘Can we confirm who owns the next step?’
Assumed understanding is how problems travel quietly.
Choose the right medium
Not every message belongs in the same channel.
Quick coordination → chat
Documented decision → email or project system
Complex disagreement → conversation
Sensitive issue → more than text
As nuance rises, text becomes less reliable.
Sometimes the best message is: ‘Let’s talk for ten minutes.’
Listen for information, not your next answer
Most listening is just waiting to respond. Real listening means:
What are they actually saying?
What is unclear?
What should I ask next?
Understanding accurately comes before responding.
Communicate early
Bad news does not improve with time. Raise risks, delays, disagreements early.
Early communication gives options. Late communication gives surprises.
Do not confuse confidence with certainty
Strong communication does not require pretending to know everything. ‘I don’t know yet. I’ll check and come back by 3 PM.’
Trust grows when people know which parts are:
• facts
• judgment
• uncertainty
Know when the conversation is finished
Repeating the same point does not strengthen communication. A conversation is complete when:
the decision is clear
ownership is clear
the next step is clear
Then move on.
The ferdge communication formula
Before you speak:
Fact → Purpose → Audience
During the conversation:
Say → Ask → Listen → Clarify
Before you finish:
Decision → Owner → Deadline
Effective communication is not about saying more.
It is about reducing uncertainty.
Ask instead of assuming. Clarify instead of interpreting.
Create shared understanding.

