WisTex

One challenge that I have struggled with are tasks that aren't quite "must do," but are more than "should do." This actually happens a lot when you are creating something new, such as a website or app. You wind up with items that you think should be part of the project, and would be very very beneficial, but aren't actually required.

For example, let's say you are building a project management app. To create a minimal viable product (MVP), there are certain things that you must have. Those are "must do." And you have features that would be nice to have. Those are "should do" or even "could do." But there are certain

I have been developing my own version of ABCDEF+ priorities combined with scheduling to achieve something similar. Thanks to this post, I have actually made changes to the definitions of each priority level, which has clarified things greatly.

If you define the priority levels in terms of Must Do Immediately (A), Must Do (B), Should Do (C or D), Could Do (E or F), and Someday/Paused (P), and then combine that with scheduling, you can get the important things to float to the top by sorting by priority first, then by scheduled or due date. If you hide everything that cannot be done now (usually by hiding everything with a start date after