A Partner Exercise for Clearer Written Communication
See also: Common Mistakes in WritingYou send a carefully prepared update, but a colleague replies with a question you thought the message had already answered. It is tempting to conclude that they did not read it properly. A more useful response is to investigate what they understood, what they missed and which parts of your message attracted their attention first. That conversation develops communication skills as well as improving the document.
This partner exercise uses a short written message to practise perspective-taking, active listening and constructive feedback. It works for colleagues, students or volunteers and does not require design experience. The aim is to make a request easier to understand while learning how to discuss another person's work respectfully. Typography enters the exercise as one practical tool: headings, emphasis and spacing can support a message, but they cannot replace clear wording or a shared understanding of the task.
Agree on the task before looking at the wording
Choose a low-stakes message that asks a reader to do something: review two options, prepare for a meeting or contribute to a shared plan. Remove confidential information and use a fictional example if necessary. One participant becomes the writer and the other the reader. You will exchange roles later so that both people experience giving and receiving feedback.
The writer privately records three things: the action requested, the reason it matters and the information the reader needs to respond. The reader should not see this note yet. It provides a reference against which to compare the actual interpretation, rather than relying on the writer's assumption that the message is obvious.
Agree that the exercise concerns the message, not either person's intelligence or competence: feedback should be about behaviour not personality. Here, that means discussing an observable choice, such as where a deadline appears, and the effect it had on the reader. It does not mean diagnosing someone as careless or bad at writing.
Let the reader explain the message first
Give the reader the draft without a spoken introduction. Ask them to describe what they think they must do, by when and where they would find the relevant material. The writer listens without correcting the answer immediately. Explaining the intended meaning too early removes the opportunity to discover what the written message communicates on its own.
For example, a draft says, "Please review this when you have a moment. We need your thoughts soon." The writer may intend a decision between two proposals by the next day. The reader may reasonably interpret it as an optional invitation to comment. This is a mismatch in the request itself; changing the font will not resolve it.
BEFORE
Please review this
We need your thoughts soon. The document is in the shared folder.
AFTER
Review the two options
Reply with your preferred option and one reason by 14 May, 12:00 UTC.
Illustrative revision of a fictional request. The second version specifies the response and deadline; a real message would also identify or link the relevant document.
Compare the reader's account with the writer's private note. Record the gaps without assigning blame. Was the action absent, implied or simply difficult to find? Did unfamiliar language cause uncertainty? Did the reader notice background information before the request? Perspective-taking begins with recognising that readers bring different information and expectations to a message
| Reader response | Possible issue | Question to explore |
| I thought comments were optional | The action is unclear | What response must the message request? |
| I did not notice a deadline | The detail may be hidden or absent | Where would you expect to find it? |
| I do not know this abbreviation | Shared knowledge was assumed | Which term needs explaining? |
| I cannot open the document | The task lacks an accessible resource | What access does the reader need? |
Turn reactions into useful feedback
Now the reader describes one difficulty at a time. Use an observation followed by its effect and a question. For example: "I found the deadline after the background paragraph, so I initially thought this was only an update. Could it appear beside the request?" This gives the writer something specific to consider without pretending that one reader represents everyone.
JUDGEMENT
This looks confusing
A broad verdict gives the writer little information to work with.
OBSERVATION
I missed the deadline
I read the background first. Could the deadline sit by the request?
Original sample feedback statements. The observation explains the reading difficulty and opens a discussion about a possible change.
The writer practises active listening by summarising before responding: "You understood the topic, but not the urgency until the last paragraph." The reader can confirm or refine that account. The summary is a check of understanding, not an obligation to accept every suggested edit.
If the writer disagrees, return to the purpose. Perhaps the message is intended only as background and does not require action. In that case, the revision should say so. A useful discussion can change the brief as well as the wording. Avoid defending a layout merely because it took time to produce.
When the conversation becomes uncomfortable
Pause if the discussion starts to sound personal. Replace a verdict such as "You always overcomplicate things" with a description of this particular draft. Ask whether the other person is ready to continue and choose a smaller issue to examine. In a manager–employee pairing, make clear that questioning the message is welcome; a polite agreement may conceal genuine uncertainty or disagreement.
Revise the words and the visual order separately
Make the request accurate first. Name the action, clarify the time reference and explain unfamiliar terms. For international teams, avoid relying on expressions such as "end of day" without specifying whose working day is meant. A date written with the month name and an explicit time zone can remove ambiguity, although the deadline should still be reasonable for the people involved.
Then review visual hierarchy. Give the request a descriptive heading, place necessary conditions nearby and use emphasis sparingly. If every sentence is bold, the page offers little guidance about what deserves attention. Keep paragraphs readable and allow text to wrap rather than forcing it into a rigid box. If you want to compare how the same wording looks in different typefaces, a font preview tool such as the one at typetype.org can support that comparison; ask your partner which version is easier to read rather than assuming your own preference is shared.
| Revision | What it addresses | What it cannot fix |
| State the requested action | An unclear task | Missing authority to make the decision |
| Place the deadline near the request | Difficulty finding timing | An unrealistic deadline |
| Use a descriptive heading | Scanning and orientation | An inaccurate explanation |
| Improve spacing and text size | Reading comfort | Unfamiliar jargon or missing context |
Test on the format the reader will use. A message that looks comfortable on a large screen may become dense on a phone. Offer an alternative format when someone needs one, and ask about preferences instead of making assumptions from their age, nationality or language background. Keep essential information available as text rather than only inside a graphic.
Conclusion: Building Better Written Communication Habits
After the first revision, exchange roles with a different message. The former reviewer now experiences what it is like to hear someone interpret their own work. Notice any impulse to interrupt, justify a choice or solve the problem before the reader finishes. Those reactions are useful material for reflection, provided they are discussed without blame.
If possible, give the revised draft to a third person who has not heard the discussion. Ask the same questions about action, timing and resources. The original reader now knows the intended meaning, so their improved understanding alone cannot show that the revision worked. A fresh interpretation is a more useful check, although a small exercise is not a formal effectiveness study.
Finish by agreeing on one habit each participant will try:
- State the requested action before adding background.
- Ask what the reader understood before explaining the intention.
- Describe a specific difficulty instead of judging the writer.
- Summarise feedback before deciding how to respond.
Revisit that habit after a few real messages. Look for concrete changes: fewer requests to explain the task, clearer questions or more specific feedback. Avoid treating every misunderstanding as a failure. The purpose is to build a repeatable conversation in which people can identify a gap, discuss it respectfully and improve the message together.
About the Author
Ethan Montgomery is a designer and director with more than 20 years of experience in typography, type design and font production. He regularly lectures on these subjects and contributes to educational initiatives focused on developing understanding of digital typography.
