Useful change begins with a specific question. Work through the ideas below, then use the field exercise to test one of them in context.
Match the channel to the message
Use a written document for durable instructions, a meeting for complex decisions, and a short message for coordination. Urgent does not mean every update belongs in a meeting.
- Define where final decisions live.
- Add a deadline to requests that need a response.
- Summarize meetings in writing.
Make feedback safe and specific
Invite disagreement before a choice is final. Ask what is confusing, what might fail, and what evidence is missing. Acknowledge the input even when the decision stays the same.
- Ask one focused question at a time.
- Separate observations from interpretations.
- Report back on what changed.
Design for handoffs
A handoff should contain the expected output, owner, context, and acceptance criteria. Without them, the next team must reconstruct the work.
- Use a simple handoff template.
- Confirm who takes the next step.
- Track recurring handoff failures.
The handoff brief
Use a short handoff when work crosses roles or teams. The receiver should be able to start without reconstructing the meeting, chasing a file or guessing what finished means.
- Result
Describe the output and the person who will use it. Include a concrete example when the result is easy to misread.
- Context
Link the current source of truth, constraints and earlier decisions. Leave out background that does not affect the next action.
- Owner and date
Name the person taking the next step and the date when a first response or draft is needed.
- Acceptance
List two or three observable checks that define done. Add a path for resolving unclear requirements.
Imagine a designer handing a landing page to a developer. Instead of 'please build this', the brief identifies the approved copy, responsive design file, accessible menu behavior, test widths and reviewer. A question about an unfinished illustration has a named owner.
A handoff is not a document dump. If the receiver still needs to ask which version is final, the source of truth is missing.
RESEARCH CONTEXT / Microsoft Work Trend Index: the fragmented workday ↗
Try it in your next workweek.
Take one repeated question and turn its answer into a short, findable guide with a named owner.