Chapter 4: Finite Time
tsep time-management prioritization resource-management saying-no project-selection
Status: Notes complete
Overview
Staff engineers have more potential work than they can ever do. Unlike junior engineers who are assigned tasks and execute them, staff engineers must choose what to work on — and this selection is itself one of the most important parts of the job. Choosing wrong means spending a year on something that doesn’t matter; choosing right means having outsized organizational impact.
Chapter 4 provides a framework for thinking about what to work on and when to say no. The central metaphor is the Sims dashboard: just as The Sims game tracks character wellbeing across multiple dimensions simultaneously, staff engineers must track five distinct resource dimensions when evaluating projects. Ignoring any one of them leads to poor decisions.
Core Concepts
Five resources: The five dimensions a staff engineer must monitor and manage: energy, quality of life, credibility, social capital, skills.
Time graph: A visual representation of all your commitments over time, showing when existing obligations peak and when there is slack. Used to evaluate whether a new project is feasible.
Bin-packing metaphor: Work is not interchangeable — it has shape. Committing to a big project isn’t just about total hours; it’s about whether the shape of the work fits the shape of your available time.
Project sources: The different ways work arrives at a staff engineer — some given, some chosen, some created.
The Five Resources
Staff engineers must consider five dimensions when evaluating work, not just “do I have the hours for it?”
| Resource | Description | Warning signs of depletion |
|---|---|---|
| Energy | Physical and mental capacity for work | Exhaustion, difficulty focusing, dreading work |
| Quality of life | Enjoyment, satisfaction, sense of purpose | Feeling hollow, work bleeding into personal time unsustainably |
| Credibility | The trust others place in your judgment | Promising things you can’t deliver; public failures |
| Social capital | The goodwill and relationships you’ve built | Burning bridges, calling in too many favors |
| Skills | Technical and leadership abilities | Stopping learning; falling behind in domain knowledge |
Each resource can be spent, built, or depleted. Good work can build all five simultaneously — bad work depletes them. When evaluating any project, ask how it will affect each resource.
Time Graph: Visualizing Your Commitments
The time graph is a simple but powerful tool:
- The x-axis is time (weeks, months)
- A horizontal line represents a work commitment — its length is its duration, its height is the effort level
- Stack your commitments to see when you’re overcommitted and when you have slack
Key insight: it’s not just about total hours but about when they’re needed. Two projects that each need 20% of your time are fine if they have different peak periods; they’re a problem if they both peak simultaneously.
When asked to take on new work, literally draw it on your time graph. If it pushes you into the red, you have a concrete conversation starter: “I can do this, but only if we agree to deprioritize X.”
Bin-Packing: The Shape of Work
Computer science has a problem called bin-packing: given bins of fixed size and objects of varying shapes, how do you fit as much as possible? Work has shape too:
- Some work needs deep focus (architecture, writing, complex debugging) — large, uninterrupted blocks
- Some work is high-frequency, low-depth (reviews, questions, status checks) — fits between other things
- Some work is emotionally demanding and can’t be stacked with other emotional work
- Some work needs specific timing (quarterly planning, annual reviews, launch windows)
Don’t just ask “can I fit more hours in?” Ask “can I find time blocks with the right shape?”
Project Sources
Work arrives from different directions, each with different characteristics:
| Source | Description | Typical expectation |
|---|---|---|
| Invited | Manager or leader explicitly assigns you | High priority; decline at cost |
| Ask | You’re asked by peers, stakeholders, or other teams | Medium priority; relationship cost to decline |
| Idea | You initiate the work yourself | Your discretion; you own the outcome |
| Fire alarm | An urgent problem that needs your skills now | High urgency; can displace other work |
| Claiming | You take ownership of unowned work | Useful for impact; risky if under-resourced |
| Grassroots | A bottom-up initiative that needs champion support | High leverage; can be inspiring |
| Meddling | You’re inserted into work that doesn’t really need you | Usually low value; often a trap |
Meddling — jumping into work that would be fine without you — is one of the most common ways staff engineers accidentally make themselves busy while creating little value.
The Resource Questions
For each of the five resources, ask a diagnostic question when evaluating a project:
| Resource | Question to ask |
|---|---|
| Energy | Will this project energize or drain me? Can I sustain it for its expected duration? |
| Quality of life | Will I be proud of this work in a year? Does it fit with how I want to spend my working life? |
| Credibility | Am I the right person to lead this? Will success or failure be attributed to me? |
| Social capital | What relationships will I need to use or build? What goodwill will I spend? |
| Skills | Will I learn from this? Does it keep me sharp in areas I need to maintain? |
Options When a Project Is Wrong for You
When you’ve evaluated a project and concluded it’s a bad fit, you have five options:
| Option | When to use |
|---|---|
| Do it anyway | The org needs it and your other resources can absorb it |
| Compensate | Accept the project but get something else in exchange (less of another project, support resources, timeline relief) |
| Let others lead | You participate but cede the driver’s seat to someone better suited or who needs the opportunity |
| Resize | Negotiate the scope down to something that fits your resources |
| Say no | The project will deplete your resources and the org can find another way |
Saying no is genuinely hard for staff engineers who want to help. But a staff engineer who says yes to everything becomes an unreliable bottleneck — they commit to more than they deliver, which damages credibility more than declining would have.
Key Takeaways
- Choosing what to work on is one of the most important parts of the staff engineer job.
- The five resources — energy, quality of life, credibility, social capital, skills — must all be considered when evaluating projects.
- The time graph makes overcommitment visible before it becomes a problem.
- Work has shape (depth, frequency, timing), not just volume — check shape fit, not just total hours.
- Projects arrive from many sources; meddling is a trap that creates busyness without value.
- When a project is wrong, you have five options: do it, compensate, let others lead, resize, or say no.
- Saying no preserves credibility; overcommitting destroys it.
Related Resources
- ch05-leading-big-projects — Once you’ve selected the right project, how to lead it
- ch06-why-have-we-stopped — Chapter 6 references the time graph when cautioning against too many side quests
- ch09-whats-next — Career-scale version of the resource questions