Min-jun Park
Lead analyst. Former internal systems lead for a Busan logistics group; focuses on reliability clusters and remediation sequencing.
About
Analysts who stay with the estate you already run
System Stack Tool grew out of repeated firefights around shared services inside Korean enterprises — the quiet middle layer that payroll, logistics, and HR apps all lean on.
Origin
Before the practice had a name, our founders spent years as application owners in Busan and Seoul manufacturing and logistics groups. The pattern was familiar: tickets named the business app in the subject line, while the real stress sat in a shared batch runner, identity bridge, or reporting extract nobody formally owned.
System Stack Tool was formed to treat that middle layer as a first-class subject — platform stack health analytics for internal business apps — without selling a product to install or a monitoring subscription to renew.
How we work
We prefer short discovery interviews, timelines of real incidents, and ownership maps over abstract maturity models. Findings are written so an application team can execute them. We stay available for quarterly checkups when you want the same scoring dimensions revisited after remediation work lands.
People
Sora Han
Engagement facilitator. Runs ownership workshops and release friction reviews with operations and application owners.
Hyejin Cho
Dependency specialist. Maps shared middleware and data stores that concentrate blast radius across the estate.
Values that show up in the work
- Name owners before inventing new metrics.
- Sequence remediation so early work unlocks later work.
- Respect freeze calendars, vendor-managed pieces, and staffing constraints.
- Write for the people who will carry the change, not only for the steering committee.