How product designers turn research, strategy, decisions, reflections, and learning into shared understanding.
Malik once watched a senior Indonesian diplomat answer a difficult question during a public forum.
The question was sharp. Several groups in the room wanted different outcomes. Journalists needed a clear statement. Officials needed accuracy. Community representatives wanted their concerns acknowledged. A careless phrase could close a door that months of conversation had opened.
The diplomat did not simply speak beautifully. He understood the people in the room, the history behind the question, the consequence of each word, and the action the conversation needed to make possible.
He paused, named the shared concern, separated what had been decided from what was still being discussed, and offered a concrete next step.
The answer worked because it was designed for the situation.
Product designers also work in rooms where people hold different information, incentives, responsibilities, and levels of power. Research can be excellent and still fail to influence a decision. A concept can be strong and still be misunderstood. A presentation can be polished and still leave everyone with a different interpretation.
The Stanford d.school calls the ability to shape understanding with purpose Communicate Deliberately.
🗂️ The Presentation Everyone Approved and Nobody Understood
Malik’s team had spent six weeks studying why small business owners stopped using an invoicing product. They observed users, reviewed behavior data, mapped journeys, and tested early concepts.
At the final stakeholder review, Malik presented fifty-two slides.
The research lead appreciated the detail. The commercial director asked when the new dashboard would launch. Engineering assumed the recommendation was a new notification system. Operations believed the main issue was customer education. The meeting ended with polite nods and no shared decision.
The team had transmitted information without creating common understanding.
Malik first blamed the audience. They had not paid enough attention. Later, he looked again at the deck. The central point was hidden across dozens of findings. Evidence, interpretation, recommendation, and open questions were mixed together. The final slide asked for “feedback” without naming what decision was required.
Communication had been treated as packaging added after the design work.
It needed to be designed as part of the work itself.
🎯 Start With the Change the Communication Must Create
Before rebuilding the story, Malik asked three questions:
- Who is this for?
- What must they understand or feel differently?
- What should become possible after the communication?
For the executive review, the team needed agreement on the problem and approval to test a new product direction. For engineering, the team needed a shared model of the experience and clarity about technical unknowns. For customer support, the team needed to compare research patterns with frontline reality.
One presentation could not serve all three audiences equally well.
Malik created a short executive narrative, a working session for engineering and operations, and a detailed research repository for anyone who needed the evidence. The core truth stayed consistent. The form, depth, and invitation changed.
Deliberate communication is not manipulation. It does not hide inconvenient evidence to win support. It respects the audience enough to make the relevant meaning accessible while preserving the integrity of what is known and unknown.
🧵 Give the Evidence a Narrative Spine
The strongest research communication is not a list of facts. It helps people follow a change in understanding.
Malik rebuilt the executive story around one business owner named Ibu Rina, a composite grounded in several observed patterns. She could create an invoice quickly. The problem began after sending it. She did not know whether the customer had seen it, whether a reminder would feel rude, or when to stop waiting and make a phone call.
The product measured invoice creation. Ibu Rina experienced the product as an uncertain social process of getting paid without damaging a relationship.
From that story, Malik connected the evidence:
- Usage declined after the first invoice cycle, not during initial setup.
- Support tickets clustered around reminders, status, and payment follow-up.
- Users created WhatsApp messages and spreadsheets outside the product to manage the relationship.
- Concepts that offered visibility and tactful follow-up tested better than a more powerful dashboard alone.
The narrative did not replace evidence. It gave the evidence sequence and meaning.
🧭 Separate What We Know, What We Believe, and What We Need to Decide
High-stakes communication becomes confusing when certainty is not labeled.
Malik divided the recommendation into four parts:
- What we observed: behaviors, quotes, support patterns, and data.
- What we believe it means: the team’s synthesis and current point of view.
- What remains uncertain: assumptions requiring experiments or technical discovery.
- What we need today: the specific decision, resource, or participation required.
This structure gave stakeholders room to challenge the right thing. Someone could question the interpretation without dismissing the evidence. Engineering could identify a technical unknown without rejecting the user need. Leadership could approve an experiment without pretending the whole strategy had been proven.
Good communication does not create false certainty. It creates useful clarity about uncertainty.
🤝 Alignment Is Not the Same as Agreement
A diplomat does not expect everyone in a room to want the same thing. The work is to find enough shared understanding for responsible movement.
Product teams are similar. Sales may prioritize adoption. Risk may prioritize protection. Engineering may prioritize reliability. Design may prioritize a coherent experience. These interests can conflict without any group being foolish.
Malik stopped presenting stakeholder objections as resistance. He interviewed key people before the decision meeting and asked what consequences they were responsible for. The risk team worried that automated reminders could become harassment. Sales worried that cautious language would weaken urgency. Support worried that users would not understand new statuses.
The final concept included user-controlled reminder timing, clear message previews, and escalation rules. The communication showed how these decisions responded to the legitimate concerns of each group.
Alignment meant people understood the direction, the tradeoffs, their role, and why the decision had been made. They did not need identical preferences.
🪟 Choose the Medium That Lets People Participate
A slide deck is only one communication form.
Sometimes a prototype allows a faster shared understanding than a long explanation. Sometimes a one-page decision memo is better than a meeting. Sometimes a workshop is necessary because the team must build the meaning together. Sometimes an annotated journey, short video, service role-play, or written narrative lets people see consequences more clearly.
Malik used a prototype to demonstrate the emotional timing of invoice reminders. A static screen could show the wording, but the timed interaction revealed when a reminder felt supportive and when it felt aggressive. Operations used a service blueprint to discuss what happened after a customer replied. Leadership received a concise memo before the meeting so discussion could focus on the decision.
The medium was selected according to the job, not according to habit.
🪞 Communicate Learning, Including Your Own
Communicate Deliberately also includes the ability to express reflections and learning. A team becomes stronger when it can say not only what it made, but how its understanding changed.
Malik opened the revised meeting with a sentence that would have felt uncomfortable weeks earlier:
“We began by assuming users needed a better invoice dashboard. The research showed that the harder problem begins after the invoice is sent, when business owners manage uncertainty and relationships outside our product.”
Naming the change did not make the team look weak. It demonstrated that the design work had produced learning.
It also gave stakeholders permission to update their own views.
Deliberate communication is not performance from a person who was always right. It is the careful construction of shared meaning so a group can think, decide, and learn together.
🕊️ The Sentence That Keeps the Door Open
At the public forum, the diplomat’s answer did not solve the whole conflict. It did something more realistic. It established common ground, clarified the present position, and created a next conversation that could move the issue forward.
Malik’s revised stakeholder meeting ended in a similar way. Leadership approved a limited experiment. Engineering named the technical questions. Risk joined the message design. Nobody believed the work was finished, but everyone understood what would happen next and why.
That is often the real measure of product communication.
Not whether the presenter sounded impressive. Not whether every slide was admired. Not whether all disagreement disappeared.
The measure is whether people can leave with a shared understanding strong enough to support the next responsible action.
Every artifact, meeting, sentence, and silence shapes that understanding. Design them deliberately.
🧺 Takeaways to Bring Into Your Next Project
- Communication is part of design work, not packaging applied after the important decisions.
- Begin with the audience, the intended change in understanding, and the next action.
- Use narrative to connect evidence, meaning, and consequence without replacing evidence.
- Separate observations, interpretations, uncertainties, and decisions.
- Treat alignment as shared understanding of direction and tradeoffs, not identical preference.
- Choose a medium that helps the audience participate in the kind of thinking required.
- Communicate how the team’s understanding changed so learning becomes visible and reusable.
P.S. Next up:
“Navigate Ambiguity: Like a Captain Forging the Route Through the Fog” 👀
🔗 About This Series
This is article 7 of Designerly Thinking: Eight Core Design Abilities, followed by a reflection epilogue. The abilities come from the Stanford d.school and are not intended as a rigid sequence.
- Design Your Design Work: Like Setting Up Your Kitchen Before You Cook
- Learn from Others: Like Watching a Barista Who Knows Your Order and Your Mood
- Synthesize Information: Like Sifting Gold from Sand to Find Meaning in Messy Research
- Rapidly Experiment: Like a Chef Testing Small Portions Before Serving the Full Menu
- Move Between Concrete and Abstract: Like a Doctor Connecting Symptoms to the Larger System
- Build and Craft Intentionally: Like a Watchmaker Engineering Every Gear
- Communicate Deliberately: Like a Diplomat Aligning Allies in a High-Stakes Room
- Navigate Ambiguity: Like a Captain Forging the Route Through the Fog
- Reflection: Like a Warung After Closing, Turning a Busy Day into Better Judgment
