PM Brainfood #101

Written by Published in News and truths
PM Brainfood

Biweekly we select for you the best articles in product management.

Enjoy and have a PRODUCTive week!

Interesting Reads


1. How Product Can (and Can’t) Speed Up Development
It’s not Product’s role to wring more code out of the maker team (developers + designers + CloudOps + test engineering + tech docs) or to restructure the development process. It is Product’s job to get the most customer value out of that process and to push for healthy product economics. Let’s unpack things that product managers shouldn’t do, can do to deliver more value, and recognition that our maker teams are craftspeople rather than robots. (Rich Mironov)

2. Seven Product Management Principles
The constant evolution of product management means that oftentimes, what is best practice today might be outdated approach tomorrow. Product leader Jens-Fabian Goetzmann writes, “Instead of chasing a changing understanding of best practices, uncover the principles underlying these practices. These principles are higher level than the practices and also more stable over time. You can then implement these ‘best principles,’ not the best practices themselves, for yourself, your team, and your larger organization, in a way that fits your specific context. In this article, I will share seven principles for product management and leadership and some of their implications.” (Jens-Fabian Goetzmann)

3. How to Prioritize Features and Projects: Here’s the Ultimate List of Prioritization Frameworks
As the title suggests, this is an exhaustive list of prioritization frameworks with overview, highlights, and resource links. This is meant to be a scannable, inspirational resource for managers in product or anywhere. (Product Coalition)

Super Early Bird tickets for PMF Europe 2021 (13-14th September) are on sale now. Get them while they last!

4. For Better Products, Start with a Problem Statement
A problem statement is useless if it’s not written correctly. It isn’t a product requirements document (PRD) or a specification (spec). A problem statement focuses on what the customer needs, not what you think the solution should be. This makes it hard and counterintuitive, because as humans, we’re wired to think in solutions. So what should your problem statement include, and how can you write a great one? (Intercom)

5. Four Fundamental Mistakes You Are Making With Product OKRs
OKRs are an amazing tool to drive business success. Starting with OKRs is easy. Doing it right is not necessarily so, and especially with product OKRs that are a unique beast. Here are a few common mistakes to avoid. (Noa Ganot)

Best wishes,
The Product Management Festival Team

Leave a Reply

Your email address will not be published. Required fields are marked *