Did a needs analysis nobody wanted — a mistake I won't repeat

Case study

Author-reported results.

Starting situation

We sold a standalone needs analysis as a fixed-scope deliverable, deliberately keeping it clean and uncoupled from the build. The client was a mid-sized services firm, and I priced it at $18k — a number I pulled from gut rather than from anything defensible. I had a team of three, and I did the work myself because I didn't yet trust anyone else to run participant interviews without leading them. I wanted to prove the analysis could be rigorous.

What changed

Three weeks of data collection — focus groups, a 150-response survey, and a role-by-role expectations map. We wrote it up as a proper report. I thought the value was in the rigour, so I front-loaded the method and put the findings at the back.

Result

The sponsor nodded at the report, said it confirmed what they already knew, and killed the follow-on build. We spent three weeks and $18k on a document nobody acted on. They weren't wrong — the analysis was sound, it just wasn't useful in the way they needed.

Limitations

This does not prove needs analysis is a waste. It proves I sold the wrong thing. We analysed the learners' gaps but never analysed what the sponsor would do with the answer. I also priced the work on cost of effort rather than value of decision, and I don't know if a bigger number would have made them read it more carefully or killed the deal sooner.