The CORE Coaching Framework: Behavioural Coaching Built for Real Managers

13 min read

Every leader knows coaching their team matters. They also know they have a quarterly budget reconciliation on Tuesday, a two-day offsite to finalise next year's strategy, and that new software implementation training they are already two weeks behind on. Toss in a major customer escalation that has derailed their entire morning, a cleanup of the team's knowledge base so the AI assistant stops hallucinating, and a stack of resumes to review and interviews to conduct before the end of the week. The backlog has been quietly stretching for weeks.

That tension is the heart of the problem. The "do more with less" culture, the pressure to perform, the pace of change. None of it leaves much room for the slower work of coaching. And coaching is the one thing you are able to put off without anyone noticing right away. The offsite, the customer fire, the software training, the hiring interviews. Those things will not wait. Coaching, quietly, will. Until it does not.

Most coaching frameworks do not help with this. GROW assumes you have time to set goals. Co-Active assumes you are a trained coach with an hour-long session ahead of you. CLEAR opens with a contracting stage that is hard to honour when the conversation has already started. Most coaching content assumes the work happens in formal one-to-ones, scheduled in advance, with a clear development plan in the background. None of that matches the reality of leading a team while also being expected to deliver.

The CORE coaching framework is built for that reality. It is a four-step sequence designed for managers coaching behaviour in the flow of work. Short enough to use in a corridor conversation. Structured enough to anchor a longer development session. Built for the manager who wants to coach well, whether they have ten minutes or an hour.

This piece walks through what CORE is, how it works, where it sits alongside GROW and other coaching frameworks, and two examples of it in action.

A Brief Word on Coaching Frameworks

If you are reading a piece about coaching frameworks, you are likely already familiar with a few. Perhaps your organisation has standardised on GROW, or your last leadership program ran you through Co-Active or CLEAR. Maybe one of them works for you. Maybe one of them works for some conversations and feels awkward for others.

This is normal, and it is not a problem. Coaching frameworks like GROW, OSKAR, CLEAR, FUEL, and Co-Active are tools for different jobs. Experienced coaches learn several and use whichever fits the situation in front of them.

CORE sits inside this tradition. It builds on the principles that the Co-Active model articulated most clearly and that most coaching frameworks draw from. The person being coached is not broken and does not need fixing. They have more of the answer than the manager does. And telling them what to do rarely changes anything that matters. What CORE adds is a structure built for one specific job that the existing frameworks do not handle well.

The Job CORE Was Built For

Most coaching frameworks were built assuming time and structure. Either a professional coach with an hour-long session, or a manager running a planned coaching conversation with a direct report.

It is also worth pausing on when these frameworks were built. GROW was developed in the late 1980s. CLEAR in the early 1980s. Co-Active emerged in the early 1990s. OSKAR in the 2000s. They were created in a world without smartphones, without always-on email, without team chat, without AI agents reshaping how work happens. Whether you are coaching a sales rep, a customer service lead, or a senior leader, the manager doing the coaching is operating inside a context the original frameworks were not built to handle. That does not make them wrong. It does mean they leave a gap.

Real manager coaching looks different today. It happens in the five minutes after a meeting. In the kitchen at the office. In the message thread after a difficult call with a customer. It also happens in the scheduled 45-minute one-to-one, and in the half-day offsite where a leader is working through their 360 feedback. The trigger is often a specific behaviour, not a goal. The manager needs a tool that handles feedback, perception, and behaviour change. Not goal pursuit.

This is where GROW starts to creak. GROW asks "what is your goal?" That is the right question when someone wants to grow into a new role, lift their performance against a target, or work toward a clear outcome over time. It is the wrong question when someone has stepped out of a meeting where they shut down a peer's idea and they are wondering why people find them difficult to work with. The conversation is not about a goal. It is about what happened.

CORE is built for that second conversation. It is the alternative to GROW that managers reach for when the coaching is about behaviour, feedback, and the gap between how someone sees themselves and how others experience them.

What CORE Stands For

CORE is a four-step sequence. Context, Observation, Response, Evolve.

The CORE coaching framework consists of four steps:

Context. Anchor the conversation in a specific moment.
Observation. Shift from intent to impact.
Response. Get specific about the behaviour and the choice.
Evolve. Lock in a concrete, time-bound commitment.

Each step does specific work. The sequence is short enough to memorise and flexible enough to use in any setting from a five-minute corridor conversation to a long development session.

The four steps are a guide, not a script. The conversation will dictate the order and how long you spend on each step. Some conversations will spend most of the time in Context. Some will jump to Observation almost straight away. Some will loop back. Follow the conversation, not the framework.

Context

Anchor the conversation in a specific moment. Not a category. A moment.

Generic coaching conversations float. They drift into themes ("you need to be more strategic") or judgements ("you have a confidence issue"). Specificity is what makes coaching land. A specific moment gives both of you something concrete to work with.

