Talk Smart · Growth Library
Check Who, What, Where, When, Why, and How
Ask the 5 Ws and H
Try this
Review an important operational message using six questions: Who? What? Where? When? Why? How? Add only the missing details the reader needs to act, then send the shortest version that is still clear.
Check-in: Could the reader act without guessing, and did I include any detail that was unnecessary or sensitive?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: Public content is replaced by a concise operational-clarity checklist. Fabricated meeting metrics, internal-trial claims, arbitrary timing rules and unnecessary numerical examples are removed.
Who, What, Where, When, Why, and How is a simple check for operational messages. It is useful when missing context could create delay, confusion, or unnecessary follow-up. The aim is not to make every message longer. It is to remove important gaps before sending.
1. Start with what needs to happen
Make the requested action or outcome easy to find. Replace vague wording such as let's discuss this with the decision, review, delivery, or response you actually need.
2. Check who is involved
Ask whether responsibility is clear. Name the person or role that needs to act when that matters. Do not confuse a long recipient list with clear ownership.
3. Check where and when
For meetings, visits, deadlines, or handoffs, include the place or link and the timing needed to act. Add a time zone when different locations make it ambiguous.
4. Add the reason when it changes priority
Explain why the request matters when that helps the reader make a better decision about urgency, trade-offs, or preparation. Keep the reason short and appropriate for the audience.
5. Explain how to proceed when needed
Include the file, tool, preparation, format, or next step only when the reader would otherwise have to guess. Avoid turning a simple request into a procedural manual.
6. Remove what the reader does not need
Read the message once more. If the essential action is clear, remove duplicated background, unnecessary labels, and sensitive details. The checklist is successful when it makes the message easier to use.
Questions to consider
Do I need all six items in every message?
No. Use the questions as a gap check. A familiar conversation may already have shared context, while a handoff, meeting invite, site visit, or request may need most of the details.
Will this make messages too long?
It can if you treat the checklist as a form to fill. Add only information the reader needs to understand or act. Completeness does not require six labeled paragraphs.
What about sensitive information?
Do not add private details simply to satisfy a checklist. State the operational reason at the level needed for the audience and move sensitive context to the appropriate private channel.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-08-18 · reviewed · Brali editorial agent Source: protocol-content-overrides-5w1h.json
Replace an inherited communication article containing fabricated meeting metrics, arbitrary word and timing rules, made-up internal trials and unnecessary numerical examples with a concise operational-clarity checklist.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-08-18: reviewed by Brali editorial agent; evidence state is
practical.
Canonical source record · Evidence state: practical.