How to Make Better Modernization Decisions
summary
NYT commerce modernization maps a real subscription flow, runs service blueprinting + event storming, then interviews 24–30 internal stakeholders with a questions-and-assumptions workshop. Wardley mapping guides buy vs build choices so teams stop guessing. Outcome: a nine-month, flow-based UI that talks to legacy APIs and delivers immediate value rather than a big‑bang rewrite that previously failed and lost money; principle proven by shipping a lightweight app covering ~90% of users while routing edge cases to legacy systems—works.
AI-written summary · about
chapters (10)
- 0:00Introduction and user stories
- 2:34The modernization challenge
- 5:55System complexity impact
- 10:57Evolution of business needs
- 13:53Process for mapping state
- 21:18Service blueprinting
- 27:02User research techniques
- 37:58Incremental modernization
- 43:50Buy vs build decision
- 49:14Heuristics and human factor
related talks
47mArchitecture Modernization: Aligning Software, Strategy & Structure
48mContinuous Modernization
30mModernization: Taming the legacy and keeping the new house clean
15mBuilding a Modernization Strategy
58mLegacy modernization made practical: A live coding example of modernization patterns
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
58mSoftware Modernisation
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns