As-Is to To-Be: you can't design the future on a guess
Every organisation wants the To-Be: the clean, efficient future-state process. The mistake is jumping straight to it. A To-Be designed without an honest As-Is isn't a target – it's a wish, and it tends to fall apart the moment it meets reality.
Start with an honest As-Is
The As-Is isn't the process as the policy says it runs. It's the process as it actually runs – workarounds, undocumented exceptions, the spreadsheet someone keeps "just in case." Capturing that honestly is uncomfortable, because it surfaces things people would rather not show. But you cannot improve what you won't first look at squarely.
Then design the To-Be deliberately
With a real baseline, the future state becomes a set of decisions rather than guesses:
- Remove – steps that exist only out of habit, duplication or fear.
- Simplify – handoffs, approvals and exceptions that have quietly multiplied.
- Assign – clear ownership for every step, so the new process has someone accountable for keeping it true.
- Control – the checks and evidence the business (and its regulators) actually need, and no more.
A good To-Be isn't just "the As-Is with the obvious waste removed." It's a deliberate choice about how the work should flow, made with eyes open.
Mind the gap
The most valuable artefact is often the gap between the two – the explicit list of what has to change to get from here to there. That's what turns a nice diagram into a plan: the process changes, the system changes, the role changes, and the controls that have to come with them.
Don't design in a vacuum
The To-Be is also where buy-in is won or lost. Design it with the people who do the work, not at them – partly because they know where the bodies are buried, and partly because a future state imposed from outside rarely survives contact with the floor.
The bottom line
To-Be is the exciting part, but it's only as good as the As-Is underneath it. Look at how the work really happens, decide deliberately how it should happen, and make the gap between them explicit. That's the difference between a transformation that lands and a glossy diagram nobody follows.