📎 Webclip
Prioritization systems
The page argues that small projects can be managed with simple task lists, but large, long-lived projects need explicit prioritization because estimates get harder and technical debt matters more. It presents four systems that help choose what to work on and when to stop.
Reading notes#
- Use an impact-versus-effort frame to look for tasks with the smallest effort and the biggest user impact.
- If the effort is hard to estimate, try the task for a fixed amount of time and stop if it still raises the same questions.
- Define project design principles, such as keeping interactions fast, and set aside work that would break them.
- After a product is in production, use user behavior and simple database queries to decide what to improve or fix.
