The Evolved Leader — Coaching Club Professional

Coaching Club Professional — Leadership Development Programme

The Evolved
Leader

Six modules to transform the way you lead people. Not a catalogue of techniques — a journey of awareness, grounded in solid theory, concrete examples and practical reflection.

6Theory modules
6Practical exercises
12Authors & models
1Personal profile

Module 01

01

The Six Models
of Leadership

There is no single ideal leadership style. There are six complementary approaches — each with its own logic, strengths and limitations. The evolved leader knows them all and knows which to activate.

Why one style is never enough

For decades, management thinking has searched for the "perfect formula" of leadership: the charismatic leader of the 1980s, the empathic leader of the 1990s, the agile leader of the 2000s. Each decade produced its own archetype. The problem is that none of these models works in every context, with every person, at every organisational stage.

Modern research — from Bernard Bass's foundational work on transformational and transactional leadership to Daniel Goleman's studies on six emotional leadership styles — tells us something fundamental: a leader's effectiveness depends on their ability to modulate behaviour according to the situation, not on how skilled they are with a single style.

Goleman, Boyatzis and McKee, analysing data from thousands of managers worldwide, found that the most effective leaders mastered an average of four or more styles, moving between them fluidly depending on context. Those who relied on a single style — even if they deployed it expertly — produced significantly lower results over time.

This module gives you a map of the six principal approaches: not to choose which one "is you", but to understand which registers you have available and which ones you are not yet using.

The most effective leaders don't limit themselves to one style. Like a skilled golfer who selects the right club for each shot, they know which style to use in which situation — and can switch between them with ease.

— Daniel Goleman, Primal Leadership (2002)
ModelCore principleWhen it worksMain limitation
TransactionalClear performance-reward exchangeOperational standardsGenerates compliance, not commitment
TransformationalInspire vision, growth and changeInnovation and purposeRequires time and cultural maturity
Emotional / PrimalManaging emotions as a leadership leverHigh pressure, conflictRisk of excessive empathy
SituationalAdapting to each person's maturity levelAlways, person by personRequires accurate team reading
Adaptive / SystemicLeading change in complexityUncertainty, transformationDifficult to apply in practice
Servant LeadershipThe leader serves before guidingEmpowerment, trustRisk of loss of authority

Case study

Mark, Operations Director at a mid-size manufacturing company

Mark was a solid, respected leader known for his technical expertise. Over the years he had developed a predominantly transactional approach: clear objectives, immediate feedback on errors, rewards tied to results. His team performed well, but turnover was high among younger employees, and innovative ideas rarely surfaced.

During a management development programme, Mark discovered something that surprised him: he was using the same style with everyone, regardless of their experience, motivation or personality. With the seasoned, autonomous collaborator he applied the same directive approach that would have made sense for a new hire. With those going through a period of disengagement, he responded with tighter targets instead of pausing to listen.

Within six months of learning to modulate his style, team retention improved substantially. Not because he had become a different leader — but because he had learned to be the right leader for each person at the right moment.

The principle to carry forward: stylistic rigidity is not strength. It is a form of blindness to the people we lead.
Further
reading

Recommended

Primal Leadership — Realizing the Power of Emotional Intelligence

Daniel Goleman, Richard Boyatzis, Annie McKee — Harvard Business Review Press (2002)

The definitive text on emotional leadership. Goleman describes the six leadership styles with empirical data, demonstrating their measurable impact on organisational climate and results. Particularly valuable is the model of "resonance" and "dissonance" as a compass for understanding the effect we are having on the team.

Reflection 01

My style map

Before exploring each model in depth, it helps to take a snapshot of where you stand today. This is not a test — it is an invitation to look at yourself honestly, without defensiveness.

Very rigidVery flexible
3
01 / 06

Module 02

02

Primal Leadership
and Emotional Intelligence

