Discussion about this post

User's avatar
James Thornton's avatar

Rick, this is solid. I've been running a version of this for my task backlog at (EV divided by effort hours, sort, pick the top 3). Your framework is better because it forces you to decompose that single "value" number into Impact, Reach, and Recurring. Harder to lie to yourself when you have to score each one...

The inverted effort scale is smart; I haven't seen anyone else do that. Your AI footnote on effort drift is also interesting. I'm using an agentic coding assistant that turned a 2-week report build into a 3-hour conversation last week. If I hadn't re-scored effort, that task would still be sitting at the bottom of my list.

Already integrated this into my Friday review workflow. Appreciate the framework, neighbor.

No posts

Ready for more?