Product Development Philosophy


We rally around the goal of empowering storytellers to do their best work. We strive to improve our products through regular iteration and experimentation. We ascribe to the following core philosophy in order to achieve these goals.

We Iterate

We build lean and fast in order to get early feedback and then repeat. Constant iteration and feedback is the engine that drives the company forward. We value iteration over perfection.

Prototyping is a means of product discovery

Our approach to product development starts with rapid prototyping that aims to deliver a high fidelity user experience that we can use to test our assumptions and vet with customers. It's a creative process that is highly iterative.

Building prototypes is on the critical path of product discovery. We rapidly prototype in order to learn how the product will live and breathe. Prototypes are the real deal. We expect our prototypes to become products that thousands of clients will use. As we prototype, we do so with an eye toward scalable architecture and best practices.

Emotion plays a key role

It matters to us how our product makes us feel. We engage with it on an emotional level because we know our customers will do the same. How the product connects with us emotionally is deeply important at every stage of development

Code is not king

We know that code is malleable and may be transient. The product drives the code, not the other way around. As the product evolves our code changes accordingly. We iterate and re-write portions of the codebase fluidly when the product requires it.

Because young features change frequently we limit the cost of that change by limiting our commitment in code. We commit to the feature in code when we've committed to the feature in the product.

Keep It High Level

We believe that the cost of change increases the further down the stack you go. So, we prototype at the highest level possible make as few commitments to the lower layers of the stack as possible. As an example, it's highly unlikely that we would ever implement database schemas during early phases of development. In fact, we may prefer to not integrate with API at early stages either. Instead we may prefer mock API's or static data.

This is in our soul

Creating a product is first and foremost a creative exercise. We are breathing life into something new. We view product creation as a fundamental means of human expression. It is in our soul to create.