Kassen Qian

The Think It stage ends when management and the squad jointly believe that this product is worth building.

Features work as a management control because they manifest in the final product, and their relationship to programmer-hours is about as close to linear as you’re going to get.

1. Know Your Team's Dunbar Number : Building real relationships both broadly and deeply within the company while not overextending. Engineers should have a keen and current understanding of not only what the work is, but also the decisions behind each product feature. Context is king for cross-functional teams.

6. Always Be Grooming New Leaders: Articulate the mission early in candidate interviews. Hire listeners that display intellectual curiosity. Offer high-performing PMs opportunities to onboard others.

Another thing is a sense of urgency. The company is especially dedicated to moving very, very fast .

Most PR/FAQs are rejected, and the ones that pass often generate further questions that need to be answered. This is a feature, not a bug. Spending time up front to think through all the details of a product preserves your company's resources to build products that will yield the highest impact for customers and the business.

Another one of the biggest benefits of a written PR/FAQ is that it enables the team to truly understand the specific constraints and problems that would prevent a new product idea from being viable and aligning on them.