The opening question is some version of: "Take me into that conversation. What was happening, and what were you thinking?"

This step does three things. It surfaces what the person noticed in the moment. It gives you their interpretation of events, which is information you need. And it slows the conversation down enough for the real work to happen. Most coaching fails because it skips this step and jumps to advice or evaluation. Context is the foundation everything else sits on.

Observation

Shift from intent to impact. From what they were trying to do, to what others experienced.

The opening question is: "If you step into their shoes for a second, what do they see?"

This is where the perception gap shows up. People rarely see themselves the way others experience them. The gap between intent and impact is where most behavioural growth happens. A person who interrupts in meetings often does not realise they are doing it. A person whose feedback lands as harsh often believes they are being clear and helpful. The observation step opens that gap up gently, without telling the person they are wrong.

For solo behaviours where no one else was in the room, the question shifts. Instead of "what did they see," ask "if you watched yourself back, what would you notice?" The work is the same. Helping the person see what they were too close to see in the moment.

This step is the hardest for managers to hold. The instinct is to tell. To say "well, what they saw was..." Resist it. The work happens when the person being coached arrives at the observation themselves. Your job is to ask the questions that let them get there.

Response

Get specific about the behaviour. Not the person, the behaviour.

The opening question is: "What did you choose to do in that moment?"

Two things matter in how this is asked. First, "did" is past tense. It is descriptive, not evaluative. You are not asking them to defend themselves. You are asking them to look at the behaviour. Second, "choose" matters. People are not their behaviour. They chose it, and they are free to choose something different next time.

This is the step where the reframe happens. The person stops seeing themselves as someone who is "bad at meetings" or "too direct" and starts seeing themselves as someone who chose a particular response in a particular moment. Choices are changeable. Identity is not. The Response step quietly moves the conversation from identity to choice.

Evolve

Lock in a commitment that is concrete and time-bound.

The closing question is: "What is one thing you will do differently next time?"

This step is where most coaching falls apart. People leave with vague intentions. "I will work on being more present." "I will try to listen more." Neither of these will change anything. They are too abstract to act on and too vague to track.

Concrete commitments sound different. "I will pause for three seconds before responding to a challenge in the Monday standup, starting this week." "When I notice myself wanting to interrupt, I will write the thought down instead and let them finish." "Before next Wednesday's meeting, I will ask Jess for one piece of feedback on how I came across in last week's session."

The Evolve step demands specificity. Time-bound, behaviour-level, observable. If you are unable to tell whether they did the thing or not, the commitment is not concrete enough.

Two Examples of CORE in Action

These are not tidy. Real coaching conversations rarely are. Both examples below show the steps as they unfold in practice, with the resistance, false starts, and side trips that come with the territory.

Example One: The Short One. A Sales Manager and a Lost Deal

A sales rep loses a deal they were close on. They drop into your office, frustrated, blaming the procurement process. You have eight minutes before your next meeting.

Context. "Take me into the last conversation with them. What were you focused on?"

The rep starts on procurement. The buyer's process was a mess. The competitor had a relationship with the new CFO. The pricing model the buyer wanted was unfair. You let them vent for a minute, then pull them back. "Sounds like a lot was going on. Take me into the meeting itself though. The last one. What did you say in the first ten minutes?"

They slow down. They walk you through it. Mostly product talk. They opened with a recap of the proposal.

Observation. "Step into the buyer's chair for a second. What did they want from that meeting?"

The rep pushes back. "They wanted answers on pricing. We gave them answers on pricing." You hold your ground. "I am not asking what they got. I am asking what they wanted." There is a pause. The rep looks slightly annoyed. Then says, "Reassurance, I guess. They had a new CFO. They needed to know the rollout would not blow up in their face."

"And what did you give them?" The rep looks down. "A walk-through of the platform."

Response. "What did you choose to do when they asked about the rollout?"

The rep is quiet for a beat. "I deflected. I went into capability. I thought reassurance meant proving we had the features."

You leave the silence. They fill it. "Yeah. I missed it."

Evolve. "What is one thing you will do in your next late-stage meeting?"

The first answer is vague. "I will listen better." You push. "What does that look like, specifically?" They think. "Before I open the deck, I will ask one question about what they are most worried about between now and signing. Then I will answer the worry, not the brief."

The conversation took seven minutes. The rep walked out still annoyed about procurement. But they had one specific behaviour to try in their next meeting, and a clearer view of what they had missed.

The Context step is where most of the time went. The rep needed to vent before they were ready to look. That is normal.

Example Two: The Long One. An HR Business Partner and a Senior Leader

A senior leader receives a 360-degree feedback report. The theme that keeps coming up is that people find them intimidating in meetings. The leader books an hour with you, the HR business partner. They open by telling you the feedback is not really fair, and they want to talk through "how to manage upward perceptions."

Context. "Before we get to perceptions, take me into a recent meeting where you think this feedback might have come from. Doesn't matter if you agree with it. Pick one moment."

