6 ms·
It feels like this kind of dismisses prioritization. But that's only if you're not doing proper prioritization. In reality prioritization is important, but it
by Ozzie_osman 4y ago
It feels like this kind of dismisses prioritization. But that's only if you're not doing proper prioritization.
In reality prioritization is important, but it is affected by dependencies, effort, and "inspiration."
Dependencies: obviously if a P0 task requires a P2 task to complete, the latter is now a P0.
Effort: if a P2 can be done in an hour, it's probably higher impact than a "P0" that will take a quarter. So really what you need is some cost/benefit framework or RICE framework.
Inspiration: sometimes, someone on the team will just see a path to getting something done. They will be irrationally excited about it. You can't prioritize purely based on inspiration of the moment, but I've found leaving some flexibility in the system for capturing that inspiration can be very powerful.
- tbrownaw 4y ago> Effort: if a P2 can be done in an hour, it's probably higher impact than a "P0" that will take a quarter. A "P0" that far out sounds to me like something with a tight (calendar vs estimated effort) deadline and some sort of fairly serious contractual or regulatory penalties for missing it.
- xyzzy123 4y agoI have trouble parsing the idea of a P0 that takes a quarter, I guess I'm too stuck in Pn as "incident" rather than planned work. Indelibly etched in my mind is that P0 is like "patient is not breathing" / "everything else is pointless until we fix this".
- tbrownaw 4y agoYeah, it's not the terminology I'd expect to see, but I think it's at least somewhat comprehensible even though not really correct.