Prioritization

A systematic and objective way to choose the ideas to test and build using evidence and other factors.

Don’t Let Hype Run Your Product

Observing tech companies you may notice a broad, disturbing phenomenon: everyone’s hard at work “selling” their product ideas — stakeholders and engineers are selling to product managers, product managers are selling to management, and management is selling to everyone (just listen attentively in the next all-hands meeting). As a product manager I too had to

Don’t Let Hype Run Your Product Read More »

Your Customers Are Not Always Right

When talking to product managers, company leaders, and customer-facing folk, a common belief surfaces: if enough customers (b2c), or an important customer (b2b) ask for something, then we should build it. This axiom is reflected in prioritization discussions as well as in many product management tools that rank ideas by “customer votes”.  Customer feedback, whether it

Your Customers Are Not Always Right Read More »

Enough With Must-Have Features

Here’s a sentence that always fills me with dread: “We plan to adopt this new approach, just as soon as we launch these must-have features.”  The must-have feature list (AKA catch-up features) has become my nemesis—it’s forever standing in the way of progress. Usually it’s a laundry list of things copied from leading competitors, from

Enough With Must-Have Features Read More »

Stop Obsessing Over Development Velocity, Focus on This Instead

An awful lot of effort is going these days into boosting product teams’ productivity: getting them to burn those story points faster, deliver the planned scope in every sprint and cycle, and generally ship more stuff, faster. The term “development velocity” is often thrown around by executives, but what they’re actually aiming for is upping

Stop Obsessing Over Development Velocity, Focus on This Instead Read More »