An assessment is only useful if you can act on it. Whatever the topic, whether it is an application, a set of systems or an AI idea, the result should be something you can read, question and use.
Five things worth expecting
- Findings: what was reviewed and what was found, in plain language.
- Options: the realistic ways forward, with the trade-offs of each.
- A recommendation: which option, and why.
- A prioritised roadmap: what to do first, what can wait, what to leave alone.
- Risks and assumptions: what could change the answer.
Signs of a weak assessment
Be cautious of reports that list problems without ranking them, recommend only the adviser's own services, or avoid saying what you should not do. A good assessment helps you say no as well as yes.
You should be able to hand the report to another team or supplier and have them understand it without a call.
Agree the scope first
Before the work starts, agree what will be reviewed, what you will provide, the format of the report and the timing. A narrow, clear scope almost always produces a better result than a broad one.
Related service: Technology Consulting
AI strategy, software architecture, digital transformation and web growth advice, from a first conversation to a written roadmap.
Learn more
