Decision operations guide
How to prioritize multiple projects when everything feels important
A useful priority system considers more than urgency. It should account for deadlines, dependencies, blockers, strategic importance, effort, and whether an action actually unlocks other work.
Start with outcomes, not a giant task list
Separate projects from individual actions. Define the outcome each project is trying to produce and the next concrete action that can move it forward.
Identify hard constraints
Record true deadlines, dependencies, waiting-on items, and blockers. A task that unlocks several other tasks may deserve attention before a seemingly urgent standalone item.
Compare strategic value and effort
Ask what happens if the work is delayed, what value completion creates, and how much founder or operator time it consumes. High-value low-effort actions can be useful accelerators, but important long-horizon work should not disappear simply because it is difficult.
Create an explainable next-actions queue
The final ordering should be understandable. A person should be able to see why an action is ranked above another and override the system when new information changes the decision.
Where NorthStar fits
NorthStar Decision Suite is designed around this decision-operations problem: organizing projects, deadlines, dependencies, blockers, waiting-on work, effort, and strategic importance into an explainable next-actions queue.