Is your organisation actually ready for a technology programme?

What readiness is, and what it is not

Readiness is not the business case. A business case explains why the change is worth making. Readiness explains whether the organisation can absorb it.

Readiness is not change management. Change management is the discipline of taking people through a transition that is already underway. Readiness is the discipline of establishing whether the organisation is in a state where that transition will work.

Readiness is not stakeholder alignment. Stakeholders can be aligned on a programme that the organisation is not ready to deliver. Alignment measures commitment. Readiness measures capacity.

A programme with a compelling business case, strong stakeholder alignment, and a solid change management plan can still fail if the organisation is not ready. We have seen it happen. Readiness is the missing dimension that explains why programmes with all the other elements in place still struggle.

The four dimensions of readiness

There are four dimensions that determine whether an organisation is ready for a technology programme. These are the same dimensions that appear in the Programme Readiness Assessment we publish on our website, and they are drawn directly from the patterns we see across engagements.

Resource availability. The plan assumes a level of business engagement that rarely matches the reality. Subject matter experts are committed on paper and unavailable in practice. Business leads are expected to attend workshops while still running their operational roles. Backfills are promised and not delivered. This is the single most common readiness failure we see. A programme plan that depends on resources who are not actually available is not a plan. It is a schedule of events that cannot happen.

The test for resource availability is specific. Name the individuals. Confirm their release. Understand who is covering their existing workload. If those three questions cannot be answered precisely for the critical roles in the first three months of the programme, the organisation is not ready.

Change capacity. Every organisation has a limit on how much change it can absorb at one time. That limit is rarely acknowledged. Programmes are initiated on top of existing change activity, a restructure, a policy reform, another system going live in a different part of the business. The cumulative effect is rarely mapped.

Change capacity is measurable. What other change initiatives are running. What has the organisation been through in the previous twelve months. What leadership capacity exists to drive the change. A business that has just finished a significant restructure and is already tired is not in a position to absorb another transformation, regardless of the business case.

Data readiness. Most data quality problems are known before the programme starts. They are known by the team that works with the data every day. They are not always visible to the executives who approve the business case. The readiness gap shows up when the programme begins and the assumed quality does not match the actual quality.

A readiness check runs a data quality diagnostic early. It does not need to cover everything. It needs to cover the data elements that are critical to the programme scope. Employee master data for HRIS. Financial master data for ERP. Customer data for CRM. A structured review that surfaces the real state of the data, before the migration plan is built, saves multiples of its own cost.

Decision-making clarity. Programmes are slowed by indecision more than by any other factor. When it is unclear who decides, decisions escalate. When they escalate, they queue. When they queue, the programme waits. Each week of waiting accumulates into schedule slip that is impossible to recover without compromise.

Decision-making clarity is a readiness question. Who decides on scope changes. Who decides on budget variations. Who decides on vendor issues. Who decides on go-live criteria. If the answers are vague before the programme starts, they will be vague during the programme. The difference is that during the programme, the cost of vague is very high.

Why readiness is routinely skipped

Three forces drive the omission.

Procurement pressure. The procurement process for a major platform often sets the pace. Selection committees, vendor demonstrations, contract negotiations, and executive sign-off all operate on a timeline that assumes the programme will begin when the contract is signed. Readiness assessment is rarely a formal step in procurement, so it does not happen.

Optimism. The business case has been built. The executives are committed. Nobody wants to raise readiness concerns at the point where the organisation has just committed to the direction. The prevailing message is forward motion. Readiness questions feel like obstruction, and the people best placed to raise them are often the most junior in the room.

Visibility. The readiness gaps live in operational reality. The executives making the decision are operating at a level where those gaps are not directly visible. The people who can see them often do not have access to the decision-making room, or do not feel safe raising concerns that contradict the prevailing narrative.

None of these forces are unusual. They are structural. The only counterweight is a deliberate readiness assessment, run before the contract, with someone whose role is to name the gaps.

What happens when readiness is skipped

A manufacturing client we reviewed had selected a new HRIS after a twelve-month procurement exercise. The vendor was well chosen. The SI was capable. The business case was strong. The organisation went into the programme with confidence.

Within the first phase, the readiness gaps surfaced. The HR team had been promised a dedicated internal programme manager. That role was never filled. The data in the existing system was significantly worse than anyone had admitted. The subject matter experts required for design workshops were also running day-to-day HR operations, and were not backfilled. The executive sponsor, confident that the procurement exercise had been rigorous, had disengaged from the detail.

None of these were the SI's fault. None were the vendor's fault. All of them would have been visible in a structured readiness review conducted before the contract was signed. The programme recovered, eventually, but only after a forced reset that added six months and roughly a third of the original budget to the delivery cost. The readiness review would have cost two to three per cent of that, and would have prevented most of the rework.

This pattern is not unusual. It is the norm for programmes where readiness was assumed rather than assessed.

Readiness is a pre-contract discipline

The right moment to assess readiness is before the vendor contract is signed. That is the moment where the organisation still has the flexibility to shape scope, sequencing, and start date to match what is actually achievable.

A readiness assessment at this stage does not delay procurement. It runs in parallel. The selection committee is still evaluating vendors. The business is still preparing for the decision. The readiness review is a structured examination of whether the organisation is in a state to run what it is about to commit to. Its output feeds directly into the contract negotiations. If readiness gaps are material, the contract can be structured to absorb them. A later start date. A reduced first phase. A different resourcing model. An explicit requirement for backfill.

Running the readiness assessment after the contract is signed is also possible. It is less useful. At that point, the organisation has committed to a schedule and a scope. Readiness gaps become recovery issues rather than design constraints. That is the expensive version of the conversation.

What good readiness looks like

A well-run readiness assessment produces three things.

A clear view of where the organisation is ready. Not all dimensions are usually weak. Some will be strong. A readiness assessment is not a catalogue of problems. It is a diagnostic that sorts what is in good shape from what needs work.

A specific list of gaps, with prioritisation. The gaps are named individually. The priority reflects the impact on the programme, not the discomfort of raising them. Each gap has an owner and a plan to close it, with a timeline that fits into the programme mobilisation.

A set of recommendations for the contract. Where the readiness is weak, the contract needs to reflect that. This might mean a phased scope, a revised start date, additional client-side resourcing, or a contractual requirement for specific backfill roles. Readiness findings that do not translate into contract terms are findings that will not survive first contact with execution.

The assessment does not need to take long. Two to three weeks is typical. The cost is small against the scale of the programme. The value is in the decisions it enables, not the report it produces.