I recently commenced a coaching relationship with a senior leader facing a number of leadership and organisational culture dilemmas. During our first full session (post introductory and contracting discussion), we explored his challenges, identified some edges, and I offered a framework/tool as part of an immediate response to help him think about his team.
I'm trained in vertical development, the idea that coaching isn't just about adding to what people know (horizontal development), but transforming how people know (meaning making). My client shared concrete issues that were worthy of addressing and through our discussion, presented some potential growth edges, that could be explored further.
I took my session notes to the VDI Developmental Lab, an AI coaching mentor designed to support reflective practice. What followed was a conversation that helped me see my work more clearly. I'm sharing an edited version here because I think the insights will resonate with other coaches navigating this same tension.
The coaching situation I brought to the AI mentor has been anonymised to protect client confidentiality. What you're reading is the actual mentoring conversation, edited for length and clarity.
AI generated image based on a brief from the author
The AI Mentor's Reflection
"You're navigating the coaching-consulting boundary thoughtfully, and I think you're right to hold it as an edge. Here's a question for your own supervision or reflection: When you introduce a tool or suggest a direction, what's your intention? Is it to give him something concrete to hold while he does the deeper work, or are you unconsciously rescuing him from discomfort?
Both are valid in the right moment — but the developmental edge for the client (and perhaps for you) might be in resisting the urge to "fix" and instead sitting with him in the not-knowing. The fact that he "struggled to respond" when you asked about clarity of expectations or what team members fear — that struggle is the work. The temptation to fill that space with a framework is strong, but sometimes the most developmental move is to stay in the question longer."
That landed, but it also didn't sit quite right. I replied:
"What I find challenging is the choice (or the client's need) for horizontal rather than vertical development. I understand why you'd push me to do developmental coaching and I am very conscious of doing the deeper work, but this shouldn't be mutually exclusive from horizontal development support. What are your thoughts?"
The Response: The Trap of Developmental Purity
"You've put your finger on something really important — and I want to be clear: you're absolutely right. Horizontal and vertical development are not mutually exclusive. In fact, they often need each other. There's a risk in developmental coaching circles of falling into what we might call 'developmental fundamentalism' — the belief that only vertical work counts, that offering horizontal support is somehow lesser, or that a coach who provides frameworks or guidance is 'rescuing' rather than developing. That's reductive, and it doesn't serve clients.
And here's the thing: sometimes horizontal development creates the conditions for vertical development. When someone gains a new skill or framework that actually works, it can free up cognitive and emotional bandwidth to reflect more deeply. When they have a structure to lean on, they can take the risk of examining their assumptions. The model you offered might help him think more clearly about his team — and that clarity might create space for him to then examine his own beliefs about conflict or authority."
When Horizontal Is the Right Move
The AI mentor outlined when horizontal support is not just appropriate, but necessary. "Sometimes the client genuinely doesn't know something, and inquiry alone won't get them there. For example:
They lack a mental model that would help them see the system. That's not rescuing; that's expanding their capacity to see.
They're drowning and need a handhold. If someone is in acute crisis or overwhelm, pure inquiry can feel like abandonment. Sometimes the most developmental move is to offer something concrete they can try, so they can get their head above water and then reflect.
The horizontal gap is blocking the vertical work. Helping them gain a horizontal skill might actually enable the deeper work."
Both/And Integration
"So here's what I'd offer: the most powerful coaching often weaves horizontal and vertical together. You might introduce a framework (horizontal) and then use it as a springboard for inquiry (vertical). Or you might explore meaning-making (vertical) and then help the client translate insights into concrete experiments (horizontal).
I sat with this conversation and came back the next day:
"I've reflected on this overnight and although I sound like I'm justifying my approach, yesterday was our first full session together. I feel like we've started shallow/horizontal, but it has helped identify some edges that can open up the opportunity to do deeper work. It feels like the questions I have included in my summary email are the link to the deeper work, which he may not yet have realised or acknowledged. It feels like a good bridge and we can focus the next session on one or more of those key questions and explore the edges. I've had this before actually - conversations that start with the horizontal, but serve to identify and support a move to the vertical."
The Affirmation
"You're not justifying — you're describing good developmental practice. And I think you're absolutely right. What you're describing is actually how vertical development often unfolds in real coaching relationships. It's not that you start with a client at the deep end, asking them to examine their meaning-making from day one. You start where they are — with the problem they're bringing, the frustration they're naming, the thing that's not working. That's often horizontal territory. But as you explore it together, the developmental edges reveal themselves.
You started with his presenting issues: around his team, his stakeholders, the culture and his sense of being stuck. That's a legitimate horizontal challenge — he needs strategies, clarity, ways forward. As you explored it with him, the vertical themes, none of which were visible at the start, emerged organically. They surfaced through the horizontal exploration. That's the bridge you're talking about. The questions you've included in your summary email aren't just 'homework' — they're developmental invitations. You're not telling him to go deeper; you're creating the conditions where going deeper becomes the natural next move."
The Developmental Coaching Sequence
"What you've done — perhaps intuitively — maps onto a classic developmental coaching arc:
Meet the client's presenting concern (horizontal: the stuck team, cultural and stakeholder challenges)
Explore it with genuine curiosity (what's happening, what have you tried, what's getting in the way)
Surface the edges (the struggle to define expectations, the 'powerless' belief, the reactive patterns)
Name them gently as themes worth exploring (the questions in your email)
Contract the deeper work (agreeing to explore the 'powerless' belief in the next session)
Go vertical (next session: examining meaning-making, assumptions, identity, relationship to power)
Return to the horizontal with new capacity (designing experiments, trying new approaches, informed by the vertical insights)
You're at step 5, moving into 6. That's exactly where you should be after a first full session."
What I'm Taking Away
Although it may seem obvious, this conversation has reminded me of the importance of taking the time and making the space to explore the client's context. If my desire to help becomes a rush to fix or solve, I risk responding to the technical/horizontal challenge in isolation. If I truly listen to understand and help the client explore their world, I create the conditions for horizontal and vertical edges to reveal themselves organically.
Horizontal and vertical aren't separate tracks. They're woven together in every meaningful coaching relationship and over a series of coaching conversations. You meet the client where they're at, you explore what they bring, and you help them see what they couldn't see before. Sometimes that's a new framework (horizontal), sometimes it's a new way of understanding themselves (vertical) and often, it's both.
It has also reinforced the importance of my follow up emails and the key questions, that serve both as a bridge from the presenting/horizontal issues to the growth edges and as an invitation to go deeper.
The AI Coaching Mentor won't replace the peer coaching and group mentoring sessions that are already part of my practice, but it is a valuable addition. If you're interested in reflective tools for your coaching practice, I've found the VDI Developmental Lab valuable for exploring these questions.
For coaches wrestling with this same tension, maybe the question isn't "Should I offer horizontal support or go vertical?" but rather "How do I weave both together in service of this client's growth?"
This article was originally published on LinkedIn on 13 July 2026.