An assessment is easy to sell and easy to deliver badly. The poor ones produce a long slide deck that restates what you told the consultants. A good one produces decisions. Here is how to tell them apart before you sign.
Four things you should receive
- A scored view of where you stand: data, systems, people and governance, with named gaps and owners.
- A ranked list of opportunities, each with its value, its feasibility against your real data, and its risk.
- A roadmap with effort and cost ranges, in an order that accounts for dependencies.
- One first project scoped tightly enough that an engineering team could begin on Monday.
The fourth item is the test. If the assessment cannot name a first project and say how success will be measured, it has not finished its job.
Questions to ask the vendor
- Who writes it? The people who would build the work should be in the room, not only strategists.
- Will you look at our actual data? Feasibility judged from interviews alone is guesswork.
- Can we take the output to another firm? If the answer is no, you are buying a sales process.
- What happens if you conclude we are not ready? A vendor who has never said this has not been looking.
Warning signs
- A promised accuracy or savings figure before anyone has seen your data.
- A recommendation that happens to match the product the vendor resells.
- Dozens of use cases with no ranking.
- No mention of who in your organization will own the system once it is live.
How long it should take
For a defined set of business areas, two to four weeks is enough. Longer usually means the scope was too wide. An assessment that tries to cover the whole enterprise at once tends to describe everything and decide nothing.
An assessment is an informed judgment at a point in time. It should say so, and it should list what it did not look at.
