Try one useful
conversation tool.
Two short exercises from the version-one curriculum: make a specific request, then distinguish a request from a boundary.
No account. No email. No need to share your history. Use an ordinary, fictional, or workplace example.
Make a request someone
can understand.
Objective: turn a vague frustration into a specific action you can ask another person to take.
Instead of: “We need better updates.”
Try: “Please post the weekly status in the shared note by Tuesday at noon.”
- Choose an ordinary situation.
What would help? Keep the example manageable.
- Name a concrete action.
Say what you are asking for, without guessing the other person’s motives.
- Check the request.
Could another person tell what action you mean? A request leaves room for an answer or discussion.
Learning check: what made the second example clearer?
It identifies a concrete action, a place for the update, and a time. The first version does not say what kind of update is needed.
A request asks.
A boundary names your limit.
Objective: distinguish what you are asking another person to do from the action or limit within your own control.
Request: “Would you send the material by noon?”
Boundary: “I can review material received by noon. Later material will need to wait until tomorrow.”
Use a non-threatening situation. This is not an assignment to confront someone abusive or unsafe.
Learning check: can a boundary guarantee agreement?
No. A boundary describes a limit or action within your control. It cannot guarantee another person’s response.
Optional homework: practice the statement privately or use it in a suitable ordinary situation. Notice whether your meaning was clear, not whether you sounded impressive.