Cognition–Action Cycle
Separate both people’s actions and interpretations, then ask about assumptions before trying a clearer communication practice.
Start with a concrete exchange. Record the other person’s action, my interpretation, my response and their possible interpretation. Use dialogue to replace guesses with attributed statements while retaining unresolved differences.
Dated words and actions, my interpretation and response, labelled hypotheses about the other person and dialogue records.
A two-person cognition/action map, confirmed statements and unknowns, plus a reviewable communication change.
How to use it
- Choose one incident and record the other person’s words and actions.
- Separate my feelings and interpretation from the record.
- Record my actual response and what information it conveyed.
- Label the other person’s possible interpretation as a hypothesis or leave it blank.
- Invite their account, keep differences and agree an observable next practice and review.
Keep its limits in mind
Another person’s cognition is a hypothesis until they speak about it; a self-report still is not proof of every motive. The loop is a reflection aid, not established causation. Do not label personalities or force agreement or blame. An unagreed deadline cannot become a retrospective breach. Use appropriate conflict processes where needed.
Check a deadline that was never mutually agreed
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.
Separate the four positions: The reply and reminders are actions. Lin’s concern is an interpretation. A guess about Qiao’s experience remains a guess until separately attributed dialogue.
Keep the changed account: Qiao’s Oct 7 statement adds an explanation without proving all motives. A clearer next request can be tried; it does not create an earlier agreement or prove repair.
Keep Oct 6 actions, pre-dialogue hypotheses and Oct 7 self-reports distinct; no retrospective deadline.
Next step: If the incident is clearer but needs and support remain uncertain, list personal wants and offered contributions before negotiating cooperation.
Three situations where the loop should remain incomplete
First, pause when the incident has no traceable wording or time. “They never cooperate” is a general judgment, not an observed action. Choose one exchange and preserve what was actually requested and answered. If a version, recipient, or deadline was never agreed, keep that gap rather than reconstructing an agreement afterward.
Second, do not complete the other person’s interpretation from your own reaction. Silence, a short reply, and repeated reminders can have several explanations. Record your feeling as yours and label a possible explanation as a question. A later self-report adds the person’s account; it does not reveal every motive or prove a causal chain.
Third, stop using reflection as a substitute for an appropriate conflict process. It should not force disclosure, excuse harmful behavior, or assign a personality label. Choose a suitable setting and retain unresolved differences. The purpose is a clearer account and an observable next practice, not a compulsory agreement about who was at fault.
Choose between interpretation, needs, roles, and task support
This four-position reflection helps examine one exchange between two people. Related dialogue guidance can inform how to ask, but this diagram is not a validated causal model or a renamed feedback technique. Choose the next method according to the missing material.
| Question and input | Method | Output and boundary |
|---|---|---|
| Words, actions and interpretations are mixed | Cognition–Action Cycle | Attributed observations and hypotheses; no mind-reading or causal proof. |
| People need to state requests and offered help | Want/Commitment | Possible cooperation and acceptance status; no forced exchange. |
| Execution and approval for a deliverable remain unclear | RACI matrix | Explicit role discussion; prior duties are not invented. |
| A person wants to explore a goal, barriers and choices | GROW | A coaching conversation; suggestions are not personal commitments. |
Reconstruct the Clearbrook exchange without inventing a breach
The complete fictional I5 incident starts on October 6 at 10:00 when Lin requests “Give it to me today.” At 14:00 Qiao replies “Tomorrow morning.” The parties have not agreed a deadline, version, or recipient. Lin interprets the reply as not taking the work seriously, feels rushed, and then sends three reminders. The reminders are actions; Qiao’s feelings about them are not supplied.
Before dialogue, “the version may be unclear” is only a hypothesis about the other person’s experience. On October 7 Qiao says they were waiting for the latest fields and wanted the version clarified. Retain that dated account beside the earlier hypothesis. It offers an explanation but does not establish all motives, prove the reminders caused the reply, or create an earlier promise.
The proposed next practice is to state version, explicit time, and recipient and ask the other person to check whether the request can be met. Those values still need a real agreement. This is a request format to try, not a message already sent or a tested communication improvement.
| Record or position | Supplied material and status | What still needs checking |
|---|---|---|
| Original request, Oct 6 10:00 | Lin: Give it to me today; recorded action | No mutually confirmed time, version or recipient. |
| Other person’s action, 14:00 | Qiao: Tomorrow morning; recorded reply | Meaning and conditions need clarification; not a motive. |
| My cognition and response | Lin feels rushed, reads lack of seriousness; then 3 reminders | Interpretation and feeling separate from the three observable actions. |
| Other person’s cognition before dialogue | Version may be unclear; hypothesis | Do not turn it into Qiao’s statement retrospectively. |
| Dialogue, Oct 7 | Qiao reports waiting for latest fields; wants version clear | Attributed self-report; not exhaustive or independently proven motive. |
| Proposed next exchange | Specify version, time, recipient and invite checking | Not tried, agreed or reviewed; no relationship result. |
Review the next request without rewriting the earlier one
Before trying the format, identify the actual item and version, the needed time, and the intended recipient. Ask what dependencies or constraints the other person sees. A clear request can still be declined or renegotiated. The record should show the actual reply and any agreement rather than treating a well-written message as consent.
For the later exchange, preserve when the request was sent, what was confirmed, what remained open, and what was delivered. An acknowledgment is different from accepting the requested time. If a condition changes, record the change and the new discussion. Do not import an agreement reached later into the October 6 event.
At review, ask whether the practice clarified the work and whether either person still interprets it differently. Describe observed changes and attributed feedback separately. One smoother exchange would not demonstrate a lasting relationship improvement or prove the original explanation correct. No trial or reviewed outcome is supplied in this case.
The useful decision may be to clarify a version, agree a different delivery arrangement, or use another appropriate process. Keep the action record, personal interpretation, other person’s stated account, and unresolved hypotheses distinguishable. That lets a future reader ask what was known at each point without accepting a story about someone’s character.
Check your work
- Both people and action versus cognition are distinct.
- Hypotheses and dated self-reports stay distinguishable.
- A proposed practice is not an observed relationship improvement.
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.