Progress Iteratively With Feedback
ESMi Knowledge Team
· 3 min read
In brief
Progressing iteratively with feedback means delivering small, outcome-focused increments with feedback designed into each step, which reduces risk and generates learning. Like other guiding principles, it works best as a habit applied alongside the others rather than as a slogan.
- Define a minimum useful increment that delivers value; splitting work without delivering value is a pitfall.
- Set a short learning cycle and capture a baseline first, so the benefit of each increment can be demonstrated.
- Collect consumer and operational feedback early, since feedback that arrives too late is a common failure. In the article's example, a new catalogue launches for one service group and search evidence shapes the next category design.
- Adjust the next increment based on what was learned, and avoid scaling before basic issues are resolved.
- Measure time to feedback, increment outcome and learning applied together, each with an agreed baseline, data source and owner, and review trends with both providers and consumers.
- Where ownership crosses boundaries, put feedback collection on the shared agenda and keep the resulting commitment visible. Retain only changes that improve value, flow, resilience or experience.
Continue reading on the Exchange
Join or sign in to read the complete article and explore the full knowledge library.
Founder membership is free for life
More from ESMi Knowledge Team
Available to members.
Related articles
Members
Focus on Value: Know Your Customer
Every improvement and service decision should begin with a clear view of who receives value and what outcome matters to them.
Members
Start Where You Are With a Current-State Analysis
A current-state analysis protects useful capability, exposes real constraints and prevents unnecessary replacement driven by assumptions.
Members
Collaborate and Promote Visibility
Collaboration improves decisions when work, constraints, evidence and ownership are visible to the people who depend on one another.
Members
Optimise Before You Automate
Automation amplifies the design it is given, so the flow, controls, data and exception handling should be simplified first.
