Kassen Qian

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.

Good product managers think about the story they want written by the press. Bad product managers think about covering every feature and being really technically accurate with the press.

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.

I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: those who need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it.

Good product managers know the market, the product, the product line and the competition extremely well and operate from a strong basis of knowledge and confidence. Bad product managers have lots of excuses. Once bad product managers fail, they point out that they predicted they would fail.

The absence of one or more is almost certainly correlated with weak product organizations.

The flow: Think It = figure out what type of product we are building and why. Build It = create a minimum viable product that is ready for real users. Ship It = gradually roll out to 100% of all users, while measuring and improving. Tweak It = Continuously improve the product. This isn't really an end state; the product stays in Tweak It until it... See more

1. The Role of Technology: in strong product companies, technology is not an expense, it is the business.