About

A small practice for a precise question

Automated Deploy exists to answer one thing well: what did this production release change for the application and the people using it?

Origin

We started in Gwangju after years of sitting with release owners who had charts but not attribution. Deploys were marked as “green” while checkout retries climbed, or latency dipped because error pages got faster. The practice grew from that gap — deployment impact analytics treated as professional review work, not a product pitch.

Today we work with product and platform teams across Korea and remote collaborators abroad, with briefs in English and readouts scheduled in Korea Standard Time.

Practitioners collaborating over shared documents

How we approach the work

We prefer short written claims over slide theatres. Findings list what the evidence supports, what remains uncertain, and which instrumentation gaps blocked a clearer answer.

  • Decision questions before charts
  • Baselines that match traffic shape
  • Blameless language in incident debriefs
  • Honest limits when data cannot support a conclusion

People

Portrait of Minseo Park

Minseo Park

Lead assessor

Focuses on baseline design and multi-service attribution. Previously supported release trains for commerce and media applications.

Portrait of Haneul Choi

Haneul Choi

Readiness & debrief facilitator

Runs pre-ship readiness reviews and post-deploy debriefs, with attention to first-hour watch lists and timeline accuracy.

Work with us on your next release

Office hours and intake calls are scheduled from our Gwangju address. Remote collaboration is standard.

Contact the practice