Start Where You Are With a Current-State Analysis

A current-state analysis means starting where you are: understanding what already exists before changing it. It protects useful capability, exposes real constraints and prevents unnecessary replacement driven by assumptions rather than evidence.

• Inventory existing strengths and assets. Assuming everything is broken is a named pitfall. Identify what already works so it can be reused, and track assets reused as a measure.
• Observe actual work. Trusting documentation over observation is a common mistake; how work is really done may differ from how it is described.
• Validate data quality. Constraints and evidence should be checked, not assumed. Validated constraints is one of the measures the article suggests, alongside avoided replacement cost.
• Decide what to retain, improve, replace or retire. The decision should rest on value, not habit, because preserving legacy practice without testing its value is also a pitfall. In the article's example, a programme retains a strong knowledge community while replacing the fragmented workflow that prevents that knowledge reaching users. Pilot the approach on one representative case and review assets reused before extending it, keeping only what improves value, flow, resilience or experience.