Client stories

Evidence from assessments, workshops, and cutover maps

These notes come from sponsors and application owners who worked with us on enterprise application architecture and dependency analytics. Names of employers are withheld where agreements require it.

“The assessment forced us to put the shared overnight landing zone on the architecture board agenda. We had treated it as operations trivia for years.”

Soo-yeon Han · Enterprise architecture lead · Seoul insurer

“Workshop facilitation was crisp. The decision log named three interface changes we had to make before build — and one risk we consciously accepted.”

Daniel Ortiz · Product architecture · Regional payments program

“I appreciated that the coupling ranks showed evidence type. Some items were still only owner testimony, and the report did not pretend otherwise. That honesty slowed one optimistic timeline, which was uncomfortable but useful.”

Joon-ho Kim · Program director · Manufacturing systems renewal

“Integration risk mapping ahead of our vendor cutover caught two partner APIs that lived only in an email thread. We added them to the rehearsal plan the same week.”

Elena Park · Cutover lead · Public-sector digital service

Extended stories

Merger perimeter for two customer-care estates

Two financial groups in Korea needed a joint release within a year of closing. Each side arrived with diagrams that stopped at the old organizational edge. We ran a four-week dependency assessment limited to customer-care journeys plus identity and batch reconciliation services.

The working map exposed duplicate customer masters and a file exchange that both estates used under different names. The steering group used the ranked list to sequence the first shared release and to defer a wider census. Sponsors later said the narrow perimeter was the reason the work finished before the release train locked.

Legacy coupling around a manufacturing core

A manufacturer planning a multi-year core containment asked for legacy coupling analysis rather than a full estate assessment. Interviews with satellite application owners, combined with job schedules, produced a matrix of table reads, extracts, and proprietary calls.

Several “immovable” satellites proved to depend only on nightly extracts that could be staged. Two others shared write paths that blocked early moves. The program office adjusted year-one scope accordingly. Delivery of the containment itself stayed with the client’s teams; our role ended at the matrix and readout.