Limits to prioritization
Joe, after several days of writing, came to me with a written proposal for a project, IVORY SNOW. Joe has carefully filled the proposal template: the proposal describes a problem, and the proposed solution; it considers alternative solutions and shows why they’re inferior; it lists work required and an effort estimate; it has a RACI, et cetera. I thanked Joe’s for his proposal, and read it carefully. I looked for negative side-effects of IVORY SNOW, but Joe has addressed those. I did an impact/effort analysis, and the impact of IVORY SNOW ($1M revenue) seems much greater than the effort required ($10K in costs). The proposal passed all our analysis tools with flying colors, so I accepted the proposal, and Joe began work on project IVORY SNOW.
What’s wrong with this common picture? I didn’t consider all the other projects Joe could have worked on instead! The cost of IVORY SNOW is not just Joe’s salary; it’s also the foregone revenue I could have got from Joe working on FLYING STALLION! This cost is called “opportunity cost”, and it can seriously outweigh the explicit costs.
To show opportunity cost, the only tool I know of is a prioritized backlog. Here’s an example:
|Priority||Project||Revenue estimate||Explicit cost estimate|
When Joe presented IVORY SNOW, what I should have done is insert it into this backlog. This would have made it clear that FLYING STALLION is the right thing for Joe to work on. The prioritized backlog seems like the miracle cure to invisible opportunity cost. So why didn’t I use the backlog? There are, unfortunately, many reasons!
One common we forget the backlog is focus. We’re taught that focus is a virtue. But focus can also lead to myopia! By considering IVORY SNOW in such detail, I became unaware of other things we could be doing.
Another limit to prioritization is incomparability. These
One fundamental limit is centralization. To prioritize everything, you need a single backlog. This backlog is a bottleneck. Its owner, such as a Product Manager, is a bottleneck.
Another fundamental limit is multiple skills. Joe is competent to work on IVORY SNOW or FLYING STALLION. Jane is competent to work on IVORY SNOW or ROWDY TRUMPET.
A common work-around is multiple backlogs: the PM has one, the team has another, and each contributor has their own. The trade-off is that items from different backlogs are incomparable.
Another fundamental limit to prioritization is incompleteness. I do not have the imagination to list everything I could be doing!
- Multiple backlogs.
- We use systems that hide the backlog. You might use quarterly OKRs (Objectives and Key Results) at work. These tools omit the non-objectives.
Signs you’re not considering opportunity cost, and not doing enough prioritization:
- You answer “yes” or “no”. Usually, the answer should be “not yet”.
- You say “yes” too much. Considering opportunity cost, you should only be saying “yes” to one thing.
- You’re always very busy.
Limits to prioritization. Centralization. Everything has to go through one backlog.
More by Jim
- Smear phishing: a new Android vulnerability
- A probabilistic pub quiz for nerds
- Time is running out to catch COVID-19
- The inception bar: a new phishing method
- The hacker hype cycle
- Project C-43: the lost origins of asymmetric crypto
- How Hacker News stays interesting
- My parents are Flat-Earthers
- The dots do matter: how to scam a Gmail user
- The sorry state of OpenSSL usability
- I hate telephones
- The Three Ts of Time, Thought and Typing: measuring cost on the web
- Granddad died today
- Your syntax highlighter is wrong
Tagged . All content copyright James Fisher 2019. This post is not associated with my employer. Found an error? Edit this page.