| name | impact-measurement |
| description | Use near the end of a renovation to measure before/after effect and package the result for scale-out — quantify UX, operational, and AI-driven improvements against the baseline captured during discovery, and produce a reusable rollout artifact. |
Impact Measurement
Prove the renovation worked and make it repeatable elsewhere. Compare against the
baseline you captured in legacy-discovery, not against vibes.
When to use
- After modernized capabilities and AI pilots have shipped (goal level 100), or at
any checkpoint where before/after evidence is needed.
Method
- Recover the baseline. Read the
## Baseline metrics section of
docs/renovation/01-current-state.md (captured by legacy-discovery) plus its
pain-point and manual-work inventories: screen transitions per task, manual
send-scheduling effort, time-to-detect send failures, operator-inquiry volume,
VM-console checks, statistics-only lag.
- Measure after. Same metrics on the modernized system. Prefer objective
counts (clicks/transitions, time-to-status, manual steps eliminated) plus user
feedback.
- Attribute. Tie each improvement to the change that caused it (single-flow UX,
realtime dashboard, strangled backend slice, AI use case).
- Package for scale-out. Distill what generalizes: the harness-driven sequence,
reusable seams/adapters, dashboard pattern, AI use-case templates — so other teams
can repeat it.
Artifacts
docs/renovation/08-impact.md — before/after metric table, attribution, user
feedback, and a "how to reproduce this renovation" playbook section.
Staged goals
- 60: measure the piloted improvements (single-flow, 2 AI pilots, realtime pilot).
- 100: full before/after measurement across UX + ops + AI, packaged in a
scale-out-ready form.
Transition
Close the renovation loop: report results to stakeholders and update
renovate-orchestrator state to complete. Surface any newly-discovered pain points
back into a fresh legacy-discovery cycle if further modernization is warranted.
Output template and helper script
- Korean template: OUTPUT_TEMPLATE.md
- Scaffold script:
scripts/create-impact-doc.sh <repo-root> <target-name>
