The way we think about Product.

• Build workflows, not features: Customers aren't concerned with features; they care about the outcomes that impact their business.
• Reduce the scope, and increase quality: Quality yields long-term benefits. This requires a concentrated focus on a limited number of topics. Stop starting, start finishing.
• Make decisions informed by data, but not solely based on data: Data provides valuable insight, but won’t tell you what to build next. Combine it with a deep qualitative understanding of your users.
• Listen to your users, but don't obey: Users often have strong opinions about what they want next. Listen carefully to the underlying problem they're trying to solve, not just their proposed solution.
• The user is always right: Our role is to ensure our users succeed with our product. If users struggle, express frustration, or experience other issues, it means we missed something.
• Building a product is a loop: There's no such thing as a finished feature. Release it, measure its performance, learn from the feedback, and then improve upon it.
• Build as a team, incorporating diverse skills for the best results: Product, engineering, design, and customer-facing teams each bring unique perspectives to problem-solving, leading to better end results.
• Make your users feel at home: Don't reinvent the wheel; some product patterns are standard. Only create something new if the problem truly demands it.
• Build for teams & individuals: We're creating a product for teams, but each team member also uses the product for their own workflow. Consider how to enhance individual workflows, and how to add more value when switching to multiplayer mode.
• Do it with style: Design matters in a hyper-competitive world. Users often form emotional attachments to products based on their appearance.
• Onboard continuously: Onboarding isn't a one-time task—it's a continuous journey. Your job is to make your customers successful.

Oh, and that might interest you: