Archive

Book an hour on Thursday or Friday for the team to meet. Don't have an agenda, don't try to lead the discussion, and don't collect action items. Simply talk informally about whatever comes up, like a Quaker meeting.

The classic problem with MoSCoW prioritization is that you end up with too many Must Have items, and the PM gets stuck, unable to prioritize them.

Context Most product leaders have packed calendars, and this can mean it's hard to find time for quick, spontaneous conversations - especially with other product people who are equally busy. And as organizations scale, it's harder to rely on scheduled checkins to connect with all of

Use a User Story Map as a negotiation tool with the team to figure out what your product increments will be.

Form product councils for each of your main product areas. Hold a monthly, 90 minute meeting with 5-20 stakeholders where you share progress, present priorities, get feedback, and build buy-in all at once.

Does your team ignore written messages? Get in the habit of making quick videos, not more than 7 minutes.

The roadmap is full of dates with unknown origins. Engineering is complaining about shifting priorities. PMs are surprised by and complaining about dependencies. PMs are barely keeping up with sprint planning and not providing their teams with a mid- or long-term view.

There is no single set of strategic documents. The PMs are struggling to prioritize, or make prioritization decisions in conflict with each other.

You have a lot of offerings in your product portfolio and your spending on them is based on a mixture of tradition, emotion, and advocacy.

You want to roll out a change, but that change involves other humans who have other things in mind.

The ideal context for this play is a financially savvy company struggling with product prioritization conversations that are emotional, anecdote-driven, and intuitive.