Focused and deliberate work is vital to our success. Which is why we align ourselves with cycles of work.

We know that there are endless ways to do efficient work together. So we iterate a lot on how we work. The following is a living documentation of our product development process. It should be updated when we change it.

Our Product Development process:

TL;DR;

There are no cycles (i.e. no fixed product development cycles). Instead we pull from our Pitch stack as needed. Each pitch has an “appetite” for how much time we want to spend on it, which we treat as a hard stop. Appetite varies between pitches but is generally less than 4 weeks and commonly quite shorter. Cooldown is flexible but max 5 working days per team member between working on pitches. That means not everyone will be in the same place in a “cycle” at the same time.

Roles

Designer: Designs a selected Pitch in accordance with our design guidelines

Developer: Collaborates with designer and other developers to deliver the changes suggested in the Pitch

Owner (decided on pitch kickoff): Makes sure everyone are aware of the deliveries, including current users, prospects, and the wider community

Gardener (CTO / Head of Product): Makes sure that the Pitch stack always has 3 items and makes sure that the items added to the Cooldown Inbox are prioritized.

First Responder: Makes sure all incoming support requests and questions in the community are responded to, supplies new tasks to the Cooldown Inbox for the Gardener to prioritize

Process

Pitch Shaping