<aside> 💡 TL;DR - We’re introducing a prioritization framework that will help squads prioritize operational and usability concerns. We’re making a few adjustments to squads to ensure there are folks assigned to building the nest across every part of our products.

</aside>

What is this?

An analogy! Building a nest reflects the careful and secure construction of each layer, starting with the outermost for protection and gradually adding layers for comfort and stability.

Just as a bird meticulously builds its nest, we prioritize Security, Privacy, and Compliance as the outer layer, ensuring a solid foundation before progressing to Reliability, Performance, Cost, Usability, and beyond.

Is this different from what we do today?

It is. Our Engineering/Product/Design org today is oriented around the egg in the nest: value and growth.

• Value = creating new customer value (e.g. introducing warehouse sync so customers find us more valuable)
• Growth = driving more customers to a feature or product (e.g. adding warehouse sync to our Setup Guide to make it easier to discover)

We are changing that orientation to prioritize the outside of our nest, instead:

1. Security, Privacy, and Compliance
2. Reliability
3. Performance
4. Cost
5. Usability
6. Value
7. Growth

In other words, if our product isn’t meeting security, reliability, performance, cost-effectiveness, or usability standards, we make it so before prioritizing our value or growth goals.

Why now?

The good news: our business has been so successful that we’ve pushed our product to its limits!