Assess: name the cost of standing still before you fix anything.

The first phase of any serious transformation is the one most teams rush past on their way to the interesting part. It is also the one that makes everything after it possible.

Before you redesign anything, before you touch a system, before you write a single line of a change plan, you have to do something deceptively simple. You have to find out how the work actually runs today, and put a number on what the current state is costing you.

I call this naming the cost of standing still, and it is the most undervalued move in the entire sequence.

See how the work really flows

Not the org chart. Not the process diagram from three years ago. The real flow, with all its detours and rework and quiet heroics.

Where does work pile up? Where does it get redone? Where do people route around the official process because the official process does not work? You cannot fix a system you have only seen on a slide.

So the Assess phase starts with process mapping, real data, and candid conversations with the people who actually do the work, because they know exactly where it breaks. They have been living with the breakage for years, and they will tell you precisely where the bodies are buried if you ask honestly and listen.

Put a number on standing still

The output of a good assessment is not a list of complaints. It is a quantified value case: what the current state costs in time, money, and risk.

This is the step that separates a real transformation from a wish. A vague sense that things are inefficient does not get funded and does not get prioritized. A credible number does.

When you can say, in dollars, what the status quo costs us every quarter, you have turned a feeling into a decision leadership can actually make. The number is the unlock for everything downstream.

The status quo has momentum, and momentum is a cost

People underestimate the status quo because it feels free. It is not. Standing still has a price that is paid continuously, in the duplicated effort, the slow cycle times, the errors, and the decisions made on bad data.

Making that ongoing cost visible does something important to the psychology of a change. It reframes the question from why should we spend money to change to why are we choosing to keep paying for the current state.

Inertia stops looking safe once it has a number attached. That reframe is half the battle of getting a transformation properly backed.

Why leaders skip it, and pay later

Assess feels slow. It does not produce anything shiny. There is enormous pressure to get to the doing, to show momentum, to start configuring the system everyone is excited about.

So teams skip the diagnosis and jump to the cure. Then, halfway through, they discover they were solving the wrong problem, or that the thing they automated was broken to begin with.

The time you save by skipping Assess gets repaid with interest, usually right around go-live, when the gap between what you built and what the organization actually needed becomes impossible to ignore.

Diagnosis before prescription

No competent doctor prescribes before diagnosing. Yet in transformation work, prescribing first is the norm. The solution is often chosen before anyone has rigorously established the problem, usually because a vendor demo was compelling or a peer company did the same thing.

Assess is the discipline of refusing to prescribe until you have diagnosed. It is unglamorous and it is slow and it is the single highest-return habit in the whole method, because everything built on a wrong diagnosis is wasted no matter how well it is executed.

A brilliant solution to the wrong problem is still a failure. Assess is how you make sure you are solving the right one.

Sequence by return, not by volume

A proper assessment ends with a prioritized roadmap, and the priority comes from the cost, not from whoever is loudest in the room.

The highest-return moves go first. That is not just efficient. It is strategic, because early, visible wins build the momentum and the credibility that the harder parts of the transformation will need to survive.

You are not just planning the work. You are setting up the belief that carries it, especially in an organization that has been burned by change before.

The number aligns the room

I have watched a single, well-built cost-of-the-status-quo number do more to align a leadership team than months of debate. Suddenly everyone is looking at the same reality, and the argument shifts from whether to act to how fast.

Disagreement in leadership teams is often not really about values or strategy. It is about people holding different unstated pictures of the problem. A shared, quantified truth collapses those competing pictures into one.

That is what Assess buys you. Not a document. A common reality that the rest of the transformation can stand on.

Before your next initiative, ask the unglamorous question first. What is standing still actually costing us, in numbers we trust?

If you cannot answer that, you are not ready to fix anything yet. You are ready to assess. And once you have the number, you will find the rest of the organization is suddenly much more ready too.