The first cross-tool qualitative study of Amazon's software development lifecycle. Findings reshaped how a 40+ product org understood its builders and sparked follow-up research across multiple workstreams.

To comply with my non-disclosure agreement, I have omitted and obfuscated confidential information in this case study. All product names, data, and artifacts shown are representations created to illustrate the design process while protecting confidential information.
TL;DR
Context
40+ tools consolidated under one org, but no shared understanding of how builders actually work across them.
Research
18 interviews across 7 orgs, following builders through their full development cycle.
Insights
Three systemic themes: information trust, dependency complexity, and tooling fragility.
Influence
Flywheel and workflow artifacts reframed org thinking. Findings sparked JTBD studies and workstream model.
Reflection
First major research effort at Amazon. Domain complexity taught me the value of embedded technical partners in synthesis.
This case study contains confidential work from Amazon. Please enter the password to continue, or reach out to request access.