Want / Commitment
Share what people want and what they can offer, then distinguish possible matches from mutually agreed and completed help.
Use this with new or existing partners. Invite each person to state a want and an offered contribution. Discuss matches only after checking willingness, capacity and acceptance; keep the contribution offer distinct from a mutually agreed commitment.
Personal wants, offered resources or help, availability, potential recipients and evidence of acceptance or completion.
Want/contribution records, possible matches and cooperation agreements with explicit status.
On this page
How to use it
- Define the cooperation scope and voluntary sharing boundaries.
- Invite personal wants and contributions with availability and conditions.
- Match specific needs to offers and ask both parties about capacity and acceptance.
- Record proposed, agreed and done separately with deadlines and conditions.
- Review delivery or renegotiate, keeping unmatched wants visible.
Keep its limits in mind
Commitment in this exercise starts as what I can contribute; it is not automatically an accepted obligation. Wants are not entitlements, and contributions need not balance in number or value. Check time, authority and acceptance. Keep proposed, agreed and done distinct, and do not compel disclosure or rate people by their entries.
One match is agreed; another still needs a time
Original fictional I5 teaching packet: Clearbrook Support. Records, statements, trials and agreements are synthetic, not real outcomes or personnel assessments.
On a small screen, scroll across the diagram to read it.
Preserve offers: A stated ability to demonstrate is an offer subject to timing, not open-ended availability. A FAQ can meet Qiao’s want without requiring equal minutes in return.
Check each status: M1 has synthetic records of mutual acceptance and reserved time but no delivery. M2 lacks a common time and remains proposed; neither can be upgraded by a diagram.
M1 is agreed but not done; M2 is proposed with unknown timing. Status never upgrades automatically.
Next step: When help is agreed but delivery responsibilities remain unclear, use RACI; an offer alone does not establish an accepted duty.
Three limits to agree before matching help
First, pause if people do not know what they are being asked to share. Invite work-related wants and contributions within an agreed scope. Someone may choose not to disclose a personal concern or an unavailable resource. An empty entry is not evidence that they have nothing to offer or do not care about the team.
Second, keep an offer distinct from an accepted obligation. “I can demonstrate the fields” does not mean any time, any duration, or any recipient. Ask about conditions, authority, capacity, and acceptance before assigning a status. In this exercise Commitment begins as offered contribution; mutual commitment needs a separate record.
Third, stop if matching becomes a requirement for equal exchange. Thirty minutes of FAQ writing and twenty minutes of demonstration need not balance. They address different needs, and either arrangement may be useful independently. Do not price people’s worth by their entries or make one person’s help conditional on an exchange they never accepted.
Choose between matching, responsibility, task fit, and reflection
This exercise helps people see possible cooperation and negotiate its status. It does not assign duties automatically. Related methods are useful when the unresolved issue concerns a deliverable, capability, or a communication incident.
| Question and records | Method | Output and boundary |
|---|---|---|
| Attributed wants and offered contributions need matching | Want/Commitment | Possible matches and agreement status; not automatic delivery. |
| Agreed work needs execution and approval roles | RACI matrix | Role agreement; an offer alone cannot fill a role. |
| One person’s interests, capabilities and requirements differ | Will/Can/Must | Task fit and development gaps; not compulsory alignment. |
| One exchange has conflicting interpretations | Cognition–Action Cycle | Observed actions and attributed accounts; not proven motives. |
Keep Clearbrook’s two matches at different statuses
The complete fictional I5 cooperation discussion takes place on October 7. Lin wants field-check guidance and offers thirty minutes to prepare a FAQ draft. Qiao wants a draft before a meeting and offers a twenty-minute field demonstration, with timing still unknown. These are voluntary teaching statements, not personnel ratings or an open-ended exchange of availability.
M1 links Lin’s FAQ offer to Qiao’s want. Both accept an October 9 delivery and reserve thirty minutes. It is agreed, not done: the packet contains no delivered draft or receipt record. M2 links Qiao’s demonstration offer to Lin’s want, but a common time has not been confirmed. It remains proposed. The agreed FAQ arrangement does not silently accept the demonstration.
The table retains each want, offer, status, and evidence gap. An agreement can cover a particular output while leaving details to clarify; those details should be checked rather than invented. No exact meeting time or demonstration appointment is supplied. Matching provides a starting point for cooperation, not proof that either participant has already benefited.
| Match and direction | Want and offered contribution | Status and next check |
|---|---|---|
| M1 Lin → Qiao | Qiao wants pre-meeting FAQ; Lin offers 30 minutes | Agreed: both confirm Oct 9 and reserved time. No delivery; check actual draft and receipt. |
| M2 Qiao → Lin | Lin wants field guidance; Qiao offers 20-minute demonstration | Proposed: shared time unknown. Confirm scope, availability and acceptance first. |
Review acceptance and delivery as different events
For M1, confirm the agreed output and how Qiao will receive it, retaining the existing October 9 date. Do not convert thirty minutes of reserved preparation into a guarantee that every possible FAQ question will be resolved. If the scope needs more work, discuss it before changing what either person is expected to deliver.
At the October 9 check, retain what was actually sent, when, and whether it matched the agreed scope. A file being sent, being received, and being useful are different observations. The present case has none of those completion records, so M1 cannot be upgraded to done simply because the date arrives.
For M2, first agree a possible shared time, the fields to demonstrate, any material needed beforehand, and whether both people accept the arrangement. Until that happens, keep it proposed. A demonstration later delivered would still need separate evidence about Lin’s understanding or independent ability; attendance would not prove learning.
If availability changes, renegotiate and retain the earlier agreement and reason. Keep unmatched wants visible without treating them as failures. The result may be a narrower arrangement or a decision not to proceed. Cooperation quality and relationship improvement require further evidence rather than being inferred from the number of completed matches.
Check your work
- Wants and offers are attributed and conditional.
- A match is not automatic acceptance.
- An agreement and its completion have separate records.
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.