Skip to content

Cases

Problem, involvement, impact

Real situations, told through the decision that was at stake, not through a company timeline.

Under confidentiality agreements, organizations and sensitive figures are described by sector and size. What matters here is the shape of the problem and what changed afterward.

Problem, involvement, impact

01Financial services · mid-sizeBoard Member18 months

The board approving AI without knowing what it was approving

Problem
The company had eleven AI initiatives in production and no way to answer, in a board meeting, who was accountable for each. Every approval was debated on projected return; none on what would happen if the model got it wrong with a real customer.
Involvement
Introduced a simple classification criterion based on consequence, not technology, as a prerequisite for any approval. Each system began reaching the board with a named owner, an explicit failure scenario, and a contestation path for the affected customer.
Impact
Two of the eleven initiatives were suspended for having no identifiable owner. The remaining nine moved to quarterly review with human-override data. Average approval time went down, because the agenda arrived ready.
02Manufacturing · second-generation family businessStrategic Advisor24 months

The succession stuck on a conversation nobody wanted to have

Problem
The succession plan had existed on paper for four years and wasn't moving. The founder said he was ready to step back; the market and the team read every decision as a sign of the opposite. The company was running on two implicit chains of command.
Involvement
Work on two fronts at once: with the founder, on which role he would move into, not only which one he would leave; with the executive team, on which decisions formally transferred to whom, with dates. The conversation moved from intent to authority.
Impact
Transition completed in 22 months, with the founder taking the board chair and a written scope. Measurable reduction in decision rework, which previously required informal validation on nearly every mid-size call.
03Private healthcare · large enterpriseStrategic Advisor9 months

Where to stop automating

Problem
The service operation had automated 78% of interactions and planned to reach 95%. Cost and time metrics improved every quarter; retention metrics started worsening with no visible explanation in the dashboards.
Involvement
Rebuilt the journey map splitting interactions by consequence for the member rather than by volume. The question stopped being 'what else can we automate' and became 'in which moments is human presence the product itself.'
Impact
An explicit boundary was defined: four interaction types were permanently excluded from automation. The retention curve stabilized the following quarter, with total cost still 31% below the original baseline.
04Technology · post-Series C scale-upExecutive Mentor12 months

The executive who inherited a team that didn't pick him

Problem
An executive promoted internally into a C-level seat, now leading peers who days earlier were colleagues, including two candidates for the same role. His initial read was that he needed to establish authority fast.
Involvement
A 1:1 mentoring cycle focused on three fronts: establishing authority without performing authority, handling the conversation with the two passed-over candidates, and choosing which decisions to make quickly and which to leave visibly open.
Impact
Both candidates stayed with the company, one taking expanded scope. The executive settled into the role and, the following year, began developing his own successor.
05Retail · national chainStrategic Advisor6 months

The AI adoption that had already happened without approval

Problem
The executive team had spent a year debating which AI platform to adopt. An anonymous internal survey revealed that 64% of analysts were already using their own tools, with company data, unapproved, and nobody knew which ones.
Involvement
Instead of an immediate block, the security team's instinctive reaction, a thirty-day amnesty window for declaring usage, paired with a fast official approval path. The goal was to map before regulating.
Impact
Forty-one real use cases mapped, of which 9 were formalized as official processes and 6 blocked for concrete data risk. The corporate AI strategy started being designed from actual usage rather than from a vendor deck.

What brought you here?

Pick the path closest to your context. The form arrives with the right subject already set, and so does the reply.

Go to contact