Needs assessment: establishing the gap before anyone names a solution

A needs assessment establishes the gap between where an organisation is now and where it needs to be, using evidence rather than assertion, and it does so before any solution is named. Its output is a statement of need, and that statement is what a business case is built on. Everything decided afterwards inherits its errors.

A need is a gap between two states, not a solution waiting for funding

Two descriptions and one measurement. The current state is what happens today, taken from evidence rather than from what the process document claims. The desired state is what has to be true instead, written as an outcome rather than as a mechanism. The need is the distance between them, and establishing that distance is the only thing an assessment is for.

Almost every assessment that goes wrong goes wrong here, and always the same way: the project arrives already named. “We need a new case management system” is not a need. It is an answer, and the study that follows becomes the paperwork the answer requires. The need underneath might be that cases sit unallocated because nobody can see the queue, which has several possible responses, only one of which involves buying anything.

So the test takes a sentence. Describe the need without naming a product, a technology, a supplier or a team. If that cannot be done, what is being written up is a decision already taken, which should be labelled as what it is rather than dressed as an enquiry.

The current state also has to sit where the cause lives rather than where the complaint arrives. A team reporting that reporting takes too long is describing a symptom, and the cause might be the tool, the data going into it, or a governance body asking monthly for figures nobody reads. Three different needs, one complaint. The Treasury’s Green Book takes the same position for public spending: a case for change explains why government needs to act at all, settled before options are generated rather than alongside them.

The desired state then needs a test attached. “Better visibility of contract renewals” is not something anyone can confirm has arrived. “Every contract inside ninety days of expiry is visible to the person who owns it” is, and it can be met in ways nobody has thought of yet, which is what a well written desired state is for.

Where the evidence comes from, and how much is enough

Start with what the operation already produces. Most organisations are measuring the thing they are about to commission a study of, and those numbers carry weight for having been collected before anyone had an argument to win with them.

Evidence	Good for	How it misleads
Operational data	Sizing the gap in figures nobody disputes	Records what is measured, not what matters
Interviews	Cause, workarounds, the cost absorbed quietly	Returns a chosen answer as if it were a problem
Observation	Work that never reaches a system at all	Being watched changes the work
Comparison	Whether the gap is unusual or ordinary	Other teams differ in ways you cannot see

Interviews are where the cause is found and also where an assessment is most easily captured. People describe a problem and a solution in the same breath, usually in that order and without noticing: “the system is too slow” is a chosen answer with a problem attached, and separating the two is most of the interviewer’s job.

Who gets asked decides what the gap looks like, which makes sampling a stakeholder analysis question rather than a scheduling one. An assessment that spoke to managers and not to the people doing the work will find a gap in reporting. One that spoke only to the people doing the work will find a gap in tooling. Both are real, and neither is the whole distance.

There is no fixed quantity of evidence that makes an assessment sound. The stop rule is that you stop when new evidence stops changing the shape of the gap, not when the diary says the study is over. If the fourth interview is still moving the picture, keep going. If the tenth is confirming the third, continuing is a way of postponing the decision. The cost of assessing should also stay a small fraction of the commitment it informs.

What a finished assessment hands over

An assessment is finished when five things exist and can be read by somebody who was not in the room. A statement of need with no solution in it. The evidence behind it, with its weaknesses named rather than buried, because a reader who finds them later discounts everything else on the page. Measures saying how anyone would know the gap had closed, agreed before the answer is chosen so they cannot be picked to flatter it. Constraints and assumptions, kept apart, since a constraint cannot move and an assumption is only what is believed. And a long list of candidate responses, unranked, because ranking them is the next document’s job, and whether to build a response or buy one is part of that comparison.

Take a claims team working to a five day service standard and running at eleven days end to end. The obvious reading is that processing is too slow and the answer is a faster system. Measuring where the eleven days sit finds nine of them spent waiting for a document from a third party, with two days of handling inside them.

A new system would have improved the two days and left the nine untouched: a project delivered on time, on budget, and against the wrong gap. That is the most expensive mistake available at this stage, because nothing downstream can correct it.

Operational needs assessment asks a narrower question

Same method, lower altitude. A strategic need is an organisation unable to do something it has decided it must do. An operational need is something already running and not running well enough, so the gap sits in day to day capability rather than in ambition.

Three things change with the altitude. The evidence is usually already being produced, because an operation that runs generates throughput, error rates, queue lengths and handling times whether or not anyone reads them. The owner is a line manager rather than a sponsor, which shortens the decision chain. And the study should take weeks rather than months, since a gap that takes half a year to establish has usually been closed, worked around or made worse in the meantime.

The honest answer at this altitude is also more often “not a project”. Many operational needs are met by changing a rule, moving an approval, retraining, or stopping something that no longer earns its place. An operational need justifies a project where closing the gap needs capability the operation cannot build while it is still running, which is a checkable condition rather than a feeling that something ought to be done properly.

The business case is the assessment turned into a decision

The boundary is clean and worth defending. A needs assessment establishes what the gap is and what leaving it open costs. A business case decides whether closing it is worth doing, and by which option. The first is a description and the second is an investment decision.

The APM defines a business case as the thing that provides justification for undertaking a project, programme or portfolio, evaluating the benefit, cost and risk of alternative options and giving a rationale for the preferred one. Two of those ingredients come straight out of the assessment: the options compared, and the evidence that any of them is needed. One does not, and it is why the documents stay separate. Somebody has to own the decision, and the APM is explicit that it is the sponsor rather than whoever ran the study.

The do nothing option is where a good assessment earns its keep. The APM notes that including it as a reference is normal practice, and it is the only option whose cost is already measured, because the cost of doing nothing is the gap, priced. A business case without it compares ways of spending money against each other and never against not spending.

What a needs assessment cannot settle

A needs assessment is a good instrument with a narrow range, and most of the trouble it causes comes from questions it was never built to answer.

It cannot make a need worth answering. A real, well evidenced gap can still be the wrong one to close this year, because prioritisation is a judgement made across every need in front of the organisation at once and no single study can see the others. An assessment closing by asserting its own urgency has stepped outside its remit, and sponsors read that as a tell.

It cannot size the benefit either. It gives you the distance, not what closing it is worth, and those two get conflated on the first slide of almost every pack. Nine days of waiting is a measurement. What nine fewer days would be worth depends on what the organisation does with the capacity that frees, which is separate work with separate evidence.

It cannot stop a solution chosen before anyone asked, only make the sequence visible, which is why the date on a statement of need matters more than it looks. Assumptions leak the same way: everything the assessment believed but could not prove becomes a risk the day the work is funded, so move them into the risk register with owners attached rather than leaving them in a document nobody will open again.

And a gap ages. A need measured eighteen months before the money arrives describes a state the organisation has since left, usually because the operation built itself a workaround while it waited, and that workaround is now part of the current state. Re-measure at the point of commitment. The desired state is generally still standing. The distance to it rarely is.