Kassen Qian

Stripe has a very, very long time horizon. If you know where you’re going over time, you can reason clearly about which specific asks are one-offs vs indicative of emerging trends relevant to many users. We talk a lot about building multi-decade abstractions. That long time horizon comes from the top, and it’s in the culture.

4. Celebrate wins

Fixed time, variable scope.

Ownership: I can give you a problem statement, but you’re the one who determines what your job is. You don’t get driven around by the team; you figure out what the team needs, and you deliver that.

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.

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.

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.

The PR/FAQ process merely increases the odds that your product would succeed; it doesn’t guarantee it.