Everyday Guidebooks
Cover of Make Your Message Easy to Follow

Business, AI & Entrepreneurship

Make Your Message Easy to Follow

Practical Communication Skills for Clear Updates, Technical Explanations, and Recommendations

by Todd Michael

Available now

Good ideas can get lost in a message that asks too much of its audience. Whether you are reporting project progress, explaining a technical problem, or recommending a course of action, clarity starts with knowing what your reader or listener needs.

Make Your Message Easy to Follow offers a practical way to strengthen communication skills without relying on complicated rules or canned scripts. Learn how to identify the purpose of a message, put information in a useful order, select the right level of detail, and make requests and decisions unmistakable.

Workplace examples show the difference between information that merely fills space and information that helps people move forward. Exercises help you practice writing concise updates, translating technical issues for nontechnical audiences, presenting balanced recommendations, and revising messages before you send them.

Make your next message easier to understand—and easier to act on.

Contents
  1. 1. Why Messages Become Hard to Follow
  2. 2. Start With the Audience
  3. 3. Choose One Primary Purpose
  4. Four Purposes, Four Different Reader Responses
  5. Find the Purpose Behind the Topic
  6. Choose the Purpose That Matters Most Now
  7. Do Not Disguise One Purpose as Another
  8. Keep Secondary Needs in Their Place
  9. When You Have More Than One Legitimate Purpose
  10. Match the Purpose to the Reader’s Role
  11. Practice: Give One Situation Four Purposes
  12. A Quick Purpose Check
  13. 4. Put the Important Part Where It Belongs
  14. Lead From the Reader’s Next Step
  15. Build an Opening That Orients
  16. Group Information by the Questions It Answers
  17. Use Transitions to Show the Relationship
  18. Structure a Routine Update Around What Changed
  19. Structure Sensitive News With Care and Clarity
  20. Structure an Unfamiliar Topic From Known to New
  21. Choose the Structure, Not Just the Facts
  22. Practice: Rearrange Before You Rewrite
  23. 5. Decide How Much Detail to Include
  24. 6. Write for Easy Reading
  25. 7. Make Requests Actionable
  26. 8. Write Concise Updates
  27. 9. Explain Technical Issues Without Losing Accuracy
  28. 10. Present a Recommendation
  29. 11. Communicate Risk and Uncertainty
  30. 12. Make Decisions Traceable
  31. 13. Adapt Your Message to the Moment
  32. 14. Revise, Test, and Build the Habit
  33. A Five-Pass Review
  34. See the Review in Action
  35. Test the Message Before It Matters
  36. Exercise: Three Messages, One Situation
  37. Turn Review Into a Practice Plan
  38. Other Books by Todd Michael

Read a sample: 1. Why Messages Become Hard to Follow

You finish a careful project update and send it to the people who need it. You have included the background, the latest findings, and the conversations that led to your current plan. A few minutes later, someone replies: “What do you need from me?”

The question can feel frustrating. You worked hard on the message. The information is there.

But information being present is not the same as a message being easy to follow. A reader may need to search through several paragraphs, infer which details matter, and guess whether you are reporting a problem or asking for a decision. Each inference is an opportunity for the reader to reach a different conclusion from the one you intended.

Most confusing workplace messages are not the result of careless thinking. They are often the result of a reasonable person writing from inside the work. The sender knows the history, recognizes the names, and understands why a small change matters. The reader may have none of that context. Even when both people are capable and attentive, they are approaching the same message from different starting points.

This chapter will help you recognize that gap. You will look at the common reasons messages become difficult to follow, then use a practical checklist to diagnose and improve an example. The goal is not to make every message short or simple. It is to make the path through the information visible.

When you are involved in a project, you collect information in the order it happens. You attend a meeting, investigate an issue, hear a concern, revise a plan, and discover another constraint. That sequence is useful to you because it reflects how your understanding developed.

Your reader usually needs a different sequence.

A manager may need to know whether the delivery date has changed. A colleague may need to know which task now belongs to them. A client may need to understand the effect on their team. The history may matter, but it may not be the best place to begin.

Consider an update that opens this way:

> After our discussion with the operations group, we reviewed the original intake process and compared it with the version used by the regional team. There were several differences in how requests were categorized, so we met with the reporting team to confirm the fields available in the current system.

A reader can follow the individual sentences and still be unsure why the update matters. Is the process broken? Is a decision needed? Has the schedule changed?

Now consider an opening built around the consequence:

> The new intake process needs an additional review before launch because the current system does not capture one of the requested categories. I recommend delaying launch until the operations team confirms how that category should be recorded.

The second opening does not tell the whole story. It gives the reader a reason to pay attention and a frame for understanding the details that follow.

That distinction matters. Clarity is not the removal of complexity at any cost. It is the arrangement of complexity so the reader can see what matters, how the pieces relate, and what remains unresolved.

Several problems tend to appear together. A message may omit context, bury a request, and use a specialist term without explaining why it matters. Learning to spot each problem makes revision more manageable.

A message can begin too far inside a conversation:

> We should use the second option. It addresses the concern from yesterday and should avoid another round of changes.

The sender may know exactly which options and concerns are involved. A recipient who missed the meeting—or attended several meetings yesterday—has to reconstruct the situation.

A small amount of context can make the message usable:

> For the customer onboarding form, I recommend using the shorter version we reviewed yesterday. It removes the questions the support team said were delaying completion.

The improved version identifies the subject, the proposed choice, and the reason. It does not repeat the entire meeting. It supplies enough context for the reader to orient themselves.

Missing context also appears when a sender assumes that an acronym, project name, or internal process is familiar. Before explaining every term, ask whether the reader needs it to understand the message. Some labels can be replaced with ordinary descriptions; others need a brief definition. A specialist colleague may need neither.

Background is useful when it helps someone interpret a message. It becomes an obstacle when the reader must pass through it before learning why the message exists.

A long history can create a false sense of completeness. The sender has documented everything, but the reader still has to decide which event changed the situation. This is especially common in updates written as a record of activity:

> We met with design, reviewed the draft, discussed the open questions, and scheduled another meeting with legal.

Those activities might represent meaningful progress, but the update does not say what changed. Did the draft receive approval? Is there a problem? Will the next meeting affect the planned release?

A more useful version might say:

> The draft is ready for legal review. Design approved the layout, but the release date remains unconfirmed until legal reviews the proposed wording.

The activities are still available as supporting detail if someone needs them. The reader first gets the status and the remaining uncertainty.

Sometimes the…

More Business, AI & Entrepreneurship

Cover of AIAIAvailable nowCover of The New Gold RushThe New Gold RushAvailable nowCover of Leadership Intelligence for Succession PlanningLeadership Intelligence for Succession PlanningAvailable nowCover of Remote Jobs and the Scam TestRemote Jobs and the Scam TestAvailable nowCover of The Entrepreneur Mindset for Patient DecisionsThe Entrepreneur Mindset for Patient DecisionsAvailable nowCover of Price Without ApologyPrice Without ApologyAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.