The "primal" task of a leader is to generate the right emotional climate so that people can perform at their best. Before strategy, objectives and KPIs: the emotional tone you broadcast every day is the most powerful force you possess.

Emotional contagion and the Primal Leadership theory

In 2002, Daniel Goleman, Richard Boyatzis and Annie McKee coined the term Primal Leadership to describe a discovery that neuroscience was beginning to confirm: a leader's emotions spread through a group with a speed and pervasiveness that no other form of communication can match.

The mechanism is biological. The limbic system — the brain's emotional centre — is an "open loop" system. Unlike other physiological systems such as digestion or respiration, which function independently of what happens around us, the limbic system synchronises with the emotional states of people in our proximity. This phenomenon, known as emotional contagion, is amplified in hierarchical contexts: we are neurobiologically primed to pay closer attention to the emotional states of those we perceive as having power over us.

The practical consequence is direct: a leader who enters a meeting carrying frustration, impatience or detachment does not "hide" it — they transmit it. The team absorbs it, often without realising. The resulting climate — more anxious, more closed, less creative — is not a side effect of the situation: it is the direct effect of that unmanaged inner state.

Emotional intelligence — defined by Goleman as the ability to recognise, understand and manage one's own emotions and those of others — is not a peripheral "soft skill". It is the central competence of effective leadership. DDI research from 2015 measured this precisely: in the most complex managerial competencies such as "leading teams" and "driving execution", the EQ component accounts for 62–83% of effectiveness. Cognitive IQ counts for very little.

Great leaders move us. They ignite our passion and inspire the best in us. The reality is far more primal: great leadership works through the emotions.

— Goleman, Boyatzis, McKee — Primal Leadership (2002)

The ABC model: understanding your emotional triggers

Before managing emotional reactions, it is necessary to understand how they form. The ABC model — developed by psychologist Albert Ellis in the 1950s as the foundation of Rational Emotive Behaviour Therapy — offers a precise tool for doing so.

Ellis observed that it is not events that provoke our emotional reactions, but the automatic interpretations we construct about those events. Between what happens (A) and what we feel (C), there is always an intermediate step, often invisible: the belief (B) we formulate almost instantaneously about the event.

For a leader, this has immediate implications. When a team member challenges your decision in a meeting (A), the defensive or irritated reaction (C) is not inevitable — it arises from an automatically constructed interpretation (B): "they are undermining me in public", "they don't respect me". These beliefs are rarely verified. They are often automatic and distorted. But they drive behaviour as if they were facts.

A

Activating Event

The triggering event, described objectively, as a camera would capture it. E.g. a team member challenges your decision in a meeting.

→
B

Belief — Automatic thought

The automatic interpretation you construct about the event. E.g. "they don't respect me", "they're trying to embarrass me". Unverified, but treated as fact.

→
C

Consequence

The emotional and behavioural response that follows. E.g. defensiveness, a sharp tone, shutting down dialogue. Change B and C changes — even if A stays the same.

Case study

Laura, head of a commercial division

Laura was known for her analytical rigour and determination. The consistent pattern emerging from her 360° feedback was that her team "was afraid to bring her bad news". Nobody raised their hand in meetings to flag a problem — everyone waited for her to find it herself, often when it was too late.

Working on her emotional intelligence, Laura uncovered her primary trigger: every time someone raised a problem in a meeting, her automatic belief (B) was "this means they are not working hard enough." Her reaction (C) was a visible stiffening, sometimes a sharp question. Within a few weeks, the team had learned not to bring problems — with devastating effects on the organisation's ability to spot issues early.

When Laura managed to shift her B — from "a problem means inefficiency" to "a problem means someone trusts me enough to bring it to me" — her behaviour changed spontaneously. And the team started talking to her again.

Remember: the psychological safety climate in your team is, to a large extent, a reflection of how you react to bad news. Your face in that moment is company policy.
Further
reading

Recommended

Emotional Intelligence — Why It Can Matter More Than IQ

Daniel Goleman — Bantam Books (1995)

