Three questions I ask in the first week of any transformation engagement

By the time an organization calls someone like me, they don’t lack information. They lack clarity — and those are opposites more often than you’d think.

They have strategy documents, vendor assessments, maturity scans, three consultants’ worth of slide decks. What they don’t have is a shared answer to the only question that matters: why, exactly, are we stuck?

When I arrived at the Walloon public administration (SPW), I was the sixth UX consultant on the program. Dozens of applications in countless technologies had to converge into five. The business refused any further delay: no research phase, no user interviews, no data. Whatever diagnosis I made had to come fast and be right. That engagement taught me to compress the diagnostic into a handful of questions that expose where an organization is actually stuck — not where its documents say it is.

Here are the three I now ask in the first week, every time.

Question 1: What have you decided that nobody is doing?

Every stalled organization has a graveyard of decisions — approved, budgeted, announced, and quietly ignored. The distance between decision and behavior is the most honest metric of organizational health, and nobody measures it.

The answers are revealing in both directions. Sometimes the decision was never translated into anything a team could act on (“we will become AI-first” — meaning what, on Monday, for whom?). Sometimes the decision was translated fine, and people are silently refusing it — which is not an execution problem but an alignment problem wearing an execution costume.

Ask this in a leadership room and watch who looks at whom. The glances are data.

Question 2: If this program succeeds, whose Monday morning changes — and how?

This is the concreteness test, and most transformation programs fail it instantly.

Visions survive on abstraction. “Improved customer experience.” “Data-driven decisions.” “AI-augmented workflows.” None of these describe a Monday morning. When I pushed for the answer at IRISnet, it eventually became brutally specific: a customer completes a task in one interface instead of five; an employee stops re-typing data between systems — including, memorably, out of an Excel file on a shared drive. That specificity is what let a small team build a product that onboarded over 50% of customers in its first year and lifted NPS by 40 points.

If nobody in the room can name a person whose workday concretely changes, you don’t have a transformation program. You have a mood.

Question 3: Where do people go quiet?

Every organization has topics that make meetings go quiet. The budget that doesn’t add up. The system nobody dares to touch. The department that “isn’t ready.” The executive whose pet project everyone routes around.

The fog is thickest exactly where the silence is. In 26 years I’ve never seen a transformation blocked primarily by technology; I’ve seen dozens blocked by an unspoken thing everyone had privately mapped and nobody had said out loud. Fear, mostly — of obsolescence, of losing control, of being exposed. Silence is how fear shows up in a governance structure.

You can’t roadmap your way around a silence. You have to name it. Naming it is usually the single highest-leverage act of the whole engagement — and the reason it often takes an outsider.

Why three questions beat three months of audit

Long diagnostics feel rigorous, but mostly they produce documentation of the fog rather than a way out of it. These three questions triangulate the same thing from three angles: the gap between deciding and doing, the gap between vision and Monday morning, and the gap between what’s known and what’s sayable.

Locate those three gaps and you have a map of where the organization is actually stuck. Everything else — the roadmap, the architecture, the change plan — is downstream.