The psychological contract-Coach and Coachee relationship

 In a strong coach–coachee relationship, the relationship itself is part of the intervention. Before GROW, OSKAR, questioning techniques or action plans work, both people need clarity about what this relationship is, what it is not, and what each person owes the other.

I would organise the foundations around eight principles.

Principle	Coach commits to	Coachee commits to	Why it matters
1. Contracting & clarity	Define purpose, process, frequency, confidentiality and boundaries	Clarify expectations and desired outcomes	Prevents ambiguity
2. Confidentiality	Protect what is discussed; explain exceptions beforehand	Speak candidly while respecting others' privacy	Creates trust
3. Psychological safety	Be non-judgmental; allow vulnerability and disagreement	Be willing to discuss difficult realities	Enables honest exploration
4. Autonomy	Don't impose answers or create dependency	Own choices and consequences	Coaching develops agency
5. Challenge + support	Empathise but also confront assumptions and patterns	Be willing to be challenged	Comfort alone rarely produces growth
6. Accountability	Follow up on commitments without policing	Convert insight into action	Prevents "interesting conversations" without change
7. Boundaries	Know when coaching becomes consulting, mentoring, therapy or performance management	Understand what the coach can and cannot provide	Protects both parties
8. Mutual feedback	Ask whether the coaching is helping	Say what is/isn't working	Allows the relationship itself to improve

The psychological contract

Before the first substantive session, I like the idea of establishing a very simple psychological contract:

"This is a confidential space in which you can think aloud without having to impress me. My job isn't to judge you, rescue you or make decisions for you. My job is to listen carefully, ask questions that may sometimes be uncomfortable, help you see patterns you may not see yourself, and hold you accountable to the commitments you choose to make. Your responsibility is to bring honesty, curiosity and willingness to act."

That changes the relationship immediately.

Trust needs four things

I'd simplify coaching trust into:

Confidentiality + Competence + Consistency + Candour

Confidentiality: What I tell you is safe.

Competence: You know how to help me think.

Consistency: I know what version of you I'm going to encounter.

Candour: You will tell me something difficult when I need to hear it.

The last one is frequently underestimated. A coach who is endlessly agreeable may feel safe but eventually becomes low-value.

The coachee should reach a point where they think:

"This person is on my side, but not necessarily on the side of every story I tell myself."

That's an excellent coaching relationship.

One particularly important corporate boundary: Who is the client?

Corporate coaching creates a triangle:

ORGANISATION ↔ COACH ↔ COACHEE

Suppose NPCI or another organisation sponsors coaching for 20 managers. HR is paying, the organisation wants leadership improvement, and the manager is receiving coaching.

So who owns the conversation?

This must be established before coaching begins.

My preferred principle would be:

The organisation owns the developmental objectives; the coachee owns the conversation.

For example, the organisation might know that the coaching concerns:

"Stakeholder management, delegation and leadership effectiveness."

But it shouldn't automatically receive:

"Mr X told me that he distrusts his boss and is considering leaving."

The coach can report progress and themes according to the agreed contract, without reporting private conversations.

That's crucial for credibility.

Coaching also requires clear role boundaries

There are moments when a coach should consciously change hats:

Coaching: "What possibilities do you see?"

Mentoring: "Would it help if I shared what I've seen other leaders do?"

Consulting: "Based on my experience, I'd recommend these three interventions."

Teaching: "There's a model that might help us understand this."

Therapy: potentially outside the coach's competence and requiring appropriate referral.

There's nothing inherently wrong with the first four. The mistake is switching roles without telling the coachee.

A good coach might simply say:

"Would you like me to stay in coaching mode, or would you find a suggestion from my experience useful here?"

That preserves autonomy.

And success needs to be defined at the beginning

One of my favourite opening questions would be:

"Imagine we meet six months from now and you tell me these coaching conversations were genuinely worthwhile. What will be different—in what you do, how you think, how people experience you, and what results you produce?"

Notice the four levels:

THINK → BEHAVE → RELATE → DELIVER

That gives you much richer success criteria than simply asking, "What are your coaching goals?"

For a corporate manager, for example:

Think: less defensive when challenged.

Behave: delegate rather than personally solving everything.

Relate: team members speak more openly.

Deliver: projects move faster without constant managerial intervention.

Now coaching becomes observable rather than philosophical.

---

The deepest boundary of all

This connects back to our discussion about Stoicism.

The coach must resist the temptation to own the coachee's transformation.

You can create the conditions. You can question. You can challenge. You can reflect. You can introduce perspective. You can hold up the mirror.

But ultimately:

The coach owns the process.
The coachee owns the choices.
The organisation owns the context.
And nobody can outsource personal responsibility.

That, to me, is the foundation on which GROW, OSKAR, Stoic reflection, CBT-style reframing and virtually every other coaching methodology can subsequently sit.

And for your proposed work with mid-level managers, I would actually spend part of Session 0 entirely on this contracting relationship before beginning any developmental coaching. It could dramatically improve the quality of everything that follows.