The leader resists for a few minutes. They want to talk about the feedback process. The sample size. Whether their detractors were the same people who had been promoted past. You stay with the question. "I hear you on the process. Will you still pick one moment for me?"

They land on a recent steering committee. A senior PM had presented an update on a project that was running late. The leader had asked a string of questions about the timeline. The PM had stopped presenting and said, "It feels like you are interrogating me." The room went quiet. The leader said, "I am asking the questions I would expect any sponsor to ask," and the meeting moved on.

Observation. "Let me ask you something. If you watched that moment back on video, what would you notice?"

The leader is quiet. Then, "I asked a lot of questions in a row. I did not give them space to answer."

You wait. The leader keeps going. "And the tone. I think the tone was sharper than I realised."

You ask, "What was the PM seeing in that moment?"

The leader gets defensive again. "I was doing my job. The project was late. Someone needed to ask the questions."

You hold it. "I'm not asking whether the questions were warranted. I am asking what the PM saw."

A longer pause. Then, "They saw someone who had already decided they had failed."

This is the moment. The leader has articulated the gap between intent (asking due diligence questions) and impact (signalling a verdict). You stay there. "Say more about that."

The leader does. For ten minutes. They talk about a pattern they have noticed. They get sharper when they are stressed. They ask more questions, faster. They push for answers when what people likely need is a moment to think. They start to connect this to feedback they have heard before, in different forms, in different roles.

You loop back to Context briefly, because the original moment is now showing up differently. "Knowing what you know now, what was really going on for you in that meeting?" The leader admits they were anxious about the project's visibility with the board. They had taken that anxiety into the room.

Response. "What did you choose to do in that moment?"

The leader is more open now. "I chose to keep pressing. I chose to make it public. I had the option to ask one question, listen, and move on. I chose not to."

You ask, "Why?" Not as an accusation. As genuine curiosity.

The leader thinks. "Because I wanted everyone in the room to know I was on top of it. That the project being late was not a reflection of me."

Evolve. "What is one thing you will try in the next steering committee?"

The first answer is too big. "I will be more empathetic in meetings." You push back. "That is hard to track. What is one specific behaviour?"

The leader narrows. "When a project is late, I will ask one question, listen to the full answer, and pause for three seconds before deciding whether I need to ask another one. If the answer is incomplete, I will name what I still need rather than asking three more questions in a row."

You agree this is concrete. You also agree on a check-in two weeks out. The leader will pick one trusted person from the steering committee and ask them, after the next meeting, "How did that land?"

The conversation took 50 minutes. Most of it was Observation, with a return loop to Context once the perception gap had opened up. The leader walked out with one specific behaviour, one trusted check-in partner, and a different read on what the feedback had been telling them all along.

Why CORE Works

The framework works because it is built around how humans really change.

People rarely change through advice. They change through awareness. The Context and Observation steps create awareness. People rarely change through general aspirations. They change through specific commitments. The Evolve step forces specificity. People rarely change when they feel attacked. They change when they see the gap between intent and impact without being told they are wrong. The Response step does this work without judgement.

It also works because it is portable. Four steps. One word per step. A manager will recall the sequence in a corridor or settle into it in a scheduled one-to-one. Most coaching frameworks fail in practice because managers do not remember them when the moment arises, or because they feel too rigid for a longer conversation. CORE is designed to be used in either, and to be used often.

How to Start Using CORE

Pick a recent moment of your own. Something that did not go the way you wanted. A meeting where you reacted in a way you regret. A piece of feedback you struggled to take. Run CORE on yourself first.

What was the Context? Step into the other person's shoes. What did they see? What did you choose to do? What is one thing you will try next time?

You will feel where the steps work and where you skipped past them. That is the fastest way to learn the framework, before you bring it to someone else.

When you are ready, pick one direct report. The next time something happens that triggers a coaching moment, run the four steps in order.

You will not get it perfect. The Observation step will be the hardest. You will be tempted to tell rather than ask. You will rush past Context. You will accept a vague commitment in the Evolve step.

That is fine. The point is to use it, notice where you got stuck, and run it again next time. Managers who become great coaches are not the ones with natural ability. They are the ones who keep practising.

The framework is the scaffold. The judgement is yours.

A Final Thought

The best coaching managers operate from one belief. Their job is to make their team outgrow them. Frameworks help. Sequences help. But the underlying mindset matters more than any tool.

CORE is a tool for the moment. It will not turn a manager into a coach if the manager is not interested in the people they are leading. It will not fix a culture where coaching is something people pay lip service to. It will not replace the trust and judgement that take years to build.

What it will do is give a willing manager a way to handle the conversation in front of them. Whether that is the ten-minute exchange in a corridor or the hour they have set aside to debrief a piece of feedback.

If you want to talk about how to make coaching part of how your team operates, get in touch. We work with leaders across Australia and New Zealand to build coaching capability that holds up in the real, messy, time-poor world managers operate in.