Spatial Metaphors in Clean Language: A Coaching Guide
Nour
Founder, Coachful
Spatial metaphors in Clean Language can help a client describe how a situation is arranged in their experience: what feels close, what seems blocked, what is behind something else, or where a demand appears. The coach explores the client’s account without supplying a hidden meaning for those positions.
This guide develops a careful conversational approach, two complete fictional examples and a bridge to an ordinary approval review. An image can become clearer while a practical problem remains. Treat that difference as useful information, especially when another person controls the deadline, budget or decision.
What spatial language can reveal, and what it cannot establish
Listen for words about location, direction, distance, size, shape and boundaries. A client may describe deadlines directly ahead, requests coming from every side, a wall across a route, or a weight above their shoulders. Ask whether these descriptions are useful to explore. A familiar expression does not automatically require an extended metaphor conversation.
| Client’s description | Possible exploration | Unsupported conclusion |
|---|---|---|
| A deadline directly in front | Its position and what the client notices there | Front always represents the future |
| Requests all around | Whether these requests differ for the client | The coach knows which request deserves priority |
| A wall across the route | The client’s own description of the wall and route | The wall proves trauma or resistance |
| A gesture toward something heavy | What the gesture refers to, if the client wants to explain | The movement diagnoses an emotional condition |
Location can be literal. Someone pointing left may be indicating an actual monitor, a colleague seated nearby or a diagram they can see. Confirm the reference before elaborating it. Even an unmistakably imaginative description remains the client’s account, not a measurement of external circumstances.
David Grove developed Clean Language. James Lawley and Penny Tompkins developed Symbolic Modelling from their modelling of his work. Their Symbolic Modelling Lite account emphasizes working with clients’ own words and nonverbal expressions from the clients’ perspective. The practice structure below is an original coaching adaptation, not a reproduction of that complete method or a credential to practice it.
Understand perceptual space without inventing a physical field
In James Lawley’s When Where Matters, perceptual space includes physical and imaginative aspects of experience. His practitioner term “psychoactivity” concerns a relationship among the perceiver, what is perceived and context. It should not be presented as a measured invisible field, a neurological finding or proof that a particular position has the same meaning for every client.
A client might locate an anticipated conversation above their desk and a completed task behind them. Another client might use entirely different positions or no spatial description at all. There is no justified shortcut from left to past, large to dangerous, far to unimportant, or a changed gesture to a changed nervous system.
Keep attention on what the person actually says. If a metaphor supplies a useful distinction, the client can decide whether to use it. If a factual question becomes more relevant, leave the metaphor. A signed approval, an available colleague or a customer response cannot be established by exploring an imagined location more deeply.
Four functions for a bounded conversation
Locate, develop, relate and integrate are useful organizing labels for this guide. They describe possible functions rather than a compulsory sequence. A coach can return to an earlier function, stop after one, or use an ordinary factual conversation instead.
Locate: establish what the client is referring to
Repeat the relevant client expression accurately and use a minimal location invitation where appropriate. Lawley illustrates the Clean Language prompt “And where is …?” The omitted part belongs to the client’s expression. Do not add a wall, edge or direction that the person has not described.
Allow a spoken answer, a gesture, a client-made sketch or a refusal. A sketch is optional working material, not a required assessment. Ask whether a mark means what you think it means; the page does not give the coach independent access to the client’s experience.
Develop: follow a distinction rather than manufacture one
Stay with a feature the client introduces. If two requests seem different to them, find out what that difference is in their account. Avoid offering a menu of symbols to select or pressing for an elaborate scene because the first answer seems insufficiently revealing.
Relate: explore relationships the client recognizes
A person may notice that one demand obscures another or that an important decision feels less noticeable than a loud request. Explore that relationship without deciding that the loud request is illegitimate. The person making it may have a real contractual deadline.
Integrate: ask what, if anything, is useful outside the image
The client can keep a distinction, reject it, leave the imagery unchanged or choose a practical inquiry. An action should follow from their judgment and checked circumstances. Turning a wall into a doorway in conversation does not authorize entering a restricted process or transferring somebody else’s responsibilities.
Six steps for using the approach carefully
- Agree the purpose. Identify the work question, the client’s interest in this approach and what would make continuing worthwhile. Offer an ordinary discussion as an alternative.
- Capture the person’s expression. Notice their exact words and the gesture’s apparent reference. Confirm rather than classify unfamiliar language.
- Choose one economical invitation. Explore only as far as the client finds useful. Pauses do not require another question immediately.
- Track changes without claiming success. Note whether the client changed a word, location or relationship. Ask what that difference means to them, including “nothing useful.”
- Check usefulness and external conditions. Separate the experience from evidence about authority, capacity, contracts or another person’s view.
- Let the client choose the next move. Agree any practical inquiry, recipient and review boundary. Record a chosen action without converting tentative imagery into an organizational diagnosis.
For more on preserving the client’s wording over time, see the vectoring and tracking guide. Track your own additions too: replacing “crowded” with “trapped” may introduce a stronger claim that belongs to the coach.
Complete example: requests all around a founder
Noel, a founder, and Tara, his coach, use two forty-five-minute sessions on 9 and 23 November 2026. Their agreed purpose is to examine how Noel chooses which approval requests need his attention. Tara has no authority to change company delegations, and the coaching agreement includes no between-session response service.
Noel describes requests “all around, close and loud.” Tara asks whether he wants to explore that description or go straight to the request list. Noel chooses a short exploration. He gestures left. Tara says she wonders whether an older issue is there. Noel corrects her: he is pointing to the monitor displaying the current queue.
Tara acknowledges that she supplied the older-issue interpretation and withdraws it. She asks Noel to describe the distinction he actually notices. The following is an original illustrative exchange, not a canonical Clean Language question sequence:
Noel: The close ones are loud. That does not mean they need me.
Tara: What distinction would you like to keep from that?
Noel: Loud is how I notice them. Important depends on what happens if nobody decides.
Tara: How would you check that with the actual requests?
Noel: I need the authority and deadline, not a better picture.
Noel makes a simple private sketch, then leaves the positions unchanged. Tara does not ask him to move the loud requests farther away. Noel says the distinction between noticeability and consequence is useful; he does not report becoming calm or discovering a hidden cause. He chooses to examine the live records.
Move from the image to an approval review
The UK HSE’s role standard concerns clear responsibilities, compatible requirements and a route for raising uncertainty. It supports checking unclear work expectations. It does not establish this company’s approval rights or make Noel responsible for every unanswered request.
Noel builds a five-field review: request, required decision, deadline, authorized owner and consequence of delay. He initially has ten records. On 10 November, operations lead Remy and finance lead Veda accept his request to check the existing delegation records by noon on 12 November. Their acceptance precedes Noel’s announcement of that review date.
Remy and Veda complete that check on 12 November. It identifies the following categories. The two unclear authority records stay unresolved; neither the sketch nor Noel’s founder title supplies a missing delegation.
| Category after source check | Records | Agreed next handling |
|---|---|---|
| Within operations authority | 4 | Remy accepts review by 19 November, within his existing allocation |
| Founder decision required | 3 | Noel accepts a decision or explicit waiting status by 17 November |
| Authority still unclear | 2 | Seek the missing basis; no substitute approval promised |
| Duplicate of a resolved item | 1 | Mark duplicate and link the earlier resolution |
A usable row makes the decision concrete. The examples below are three of the ten records, not additional requests. The stated consequence is Noel’s planning assessment, not a verified loss. A due date for reviewing an unresolved record is also different from promising its resolution.
| Request | Decision | Deadline | Authorized owner | Consequence to check |
|---|---|---|---|---|
| Supplier scope change | Accept or decline the proposed scope | Founder review by 17 November | Noel, confirmed by existing delegation | Supplier cannot schedule the changed work without an answer |
| Operations purchase | Review a purchase awaiting a specification | Remy’s status review by 19 November | Remy within the checked limit | Scheduling remains uncertain while the specification is missing |
| Cross-company exception | Establish who can approve the exception | No resolution date accepted | Unresolved in the checked records | Noel needs to explain the unresolved route rather than promise approval |
During review, ask whether the named owner actually accepted the work and whether the evidence remains current. If the supplier changes the scope again, a previous answer may no longer apply. Keep the earlier decision in the record and establish the new question instead of overwriting history to make the list look finished.
These categories concern the checked records, not different kinds of people. A request can be loud and properly urgent. A quiet request can be waiting legitimately for information. Noel records the actual deadline and consequence instead of using distance in his sketch as a priority score.
By 17 November Noel has made two decisions and marked the third waiting for an external answer. On 18 November Remy reports three operations records completed and one blocked. That report is before his accepted 19 November review deadline; it is not a missed deadline merely because the fourth item remains open. Its later outcome is outside the observed account.
| State at 18 November | Records | Interpretation |
|---|---|---|
| New operations completions | 3 | Current work completed within that authority |
| New founder decisions | 2 | Decisions made, not proof of successful implementation |
| Historical duplicate marked | 1 | Already resolved before this review |
| Still open | 4 | One operations block, one founder item waiting, two unclear authority records |
Retain the coach’s reporting error and its repair
In the 23 November session, Tara initially summarizes this as six new requests cleared. Noel checks the ten-record list and challenges the word “new.” Tara acknowledges the error: there are five new dispositions and one historical duplicate, with four records open. She corrects the summary in Noel’s presence rather than quietly changing a private note.
Noel wants the summary to record the distinction he can now use, not claim the conversation solved company approvals. Together they agree a short business-action account, explicitly dated to the 18 November operational evidence. Tara sends it on 24 November at 16:00, before their agreed 17:00 delivery time. Noel reads it on 25 November at 09:00 and confirms the counts and limits. Tara completes the coaching administration at 17:00 that day.
The two sessions total ninety coach-live minutes. This is not the whole staff effort of examining requests, checking delegations, preparing or reading the summary. Those wider durations were not measured. Nor does the account establish what later happened to the four open records. The practical distinction survived the conversation; the image itself remained unchanged.
Separate observation, interpretation and a practical test
A short working note can prevent the coach’s interpretation from becoming the next session’s supposed fact. Include the client’s correction prominently. Noel could keep the sketch personally and share only the following action-focused distinctions.
| Observation | Interpretation to avoid | What could actually be checked |
|---|---|---|
| Noel points left toward his monitor | Left represents an unresolved past event | Noel says which displayed record he means |
| He calls some requests close and loud | Those requesters are manipulative | Each request’s deadline, consequence and authority |
| Six records are described as disposed | Six new decisions resulted from coaching | Five new dispositions plus one historical duplicate |
| The sketch stays unchanged | The client resisted the method | Noel’s stated usefulness and subsequent choices |
Second example: a wall becomes a crowded corridor
Mira, a product director, describes a wall between herself and the monthly planning meeting. Her coach, Dan, agrees to explore the expression briefly before returning to the meeting issue. Mira develops it into a crowded corridor with people speaking over one another. Dan does not suggest the corridor or celebrate its appearance as a breakthrough.
Mira says the image change is not particularly important. She still wants to ask about an assumption in the plan without being interrupted. Dan accepts that judgment. They switch to a practical conversation about a speaking turn, including whether Mira wants to make the request and who can authorize it.
On 6 November, Mira asks chair Elena for a three-minute turn at the 10 November meeting, after the finance update. Elena accepts that exact slot the same day. Mira sends her two questions on 9 November as requested. The arrangement gives her a turn, not authority to require colleagues to agree or to secure information they do not have.
At the meeting Elena gives Mira the agreed three minutes. Mira uses two minutes to state the concern and first question, then chooses to use the remaining minute on the response rather than ask the second question. A colleague answers part of the first question; the cost assumption remains disputed. The second question is not asked and no later response is observed.
In the subsequent coaching review, Mira calls the turn useful but the answer incomplete. Dan keeps both parts. A wall becoming a corridor did not demonstrate improved team trust, resolution of the plan or a lasting change in Mira. The actual change was an accepted speaking arrangement that she partly used, with substantive uncertainty still present.
When to stop exploring the image
Leave the approach when the client prefers a direct discussion, cannot use the question, finds the imagery unhelpful or becomes distressed. Ask what support is appropriate within your competence. Do not intensify the process to make an experience “release,” interpret distress as necessary progress, or use this guide as a trauma-treatment protocol.
A real contract, budget or safety constraint may require factual checking or another qualified role. Likewise, the other person’s view requires asking them with appropriate permission. Noel’s image of a request cannot establish Remy’s capacity; Mira’s corridor cannot establish Elena’s intention. Preserve legitimate criticism even if a gentler description becomes available.
Lawley and Tompkins’ Clean Space describes a related but distinct process involving client-located positions. Discussing a spatial metaphor does not automatically constitute that process. The seated examples here do not reproduce its full protocol, require movement or establish that changing physical position produces a particular psychological result.
Keep client-authored reflection separate from the action record
We build Coachful. Coachful is our #1 recommendation for organizing the agreed practical follow-through described here. That is our editorial preference for our own platform, not independent evidence that software improves Clean Language practice or resolves approval problems.
Use an original preparation Form only when it serves an agreed purpose. A short prompt about the work situation and desired review may be enough; do not require a drawing or intimate metaphor history. Deliberately grant the resource and send its private client-access link. A standalone assignment does not automatically become a My Coaching next-action task merely because it was assigned.
Record an agreed action with the actual recipient, acceptance, deadline and evidence to review. A goal’s optional check-in can support a report; the saved words and status still need interpretation with the client. Noel’s five new dispositions should not become six because a progress display looks more complete.
Keep an unshared journal or takeaway page client-owned. Where an enabled Share with coach control is available, explicit sharing exposes that page to the coach. Explain that choice before the client saves sensitive material. Share a separate practical summary when that is all the work requires, rather than asking the client to expose the whole sketch.
Review session recap channels and approval settings before recording sensitive reflections. Automatic recap behavior can differ from a deliberately reviewed message; do not assume every surface waits for your approval. Check the actual recipient view. The Coachful feature overview can help you locate these workflows, while the perceptual-space guide develops the distinction between description and interpretation.
Frequently asked questions
Does left always mean the past?
No. A location has whatever meaning, if any, the client gives it in that context. Check literal references first. Noel’s leftward gesture indicated a real monitor. Treating it as a time orientation introduced the coach’s idea and required an explicit correction.
Is psychoactive space a scientifically measured field?
Not on the basis of the practitioner description discussed here. Explain the term as an account of subjective experience in context. Do not use it to claim a physical energy field, brain measurement or universal relationship between a position and an emotion.
Must the client move around?
No. This guide concerns optional conversational exploration, including seated work, speech or a client-made sketch. Clean Space is a related distinct process. Accessibility, the client’s preference and your competence matter more than producing a particular physical arrangement.
What if I interpret the metaphor?
Notice the addition, name it plainly and invite correction without demanding agreement. Withdraw the interpretation if it is yours rather than the client’s. Then ask whether the person wants to continue exploring or return to the practical issue. A later accurate note does not replace acknowledging a live overclaim.
How do I know an image led to useful action?
Agree what usefulness means to the client and examine actual events with their limits. A changed image, accepted request, completed action and downstream result are different observations. Mira received a speaking turn and an incomplete answer; Noel retained an unchanged image and still had four open records. Neither case establishes method efficacy.
