Design Principles

Our Values and Principles guide us, to make sure we're making decisions for the greater good of the Product and our beautiful Users.

Our Purpose

Let’s build better software, faster, and in a way more enjoyable way.

Our Vision

It’s time to build the best tools to help software teams collaborate.

Our Mission

To enable best-in-class execution  while facilitating transparent coordination.


Our Principles

We break down barriers so teams can focus on what matters – working together to create products their customers love (or at least like).

1. We sweat the details.

Design will ultimately decide if we succeed or fail as a business. As Charles and Ray Eames once said, "The details are not the details. They make the design." This quote is remarkably accurate in the context of our competitive market.

We believe that scrutinizing the little details leads us to a perceptibly higher degree of craftsmanship and quality.

2. We make it delightful.

We should always be looking for ways to make a task or a decision easier, even delightful. Those ways don’t just appear in the project scope on their own - it’s our job to add them and keep pushing until we get to something delightful.

3. We make it familiar.

For most tasks, people shouldn't need to read documentation to understand how to do it. We're building a cross-functional product that every person across the organization should feel comfortable using.

As Alan Cooper wrote, "Software should behave like a considerate human being." So we keep it simple, consistent, and familiar.

4. We find elegant solutions to every problem.

Solving 100% of the problem often means you end up over-designing and introducing unnecessary complexity. We consider solving 80%, 50%, or even 0% of the problem.

As John Maeda wrote, “The best solution is the one that creates the fewest new problems.” We take a step, measure, learn, rinse and repeat.