50 Top Tools for Coaching A Complete Toolkit for Developing and Empowering People

1. 1Ground the client in the four-part EI model first: Self Awareness feeds both Awareness of Others and Self Management, which lead to Relationship Management and ultimately Adding Value. Ask the client to rate themselves against each component before observing anyone else.
2. 2Ask the client to identify one specific colleague or senior person they interact with who demonstrates behaviour they admire — not an abstract paragon, a live example, because a live example accelerates learning where theory stays dry.
3. 3Probe the specifics using Table 11.7: the exact words they use, their tone of voice, their non-verbal behaviour, and the impact on others. Do not accept 'they're just good with people' — force the observable detail.
4. 4When the client cannot answer a probe, do not fill the gap yourself. Assign observation: ask them to watch that person again with greater awareness next time they work together and return with concrete evidence.
5. 5Have the client attend to three channels while visualising the person in action — what they see, what they hear, and what they feel when around the person — so the data covers behaviour and its emotional impact.
6. 6Capture powerful words or phrases worth remembering and how the person manages conflict, then convert the admired behaviours into practice targets the client can rehearse.
7. 7Feed observations into the feedback loop: base your own coaching feedback on specific observed behaviours and examples, never on evaluating the client as a person, so they can choose what to change.
8. 8Close with self-feedback and reflection — after every third or fourth session run the formal evaluation so the client's self-perception is checked against your observations.

A coach is developing a female leader working on gravitas — a quality that is hard to describe and not particularly tangible. Rather than lecture on emotional intelligence, the coach asks her to name a senior colleague whose presence impresses her, then works Table 11.7 line by line. She reports the person uses short, declarative sentences and a steady, unhurried tone; their non-verbal behaviour is open and still under pressure; and the impact is that the room quietens and listens. On the conflict question she is unsure, so the coach sends her to observe that colleague in the next contentious meeting. She returns having noticed the colleague names the tension aloud, uses appropriate humour to release it, and asserts a position without raising their voice. These become her practice behaviours: authentic leadership through high EI rather than performing a role she thinks leadership requires.

• If discussing EI turns dry and theoretical, then switch to a live admired example — observation and reflection on a real person generates better material than the model alone.
• If the client cannot answer a probe about the admired person, then do not supply an answer — assign a fresh observation with greater awareness for next time.
• If the client is underplaying their own progress or successes, then give positive feedback based on what they've told you — but stop short of false praise.
• If you feel the urge to step in and direct, then hold back; to master coaching is to master your own desire to direct — tools exist so clients find their own answers.
• If feedback is drifting toward judging the person rather than the behaviour, then re-anchor to a specific observation with examples.

• Treating gravitas or EI as a definition to explain rather than a behaviour to observe — the tell is a theoretical, dry conversation with no concrete examples on the table.
• Accepting vague admiration ('they have presence') without probing words, tone, non-verbals and impact — the tell is a filled form with no quotable phrases or specific conflict-management moves.
• Filling the gap when the client doesn't know an answer instead of assigning observation — the tell is your voice describing the admired person, not the client's.
• Giving feedback that evaluates the client as a person rather than naming specific observed behaviour with examples — the tell is defensiveness and the client unable to choose what to do next.
• Coaching the woman toward a borrowed leadership persona instead of authentic behaviour built on her own EI — the tell is her believing she has to behave in a certain way to lead.

• ▸Person observed: name the specific colleague or senior person whose behaviour you admire.
• ▸Words they use: record actual phrases, especially powerful ones worth remembering.
• ▸Tone of voice: describe how they sound, not just what they say.
• ▸Non-verbal behaviour: note posture, stillness, gestures and eye contact.
• ▸Impact on others: what happens to people around them as a result.
• ▸How they build rapport: the specific move that connects them to others.
• ▸How they manage conflict: what they do when tension appears.
• ▸What I felt around them: your own emotional response as data.
• ▸My practice target: the one observed behaviour I will rehearse next.

1. 1Listen for the linguistic tells of limiting beliefs before you intervene: phrases like 'I know I should', 'I felt so stupid/inadequate/foolish', or 'I can't achieve this'. These signal that inner dialogue is interfering with the thinking process.
2. 2Run the belief assessment first: ask the client to write down the goal about which they hold a weak, negative or limiting belief, then rate their degree of belief across the five statements (a to e). Push them off middle ratings toward their instinctive response.
3. 3Focus the discussion on the statements scored low. Ask 'What made you opt for that particular rating?' to surface the belief underneath, then re-check whether any ratings shift after discussion.
4. 4Answer questions 1 to 3 on the belief assessment sheet and, if further insight is needed, layer in the challenging limiting beliefs tool (Tables 5.3 and 5.4) to uncover what lies behind the block.
5. 5For the internal dialogue work, name the 'voices' explicitly — ask the client to describe the narrative running through their head before, during or after important situations, and probe where the feeling came from.
6. 6Where you have collected external evidence (a strengths portrait or 360 feedback) that contradicts the self-belief, put the two side by side: the true evidence others give versus the client's own perception, and frame the gap as the belief to change.
7. 7Reframe the belief into empowering language and give the client a physical written reference (portrait or belief sheet) to re-read whenever confidence starts to ebb.
8. 8Align belief, ability and desire before agreeing action — if negative thoughts still undercut belief, the agreed solution will not succeed even with sufficient ability and burning desire.

A woman completes the strengths-based portrait, collating feedback from a range of colleagues. The process surfaces comments she has 'never heard before' — actually received but not absorbed — giving an immediate confidence boost and a reference document. On review she tries to brush the feedback off, asserting people are 'just being kind', so you probe to ensure she accepts it. The exercise reveals a gap: others perceive her strengths clearly, yet her own belief about herself is undercutting her confidence. Because there is now true evidence contradicting her self-perception, you move to a second exercise on limiting beliefs — 'it is clearly time to take a look at changing that belief.' Reading the strengths feedback helps, but the deeper work is changing how she perceives herself, and she keeps the portrait to revisit 'when times get tough.'

