liveBook · Manning

Task prioritization

As explained in Think Like a Software Engineering Manager

Prioritization is the process of ranking work or projects according to their relative importance, value, urgency, or alignment with objectives.

An engineering manager may face a full calendar, a stretched team, and several projects that all seem pressing. Task prioritization means deciding what deserves attention first—and what must wait, move to someone else, or stop. Being busy is not the same as making progress: an immediate deadline can crowd out work that matters more over time. section 14.3 section 14.5

Make the decision at the right level:

  • For your own work, distinguish urgency from importance. Use the Eisenhower Matrix to do important, urgent work now; schedule important, nonurgent work; delegate urgent, less important work; and discard work that is neither. section 14.5
  • For projects, establish feasibility before ranking a new project against other planned work. Make its place in the company’s priorities clear, especially when teams depend on one another. section 10.1.2
  • For requirements, weigh customer effects, technical complexity, and operational-excellence goals. Discuss trade-offs with product and engineering partners rather than treating either set of needs as automatically dominant. section 12.4

When another urgent request arrives

Suppose your team is already stretched and a manager asks for immediate help on a new task. Compare the request with existing commitments before agreeing. Explain what would slip, consider help from another team, and tell stakeholders about any timeline changes. Pushback is a way to protect the most important work, not simply to refuse help. section 14.2.4

Revisit priorities when circumstances change. After a departure, balance workloads, reprioritize tasks, and communicate the plan to the remaining team. If shared infrastructure supports several product teams, company-wide project priorities can clarify which dependency takes precedence. At the personal level, a concrete to-do list and protected focus time help turn decisions into time spent on the chosen work. section 8.3 section 8.3.1 section 9.1.1 section 14.2.1

Check whether your time reflects your priorities. Estimate time spent in each Eisenhower Matrix category at day’s end, or record work in 30-minute intervals for a more detailed view. Look for too much reactive work, tasks that should be delegated, and work that should be dropped; protect more time for important, nonurgent goals. section 14.3.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides project-ranking guidance, requirement criteria, Eisenhower Matrix actions, and time-review methods; does not prescribe a single scoring formula.
Examples
Uses a stretched team facing another urgent request, competing project investments, and a review of time spent across Eisenhower Matrix categories.
What it assumes
Teaches the difference between urgent and important tasks before applying the Eisenhower Matrix; assumes no prior management framework.
What you can do after
Practice/perform prioritization by ranking commitments, communicating trade-offs, and rebalancing time toward important work.
How it connects
Links prioritization to project portfolio management, cross-functional dependencies, operational excellence, delegation, and time management.

Also explained in

Compare how 5 books explain task prioritization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.