Classifying tasks based on timeline of impact
8 March 2025·budding·Sabiqul Hoque
This is simply the concept of categorising tasks based off the impact they would have within a certain time period. Some changes. For example:
- A tasks
- expected to yield significant benefits over a 5-year timer span and beyond; including tasks that might yield benefits over a shorter period of time but should be expected to have ongoing impact 5+ years from now.
- B tasks
- expected to yield benefits over a 2 year timespan or less. The general expectation is that the benefits will be fully realised within the first 2 years and there won’t be much additional benefit beyond that.
- C tasks
- expected to make a difference only in the timespan of 90 days or less. Most likely won’t even remember the task or see evidence of its benefits beyond that time. This includes routine actions like answering email, paying bills & returning phone calls.
Follow On Thoughts
Can be easily achieved using the org‑priority feature in Emacs. Alternatively can just use tags. Additionally, its a good idea to review all the tasks completed in a day and categorise them accordingly to see where most of your time is going.
Personally, I prefer just using priority in a more general sense and occasionally using this method as a fall back.
Principles
The main benefit of this, is to actually apply the 50–30–20 Rule. Unfortunately, that is the hardest part.
Connected Ideas (Similar / Opposing Ideas)
- Prioritisation
- Task Management
Backlinks
50–30–20 Rule
Connected Ideas (Similar / Opposing Ideas)
Prioritisation Classifying tasks based of timeline of impact Task Management, Scheduling
Sources
Cite this note
@online{hoque2025classifying,
author = {Sabiqul Hoque},
title = {Classifying tasks based on timeline of impact},
year = {2025},
url = {https://sabicool.github.io/Braindump/notes/20250308225655-classifying_tasks_based_of_timeline_of_impact.html},
organization = {Braindump}
}