• If the client says they cannot achieve the goal, or commits to action then does not take it, then a limiting belief is operating — use the belief assessment to uncover it.
• If they use self-critical statements ('I felt so stupid', 'I know I should'), then intervene on internal dialogue and probe where the feeling originated.
• If external evidence (portrait/360) contradicts their self-perception, then reading the feedback is not enough — schedule the deeper limiting-beliefs work to change the belief itself.
• If the client goes for middle ratings on the belief sheet, then push them to their instinctive response rather than letting them analyse the scores.
• If belief, ability and desire are not all aligned, then do not lock in an action plan — solutions will fail even with ability and desire present.

• Treating strengths feedback as the fix. The tell: the client's confidence lifts briefly but their self-perception is unchanged — deeper belief work was skipped.
• Letting the client deflect evidence ('people are just being kind'). The tell: they brush off or minimise feedback; if you don't probe acceptance, the belief stays intact.
• Accepting middle-of-the-road belief ratings. The tell: scores cluster at the midpoint because the client is analysing rather than answering instinctively.
• Diagnosing a belief too early without listening for the tells. The tell: you intervene on dialogue before hearing the actual limiting statements, so you reframe the wrong belief.
• Agreeing action while belief still lags ability and desire. The tell: the client is capable and motivated but the plan quietly fails because negative thoughts were never surfaced and reframed.

• ▸Goal/outcome: write the goal about which you hold a weak, negative or limiting belief
• ▸Belief ratings a-e: rate your degree of belief in achieving it — instinctive response, no middle scores
• ▸Lowest-scored statement: identify the statement you rated weakest
• ▸Reason for that rating: 'What made you opt for that particular rating?'
• ▸Contradicting evidence: true feedback others have given that conflicts with this belief
• ▸Where the belief came from: name the origin of the feeling or narrative
• ▸Empowering reframe: rewrite the limiting belief into more empowering language
• ▸Re-rated belief: re-score after discussion — note any change
• ▸Reference reminder: where you will keep this to re-read when confidence ebbs

1. 1Test alignment first: before applying any confidence tool, check that belief, ability and desire are present. If ability and desire exist but solutions keep failing, the block is belief — target that.
2. 2Diagnose the negative thoughts holding the person back. Use the Chapter 5 tool 'Changing negative thought patterns' to surface the internal narrative that is undermining self-belief.
3. 3Reprogramme negative language (Table 6.1 negative language indicators): catch the words the client uses that signal limiting belief, then substitute language that supports capability.
4. 4Build a Personal Centre of Excellence for the specific situation — the confidence tools 'zoom in on particular situations' such as reducing nerves before a presentation, so anchor the work to a named upcoming event.
5. 5For deeper belief work with women (Chapter 11), manage the 'voices' through internal dialogue work and define the 'inner team' so competing internal positions are named and organised.
6. 6Confirm the shift links outward: connect the restored self-belief to the Chapter 7/8 work on personal impact and influence so confidence shows up in real interactions, not just internal state.
7. 7Reassess belief after the intervention using the belief assessment (Table 5.6) to verify the limiting belief has actually moved before agreeing action.

A client has a burning desire to present at a leadership meeting and clearly has the ability, yet every rehearsal collapses. Applying the alignment check, the coach finds belief is the missing piece — the client says 'I always freeze, I'm just not a presenter.' The coach uses the negative language indicators to flag 'always' and 'just not', then reprogrammes them into capability-based language. They build a Personal Centre of Excellence anchored to a moment the client did speak well, using it to reduce nerves for the specific presentation. The penny drops around the realisation that 'the only thing stopping me is me.' A belief reassessment confirms the shift before the client commits to the presentation as an action.

• If ability and desire are present but agreed solutions still fail, then treat belief as the block, not skill.
• If the client uses absolute negative language ('always', 'never', 'just can't'), then apply reprogramming of negative language before any action planning.
• If nerves are tied to a specific event like a presentation, then use the Personal Centre of Excellence to zoom in on that situation rather than working on generalised confidence.
• If you are coaching a woman and internal self-talk is loud, then use the inner-team and 'voices' tools from Chapter 11 to name and manage competing internal positions.
• If the limiting belief has not moved on reassessment, then do not proceed to action planning — return to values and beliefs work.

• Jumping to action plans while the underlying negative belief is intact — the tell is agreed solutions that repeatedly 'will not succeed' despite ability and desire.
• Treating low confidence as a skills gap and coaching technique when the real block is belief — the tell is the client performs in practice but not when it counts.
• Ignoring the client's language — the tell is you accept phrases like 'I'm not a presenter' as fact rather than as a negative language indicator to reprogramme.
• Working on generalised confidence instead of the specific situation — the tell is vague goals with no named event, so nerves are never actually tested and reduced.
• Confidence built in the room that never transfers to real relationships — the tell is no link made to the personal impact and influence work in Chapters 7 and 8.

• ▸Target situation: name the specific event or challenge (e.g. the upcoming presentation).
• ▸Desire rating: how strongly do you want this outcome, and why?
• ▸Ability check: what evidence shows you already have the skill to do this?
• ▸Belief statement: what do you currently believe about your ability here — in your own words?
• ▸Negative language indicators: which words or phrases signal a limiting belief?
• ▸Reprogrammed language: the capability-based replacement for each negative phrase.
• ▸Personal Centre of Excellence anchor: a past moment of doing this well to draw on.
• ▸Belief reassessment: rate belief before and after the work to confirm the shift.
• ▸Transfer point: where will this restored confidence show up in a real interaction?

1. 1Wait until rapport and psychological safety are established before attempting deep motivation work — never use the values/mission tool at the first session; sequence it after goals, beliefs and values have surfaced.
2. 2Build the client's mission statement using the template chain: 'Because you…' (why the topic matters), 'Therefore you…' (the benefit), 'Whenever you…' (the context), 'So that you…' (why the benefit matters in that context), 'If you…' (the precondition/what else is true), 'Although you…' (the reality check that they won't always act true to it), 'In the same way that you…' (reassurance the underlying motivation persists).
3. 3Produce a physical written reminder of 'why' the goal matters and have the client keep a personal copy to review at moments of doubt or when action becomes challenging.
4. 4When defining a goal, run part one of the framework, then explicitly ask 'Do you still want this outcome?' — if 'No,' return to step one to find the real goal; if 'Yes,' write it in measurable terms so there's a gauge for achievement.
5. 5Break the goal into measurable chunks, define milestones under 'Steps to take,' and have the client specify how they will celebrate success on achievement.
6. 6Secure ownership physically: have the client sign and date the goal at the bottom, keep it visible, and take a copy yourself to revisit at the next session.
7. 7When motivation stalls, ask the client to recall a past goal they achieved and were pleased with, work through the inner, other-people and material resources that made it work, then ask how they can access those same resources for the current goal.
8. 8Deliver feedback from specific observations of the client's own behaviour with concrete examples — never evaluate the person; the more specific the observation, the easier it is for the client to choose what to do.

