A team lead’s scarcest resource is not engineering hours - it is attention. Poor prioritization creates thrash: half-finished projects, context switching, and a culture of urgency theater. Strong leads make trade-offs explicit and defensible.
Prioritize with a shared model
- Impact: user value, revenue risk, reliability, learning.
- Urgency: real deadlines vs. artificial pressure.
- Confidence: how sure are we about the problem and solution?
- Cost of delay: what breaks if we wait two weeks?
- Team health: will this push people into chronic overtime?
Decision hygiene
Not every decision deserves consensus. Use a lightweight RACI or DACI. Classify decisions as reversible (move fast) vs. irreversible (slow down). Write Architecture Decision Records for choices that will be re-litigated later.
- Frame the decision in one sentence.
- List constraints and non-goals.
- Capture options and discarded alternatives.
- Record the decision, owner, and revisit date.
- Communicate widely enough that people stop guessing.
Say no without burning trust
“No” is a leadership tool. Soften it with alternatives: later, smaller, different owner, or a clear experiment. Explain the capacity math. Invite the requester to help deprioritize something else if their item must win.
A roadmap with twenty P0s is not ambitious. It is a refusal to lead.
Capacity math people can see
Priority fights end faster when capacity is visible. Estimate in engineer-days, subtract meeting and support tax, then show what fits. If leadership wants more, they must name what drops. Hidden overload is how roadmaps become fiction.
- Write available days for the next two weeks, not hope.
- Separate committed work from stretch bets.
- Track WIP age so thrash shows up early.
- Re-plan when a P0 arrives; do not pretend time is elastic.
Decision journal for leads
Keep a short personal log: decision, options, what you chose, what you expected. Review monthly. You will spot patterns (speed bias, people-pleasing, over-engineering) faster than any 360 review.
- Capture the one-sentence decision.
- Note the top risk you accepted.
- Set a revisit date.
- Write what would change your mind.
If you can reverse the choice in a week with low cost, decide today. If the choice locks a public API, a hire, or a migration, slow down and write it down.