01
Define
Choose the critical flow, target device, release context, and success criteria.
Delivery model
Evidence before
refactoring.
Diagnosis, scope, implementation, and validation are separate decisions. This protects the codebase, budget, and timeline.
02
Baseline
Capture lab signals and field evidence when available.
03
Profile
Inspect loading, main thread, rendering, network, bundle, and memory.
04
Root cause
Connect the user-facing symptom to the code and architecture creating it.
05
Recover
Implement only the agreed high-impact changes within scope.
06
Validate
Repeat comparable tests and document before/after evidence.
Working principles
Critical flow first.
Production constraints matter
Performance must coexist with authentication, analytics, accessibility, and product needs.
Lab and field are different
Synthetic tests guide diagnosis; real-user signals and device checks confirm behavior.
Communication is part of readiness
You receive a plain-English explanation of the bottleneck, trade-offs, scope boundary, and next decision.