A weight-loss client started well but has plateaued and begun to 'yo-yo,' growing disconcerted that they may never reach the goal, which blocks their thinking. Rather than solving the problem, you send them back to a goal they achieved and were genuinely pleased with, and ask them to picture what success looked like and how they felt. Working through it, they name the resources that carried them — an accountability partner (others), a written plan they reviewed daily (material), and their own discipline (inner). You ask what they learned and what they'd do differently, keeping the reflection in depth and positive. Then you ask how they could access those same resources now, and they decide to rebuild the daily plan and re-recruit their partner. You revisit the goal-setting framework, break the target into measurable chunks with milestones, and have them sign and date it so ownership sits with them, not you.

• If the client 'knows what they should be doing but doesn't find the will to do it,' then use the values/mission tool to connect action to what truly motivates them.
• If, after part one of goal-setting, the answer to 'Do you still want this outcome?' is 'No,' then don't proceed — return to step one to establish the actual goal.
• If the client believes the goal is a real stretch and is unsure of achieving it, then set short-term stretch targets that challenge without setting them up to fail.
• If the client is 'battle fatigued' or negative about a goal, then anchor them to a past success and its resources before touching the current plan.
• If you are about to give feedback, then base it on specific behavioural observations with examples — if you can't cite an example, don't give it as feedback.

