Early in my career I treated every assignment the same. Monthly reports sat beside long-term improvement initiatives, while unexpected requests appeared throughout the day demanding immediate attention. Everything became one large, competing list of priorities. It wasn't long before important work began losing out to urgent work.
Eventually I found a much simpler way to think about my workload.
Almost everything I do falls into one of three categories:
- Routine Work
- Ad Hoc Work
- Project Work
Once I began organizing my work this way, prioritizing became easier, planning became more realistic, and it became much clearer where my time was actually going.
Routine Work
Routine work is the foundation of the job. These are the recurring responsibilities that keep the organization informed and operating smoothly.
Examples include:
- Monthly reliability reports
- KPI dashboards
- Trend monitoring
- Data validation
- Scheduled meetings
- Regular data extracts
Because these activities repeat, they are ideal candidates for standardization and automation. The less mental energy spent remembering how to perform routine work, the more energy remains for solving problems.
Routine work should become predictable.
Ad Hoc Work
No analyst escapes unexpected requests.
An executive needs numbers for tomorrow's meeting. Operations discovers an abnormal trend that needs immediate investigation. A customer wants an answer before the end of the day.
These requests rarely arrive at convenient times.
Rather than allowing them to derail everything else, I treat them as their own category. This helps me acknowledge their urgency without losing sight of other commitments.
Keeping ad hoc work separate also provides something valuable that many people overlook—it creates a record of interruptions. Looking back over several months often reveals just how much time is consumed by unplanned work, information that can be useful when discussing staffing, priorities, or workload.
Project Work
Project work is where long-term improvements happen.
These are the initiatives that make next year's work easier than this year's.
Examples include:
- Building new dashboards
- Developing automation
- Improving data quality
- Creating new analytical processes
- Designing reporting standards
- Performing deep investigations into recurring problems
Unlike routine work, projects rarely have immediate deadlines screaming for attention. Because of that, they're often the first thing postponed when the day becomes busy.
Ironically, these are usually the activities that create the greatest long-term value.
If you never protect time for project work, you'll spend your career maintaining today's processes instead of improving tomorrow's.
Seeing the Whole Picture
Separating work into these three categories creates visibility.
Instead of asking, "Why am I so busy?", you can begin asking better questions:
- Is routine work consuming too much time?
- Are ad hoc requests increasing?
- Are projects making steady progress?
- What work could be automated?
- What should stop altogether?
Those questions often lead to improvements that would never be obvious from a single undifferentiated task list.
Tracking the Work
The tracking system doesn't have to be sophisticated.
A notebook, spreadsheet, OneNote page, Kanban board, or project management tool all work equally well. The important part isn't the software—it's consistently identifying which type of work each task belongs to.
Over time you'll begin to recognize patterns.
You may discover that most interruptions arrive on Mondays, that certain reports are candidates for automation, or that projects consistently lose momentum whenever ad hoc work increases.
Those observations become opportunities for improvement.
Final Thoughts
Many productivity systems focus on how to organize tasks.
I've found that the bigger improvement comes from first understanding what kind of work you're actually doing.
Routine work keeps the business running.
Ad hoc work keeps the business responsive.
Project work makes the business better.
When these three types of work compete on the same list, the urgent usually wins.
When they're managed separately, each receives the attention it deserves.
Sometimes the simplest frameworks turn out to be the most useful.