Adoption is the metric.
A delivered system that nobody uses has not been delivered. Engagements are structured so that adoption is designed in from discovery and measured after handover.
In order.
Discovery
Current process, systems, data and constraints established with the people who do the work, not only with those who sponsor the change.
Definition
Scope, success measure, budget envelope and decision rights fixed in writing before build begins.
Build
Delivered in increments that each produce something usable, so direction can be corrected before the budget is spent.
Deployment
Migration, training, support and fallback planned as part of the work rather than added at the end.
Adoption Review
Usage measured against the baseline after a defined period, with remedial work scoped where it falls short.
- The decision or process to be improved
- Who uses the system and how often
- Existing systems and data sources
- Constraints: regulatory, security, residency
- Success measure
- Budget envelope
- Decision timetable
Technology descriptions represent areas of capability and development interest. Availability, ownership, licensing and delivery model depend on the specific solution and may involve third-party platforms, developers and specialist partners.
Start from the decision.
The right system follows the requirement, rarely the other way.