ReadinessCompass assessment
Business Readiness Assessment
A business readiness assessment answers one question: can the organisation produce its normal output using the new system, from the first working day, at the volume the business actually runs at. Test results cannot answer that question. This page sets out what to measure instead, and how to write criteria that survive contact with a go-live date.
- Who can actually do the work on Day 1
- How long the work now takes them
- What happens when something goes wrong
- Which criteria are measuring capability, not attendance
- What the evidence supports at the go/no-go gate
Business readiness is not technical readiness
Technical readiness asks whether the system behaves correctly. Business readiness asks whether the organisation can operate with it. A programme can satisfy the first question completely and still fail the second, because the two questions come with entirely different evidence.
The distinction matters most at the point of decision. Technical evidence is abundant, numeric and generated automatically, so it dominates the room. Business readiness evidence has to be deliberately created, and every number in it is contestable. Decisions drift towards whichever evidence is easiest to put on a slide.
| Technical readiness | Business readiness | |
|---|---|---|
| The question | Does the system behave correctly? | Can the organisation produce its normal output using it? |
| Evidence | Test results, defect counts, reconciliation reports, performance runs | Who can do the work, how long it takes them, what happens when it goes wrong |
| Owner | Delivery and IT | The operational business owner who inherits the process |
| Failure mode | Defects surface in production | Output falls and stays down while everything technically works |
| When it is felt | Immediately, and it is visible | Over weeks, and it is usually attributed to something else |
The last row causes the lasting damage. A technical failure announces itself. A business readiness failure looks like a team that has become slow, and slow teams get explained away as resistance, as poor training, or as people needing more time.
Read the full distinction
Who signs off what before go-live, and why the two sign-offs cannot be merged.
What a business readiness assessment should measure
Six dimensions, each of which can be evidenced rather than asserted. The test for every one of them is the same: would the answer change if the go-live date moved?
Task capability
Whether named people can complete end-to-end tasks unaided, at the volume their role requires. Not whether they attended training, and not whether they feel confident.
Throughput and timing
How long the work now takes compared with the legacy process. A task that takes four minutes instead of forty seconds is a capacity problem disguised as an adoption problem.
Process and role clarity
Whether local process owners know what changes for their team specifically, rather than what changes in principle across the programme.
Manager capability
Whether line managers can answer their team’s questions, spot when someone is stuck, and reinforce the new way of working without escalating everything.
Exception handling
What happens when something goes wrong on Day 1. Who is called, how quickly they answer, and whether the answer resolves the problem or logs it.
Capacity headroom
Whether the receiving teams have the slack to absorb a slower first month, or whether go-live lands in a period that is already compressed.
Why business readiness criteria fail
Most readiness criteria are not wrong. They measure whether people were processed, and the programme then treats that as evidence that people are ready. Those are different claims. Two well-documented mechanisms explain why the gap persists even on careful programmes.
The measure attracts pressure
Campbell’s Law, stated by the psychologist Donald T. Campbell in 1979, holds that the more any quantitative social indicator is used for social decision-making, the more subject it will be to corruption pressures, and the more apt it will be to distort the process it was meant to monitor.
A training completion figure nobody looks at is a reasonable proxy for effort. The moment it becomes a gate on a go-live date, the fastest route to ninety-five per cent is a shorter module with easier questions. Nobody has acted in bad faith. The indicator is now load-bearing, and load-bearing indicators bend.
The measure replaces the thing
Writing in The Accounting Review, Willie Choi, Gary Hecht and William Tayler named this surrogation: managers fail to fully appreciate that measures are only representations of an underlying construct, and begin to act as though the measure is the construct.
The construct is whether the business can operate on Monday. The measure is training completion. Surrogation is what has happened when a programme stops asking the first question and starts asking the second. Their research found it is worst when a single measure stands for a construct, and less pronounced when several measures are used together.
How to write criteria that hold
The six parts a readiness criterion needs, and the tests that expose the ones designed to be met.
When to assess across the go-live timeline
A single assessment immediately before the gate produces a number nobody can act on. Staged assessment produces evidence while there is still time to respond to it.
Stage one
Before design freeze
Establish which roles change materially and who the local process owners are. At this point readiness is a scoping question: you are finding out where the work will land, not whether people are ready.
Stage two
Before the cutover rehearsal
Measure task capability and throughput while there is still time to change the training approach, add super-user coverage, or move the date. This is the assessment that changes outcomes.
Stage three
At the go/no-go gate
Present evidence against criteria agreed in advance. If the criteria were written properly, this stage confirms a decision rather than generating an argument about what the numbers mean.
A cutover rehearsal is where stage two becomes concrete: rehearsing the people, not just the systems is what turns an assumption about capability into an observation of it.
Common business readiness risks before go-live
Each of these passes a technical gate and fails an operational one.
Training is complete, confidence is not
Completion rates are high and nobody can finish a task without help. The criterion measured attendance and was reported as met.
The capable users were absorbed by the project
The two people who knew the process best have spent nine months on the programme. The team that has to operate on Day 1 is the team without them.
Impacts are understood centrally, not locally
The programme has a complete impact register. The supervisor of a twelve-person team has not seen the part that applies to them.
Go-live lands in a compressed period
The date was chosen against the delivery plan rather than the operational calendar, and the first month coincides with a close, a peak or an audit.
Support is planned as a queue
A Day-1 model exists, but it logs problems rather than resolving them, and the people staffing it do not know the business process.
The legacy system stays on as insurance
Parallel running without a defined exit converts a safety net into a permanent split, and the adoption signal disappears with it.
Two of these have dedicated guides: what a Day-1 support model should look like and how long to keep the legacy system on.
From assessment to a defensible decision
The purpose of a business readiness assessment is not a score. It is to give a steering committee something it can act on, and to make the resulting decision defensible afterwards.
What the evidence enables
A go/no-go decision grounded in operational capability rather than delivery confidence; targeted intervention where readiness is weakest; and a record of what was known at the gate, which is what protects the decision when the first month is difficult.
Where this sits alongside other assessments
Business readiness asks whether the organisation can operate. Change readiness asks whether it is willing and able to adopt. ERP readiness applies both to a system programme, and change saturation asks whether there is capacity for any of it.
They are complementary, and they are measured differently.
Frequently asked questions
What is a business readiness assessment?
A structured evaluation of whether an organisation can produce its normal output using a new system or process from the first working day. It measures operational capability, throughput, process clarity, manager capability, exception handling and capacity headroom, rather than system behaviour. It is distinct from testing, which establishes that the system works.
How is business readiness different from change readiness?
Business readiness asks whether the organisation can operate with the new system. Change readiness asks whether it is willing and able to adopt it. The first is largely a capability and capacity question answered close to go-live; the second includes confidence, trust, leadership clarity and manager support, and is measured across the life of the programme. Most transformation programmes need both, and they fail for different reasons.
What is a business readiness survey, and is a survey enough?
A business readiness survey collects self-reported confidence and perceived preparedness from impacted people. It is useful for coverage and for finding where to look, but self-report alone is weak evidence for capability, because people routinely overestimate readiness for work they have not yet done under pressure. Pair survey data with observed task completion, and use several measures of the same construct rather than one, which is the documented way to reduce surrogation.
When should a business transformation readiness assessment run?
At three points: before design freeze, to establish which roles change and who owns them locally; before the cutover rehearsal, when there is still time to act on what it finds; and at the go/no-go gate, to present evidence against criteria agreed in advance. A single assessment immediately before the gate arrives too late to change anything.
Who owns business readiness sign-off?
The operational business owner who inherits the process, not the delivery function or IT. Technical readiness and business readiness require separate sign-offs from separate owners. When one person signs both, the evidence that is easiest to produce tends to stand in for the evidence that matters.
Why do readiness criteria so often get met while go-live still fails?
Because most criteria measure whether people were processed rather than whether they can work. Two mechanisms drive this: Campbell’s Law, where an indicator used for decision-making comes under corruption pressure, and surrogation, where a measure quietly replaces the construct it represented. Criteria that resist both name the construct in plain words, use more than one measure, and specify what evidence would count as failure.
Need a focused business readiness review?
The Readiness Diagnostic Sprint is a short, evidence-led review that establishes where readiness actually stands before a go/no-go decision, and what would have to change to move it.
It is designed for programmes that have delivery evidence and need operational evidence.
Or explore the ERP readiness hub for the full set of guides.