Forget “Digital Transformation.” Bring One Workflow.
“Digital transformation” is broad enough to mean almost anything, which is why it rarely leads anywhere specific. We ask for one thing instead: a single recurring deliverable that costs you time, margin or control. Scoping to one workflow is what makes measurement, and a result, possible.
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. This article explains why we ask for one workflow instead, and what that looks like in practice.
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 exactly what makes it hard to measure and hard to finish.
There is no clear point at which an organisation has been transformed. There is a clear point at which one workflow is fixed. So transformation programmes tend to run indefinitely, consume budget steadily and produce output that is hard to hold up against a specific, agreed outcome.
02. What we ask for instead
One workflow, specific enough to name: the monthly client report your team assembles by hand, the approval that sits in someone’s inbox for days, the intake that needs the same information typed into three places. Not “how we operate as a business”. One recurring, identifiable piece of work.
| A transformation programme | One workflow | |
|---|---|---|
| Scope | Every process, system and team | One recurring deliverable |
| Finish line | None that is clearly defined | The point at which that workflow is fixed |
| Baseline | No single “before” simple enough to measure | A measured baseline for that workflow |
| Evidence of result | Hard to hold against an outcome | Compared against the baseline |
| Typical risk | Runs for a year and a large budget before anyone can judge it | A small, accountable step with its own evidence |
03. What makes a workflow worth bringing
Four things, all of which we look for:
- An accountable sponsor. Someone who owns the outcome.
- A workflow that is economically material. Worth measuring properly.
- Data and systems we can actually be given access to. Otherwise it cannot be mapped.
- A real business trigger. A reason the request exists now.
If a workflow does not meet that bar, we will say so, rather than scoping something broader to make the conversation more interesting. For the cases we decline, see why we turn down some projects.
04. Why narrow is 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 programme spanning a whole operation has no equivalent baseline, because there is no single “before” simple enough to compare with a single “after”.
05. What a first conversation involves
The first conversation is a free, 30-minute fit call about one workflow. Its purpose is to decide whether a paid Diagnostic is justified, and it works best if someone who actually runs the workflow joins.
We are not going to ask you to describe your organisation’s overall digital maturity, or to produce a five-year strategy. We will 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 stands, and whether that is worth measuring properly.
06. Try naming yours
Fill in one sentence: “Every [week or month], [who] spends [about how long] on [what], and the consequence is [what].”
For example: “Every month, three people spend about two days assembling the client report by hand, and the report goes out late.” If you can write the sentence, you have a workflow. If you cannot, the first job is to find the recurring piece of work that would fill the gaps.
07. Where larger change comes from
If enough individual workflows are 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 hard to evaluate until it has already consumed a year and a significant budget. You can see the starting point on our homepage.
08. Frequently asked questions
Why not start with a digital transformation strategy?
Because the word covers an entire organisation, so there is no clear point at which it is finished and no single baseline to measure against. One workflow has both.
What should I bring to a first conversation?
One recurring deliverable that costs you time, margin or control, and ideally someone who runs it.
What makes a workflow suitable?
An accountable sponsor, economic materiality, data and systems we can be given access to, and a real business trigger.
What if my problem is broader than one workflow?
Start with the one that is most material. Fixing workflows one at a time, each with its own baseline, is how larger change becomes measurable.
Do you ever say no?
Yes. If a workflow does not meet the bar, we say so rather than scoping something broader.
09. Next step
Bring the one workflow that is actually bothering you. That is the whole scope of a first conversation. Discuss one workflow →
