Case Studies

A selection of engagements across executive coaching, strategy consulting, and OKR implementation. All details are anonymised.

01

The organisation that did not know what it did not know

Context

A government-linked organisation needed to assess its marketing capability before designing a development intervention. The assumption going in was that the gaps were tactical — skills, tools, execution.

What the assessment revealed

The gaps were not tactical. They were structural. There was no shared understanding of what the organisation was trying to achieve with its marketing function. Different leaders had different definitions of success. Without that clarity, any skill-building intervention would have produced activity without direction.

What was worked on

A structured gap audit that surfaced misalignment at the leadership level before any training was designed

Establishing a shared definition of what success looked like for the function

Sequencing the intervention — first clarity, then capability, then execution

Building a roadmap that addressed the actual constraint rather than the presenting symptom

What changed

The organisation entered the engagement expecting a training needs analysis. It left with a diagnostic that reframed the problem entirely. The roadmap that followed addressed the structural gap first — and the capability work that came after it landed on a foundation that could hold it.

02

The company where goals existed but alignment did not

Context

A fintech company had been setting quarterly OKRs for over a year. The framework was in place. Objectives were written. Key results were defined. On paper, the organisation was running OKRs. In practice, each function was running its own version of them.

What the assessment revealed

There were no company-level OKRs. Each function had written its own objectives in isolation. The sales team was optimising for acquisition. The product team was optimising for retention. The operations team was optimising for cost. All reasonable. All pulling in different directions. There was no vertical alignment connecting function-level goals to a shared company direction.

What was worked on

Establishing a single company-level annual OKR that every function's objectives had to connect to

Rebuilding each function's OKRs from the top down so vertical alignment was visible and traceable

Designing a quarterly review cadence where function-level progress was visible at the company level in the same conversation

Making cross-functional dependencies visible before they became conflicts

What changed

For the first time the leadership team could see whether the company was winning — not just whether each function was hitting its numbers. The annual OKR became the anchor for every quarterly planning conversation. The founder stopped being the person who held the picture of the whole business in their head alone.

03

The institution that was growing faster than its systems

Context

A group of academic institutions had expanded significantly — more campuses, more students, more staff. The operational model that had worked at smaller scale was breaking down. Each campus was running differently. Leadership was stretched. The founder was involved in decisions that should have been resolved at the campus level.

What the assessment revealed

There was no shared operating standard across campuses. What looked like an execution problem was actually an alignment problem. Campus heads had different interpretations of what good operations looked like. There was no cadence connecting campus performance to group leadership — which meant problems surfaced late and responses were reactive.

What was worked on

Establishing a shared operating standard that defined what each campus was accountable for

Clarifying which decisions sat at campus level and which required group leadership

Building a monthly review cadence that gave group leadership visibility without requiring them to be present in every campus conversation

Separating operational decisions from strategic ones so the founder could lead the group rather than manage its parts

What changed

Campus heads began operating with more confidence and less escalation. The monthly review became the primary mechanism for surfacing issues that needed group attention. The founder was able to shift from managing operations to leading the group's direction. Expansion decisions became easier because there was now a standard to expand into.

Ready to explore?

Book a 30-minute discovery call. No commitment required.

Book a Call