Skip to main content
Welcome, Soft Skills students — I’m Michael Forrester. This lesson covers the starting point for effective time management and capacity planning: prioritization. Structuring your time and focus is essential. To make your work visible and reliable, you must track it, evaluate it, and know how to respond when new requests arrive while you already have a queue. Structuring effort vs. scattering effort: without a deliberate approach, you can produce lots of activity while still working on the wrong things — misaligned with client needs or the goals of those who manage those clients.
A presentation slide titled "Prioritization – Why?" that compares "Structured Efforts" (a grouped team icon inside one circle) with "Scattered Efforts" (separate individual icons in multiple circles). A small inset video of a person speaking appears in the bottom-right.

​
What prioritization is (and what it isn’t)

Prioritization is the practice of balancing maximum value with the shortest reasonable time to deliver that value. This does not always mean choosing the quickest tasks — sometimes a larger item with higher value is the correct early focus. The practical approach is to:
  • Break large items into consumable chunks (aim for units you can complete in a day or two).
  • Balance impact (value) against effort and time.
  • Iterate on estimates as you get feedback from completed work.
A presentation slide titled "Understanding Prioritization" showing a seesaw/balance diagram comparing four tasks (Task 01–Task 04) by task value on the left and effort/time on the right. Colored horizontal bars with percentage indicators and icons illustrate high value & impact versus high effort & time, and a presenter appears in the bottom-right corner.
Estimating effort is iterative. For example: if you plan to write a book, break it into chapters, outlines, and publishing steps. If a chapter takes three days, adjust your cadence (e.g., target half a chapter every 1–2 days). Compare estimates to actuals and refine your future planning. Two practical strategies useful for balancing value and effort are: Weighted Shortest Job First (WSJF) and the Pareto (80/20) principle. Other techniques (FIFO, Eisenhower Matrix) can also be helpful depending on context.

​
Weighted Shortest Job First (WSJF)

WSJF gives a repeatable, comparative approach to ordering work: WSJF = (Business Value + Time Criticality) / Job Size
  • Business Value: how much benefit completing the item brings.
  • Time Criticality: how urgent or deadline-sensitive the item is.
  • Job Size: the relative effort required.
A presentation slide explaining the Weighted Shortest Job First (WSJF) prioritization formula: WSJF = (Business Value + Time Criticality) / Job Size, with example scores for Features A, B, and C. A small video thumbnail of the presenter appears in the bottom-right.
Example calculations:
Higher WSJF values indicate higher priority. From the example above, prioritize Feature C, then Feature A, then Feature B. Recalculate when business value or time criticality changes. Notes on scoring:
  • Use a consistent rubric across the team. Define what each numeric value means (for example, Time Criticality = 3 might mean “deadline within one week”).
  • Express Job Size using time ranges or a relative scale (many teams use Fibonacci numbers to reduce false precision).
  • Treat estimates as approximations that improve with feedback.
When you estimate, treat the numbers as a consistent rubric, not absolute truth. Revisit estimates frequently and adjust based on actuals to improve future planning.

​
Pareto (80/20)

Pareto is less mathematical and more judgment-based: roughly 80% of outcomes come from 20% of efforts. Identify the small set of tasks that will move the needle most and focus your attention there.
A presentation slide titled "Strategies for Prioritization — Pareto" with a bar chart showing task percentages (20%, 40%, 60%, 70%, 80%) illustrating the 80/20 rule. A caption explains that roughly 80% of results come from 20% of efforts, and a small presenter video appears in the bottom-right.
Use Pareto when a few clear items drive most results (revenue, reputation, or customer impact). It’s fast and effective when outcomes are concentrated in a small number of tasks.

​
Choosing the right method

Try different approaches and adopt what fits your team and workflow. The table below summarizes strengths and trade-offs.

​
Adapting to rapidly changing inputs

Priorities change — incidents happen and business needs shift. Adopt a mindset for a rapidly changing reality (RCR) and ensure changes are communicated clearly and immediately.
A presentation slide titled "Adapting to Rapidly Changing Inputs" shows a horizontal bar chart with Task 01 as a long orange bar and Tasks 02–05 as shorter gray bars. A gray footer reads "Stay aligned while adapting to current realities!" and a small video thumbnail of a person waving appears in the bottom-right.
When you change priorities:
  • Notify stakeholders immediately.
  • If you demote someone else’s agreed task, engage affected parties to renegotiate. Silent reprioritization breaks agreements and erodes trust.
If you change an agreed priority and don’t communicate it, you effectively break your agreement with stakeholders — always notify and, when appropriate, involve them in the decision.

​
Separate interrupt-driven work from project work

Work generally falls into two buckets:
  • Interrupt-driven work: support tickets, incidents, ad hoc requests.
  • Project or deep-focus work: planned feature development, research, or major deliverables.
Interrupts force context switching and slow deep work. If a team spends more than ~20–30% of its time on interrupts, project timelines will slip. Protect focus by time-boxing:
  • Example rotational schedule: 90 minutes for interrupts, 90 minutes for project work; repeat and adjust to fit SLAs and team needs.
  • If continuous coverage is required, rotate the interrupt role to avoid burnout.

​
Visualize your work

Make work visible using a simple board (To Do → In Progress → Completed, with an optional Backlog). Visual boards reduce context switching and help stakeholders see priorities and progress.
A presentation slide titled "The Power of Visualizing Work" showing two colored workflow bars for Stage 01 and Stage 02 mapped across "To Do," "In Progress," and "Completed" columns with user icons at the start. A gray footer reads "In DevOps, visualizing work enhances understanding and management," and a small video overlay of a person appears in the bottom-right.
A simple workflow:
  • Pull the top-priority item into “In Progress.”
  • Focus on one item (or a very small number) until it’s done.
  • Move it to “Completed” and pull the next item.
Visualization makes it easier to show what you’re doing and why, and it helps stakeholders understand when and why priorities change.

​
How prioritization ties into time management and capacity planning

These three disciplines are tightly connected:
  • Prioritization: What to do first.
  • Time Management: When you will work on it (time-boxing).
  • Capacity Planning: Who will do the work.
A presentation slide showing a three-circle Venn diagram labeled Prioritization, Time Management, and Capacity Planning with small icons in each circle. A small video feed of the presenter appears in the bottom-right corner.
For teams, ask these three questions for each piece of work:
  • What are we doing?
  • When will we work on it?
  • Who will do it?
These questions help scope effort and set realistic commitments.

​
Summary

  • Prioritize work to maximize value for the least reasonable effort.
  • Use WSJF, Pareto (80/20), FIFO, or the Eisenhower Matrix depending on your context.
  • Define consistent rubrics for Business Value, Time Criticality, and Job Size; iterate on estimates using feedback.
  • Communicate priority changes immediately to stakeholders.
  • Separate interrupt-driven and project work to reduce context switching and missed deadlines.
  • Visualize work to make priorities and progress visible.
  • Combine prioritization with time management and capacity planning to set achievable plans.
Thanks for reading.

Watch Video