• Solving the problem for the client or adding your own suggestions too early — the tell: you're talking more than they are and the plan is yours, not theirs; hold the ORACLE principle that the client has the solution and only offer ideas at the end if they're genuinely stuck.
• Asking multiple or leading questions ('Are you happy with that?', 'So you didn't mind…?') — the tell: you're assuming the answer or putting words in their mouth, letting them dodge the most important question.
• Setting a goal the client hasn't bought into — the tell: no signature, no visible copy, and the client can't articulate the 'why'; ownership hasn't transferred.
• Using the deep values/mission tool before rapport and safety exist (e.g. at session one) — the tell: the client stays surface-level and won't explore the deeper topics.
• Turning feedback into evaluation of the person rather than observation of behaviour — the tell: the client gets defensive instead of curious, because the comment named who they are, not what they did.

• ▸Because you… — the reason this topic/goal is important to you
• ▸Therefore you… — the benefit you get from it
• ▸Whenever you… — the context in which you achieve that benefit
• ▸So that you… — why that benefit matters in this context
• ▸Although you… — the honest reality check: how you won't always act true to it
• ▸In the same way that you… — reassurance that the underlying motivation is still there
• ▸My outcome (goal), in measurable terms — what, where, with whom, by when
• ▸Steps and milestones to achieve it — the measurable chunks and how you'll celebrate
• ▸Signed and dated by client — the ownership marker; keep visible, coach keeps a copy

1. 1Run the client through the full ORACLE cycle before planning: clarify the Outcome, find the Real issue, generate Alternatives, add Creative ideas, rate Likelihood of success 1-10, then Execute — do not rush to alternatives while the problem is still unclear.
2. 2At the Execute step, build the plan with the client, not for them: define what the plan is, who is involved, who will help, and how they will communicate.
3. 3Pressure-test each planned action against timings, potential barriers, environment, and support required; capture suggestions to overcome each barrier.
4. 4Rate every candidate action 1-10 for likelihood of success and reflect on the consequences before committing, so momentum goes to options the client believes in.
5. 5Anchor motivation to a written 'why' using the powerful-intentions template so the client can review it when taking action becomes challenging.
6. 6Record actions on the action plan (Table 1.7) with a spatial or timeline layout so the sequence and deadlines are visible.
7. 7Stay out of 'telling' mode — if you hand over your solutions the client may look grateful but come away frustrated because the fix isn't right for their situation; let them try, return, and modify.
8. 8At the end of each session ask for feedback on what the client is taking away, and after every third or fourth session review formally to check actions are sticking.

A client states an overall issue: they keep missing a workplace target. Using ORACLE, you avoid detail questions and keep them in flow, then summarize and reflect back to confirm accuracy. In Outcome, you ask them to describe success using all senses — what it looks like and what others would say. Testing the Real issue reveals the stated problem (poor planning) is actually avoidance driven by negative self-talk, so you note it links to a beliefs and confidence tool. You generate Alternatives and one Creative idea never tried before, rate each 1-10 for likelihood and consequences, and select the highest. In Execute you set out timings, likely barriers, who will help and how they'll communicate, then have the client write a 'Because you… therefore you…' intention to keep with them. Because a deeper concern surfaced, you cycle back rather than settle for a symptom-level fix.

• If the client knows what they should do but consistently avoids acting, then use the powerful-intentions template to anchor motivation before more planning.
• If the stated issue still feels like a symptom, then re-enter the ORACLE cycle rather than executing a plan on root-unclear ground.
• If belief, ability and desire are not all aligned, then address the confidence/beliefs gap first, because agreed solutions will fail even with ability and desire present.
• If you catch yourself giving solutions, then stop and return to questioning — let the client generate options they own.
• If a planned action carries clear barriers, then attach a named overcome-suggestion, support source and communication method before it goes on the action plan.

• Jumping to alternatives before the outcome is well-formed — the tell is a plan that keeps stalling because it targets the wrong problem.
• Slipping into telling mode — the tell is the client looking grateful in-session but returning with the actions undone or ill-fitting.
• Skipping the likelihood rating — the tell is committing to actions the client doesn't actually believe will work, so momentum dies between sessions.
• No written 'why' — the tell is motivation collapsing the moment action becomes challenging, with nothing to review.
• Treating the first surfaced issue as the real one — the tell is repeated returns to the same problem because you fixed a symptom, not a root cause.

• ▸Outcome: describe success with all senses — what it looks/feels like and what others say
• ▸Real issue: state the underlying issue confirmed after probing (not the presenting one)
• ▸Chosen action: the single option you're committing to
• ▸Likelihood score (1-10): rating plus the main consequence to weigh
• ▸Who's involved / who helps: named people and the support required
• ▸Barriers + overcome suggestion: each risk paired with a countermeasure
• ▸Timings: start date and deadline for this action
• ▸Communication: how and when progress will be shared
• ▸Why it matters (written intention): 'Because you… therefore you…' statement to review when it gets hard

1. 1Establish absolute goal clarity first: before exploring solutions, use goal-setting and visualization tools so the client can state precisely where they want to get to — clients think more clearly about solutions once they have this clarity.
2. 2Decide whether the work is remedial (resolve a problem) or generative (increase performance and potential); expect to move from remedial to generative once the client resolves the problem and starts to experience progress.
3. 3Align the three requirements for full goal attainment — belief, ability and desire — and use confidence-strategy tools to address negative thoughts that undermine belief.
4. 4Set a measurable baseline using 360-degree feedback or the communication skills audit at the beginning of the relationship to design coaching goals and capture starting scores.
5. 5Run the feedback process with rigour: have the client randomly select ~6 recipients per group (send to all if a group is 6-8), issue anonymous questionnaires scored 1-6 with a sealed-envelope return and a two-week deadline.
6. 6Analyse results together for trends, similarities, gaps in perception and unusual variations; identify both strengths and areas for improvement.
7. 7Convert findings into a specific, prioritized action plan limited to two or three areas at a time (top three first, then the next three).
8. 8Re-run the same instrument at the end of the relationship to measure progress against the baseline, and use validating feedback to recognize progress the client may be underplaying.

A leader who is 'achieving success but doesn't know why' seeks structured 360-degree feedback. At the start, the coach helps them select relevant groups — direct reports, indirect/virtual team members, bosses and peers — and randomly picks about six per group to avoid bias, sending to everyone in any group of six to eight. Recipients score management skills on a 1-6 scale, return sheets anonymously in sealed white A4 envelopes within two weeks, and the client completes their own self-assessment without over-analysing. In the next session (allow 60-90 minutes) the coach places scores on the results sheet and analyses trends and gaps — noticing, for example, that management skills score higher than team-building skills. Together they identify strengths to capitalize on and pick two or three areas for an action plan. Because the same tool can be run at beginning and end, the client can later measure improvement against this baseline, demonstrating measurable positive change.

• If the client lacks clarity on the desired outcome, then do goal setting and visualization before any problem-solving — clarity precedes solutions.
• If the presenting issue is a problem to resolve, then use remedial coaching first; once progress is felt, then shift to generative coaching for higher performance.
• If negative thoughts are affecting belief, then work on confidence strategies, because full goal attainment needs belief, ability and desire aligned.
• If a group being surveyed contains six to eight people, then send the questionnaire to everyone; otherwise randomly select about six to stay representative and unbiased.
• If the client identifies more than three improvement areas, then plan the top three first, then the next three — never action-plan all at once.
• If you want to demonstrate measurable change, then run the same feedback instrument at both the beginning and the end of the relationship.

• Skipping goal clarity and jumping to solutions — the tell: the client generates scattered options and struggles to evaluate them.
• Treating feedback as evaluation of the person rather than specific behavioural observation — the tell: the client becomes defensive instead of gaining understanding of what to do.
• Withholding recognition of progress to stay 'objective and detached' — the tell: the relationship stays cool and the client underplays their own successes.
• Compromising anonymity or confidentiality of feedback data — the tell: recipients give guarded scores and the feedback is too bland to design improvement actions.
• Overloading the action plan with too many areas — the tell: nothing gets done because focus is diluted beyond two or three priorities.
• Setting the return window wrong: too long and recipients forget, too short and they don't complete — the tell: low or rushed response rates.

• ▸Desired outcome: state precisely where the client wants to get to
• ▸Coaching type: mark remedial (resolve problem) or generative (increase performance)
• ▸Belief-Ability-Desire check: note gaps in each of the three and how to align them
• ▸Baseline measure: instrument used (e.g. 360-degree / communication skills audit) and start-of-relationship scores
• ▸Strengths identified: what to capitalize on and continue using as a resource
• ▸Priority improvement areas: list the top two or three only
• ▸Action plan: specific steps for the priority areas with a review date
• ▸Progress validation: recognized gains fed back to the client (avoid false praise)
• ▸End-of-relationship re-measure: repeat scores and change vs baseline

1. 1Start any neurodivergence-focused session by eliciting strengths before difficulties: ask the person to describe their unique gifts first, then where they need more support, so they don't lead with self-negative framing.
2. 2Build psychological safety as the precondition — if you manage the person, create a culture where open dialogue about needs and goals is expected, not exceptional; this is your responsibility, not the coachee's.
3. 3Audit for concrete barriers before adapting: inflexible systems, sensory sensitivities, communication difficulties, the setup of the working day, and misunderstandings from managers or colleagues. Name which apply to this individual.
4. 4Adapt coaching methods to the person's actual thinking style rather than a generic template — align questioning pace, structure, and sensory environment to how they process information.
5. 5In hybrid/tech-mediated settings, decide your position on the technology before the session: form a clear coaching philosophy and framework (see The Coaching Process), then classify whether AI or coach bots fit as transactional support or whether the work is transformational and needs a human.
6. 6Shift from presence to performance: refine delegation, strengthen communication, and run explicit conversations checking that people feel comfortable working at home and that you're using the right management style to get the best from them.
7. 7Reuse and reshape existing tools to fit the individual — repurpose any of the book's tools rather than starting from scratch, adapting for the outcome the coachee seeks.

A coach works with a mature autistic professional who consistently describes their neurodivergence only through its negative impact. Rather than problem-solve the difficulties first, the coach uses the 'Identifying and communicating strengths and challenges' tool, which is especially important for people more mature in life who have long framed the condition as a deficit. They surface unique gifts first — for instance persistence ('I work through any difficulties I see to reach my goal') and empowering others — before mapping where support is genuinely needed, such as sensory sensitivities or an inflexible working-day setup. Because the coach establishes psychological safety, the person feels able to express needs openly instead of masking them. The R.E.A.C.T. tool then helps the coachee evaluate lingering negative feelings and let them go. The output is a person who can appreciate and articulate their strengths and specify precise support requirements, rather than one defined by challenges.

• If the coachee describes themselves negatively or focuses only on difficulties, then elicit strengths and unique gifts first before addressing support needs.
• If you are neurotypical and coaching a neurodivergent person, then check your assumptions against their stated experience — without exposure to varied individuals, stereotyping occurs and neurodivergence manifests differently for every person.
• If the setting is hybrid, then stop relying on presenteeism — visibility is not productivity; run performance and comfort-at-home conversations instead.
• If considering AI or a coach bot, then classify the work as transactional versus transformational first; use bots to supplement transactional coaching, not to replace transformational relationship work.
• If a barrier is structural (inflexible systems, working-day setup, sensory environment) rather than personal, then adapt the environment, not the individual.

• Leading with the problem list — starting with difficulties reinforces the coachee's negative self-description; the tell is the person only ever narrating what their neurodivergence costs them, never what it gives them.
• Assuming one neurodivergent adaptation fits all — the tell is applying a fixed protocol; neurodivergence manifests differently for every person and stereotyping follows from limited exposure.
• Managing hybrid workers by visibility — the tell is treating presence as productivity and using the same style that worked when everyone was physically present.
• Skipping psychological safety — the tell is that needs and goals never get named openly because the culture doesn't invite the dialogue.
• Treating the tool's output as the point — the tell is a completed template with no real conversation; the value is the exploration and shared understanding, not the artefact.

• ▸Strengths and unique gifts — list what this person is genuinely good at, before anything else
• ▸Support needs — where they need more support, stated as needs not deficits
• ▸Barriers present — tick which apply: inflexible systems, sensory sensitivities, communication, working-day setup, manager/colleague misunderstanding
• ▸Thinking/processing style — how they take in and work through information, and how you'll flex questioning to match
• ▸Setting adaptation — in-person, remote, or hybrid; what environmental changes are needed
• ▸Technology stance — transactional (bot/AI supplement) or transformational (human); note your coaching philosophy anchor
• ▸Psychological safety check — evidence that open dialogue about needs is actually happening
• ▸Repurposed tool — which existing tool you'll adapt and for what outcome the coachee seeks

1. 1Trigger the contracting meeting for any formal coaching relationship predicted to last more than one session — do not skip it because the client seems keen or the sponsor is in a hurry.
2. 2Open with the coaching brief (Table 1.3) to run a structured discussion that surfaces the development areas the client wants to work on and any other development activity running in tandem — ask for copies of previous profiling or feedback reports.
3. 3Name and set expectations for the tripartite relationship between client, coach and the client's manager: agree what the manager sees, what stays between coach and client, and how the three parties interact.
4. 4Use the checklist for establishing contract rules (Table 1.6) as the meeting agenda — turn each heading into a discussion point and tick items off as covered, phrasing the suggested questions in your own style.
5. 5Agree measurement upfront: capture baseline and desired outcomes so ROI can later be reported back to the client or sponsor.
6. 6Establish explicitly how you will both give and receive feedback during the relationship (this is what the periodic evaluation at Tables 1.8/1.9 later relies on).
7. 7At the end of each checklist section, ask the client if anything is missing — coaching is collaborative, so let them add items not on your list.
8. 8Document notes and, at meeting close, revisit any unchecked items and cover them before sessions begin.

A coach is commissioned by an organization to run six sessions with a mid-level manager. Before session one, the coach convenes a contracting meeting using the coaching brief and the contract-rules checklist as a joint agenda. The client discloses she recently completed a 360 profile, so the coach requests a copy to inform the work. They map the tripartite relationship: the coach will share broad themes with her line manager at a mid-point review, but the content of individual sessions stays confidential. They agree the desired outcome (improved delegation), a baseline, and how progress will be measured so ROI can be reported to the sponsor. Finally they agree that the client will give feedback formally after every third session and informally at the end of each — which becomes the basis for the later evaluation forms.

• If the engagement is predicted to last more than one session, then run the full coaching brief and contract form — a single ad-hoc conversation does not warrant it.
• If a client's manager is involved, then explicitly define the tripartite boundaries (what is shared vs. confidential) before sessions start, not later.
• If the client has prior development or profiling, then request copies during contracting so they inform the coaching process.
• If the client raises a topic not on your checklist, then discuss it — collaboration means the list is a floor, not a ceiling.
• If any checklist item remains unticked at meeting close, then go back and cover it before the first coaching session begins.

• Treating contracting as a formality and rushing it — the tell is that goals, boundaries and measurement stay vague and disputes surface mid-engagement.
• Leaving the tripartite relationship undefined — the tell is a manager expecting session-level detail the client assumed was confidential.
• Skipping baseline measurement — the tell is being unable to demonstrate ROI to the commissioning client at review.
• Not agreeing the feedback mechanism upfront — the tell is that the periodic evaluation (Tables 1.8/1.9) feels imposed and clients disengage from it.
• Being over-prescriptive about process and style — the tell is a stilted meeting where the client never adds their own concerns and disengages early.

• ▸Development areas: what the client wants to work on, in their words.
• ▸Parallel activity: other development or profiling running alongside — attach copies.
• ▸Tripartite boundaries: what the manager sees vs. what stays confidential.
• ▸Desired outcomes: specific goals agreed for the assignment.
• ▸Baseline and measurement: starting point and how success/ROI will be evidenced.
• ▸Ways of working: session frequency, format, cancellation and boundaries.
• ▸Feedback method: how and when coach and client will give/receive feedback.
• ▸Anything missing: client-added items not on the standard list.
• ▸Sign-off: items ticked, notes documented, both parties clear before session one.

1. 1Run the four Rs of effective listening (Table 2.2) in every conversation, not just formal coaching sessions — treat listening like running, a constant discipline that consumes energy, not a switch you flip on.
2. 2Recognize that you likely default to a quarter of your listening capacity; consciously stop the mind-wandering, the pre-loading of your next question, and the rush to solutions that eat the other three-quarters.
3. 3Reflect back what the client says: repeat or paraphrase to let them check what they said, verify your understanding, buy yourself thinking time, and deepen rapport — this is the skill the model calls critical to a successful outcome.
4. 4Listen without judgement and prejudice; when you notice yourself evaluating or diagnosing, park it and return attention to the client's words.
5. 5Select questioning techniques from Table 2.3 that fit the moment; use indirect, open prompts like 'What else?' or 'Anything else?' to draw out detail without leading, and record the client's exact words rather than interpreting them.
6. 6Deliver feedback using the techniques and examples in Chapter 2, keeping the amount of challenge appropriate — enough to move thinking, not so much it feels like interrogation.
7. 7Sequence the whole discussion on the ORACLE model (Figure 2.2, Tables 2.4–2.6) as your basic route map, using the step-specific questions in Table 2.6 to move the client through each stage.
8. 8Adapt any tool to your own style — these tools are non-prescriptive and lend themselves to any coaching approach, directive or non-directive; ask permission before using the more creative ones.

The logical-levels exercise (Table 4.1, adapted from Robert Dilts) shows foundation skills in action. You spread six laminated levels — environment, behaviour, capabilities/skills, values and beliefs, identity, vision — across the floor with space between them, and help the client get relaxed and comfortable. You invite them to stand on 'environment' first and move up the levels one by one. At each level you ask only indirect questions — 'What else?', 'Anything else?' — which is disciplined questioning that draws out material without leading. You write down as much detail as possible in the client's exact words, deliberately not interpreting, which is listening without judgement. When they have visited every level you ask reflective closers such as 'What surprised you?' and 'What was the most interesting thing?', letting the client discover a block they may only have felt as ambivalence.

• If the client has just made a significant statement, then reflect it back before asking anything new — this checks understanding and hands them a chance to expand.
• If you catch yourself planning your next question while they speak, then stop; you have dropped into the wasted three-quarters of listening capacity.
• If the conversation is starting to feel like an interrogation, then increase reflecting and summarizing and reduce direct questioning.
• If a tool does not fit your style, then adapt it rather than abandon it — the tools are non-prescriptive by design.
• If you are about to use a more creative tool, then ask the individual's permission first.

• Treating listening as a mode you 'wheel out' at the start of coaching — the tell is that you listen well in sessions but tune out in ordinary conversations; the model says use it every time anyone talks to you.
• Interpreting or paraphrasing into your own words instead of recording the client's exact language — the tell is your notes read like your analysis, not their statements, and the client says 'that's not quite what I meant.'
• Skipping reflecting to save time — the tell is you have no thinking gap, rapport stays shallow, and the client never gets to check what they said.
• Leading with solutions or advice because your mind raced ahead — the tell is you are talking more than the client and the discovery is yours, not theirs.
• Over-coaching everyone once you catch the bug — the tell is people find it 'a little wearing' being constantly coached; use your style with discretion and only when appropriate.
• Flicking through the toolkit in front of the client hoping to stumble on something — the tell is visible page-turning, which erodes their confidence in your ability to help.

• ▸Client's exact words (key statements): record verbatim, do not interpret.
• ▸Reflection I offered: write the paraphrase/repeat you gave back to check understanding.
• ▸Listening capacity check: note where your attention wandered or you pre-loaded a question.
• ▸Questions used (from Table 2.3): list the open/indirect prompts, e.g. 'What else?'
• ▸ORACLE step reached (Table 2.6): mark which step of the route map this covered.
• ▸Feedback given: state the observation and the level of challenge used.
• ▸Rapport/interrogation gauge: rate whether it felt like dialogue or questioning.
• ▸Permission asked: tick if you sought consent before any creative tool.
• ▸What surprised the client: capture their discovery in their own words.

1. 1Read through the full toolkit ahead of sessions so tools live in memory; the goal is to say, 'I think I know a process that will help you,' not flick through a manual in front of the client.
2. 2Classify the presenting situation before selecting a tool: goal setting, problem resolution, confidence, conflict, career, teams/leadership, or change. Match to the relevant chapter (e.g. conflict to Chapter 7's Behavioural conflict resolution, delegation to Chapter 9's delegation framework).
3. 3Separate whether the problem is situational (needs handling now) or developmental (recurring pattern needing longer work), because this determines the depth of tool — Self-coaching splits explicitly on this fork.
4. 4Match tool to available time: use the ORACLE model for a full session, coffee-break coaching or the two-minute summary/five-minute mind map when the discussion must fit a short space.
5. 5Adapt the chosen tool to the client — feed it with the client's own descriptions and observed language, and check your own emotional state so you are not imparting wisdom or externalizing frustration.
6. 6Teach self-directed tools (Self-coaching) so clients keep momentum between sessions and do not become dependent on you.
7. 7Build a written plan inside practical tools (delegation, goal setting) so the client is more likely to act at the right time with the right person.

A manager client arrives overloaded and stuck in transactional work — the tell that signals the Improving the delegation process tool (Table 9.2). You first ask her to assess her delegation skills and to name the reasons she does not delegate; she says, 'It's quicker to do it myself.' You discuss whether that reason is real or perceived, then work through the form to identify a specific team member and the impact on her workload if she hands the task over. You ask what is most critical about the task — accuracy, deadline, or content — and how she will get that message across. You then explore what training or coaching that team member needs to reach the required standard, and what she herself learned from doing the task (a shortcut, a specific step). The output is a written delegation plan, which makes it more likely she delegates to the right person at the right time.

• If the problem is situational and time-boxed, use Self-coaching or a short-form tool; if it recurs and is developmental, move to a fuller developmental process like goal setting or belief work.
• If the client is overloaded or too transactional, apply the delegation tools; if there is role confusion or conflict between teams, use the Chapter 7/9 conflict and team climate tools instead.
• If you have only minutes, run coffee-break coaching or the two-minute summary rather than trying to force ORACLE.
• If you feel the urge to give feedback, use it only when it will help the client — check whether you are validating progress or venting frustration first.
• If a client is underplaying genuine successes they told you about, give positive feedback grounded in their own words, but stop short of false praise.

• Flicking through the toolkit in front of the client hoping to stumble on something — the tell is loss of client confidence and a stalled session.
• Applying a tool without classifying situational vs developmental first, so you treat a recurring pattern with a one-off fix (the tell: the same dilemma returns next session).
• Using feedback to impart your wisdom or offload frustration — the tell is feedback that evaluates the person rather than helping them.
• Treating feedback as objective truth when you only have the client's distorted single-perspective account of a situation you never observed.
• Letting the client become dependent on you by never handing over self-directed tools — the tell is they cannot resolve anything between sessions.

• ▸Presenting situation: name it (goal / problem / confidence / conflict / career / team / change)
• ▸Situational or developmental? — is this a now-problem or a recurring pattern
• ▸Objective: what does the client want to solve or resolve
• ▸Time available: minutes / one session / ongoing — pick tool length accordingly
• ▸Candidate tool + chapter source: which specific tool matches
• ▸Client/context adaptation: what to change for this person's language and situation
• ▸Congruency check: how does the proposed approach feel to the client
• ▸Handover: which part the client can run themselves between sessions

1. 1Set psychological issues explicitly in the contract meeting, not by assumption: agree how you will both check the relationship is going well, who initiates reviews and how often, and what you will each do if things are not working. Allow 30 minutes to cover the full checklist.
2. 2Define confidentiality limits precisely before the first session, including what you record, where it is stored, who has access, and what (if anything) a third party or organization can see. Get the coachee's explicit agreement to any record-keeping.
3. 3Nail down the physical conditions for safety: choose a private venue, refuse cafés or public places, and assign explicit responsibility for ensuring meetings are private and uninterrupted.
4. 4Agree a shared definition of honesty and feedback so the coachee knows candour will not become judgement, and surface any hidden agendas openly.
5. 5Build listening that creates space: be comfortable with silence, offer observations and intuitions rather than verdicts, and signal that you 'get' them in a spirit of mutual support so they feel safe to disclose.
6. 6In groups, co-create a manifesto (e.g. 'creating a feeling of safety over challenging comfort zones') as version 1.0 that the group adapts, so safety is owned collectively rather than imposed.
7. 7Only run high-exposure exercises (like the group 'hot seat') once good working relationships and psychological safety are already established, and always keep an explicit opt-out — being coached is always by agreement.
8. 8Confirm agreed points in writing after the meeting so both parties share the same understanding and any concern can be raised and addressed before session one — not as a legal contract but as a common reference point.

In the group coaching 'hot seat' tool, one person volunteers to be coached while the group becomes the coaches. This exercise both requires a psychologically safe environment and creates one — so you only use it where the group has already formed good working relationships and safety is well established. No one is pressured into the chair; inviting people forms part of contracting and the opt-out option is always on offer. Some coachees choose it precisely to step out of their comfort zone because they place great trust in the coach and their colleagues. The coachee keeps pen and paper to capture what is useful, and coaches may take notes for them. The real depth comes from the reflection at the end: what people learned about the process and about themselves — building trust and supporting behaviours as the key outcomes.

• If a client suggests meeting in a café or public place, then refuse and relocate — coaching always requires privacy.
• If safety and working relationships are not yet established in a group, then defer high-exposure tools like the hot seat and build trust first.
• If any record will be kept, then get the coachee's explicit agreement on what is recorded and where it is stored before proceeding.
• If a group is over-editing — evaluating and judging so they won't share unfinished ideas — then co-create or improvise a tool to demonstrate it's ok to experiment.
• If leading in a hybrid/virtual setting, then shift from presence- and visibility-based management to trust-based leadership, since it does not come easily and its absence reads as micromanagement.

• Treating the contract as paperwork and skipping the psychological issues — no agreed review cadence, no definition of honesty, hidden agendas left buried. Tell: the client goes guarded or stops disclosing and you don't know why.
• Leaving confidentiality limits vague, especially with an organization paying. Tell: the client hedges on what they say 'in case it gets back'.
• Compromising on venue privacy. Tell: interruptions, a client glancing at the door, thin surface-level conversation.
• Just 'showing up' rather than attending to how you show up — filling silence, giving verdicts instead of observations. Tell: no thinking space, questions land flat, client doesn't feel 'got'.
• Pressuring participation in group exposure exercises or forcing the opt-out closed. Tell: reluctant volunteers, defensiveness, withdrawal after the session.
• In hybrid work, managing by presenteeism and visibility. Tell: employees report feeling micromanaged, disconnected or anxious about visibility.

• ▸Confidentiality limits — state exactly what stays private and what any third party may see.
• ▸Records — what you record, where stored, and confirm coachee agreement (Y/N).
• ▸Venue & privacy — named private location; who ensures meetings are uninterrupted.
• ▸Definition of honesty — agreed meaning of candour, especially for feedback.
• ▸Ongoing check-in — how you'll both check the relationship is working; who initiates reviews and how often.
• ▸If things go wrong — what each of you will do; how to end or conclude the relationship well.
• ▸Hidden agendas — any surfaced now (list) / none.
• ▸Opt-out clause — confirm no one is pressured into any exercise; participation by agreement (Y/N).

1. 1Open by asking clients to name the development area in depth, then ask them to outline desired outcomes in observable terms: 'How will you be different in six months?'
2. 2Sharpen each outcome into sensory-specific detail using the calibration questions: 'What would success look like?', 'What would I see you doing differently?', 'What would others notice that was different about you?'
3. 3Test how well formed the outcome is — the Outcome stage of ORACLE asks both 'What is the desired goal?' and 'How well formed is it?' — and keep working until the client can describe it, not just state it.
4. 4Run a visualization: ask clients to use all senses to describe how they would feel if they achieved the outcome, since imagining the achieved state supplies the driving force.
5. 5Pressure-test relevance and impact: push clients to describe what impact their changed behaviour would have on the business; if they genuinely can't name any impact, reconsider whether to proceed.
6. 6Record the outcomes on the coaching brief (Development area; Desired outcomes 1, 2, 3; Measurement of success) so goals are documented and ROI is measurable.
7. 7Surface obstacles and fears attached to the goal now (personal fears, confidentiality, time constraints) and agree how they'll be handled, so the goal survives contact with reality.

Using the coaching brief and contract form, you explain its purpose, then ask the client to describe their development area in depth. Once explained, you ask them to outline desired outcomes: 'How will you be different in six months' time?' To make it well-formed rather than vague, you ask 'What would success look like?' and 'What would others notice that was different about you?' You then push them to describe the business impact of that changed behaviour — and note that if they truly cannot describe any impact, you would think hard about whether to proceed. You capture Desired outcome 1, 2, 3 on the form along with Measurement of success, and discuss potential fears and obstacles and how each can be handled. The whole discussion takes about 45 minutes, and you let the conversation flow rather than sticking rigidly to the form, filling gaps with specific questions afterwards.

• If the client can only state a goal but cannot describe what success looks like or what others would notice, then keep asking calibration and visualization questions before moving to solutions — clarity on the destination precedes generating options.
• If the client cannot describe any potential business impact of their changed behaviour at all, then reconsider whether you should proceed with the coaching.
• If the client was nominated with minimal discussion and hasn't thought through what they want, then use the self-assessment questionnaire before the first meeting to build their own clarity on expectations and outcomes.
• If new problems or issues surface while defining the outcome (as often happens in ORACLE), then be prepared to cycle back rather than force linear progress, continuing until you've tackled root causes not symptoms.
• If the client has absolute clarity on where they want to get to, then expect them to start thinking more clearly about solutions on their own — this is the tell that the goal is well-formed.

• Rushing to alternatives and creative ideas before the outcome is well-formed — the tell is that the 'stated issue is rarely the real issue' and solutions keep failing to stick because you tackled a symptom.
• Accepting a stated goal as clear when it's only labelled, not visualized — the tell is the client can name the goal but goes blank on 'What would others notice that was different about you?'
• Keeping too rigidly to the brief form and interrogating for detail — the tell is the conversation stops flowing; instead let it flow and fill gaps with specific questions later.
• Setting goals at the wrong level — the self-reflection checklist explicitly asks 'Did you set goals at the right level?', and getting this wrong means the goal fails to provide direction or driving force.
• Skipping the impact/measurement conversation, so the goal has no ROI anchor — the tell is you cannot later demonstrate return on investment or measure success.

• ▸Development area: state the area the client wants to work on in depth
• ▸Desired outcome (1–3): how the client will be different in six months, in observable terms
• ▸What success looks like: sensory-specific description — what you'd see them doing differently
• ▸What others would notice: how the change registers to colleagues or manager
• ▸How it feels achieved: visualize the outcome using all senses and note the feeling
• ▸How well formed (1–10): rate the clarity of the outcome; below threshold, keep working
• ▸Business impact: the effect of the changed behaviour on the business (if none, reconsider)
• ▸Fears/obstacles + handling: concerns or hurdles attached to the goal and how each is addressed
• ▸Measurement of success: the evidence and information that will confirm the outcome is met