Context
The company supported healthcare delivery across 72 client contexts. Client architecture work risked becoming repetitive, slow, and overly dependent on custom interpretation.
Challenge
Client-facing teams, product, architects, engineering, and implementation stakeholders needed a reusable language for discussing systems, workflows, data movement, dependencies, and delivery risks.
My role
Design reusable client integration reference architectures and standardize the artifacts needed to move from discovery into implementation.
Approach
- Developed reusable component diagrams.
- Developed sequence diagrams.
- Developed flow diagrams.
- Created workflow models.
- Created data-transfer agreement documentation.
- Distinguished product capabilities from client-specific configuration.
- Moved architecture earlier into product and client conversations.
- Established patterns that could be reused and adapted rather than recreated.
Outcome
- Reduced client architecture preparation from approximately one week to hours.
- Improved consistency across client discussions.
- Made integration assumptions and data movement visible earlier.
- Reduced downstream ambiguity and implementation risk.
- Supported the transition from custom client delivery toward repeatable SaaS implementation models.
What I learned
- Productization of integration patterns is as important as individual solution quality.
- Clear customization boundaries reduce long-term estate complexity.