Solving the prioritization dilemma, by choosing what not to do

The right thing

The most important thing a team can do, is not chose what to do but what not to do. It is in the deliberate choice of choosing what your ideal customer profile is not, you know what it is. It informs the product you will build, the features you will choose, the principles you will follow, the patterns you will implement.

Stakeholder driven prioritization, is not product orientation, is definitely not product development, it is definitely not leadership.

Stop outsourcing decisions to "the market" or "the users" or "the customers", be opinonated instead of bloated. High-velocity delivery and polished agile ceremonies mean nothing if the team is executing flawlessly on irrelevant work

Deciding what comes first is easy, but deciding what does not get done at all takes executive spine.

A roadmap that has so much in parallel that nothing is visible is not a roadmap at all.

Draft, will add content later

Link back to scoping here

Smaller scopes forces everyone to think clearly about which features to actually prioritize.

High, medium and low priority

First things first, and second things not at all

Dont ever waste time on second priorities, only on the high ones. If you have high priority tasks on the left side.

By scoping solutions into phased implementatons with clear boundary conditions (what is and is not included) before we describe the solution itself, this is often done through business cases or similar documents.