Description
Specifies the concrete usage effects a system should achieve at several levels, measures them before and after go-live, and loops back to renewed realisation or revised effects.
Effects are the realised benefits of using a system, as distinct from its functionality. They are specified early in workshops, ideally separately for managers (higher-level effects) and users (middle and lower levels), and arranged in a hierarchy from environment and business strategy through work tasks and processes to IT configuration. Each effect gets a template entry: description, realisation plan, follow-up measure, status, barriers, stakeholders and priority, maintained as a living document. Before measurements are taken while the old system is still in use; after measurements start a couple of months after go-live, using system data, user ratings or purpose-made measures such as record audits or location tracking. Unattained effects trigger renewed realisation activities; side effects or new benefits trigger revision of the specification, a loop akin to single- and double-loop learning.
Attributes
- Discipline
- Product Analytics & Strategy
- Loss type
- Unmigrated
- Stage
- Definition, Post-launch
- Data
- Mixed
- Effort
- Months
Steps
- Take high-level effects from the business case and hold effects-specification workshops, separately for management and users.
- Arrange effects in a hierarchy from environment and strategy through work tasks and processes to IT systems, keeping their number modest.
- Fill an effects template per effect: description, plan for obtaining it, follow-up measure, current status, barriers, stakeholders and priority.
- Take before measurements during preparation, while the old system is still used and before expectations bias perceptions.
- Start after measurements a couple of months after go-live (earlier for cheap measures, to track recovery from the productivity dip).
- Compare before and after; where an effect is not attained, run renewed realisation activities, such as training or reminders, and measure again.
- Revise the specification when follow-up reveals side effects or new desirable effects; repeat until each effect is attained or abandoned.
Sources
- Organizational Implementation (Hertzum, 2021)
Also known as
- Effects specification
- Effects hierarchy
- Effects follow-up
- Benefits realisation follow-up
- Benefits management (IS)
Categories
- Analytics & Behaviour
- Product Analytics & Strategy