The foundational text. Goleman demonstrates with scientific rigour — and accessible narrative — why EQ predicts professional and relational success more reliably than IQ. The chapter on the emotional brain and amygdala hijack is essential reading for understanding why "knowing" is not enough: the emotional system responds before the prefrontal cortex, and leaders must build conscious self-regulation practices.

Reflection 02

My emotional contribution to the team

Emotional leadership requires two things: honesty about what you actually transmit, and a clear intention about what you want to transmit. Often the two do not align. This exercise is a bridge between them.

02 / 06

Module 03

03

Situational Leadership
Guide, Don't Command

The Hersey–Blanchard model is one of the most practical and powerful frameworks in modern leadership. Its logic is simple: the right style does not depend on who you are, but on who you are facing at this specific moment.

The original model: Hersey and Blanchard's research

In the 1970s, Paul Hersey and Ken Blanchard — working at Ohio State University — proposed a model that would change how management thinks about guiding people. Their starting thesis was provocative: there is no universally superior leadership style. The effectiveness of a style depends on the development level of the collaborator in relation to a specific task.

This idea seems obvious, but its implications are profound. It means that an experienced, motivated collaborator needs a radically different kind of guidance than someone learning a new role. It means that the same person may require different styles depending on the task — technically strong in team management but still uncertain in commercial negotiations, for example.

The model rests on two variables of leader behaviour: direction (task behaviour — how much the leader provides instructions, structure, close supervision) and support (relationship behaviour — how much the leader listens, encourages and provides emotional backing). Combining high or low direction with high or low support produces four distinct styles, applicable to four levels of collaborator maturity.

A common error is assuming one must always "progress" towards full delegation (S4). In reality, the same collaborator may regress to earlier stages — when facing a new project, living through a difficult period, or being promoted into a role with unfamiliar responsibilities. The situational leader moves in both directions, with awareness and without judgement.

There are no people who don't want to grow. There are only leaders who haven't yet found the right way to accompany them.

— Ken Blanchard, The One Minute Manager (1982)
S1

Directing — High direction, low support

The collaborator has little competence on the task and limited experience. They need to know exactly what to do, how to do it and when. The leader provides clear instructions, detailed structure and frequent supervision. This is not authoritarianism — it is necessary orientation. Without this initial clarity, the collaborator experiences paralysing anxiety.

S2

Coaching — High direction, high support

The collaborator still needs technical guidance but now also needs to be involved. They are developing competence, know enough to have questions and doubts, and motivation can fluctuate. The leader explains decisions, asks for opinions, provides frequent feedback and emotional support. This is the most demanding phase for the leader — it requires time, presence and the ability to hold guidance and listening together.

S3

Supporting — Low direction, high support

The collaborator knows how to do their work but is going through a phase of disengagement, uncertainty or discouragement. Technically autonomous, they need emotional presence. The leader reduces instructions and increases listening: asks questions, recognises the contribution, facilitates autonomous problem-solving. Decisions are made together, but the technical expertise belongs to the collaborator.

S4

Delegating — Low direction, low support

The collaborator is competent, autonomous and motivated. The leader fully transfers responsibility — not because they "trust and hope for the best", but because they have built the foundation of trust, competence and objective clarity that makes this delegation solid. The leader remains available but does not interfere. This is the culmination of professional development for both parties.

Case study

The new director and the team of veterans

Julia had been promoted to lead a team of eight, six of whom had more tenure than her. The temptation — and the advice from many — was to "be decisive from day one, so as not to appear weak." Julia began with a strongly directive approach: frequent one-to-ones, daily update requests, procedures she had already decided unilaterally.

Within three weeks the climate had deteriorated. The more experienced collaborators felt undermined. Productivity was falling. Meetings emptied of substance — everyone said "yes" without contributing.

