Escaping the Build Trap: How Effective Product Management Creates Real Value
Rate it:
Open Preview
Kindle Notes & Highlights
5%
Flag icon
The build trap is when organizations become stuck measuring their success by outputs rather than outcomes. It’s when they focus more on shipping and developing features rather than on the actual value those things produce.
7%
Flag icon
Everyone is so focused on shipping more software that they lose sight of what is important: producing value for customers, hitting business goals, and innovating against competitors.
8%
Flag icon
Every feature you build and any initiative you take as a company should result in some outcome that is tied back to that business value.
8%
Flag icon
When companies do not understand their customers’ or users’ problems well, they cannot possibly define value for them. Instead of doing the work to learn this information about customers, they create a proxy that is easy to measure. “Value” becomes the quantity of features that are delivered, and, as a result, the number of features shipped becomes the primary metric of success.
9%
Flag icon
You have to get to know your customers and users, deeply understanding their needs, to determine which products and services will fulfill needs both from the customer side and the business side.
9%
Flag icon
To realize the maximum value, organizations need to have the right individuals, the right processes, the right policies, the right strategy, and the right culture.
16%
Flag icon
The real role of the product manager in the organization is to work with a team to create the right product that balances meeting business needs with solving user problems.
19%
Flag icon
“The biggest thing I’ve learned in product management is to always focus on the problem. If you anchor yourself with the why, you will be more likely to build the right thing,”
23%
Flag icon
The danger is when a product manager is 100% operational, focusing only on the process of shipping products and not on optimizing the feature from a holistic standpoint. When they only optimize for the day-to-day execution of the team, they usually fall behind in the strategy and visioning work that is needed for the success of the features.