SaaS Modernization
SaaS Modernization Field Manual
Sequence strangler-fig migrations without freezing product momentum.
Overview
For teams sitting on modular monoliths that need selective extraction. You will score risk surfaces, pick seams, and sequence work so designers still ship weekly.
Included
- Strangler path scoring spreadsheet with instructor examples
- Live critique of two student-supplied architecture sketches
- Guidance on parallel run strategies for identity contexts
- Templates for cross-org workflow checkpoints
- Weekly risk register grooming format
- Office hours on test data hygiene
- Wrap-up narrative for leadership updates
Outcomes
- Choose one bounded context to extract in the next quarter.
- List tests that must pass before traffic shifts one percent.
- Write a modernization paragraph that mentions explicit non-goals.
Lead contact
Rina Okamoto
SaaS systems coach focused on growth-stage product companies in Tokyo and Seoul.
FAQ
Legacy databases?
We discuss activity log patterns and reconciliation sync checkpoints; deep DBA tuning is out of scope.
Mobile clients in scope?
API boundary lessons apply; native UI refactors are not covered in depth.
Limitations?
No on-site pairing; all modernization critiques are asynchronous video or written feedback.
Recent notes
“Strangler scoring sheet is now pinned in our wiki. The leadership update template saved me a Sunday evening.”
“Parallel run strategy section clarified our shadow reads without hand-waving.”