Working with a coach, Julia understood the mistake: she was applying an S1 style to people who were structurally at S4 — competent, experienced, capable of managing themselves. She changed approach: reduced operational instructions, increased time for listening to their perspectives, began making decisions more collaboratively. Three months later, the situation had completely transformed.

Situational leadership is not a formula — it is continuous reading. Every collaborator, every task, every moment requires its own diagnosis.
Further
reading

Recommended

Leadership and the One Minute Manager

Ken Blanchard, Patricia Zigarmi, Drea Zigarmi — HarperCollins (1985)

The most accessible and practical version of the situational model, presented through dialogue-driven narrative. Blanchard introduces the concept of "Development Level" with concrete examples that make immediate application straightforward. Ideal as a first encounter with the model before exploring Hersey's original academic work.

Reflection 03

My team map

The practical value of the situational model lies in applying it person by person, task by task. Take time to make this diagnosis carefully — it is one of the most useful exercises a leader can undertake.

03 / 06

Module 04

04

Motivating People
to Grow

The most urgent question for a leader is not "how do I motivate my team?" — it is "what is keeping this person's potential switched off, and what could I do to switch it on?" Three models, one integrated map for understanding every collaborator.

Maslow reconsidered: reading where each person stands

Abraham Maslow's hierarchy of needs — proposed in his 1943 paper A Theory of Human Motivation — is perhaps the most cited psychological framework in management. Yet it is also one of the most misunderstood. Many reduce it to "first pay well, then offer benefits, then give meaning". The reality is more nuanced.

Maslow described a hierarchy of needs that activate sequentially: physiological (material and physical safety), safety (stability and predictability of context), belonging (meaningful relationships and group sense), esteem (recognition and respect), self-actualisation (expression of full potential). The key dynamic is not that one satisfies a level and permanently "moves up": a threat to lower-order needs can immediately redirect all attention back to those levels, regardless of how satisfied they were previously.

A collaborator working with enthusiasm and a full sense of purpose (self-actualisation active) may revert to focusing exclusively on job security the moment a restructuring is announced. In that phase, talking to them about "exciting projects and growth opportunities" is a message that does not land. A situationally intelligent leader understands where each person stands at any given moment, and acts accordingly.

Herzberg: the distinction that changes everything

Frederick Herzberg, in his research from the 1950s and 1960s, discovered something many managers still do not apply: the things that make people dissatisfied at work are categorically different from the things that make them motivated.

Hygiene factors (adequate salary, job security, good physical working conditions, acceptable interpersonal relationships, clear company policies) prevent dissatisfaction. Without them, people are unhappy and leave. But their presence does not create motivation — it simply removes pain. Nobody wakes up energised to go to work because their office has good air conditioning.

Motivating factors (recognition of contribution, increasing responsibility, stimulating challenges, continuous professional development, meaningful work) generate authentic engagement, creativity and discretionary effort — the voluntary investment people make when they truly believe in something. And these cannot be substituted by hygiene factors: no salary increase compensates over time for the feeling of doing work devoid of meaning.

Herzberg — Hygiene Factors

They keep people

Adequate salary · Job security · Comfortable physical environment · Clear company policies · Positive interpersonal relations · Sustainable hours. Their absence creates dissatisfaction. Their presence does not create motivation.

Herzberg — Motivating Factors

They make people flourish

Recognition of contribution · Growing responsibility · Challenges calibrated to ability · Continuous professional development · Meaningful work · Decision-making autonomy. Their presence generates authentic commitment.

Self-Determination Theory: the three fundamental needs

Edward Deci and Richard Ryan, from the 1980s onwards, built the most solid and widely validated psychological theory of motivation: Self-Determination Theory (SDT). Their central thesis is that motivation is not a single phenomenon — it exists on a continuum from extrinsic motivation (I act because I obtain a reward or avoid a punishment) to intrinsic motivation (I act because the activity itself is satisfying and meaningful).

