Clean Language Intentions: Sources and Real Choices
Nour
Founder, Coachful
Clean Language intentions work explores what a client says they want and the distinctions that help them choose a next step. Source questions explore where something is experienced as coming from. Keep those purposes separate: an association about an origin does not reveal a verified cause or prove a hidden motive.
Use the client's account rather than imposing a benevolent intention on every behavior or symbol. Someone can prefer literal language, decline historical exploration or decide that the practical information is already sufficient. The conversation should serve the agreed coaching purpose.
This guide explains five original inquiry checks and distinguishes Clean Setup and Clean Feedback from Grove's original work. A complete fictional technology-review case follows the questions through a real refusal, accepted specialist scope, completed answer and corrected status record. No technical release or restored trust is inferred.
Distinguish the methods and the claims
David Grove originated Clean Language. Penny Tompkins and James Lawley modelled his work through Symbolic Modelling. Lawley's 2011 account also distinguishes Clean Language, Clean Space and Emergent Knowledge. Learning a few question forms does not make these approaches interchangeable or establish competence to deliver a therapeutic process.
In Context makes Clean clean (2023), Lawley explains that questions need a fitting context. Intention inquiry requires some indication of wanting or acting; an object in a client's description does not automatically have a wish. Source inquiry can invite varied associations and may lead away from the present purpose. Necessary conditions and knowing have their own functions.
Two brief traditional forms illustrate the difference: “And what would you like to have happen?” concerns a desired outcome; “And where could that come from?” invites a possible source. Neither wording is a guarantee of neutrality or truth. The choice of question still directs attention and can introduce an assumption.
Treat those descriptions as practitioner models. They do not establish a neuroscience mechanism, uncover an unconscious fact or validate a technical decision. The practical checks below are original coaching applications, not a prescribed Grove sequence or a substitute for training.
Check 1: Clarify the client's stated purpose
Begin with the work the client actually wants to do. A wish to explain a proposal is different from a wish to make a colleague agree. Ask what would make the conversation useful, what is within the client's choice and what depends on someone else. A compelling intention is not authority over another person's response.
Keep the purpose revisable. If the client notices that the initial request assumes agreement, they may choose a narrower question. Record the revised purpose rather than continuing toward the original target simply because it sounds ambitious. A good outcome can be discovering that a decision is premature.
Stay alert to your own preferred explanation. A coach may want the client to become more trusting, assertive or collaborative. Those ideas need discussion, not silent insertion into questions. The client may instead need a review criterion, a clearer invitation or permission to stop an unhelpful exercise.
Check 2: Explore meaning without assigning agency
Use the words the client chooses and check what they mean in this context. An image can describe an ordinary label, a feeling, a relationship or a practical condition. The client decides whether it is useful to develop it further. Do not turn every image into a personality part that needs to speak.
When you introduce an assumption, make it correctable. If a client says the symbol does not want anything, accept that information. Rephrasing the same question until the client produces a wish would replace inquiry with compliance. Working directly with the stated decision can be the better choice.
Likewise, do not require a bodily location, movement or visualization. Those are optional ways someone might express experience, not mandatory evidence of depth. A person who prefers a written list or a literal explanation has not demonstrated resistance or a hidden psychological problem.
Check 3: Distinguish association, history and evidence
A client may connect a current concern with a past event. Record that as their present account of an association. Establishing what actually occurred, what caused it and whether it explains today's behavior requires different evidence. A coaching answer is not independent historical corroboration.
Ask whether pursuing the origin serves the agreed task. The client can leave an association unexplored and work with the current information gap. Do not use a workplace conversation to search for childhood trauma, recover a memory or explain a colleague's psychology. Those are different claims and may be outside the practitioner's competence.
A source may also be practical: an old instruction, an inherited template or a rule whose owner is unclear. In that case, examining the authoritative record can matter more than deepening a metaphor. Keep a client's recollection distinct from a document or specialist answer you have actually obtained.
Check 4: Make conditions and support real requests
Separate the desired result from what the client believes must happen first. A requirement may be genuine, assumed or still unknown. Ask what information supports it and who can clarify it. Understanding a condition does not mean the coach can remove it or assign the associated work.
Support needs become practical when a recipient understands the material, role, time and response being requested. State what is outside the request. A person may agree to identify missing information while declining an assessment, a deadline or responsibility for the final decision.
Count the recipient's preparation and handling. An accepted fifteen-minute conversation can involve more work than fifteen minutes. A funding allowance or an empty calendar slot is not the same as the person's agreement to the whole task.
Check 5: Preserve consequences, disagreement and choice
Understanding an intention does not excuse its effects. A client may want to prevent mistakes while imposing repeated checks that obstruct colleagues. Discuss the observable work, obligations and authority without concluding that a positive-sounding wish makes the arrangement acceptable.
Ask what the proposed choice would mean for the people affected and what remains unsettled. The client can understand a colleague's concern and still disagree about cost, timing or priority. Do not require a harmonious synthesis as proof that the coaching worked.
The nested metaphor guide helps distinguish several descriptions. The emerging metaphor guide addresses keeping an evolving account provisional. Neither removes the need to examine the actual business decision.
Use meeting preparation and feedback with clear attribution
Caitlin Walker's 2008 Clean Setup account develops a useful event, the individual's own contribution and requested support, including evidence and actual agreement. These are distinct from treating a client's image as a hidden motive. The record below uses those purposes with original workplace content; it does not reproduce her question set or source examples.
Nancy Doyle and Caitlin Walker's 2008 Clean Feedback article distinguishes what the giver observed from interpretation and preference. The receiver need not accept the evaluation as an objective truth. In a work setting, an invitation to correct an interpretation can coexist with a formal requirement that remains applicable.
These are practitioner accounts with examples, not evidence that a short preparation record guarantees agreement or that feedback automatically repairs a relationship. Keep the conversation proportionate to the task, explain its audience and leave personal material out when it is unnecessary.
Begin the original case with an actual correction
In this fictional example, Amina is a technology lead in a financial-technology firm, Rowan is the revenue lead, Priya owns a specialist security-review function and Jules is Amina's private coach. Dates are 1–18 September 2036, in UTC. The coaching uses generic descriptions, not customer records, credentials or confidential implementation details.
Amina spends twenty minutes preparing her account. Jules reads and prepares for fifteen minutes before their forty-five-minute session on 1 September. Amina says the proposal has a “red tab.” Jules asks what the tab wants to achieve. She corrects him: “It is a label, not someone who wants something. I want us not to promise what we cannot operate.”
Jules accepts the correction and asks, “And what would you like to have happen?” Amina answers that she wants a useful comparison with an accurate review status, not an implied approval. She associates her repeated checking with a late handover the previous year, but says she does not want to investigate that history. They retain it as an unverified association and return to the present question: what can the specialist review, and what information would allow options to be compared?
Her initial purpose, getting Rowan to admit that a review is needed, becomes a narrower intention: explain the required review and ask what can be examined next. She chooses literal language. No metaphor is transformed, no past incident is investigated and no diagnosis is made.
Distinguish a requested date from an accepted commitment
Despite that useful coaching distinction, Amina spends fifteen minutes on 2 September drafting and sending Rowan and Priya a brief headed “API review sign-off by 8 September.” It asks for a discussion on 4 September at 14:00. The wording again combines an information request with a release implication. Neither date is an accepted promise.
Priya spends fifteen minutes on 3 September reading and replying: “I cannot attend on 4 September or give full sign-off from this brief. I can accept a sixty-minute bounded task within my paid review allocation: fifteen on this reading and reply, five on your confirmation, ten preparation, fifteen together on 9 September at 11:00, ten preparing an answer by 10 September at 16:00 and five checking your corrected status note. I can identify the evidence questions, not approve a release.”
Rowan spends ten minutes reading the brief and Priya's counterproposal, then replying that he wants to compare options without implying a committed merchant date. He accepts the 9 September discussion and the associated preparation and reading. He has no authority to turn it into funding or release approval.
On 4 September, Amina uses ten minutes reading both replies and sending her acceptance of the bounded scope, dates and written answer. Priya and Rowan each spend five minutes reading her confirmation on 5 September. Priya has seventy-five paid minutes available for this project inquiry and accepts sixty; Rowan has sixty available and accepts the fifty-minute participation account below.
Complete the meeting-preparation record
On 8 September, Amina spends twenty minutes replacing the first brief with a literal version and sending this completed preparation record. Priya and Rowan each use ten minutes reading and preparing. Those are their actual preparation blocks, not additional uncounted reading.
| Preparation purpose | Completed original record |
|---|---|
| Useful meeting | Identify the evidence questions that must be answered before comparing API options. Record what has and has not been reviewed. Do not make a release decision. |
| Amina's own contribution | Explain the proposed discussion scope, separate the commercial request from technical assurance and accept correction of the earlier “sign-off” wording. |
| Support actually accepted | Priya's bounded evidence-question review, Rowan's clarification of the merchant need and the agreed preparation, fifteen-minute discussion, written answer and final status check. |
The meeting on 9 September runs from 11:00 to 11:15: three minutes confirming scope, seven on questions, three on owners and two closing. All three participate. Priya does not perform a complete security assessment in the fifteen minutes.
Rowan says the first brief's heading made him think technology would block every option. Amina agrees that her wording was misleading but does not agree that she intended to block everything. They use the following original feedback record within the meeting rather than assigning motives to one another.
| Feedback field | Completed original account |
|---|---|
| Observed material | The first brief asked for “sign-off by 8 September” and did not label the request as an evidence-question discussion. |
| Rowan's interpretation | I read that as a choice between full clearance and stopping all options. |
| Concern | I could not tell what discussion could happen before full review. |
| Amina's correction | The brief was misleading. I wanted the necessary review understood, but did not mean no option could ever be compared. |
| Preferred next contribution | A status note distinguishing the questions identified, evidence still missing and the decision nobody has yet authorized. |
This changes the account of the communication. It does not waive a technical requirement, prove the participants' private motives or show that their working relationship is repaired.
Obtain the actual specialist answer and correct its status
Priya uses her ten-minute writing block on 10 September and sends the accepted answer by 16:00:
Priya's completed answer: “For this proposed comparison, the current brief still needs a named owner for the merchant-task description, a bounded description of what would be compared and references to the authoritative constraints the owners say apply. These are questions identified from this brief, not a completed security review or a list proving compliance. Rowan can propose who supplies the merchant description; that work needs its own agreement. I have not approved a test, release date or control design. Any further specialist assessment needs a defined scope and allocated time.”
Amina spends ten minutes reading the answer; Rowan spends five. Amina then uses a separate ten minutes to correct and send this completed status note to both. The reading and writing are not counted as twenty uninterrupted editing minutes.
Corrected status note: “Status: evidence questions identified. Priya completed the bounded review of this brief and supplied the questions we need to route. The merchant-task owner, comparison boundary and authoritative constraint references remain to be established. No test, control design, funding or release has been approved through this discussion. Do not use the original 8 September sign-off heading as a commitment. Further evidence preparation and specialist assessment need separate agreement and capacity. The next decision is who can supply the missing material, not whether we can announce a launch.”
On 11 September, Priya uses five minutes reading and confirming that the note accurately limits her work. Rowan uses five minutes reading and replying that the note is accurate but he still cannot promise a commercial date. Amina uses five minutes reading those actual replies. No additional evidence preparation or later release is described as completed.
Review the intention against what actually happened
Amina spends ten minutes sending Jules a selected generic account on 16 September. Jules reads it for ten minutes before their twenty-minute review on 18 September. Amina initially says that understanding their shared intention made the proposal ready. They correct that claim using the actual answer and status.
Amina's revised account: “I clarified what I wanted, accepted a different specialist date and corrected my first request. We obtained an evidence-question answer and an accurate status note. We did not establish a shared private motive or readiness to test or release. I still want a timely comparison, and Rowan's commercial concern remains. Missing evidence needs another authorized step.”
Jules spends ten minutes returning a private client comment: “Keep your stated intention distinct from the evidence obtained. Your association with the old handover remains unexplored, as you chose. Priya completed the task she accepted, not a full assessment. The next question concerns the missing material and who can provide it. Understanding does not make that work available automatically.”
Amina spends five minutes reading and replying that this is accurate and that she is not expanding the inquiry now. Jules spends five minutes reading her existing reply and completing notes. No new acknowledgment or unbudgeted colleague request follows.
Reconcile the complete bounded work
| Person | Actual active minutes | Used / available |
|---|---|---|
| Jules | 15 preparation; 45 initial coaching; 10 account reading; 20 review; 10 returned comment; 5 final reply reading and notes. | 105 / 120 |
| Amina | 20 initial account; 45 coaching; 15 first brief; 10 reply reading and acceptance; 20 revised brief and preparation record; 15 discussion; 10 specialist-answer reading; 10 status correction and send; 5 confirmation reading; 10 coach account; 20 review; 5 comment reading and reply. | 185 / 210 |
| Priya | 15 request reading and counterproposal; 5 confirmation reading; 10 preparation; 15 discussion; 10 written answer; 5 corrected-status reading and confirmation. | 60 / 75 |
| Rowan | 10 initial brief and counterproposal reading with reply; 5 confirmation reading; 10 preparation; 15 discussion; 5 specialist-answer reading; 5 status reading and reply. | 50 / 60 |
The bounded coordination and coaching project uses 400 of 465 person-minutes, leaving sixty-five: Jules fifteen, Amina twenty-five, Priya fifteen and Rowan ten. The fifteen-minute three-person discussion consumes forty-five person-minutes. Message reading, writing and confirmations are included.
This scope excludes the earlier handover incident, ordinary business work, future evidence production and a full technical assessment. Those are not declared completed or resourced. The remaining sixty-five minutes in this project do not establish capacity for a launch or another review round.
Use Coachful for the selected coaching record
Coachful is our #1 recommendation for organizing the client's original preparation worksheet, selected reflection and returned coaching feedback. This is an editorial workflow recommendation, not a claim that software validates an intention, supplies a Clean Language qualification or approves a technical project.
Amina can submit the generic account through her assigned worksheet. Jules opens the client, then Reflections > Forms & worksheets. Internal Coach review remains private to the authorized coach team; saving it does not deliver his comment to Amina. He sends the actual comment through her private client conversation, opened from the message icon on her profile.
The firm's specialist brief and approval records remain in its authorized systems. Do not put restricted implementation data or inferred motives into a group worksheet. A client can keep journal pages unshared or explicitly share individual pages through supported specialty flows and later revoke that sharing.
Check recording and recap audiences before using sensitive examples. Approval settings hold new unsent recaps, session-type overrides apply, and already-sent material is not recalled. The demonstration images are coaching tools, not the case's technical evidence. Explore Coachful features for the agreed preparation and review.
Frequently asked questions
Does a source answer establish a cause?
No. It records an association or account in that conversation. Historical and technical causal claims need appropriate evidence; clinical claims need appropriate expertise.
Does every symbol or behavior have a positive intention?
Do not assume so. Ask what the client means and consider effects, responsibilities and choice. An image can be a label without having a wish.
Must the client keep using a metaphor?
No. They can choose literal language or stop an exploration. That choice is useful information, not proof that they are avoiding a hidden motive.
Who developed Clean Setup and Clean Feedback?
Clean Setup is associated with Caitlin Walker. Nancy Doyle and Caitlin Walker developed the Clean Feedback model discussed here. Keep those contributions distinct from Grove's original Clean Language work.
