Planning pressure Imani has 47 feature requests, one planning meeting, and a leadership team that will challenge every tradeoff. If she sorts by requester, the loudest stakeholder wins. If she sorts by confidence and outcome, the roadmap becomes discussable. Now-next-later sorting Outcome fit -> evidence -> horizon Do not place work on a roadmap until you can say what outcome it supports and how confident the team is in the bet. Shortcut Sort by who asked or how long it has been waiting. The review focuses on sequencing logic instead of request politics. Horizon placement is a confidence decision, not…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in