Continuous Deployment

Case Study: Maze

For our next case study, we’ll look at Maze, a user research company that began its journey with continuous deployment during its startup phase. Atte Huhtakangas (engineering manager) and Maarten Ackermans (staff engineer) will walk us through their journey with the practice.

Maze’s Context

Maze is a user research platform that makes products work for people. Maze empowers companies to build the right products more quickly by making user insights available at the speed of product development. Built for ease of use, Maze allows researchers, designers, and product managers to collect and share user insights when they’re needed most, putting them at the center of every decision.

We have around 100 employees, 35 of whom are spread over seven teams in engineering.

We are members of the Developer Experience team and part of the Platform department. Our primary responsibility is to maintain Maze’s code repositories, developer tooling, and the continuous integration/continuous delivery (CI/CD) pipeline. By doing so, we aim to improve our developers’ experience and productivity, ensuring that they have the necessary tools and resources to deliver high-quality products.

Adoption of Continuous Deployment at Maze

For years, we considered continuous deployment the holy grail, which we would achieve “someday.” However, we never quite seemed able to prioritize the work needed to get there. The deployment pipeline worked well enough for our needs at the time.

The transition ...