The good news is that intrinsic motivation is not a natural gift that some people have and others do not — it is the result of a context that satisfies three fundamental psychological needs: Autonomy (feeling that one's actions arise from real choices, not imposed obligations), Competence (feeling effective, growing, mastering something important) and Relatedness (feeling part of something, connected to people who care and who one cares about).

Case study

The team that "isn't engaged" — and what was really happening

Andrew, director of a 12-person team in a services firm, had been complaining for months about low engagement: "People do the minimum, nobody takes initiative, every time I propose something I have to drag them along." He had already tried performance bonuses, a new welfare package, team-building events. Nothing seemed to change.

Examining the situation with his coach, the real picture emerged. The company had gone through three years of organisational uncertainty — two restructurings, a change of general management, objectives that shifted every six months. The team had been operating in a safety-need state (level 2 of Maslow) for two years: every initiative was perceived as a potential source of risk, every proposal as something that might be used against them.

The bonuses had not touched this mechanism because they were operating at the wrong level. The team did not need more rewards — they needed clarity, predictability and psychological safety. When Andrew began working on these elements — communicating with greater transparency, committing to stable objectives for at least a quarter, openly acknowledging that the last few years had been difficult — the change was gradual but real.

Before motivating, ask yourself: at which level of need is my team operating right now? Are you trying to nourish self-actualisation in people who don't yet feel safe?
Further
reading

Recommended

Drive — The Surprising Truth About What Motivates Us

Daniel H. Pink — Riverhead Books (2009)

Pink synthesises decades of motivation research in a powerful narrative, building on Deci and Ryan's SDT. He dismantles the myth that the carrot-and-stick approach works for complex cognitive work — and shows with data and real cases why autonomy, mastery and purpose are the true drivers of performance. A text that changes the way you think about everyday management.

Reflection 04

My team's needs map

Use the integrated framework to do a concrete analysis of one team member. The goal is not to have certain answers — it is to build better hypotheses than you have now, and turn them into specific actions.

04 / 06

Module 05

05

Delegating with
Evolutionary Trust

Delegation is the most misunderstood leadership act. Almost everyone knows they should do it — very few do it well. The difference between "handing off a task" and "delegating with intentional purpose" is what separates a manager from a leader who builds other leaders.

Why leaders don't delegate — and what really holds them back

If you asked a sample of managers whether they believe in the importance of delegation, almost all would say yes. But if you analysed their actual behaviour, a different picture would emerge: most struggle to truly delegate, especially in situations that matter. Why?

The stated reasons are almost always rational: "nobody does it as well as I do", "it takes longer to explain than to do it myself", "the risk of error is too high", "the client wants to deal with me." These motivations are not entirely false — but they often conceal deeper dynamics.

The first is identity tied to expertise. Many leaders were promoted because they were the best at what they did — the best salespeople, the best technicians, the best analysts. Their professional identity is built on being the most capable person. Delegating means relinquishing that expertise as a source of value — and this generates a subtle but real anxiety.

The second is fear of others' failure. A leader who delegates and the collaborator makes a mistake: who is responsible? The correct answer — "the leader, who had the responsibility to prepare the delegation adequately" — is often experienced as unacceptable. It is easier not to delegate than to manage that vulnerability.

Recognising these resistances is not an academic exercise. It is the first step towards building a conscious, systematic and genuinely developmental delegation practice.

The best manager is not the one who does things better than their collaborators. It is the one who can bring collaborators to do things better than they themselves could.

— Stephen Covey, The 8th Habit (2004)
Level 1

Do as I say

Detailed instructions, frequent supervision, minimal autonomy. Appropriate for those new to the task or role. Not distrust — it is necessary structure. The risk is applying it for too long, stunting growth.

Level 2

Do it, then tell me

Space for action, but frequent accountability. The collaborator acts with operational autonomy, but the leader monitors progress and adjusts the course. The moment when competence is built with a safety net.

Level 3

Decide, but consult

Real decision-making autonomy, but strategic alignment on significant actions. The leader frees time for high-value activities. Trust is mutual and balanced with alignment.

Level 4

Decide yourself, I trust you

Full autonomy. The collaborator is entirely responsible for decisions and results. The leader is available but does not interfere. The culmination of a development journey — not a starting point.

The five levers of effective delegation

Effective delegation is not simply "assigning a task". It is a structured conversation that transfers not only the "what" but also the context, the boundaries and the necessary resources. Blanchard identifies five elements that make a delegation solid and respectful of both parties.

1

Clarity of outcome

Not the "how" — that belongs to the collaborator. But the "what" and especially the "why". The clearer the destination and its significance in the broader picture, the more the collaborator can find their own path towards it. Outcome clarity is also the criterion for evaluating the work done.

2

Strategic context

How does this task fit into the strategy? Who benefits? Why does it matter now? Context transforms a task into a mission. People do better work when they understand why it matters — not just what they need to do.

3

Decision boundary

Where can they decide autonomously? Where should they consult you? Where must they escalate? This clarity prevents frustration on both sides: the collaborator does not feel blocked, the leader does not feel bypassed. The boundary expands progressively as trust grows.

4

Proportionate support

Neither micromanagement nor abandonment. The level of support must be calibrated to the person, the task and the moment. An experienced collaborator facing a new situation needs more support than usual — even if they normally operate with full autonomy.

5

Follow-up and recognition

Agreed check-in moments — not "I'm checking up on you", but "let's meet to see where we are". And recognition of work done: not the generic "well done", but specific acknowledgement of the contribution made. This closes the cycle and reinforces the behaviours you want to see repeated.

Case study

The delegation that wasn't really delegation

Frances, marketing director at a medium-sized firm, prided herself on delegating widely. "I give my people responsibility," she said. Yet the team was often stuck, decisions kept being deferred, and she always ended up intervening at the last moment to "rescue" situations.

Examining her delegations concretely, the problem emerged: Frances assigned tasks, but rarely explained the context. She did not clarify which decisions the collaborator could take autonomously and which not. She did not establish agreed check-in moments. The result was that collaborators, faced with any ambiguity, froze — afraid of making invisible mistakes.

When Frances began structuring delegations using the five levers — even just ten extra minutes of initial conversation to clarify context and boundary — the situation changed radically. People moved with more confidence, interruptions halved, and Frances recovered the time to work at a genuinely strategic level.

The question to ask before delegating: "Have I given this person everything they need to succeed — not just the task, but the context, the boundary and the support?"
Further
reading

Recommended

The 7 Habits of Highly Effective People

Stephen R. Covey — Simon & Schuster (1989)

The chapter on "stewardship delegation" is among the most profound contributions on the difference between delegating a task and delegating responsibility. Covey introduces the distinction between "gofer delegation" (do exactly this) and "stewardship delegation" (you are responsible for the outcome, with full autonomy on the how) — and explains why the latter, although more demanding to set up, produces incomparable results over time.

Reflection 05

My next delegation

Choose a real activity you are currently holding on to. Not a hypothetical exercise — something you are managing yourself right now and could hand to someone in your team. Build the delegation using the five levers.

1Do as
I say
2Do it, then
tell me
3Decide, but
consult
4Decide yourself,
I trust you
05 / 06

Module 06

06

Feedback as
a Leadership Act

Feedback is the most powerful development conversation a leader can have. Not a judgement — a dialogue. Not a critique — an investment. The quality of the feedback you give is the quality of the leader you are.

Why feedback is difficult — and why it is worth the effort

Amy Edmondson's research — at Harvard Business School — has demonstrated systematically that psychological safety is the single factor most predictive of performance in high-complexity teams. Psychological safety is not the absence of conflict or high standards — it is the shared certainty that it is possible to say what one thinks, flag problems, admit mistakes and ask for help, without fear of being punished, ridiculed or excluded.

Feedback sits at the heart of this dynamic. Feedback given badly — with an accusatory tone, in public, without specific data, conflating the person with the behaviour — does not produce change. It produces defensiveness, resentment and silence. Feedback given well — timely, specific, future-oriented, within a genuinely caring relationship — is one of the most generous acts a leader can perform.

Douglas Stone and Sheila Heen, in Thanks for the Feedback, show that the problem is not only how we give feedback — but how we receive it. The triggers that distort our ability to absorb useful feedback are three: the truth trigger (I don't agree with the content), the relationship trigger (I don't respect the source), the identity trigger (this touches who I am, not just what I did). An evolved leader learns to navigate these triggers — in themselves and in others.

Feedback is not effective if the climate is not safe. And a safe climate is not built through declarations — it is built through behaviours, one at a time.

— Amy Edmondson, The Fearless Organization (2018)

The SBI model: structuring the conversation, not the judgement

The SBI model — developed by the Center for Creative Leadership — offers a practical framework for building feedback on observable facts, eliminating ambiguity and reducing defensive reactions. It has three sequential elements.

Situation: describe the specific context in which the behaviour occurred. Not "often" or "always" — this yesterday morning, in that meeting, at that moment. Specificity is fundamental: generic feedback ("you tend to be impatient") gives the person no foothold to work with.

Behavior: describe the specific action observed using sensory data — what you saw or heard, not what you interpreted or evaluated. "You raised your voice twice" is an observation. "You lost control" is an interpretation. The behaviour must be described as a camera would capture it, without evaluative adjectives.

Impact: explain the concrete effect that behaviour had — on you, on the team, on the client, on the project. Not "it's wrong" — but "the result was that...". Impact is where feedback gains weight and meaning. It is also where the conversation can open up: often the person was not aware of the impact they were producing.

SBI applied

From generic to specific and effective feedback

Generic feedback (doesn't work): "You know, sometimes in meetings you're a bit too direct, and it creates tension in the team. You should try to be more diplomatic."

SBI feedback (works): "Yesterday morning, during the project progress meeting, when Louis presented his update you responded with 'this is unacceptable, we can't go on like this' — and Louis went quiet and didn't speak again for the rest of the hour. I noticed a drop in energy in the group, and I'm concerned that Louis won't share problems in future for fear of a similar reaction."

The second piece of feedback is specific, based on observable facts, and connects the behaviour to a concrete impact on team dynamics. It creates the conditions for an authentic conversation — not for a defence.

Feedback as coaching: the GROW model applied

The next step is to integrate feedback into a development conversation using the GROW model — Goal, Reality, Options, Way Forward — developed by Sir John Whitmore and now the most widely used coaching framework in the world.

The idea is that after sharing the feedback (the Reality in the GROW structure), the leader does not impose a solution — but facilitates a process of autonomous reflection. "What would you like to be different?" (Goal), "How do you see the situation?" (Reality), "What alternatives have you considered?" (Options), "What is your next step?" (Way Forward). In this way, feedback becomes the entry point for a development conversation — and the collaborator arrives at their own solutions, with a far higher probability of implementation than if they had been handed them from above.

Further
reading

Recommended

Thanks for the Feedback — The Science and Art of Receiving Feedback Well

Douglas Stone, Sheila Heen — Viking (2014)

A counterintuitive and illuminating book: instead of teaching how to give feedback, it teaches how to receive it. Stone and Heen show that the quality of feedback that actually lands depends far more on our ability to hear it than on the skill of the person giving it. Essential for leaders who want to build a genuinely bidirectional feedback culture — and who want to learn how to ask for and receive feedback from their own team.

Reflection 06

The conversation I keep postponing

Every piece of postponed feedback is a development opportunity withheld from your collaborator — and a signal that you are avoiding an important responsibility. This exercise is an act of courage: build the conversation you have been deferring, so that it can open something new.

The right moment for that conversation is now. The right person to start it is you.

— Coaching Club Professional
06 / 06