Kassen Qian

Side benefit of this method: by forcing multiple iterations on a PR/FAQ, you implicitly gain the approval of everyone who reviews it, demands iterations on it, and subsequently approves it. This then means that when a product passes the PR/FAQ process but subsequently fails in the market, people are more likely to take collective responsibility.

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

Problem 1: Meeting efficiency - Having every team present their updates also wasn't going to work.

Communication & Visibility: You build relationships that help the team get things done. You ensure the product’s story is told, and understood, internally and externally. You create collateral that can be leveraged by GTM teams.

Basic structures cannot be composed into larger structures unless they themselves are internally consistent, and so the creation of software, just like any artifact of language, is naturally incremental.Software is a very verbose, very precise incantation of how an information system ought to behave.

The biggest risk is building the wrong product - a product that doesn’t delight our users, or doesn’t improve success metrics such as user acquisition, user retention, etc. We call this “product risk". The 4-stage model helps us drive down risk and get products out the door quickly.