Almost every organisation of any size has, at some point, commissioned a “digital transformation” initiative. Fewer can point to what specifically changed as a result. That is not a coincidence — it is a predictable consequence of starting from a word broad enough to mean everything and therefore nothing in particular.

01. Why the phrase fails as a starting point

“Transformation” implies scope across an entire organisation: every process, every system, every team, reimagined together. That scope is precisely what makes it hard to measure and hard to finish. There is no clear point at which the organisation has been transformed, so these programmes tend to run indefinitely, consume budget steadily, and produce output that is genuinely difficult to hold up against a specific, agreed outcome.

02. What we ask for instead

One workflow. Something specific enough to name: the monthly client report your team assembles by hand, the approval process that sits in someone’s inbox for days, the intake process that requires the same information to be typed into three different places. Not “how we operate as a business” — one recurring, identifiable piece of work.

Our homepage lays out exactly what we are looking for — an accountable sponsor, a workflow that is economically material, data and systems we can actually be given access to, and a real business trigger behind the request. If a workflow does not meet that bar, we will say so, rather than scoping something broader to make the conversation more interesting.

03. Why narrow is actually the more serious approach

Scoping to one workflow is not a smaller ambition dressed up as a strength — it is what makes measurement possible at all. A Workflow Diagnostic maps one workflow end to end and establishes a baseline specific enough to judge a result against. A transformation programme spanning an entire operation has no equivalent baseline, because there is no single “before” state simple enough to measure against a single “after”.

04. What this means in practice for a first conversation

We are not going to ask you to describe your organisation’s overall digital maturity, or produce a strategy document for where the business should be in five years. We are going to ask what one specific piece of work is costing you right now — in hours, in margin, or simply in the fact that nobody can see where it currently stands — and whether that is worth measuring properly.

05. Where transformation-scale change actually comes from

If enough individual workflows get fixed this way, the cumulative effect does eventually look like meaningful operational change. The difference is that it happens as a series of measured, accountable steps, each with its own baseline and its own evidence — not as a single large programme that is difficult to evaluate until it has already consumed a year and a significant budget.

Bring the one workflow that is actually bothering you. That is the whole scope of a first conversation — discuss one workflow →