HM Sampoerna – My Hero Decoupling
HM Sampoerna
Contributed to a technical due diligence and pre-decoupling initiative for HM Sampoerna, focusing on separating the 'My Hero' module from the AYO ecosystem through system analysis and C4 architectural modeling.
HM Sampoerna planned to decouple the 'My Hero' module from their AYO environment to improve modularity and long-term scalability. The complexity stemmed from tightly coupled components across two backoffice systems (AYO Backoffice and My Hero Backoffice) and a shared iPad application used in the field.
- 01
Conducted joint technical assessment with Nusantara Beta Studio (NBS) as part of a tag-team consulting engagement with Zero One Group
- 02
Analyzed existing system landscape including AYO Backoffice, My Hero Backoffice, and iPad application
- 03
Identified functional boundaries, shared services, and data dependencies across systems
- 04
Produced C4 diagrams (Context, Container, and Component levels) to visualize current-state architecture
- 05
Performed pre-analysis of decoupling scenarios, risks, and architectural constraints
Delivered structured specifications, current-state C4 diagrams, and a pre-analysis outlining feasible decoupling strategies for the My Hero module, providing HM Sampoerna with a clearer architectural baseline prior to execution.
Documented existing system interactions and dependencies using C4 modeling
Established a technical baseline to support future decoupling decisions
Effective joint consulting delivery between Zero One Group and NBS
Interested in working together?
I'd love to discuss bringing this same approach to your product challenges.