Section 02 Flashcards — Work on What Matters
flashcards selt prioritization time-management
What is “snacking” in the context of Staff engineering?
?
Snacking is easy, low-effort work that feels productive but delivers minimal organizational impact. Examples: attending every meeting out of habit, reviewing low-stakes PRs, polishing docs nobody reads. It is dangerous because it is satisfying and socially accepted, yet crowds out high-leverage work.
What is “preening” in the context of Staff engineering?
?
Preening is highly visible work that signals effort and ownership but does not move the organization forward. Example: rewriting a working service in a trendier stack without a compelling technical case. Unlike snacking, preening also erodes social capital because peers eventually notice the gap between visibility and results.
What distinguishes preening from snacking?
?
Both are low-impact, but snacking is low-visibility and satisfying while preening is high-visibility and actively consumes credibility. Snacking is a time drain; preening is a credibility drain.
What are “chasing ghosts” in Staff engineering?
?
Chasing ghosts means pursuing technically interesting work that has no real organizational need. It is a trap for technically excellent engineers who still have an appetite for novelty. A ghost project can consume months before anyone asks whether the output will ever be used.
What are “existential risks” and why should Staff engineers focus on them?
?
Existential risks are critical problems that, if unresolved, could cause serious organizational harm — a security posture one breach from compliance failure, a scaling bottleneck about to break under load, or attrition threatening a key team. Staff engineers often have the cross-organizational visibility to see these risks first and the leverage to address them. Ignoring them is a failure of role.
What is the “work only you can do” principle?
?
At any moment there is work that requires your specific combination of context, relationships, institutional memory, and technical depth — work where no one else can substitute. This is the highest-leverage use of a Staff engineer’s time and deserves priority above everything else.
Name the four finite resources Larson identifies that Staff engineers must manage.
?
- Time — hours in the week
- Energy — cognitive and emotional reserves
- Attention — capacity for deep focus
- Social capital / credibility — accumulated trust and influence
Every allocation of these resources is also a de-allocation elsewhere.
Why is attention treated as a separate resource from time?
?
Attention is the capacity for deep, focused engagement. It is depleted by context-switching, low-stakes commitments, and shallow coordination work — independently of hours spent. A Staff engineer can be busy all day yet produce no Staff-level thinking if their attention was never unprotected. Time is necessary but not sufficient.
What is Larson’s core diagnostic question for detecting snacking?
?
“Could a competent engineer two levels below me do this work just as well?” If yes, it is almost certainly snacking and should be declined, delegated, or minimized.
Why does Larson recommend writing more and talking less?
?
Written artifacts scale. A good design doc, strategy document, or ADR can influence dozens of engineers and decisions long after the equivalent meeting is forgotten. Writing also forces precision — vague expertise that survives in conversation is exposed by the blank page. Staff engineers who invest in writing compound influence over time.
What is the “bottleneck trap” for Staff engineers?
?
A Staff engineer who inserts themselves into every decision becomes a single point of failure: teams wait for their input, decisions slow, and their own high-leverage work is crowded out by coordination overhead. The remedy is to build systems (design principles, mentoring, review processes) rather than approval dependencies.
How does the bottleneck trap differ from healthy Staff-level involvement?
?
Healthy involvement: Staff engineer writes principles so teams decide independently; mentors engineers who develop judgment; reviews decisions that genuinely require their unique context.
Bottleneck: every decision is routed to the Staff engineer regardless of whether their context is actually necessary. The bottleneck is characterized by volume of involvement, not depth.
What three mechanisms reinforce snacking behavior?
?
- Completion bias — finishing small tasks feels better than incremental progress on large ambiguous ones.
- Social pressure — declining visible requests (meetings, reviews) can feel rude or disengaged.
- Uncertainty avoidance — snacks are predictable; high-leverage work is often uncomfortable and ambiguous.
What are three signs you may be preening rather than contributing?
?
- You gravitate toward projects where your contribution will be publicly recognized over projects where it will be quietly essential.
- You rewrite things that work adequately rather than solving problems with no existing solution.
- You volunteer for steering committees but rarely complete the follow-through.
What does “saying no is a professional responsibility” mean at Staff level?
?
Every yes to low-leverage work is an implicit no to high-leverage work. Staff engineers who cannot say no effectively cannot sustain high-impact output. Saying no is not a personality trait — it is a deliberate resource allocation decision that protects the organization’s most valuable uses of the Staff engineer’s time.
What are three practical ways to say no without damaging relationships?
?
- Make the trade-off explicit: “What will I not do if I take this on?”
- Offer an alternative route: point the requester to the person or resource that can actually help.
- Negotiate scope: “I can’t own this, but I can give you 30 minutes to unblock you” is often the right answer.
Describe the two-axis framework for categorizing work by impact and personal leverage.
?
- High impact + only you can do it → Do it, protect it fiercely
- High impact + others can do it → Enable and delegate
- Low impact (snacking, preening, ghosts) → Decline or minimize, regardless of who could do it
The discipline is not just doing more high-impact work — it is actively eliminating low-impact work.
How should a Staff engineer identify existential risks in their organization?
?
- Talk broadly across teams, product, ops, and leadership to see systemic patterns no single team sees.
- Read ignored signals: repeated patched incidents, hiring unable to keep pace with attrition, technical debt blocking delivery.
- Name uncomfortable problems early, including those that implicate senior leaders’ prior decisions.
Why is addressing existential risks often unglamorous?
?
Existential risk work typically involves months of coordination, writing documents people initially resist, and pushing on problems that make others defensive — often without a visible “launch” to point to. It is the opposite of preening. Yet it is precisely the kind of work that justifies the Staff engineer title.
What is the recommended strategy for protecting deep work time?
?
Treat unprotected blocks of time as a prerequisite for Staff-level thinking, not a luxury. Batch shallow coordination work (Slack, doc reviews) during low-energy periods. Reserve high-energy, uninterrupted time for ambiguous, complex cross-organizational problems. A Staff engineer with no deep work time cannot effectively do Staff-level work.
What is the energy-matching principle for task selection?
?
Match task type to current energy level:
- High energy → complex, ambiguous, high-stakes problems requiring original thinking
- Low energy → shallow coordination, reviews, async communication
Ignoring this principle leads to using scarce high-energy periods on snacks and attempting hard problems while mentally depleted.
What is the long-term cost of preening on a Staff engineer’s career?
?
Preening erodes social capital and credibility — the informal currency that makes Staff-level influence possible. When peers and leadership notice the gap between visibility and outcomes, the Staff engineer’s ability to advocate for important work, shape technical direction, and be taken seriously in cross-functional forums diminishes. Credibility, once lost, is slow to rebuild.
What role does institutional courage play in work prioritization?
?
Many of the highest-impact problems a Staff engineer could address are uncomfortable: they implicate past decisions, require difficult conversations, or involve unglamorous work with no obvious credit. Acting on these requires institutional courage — the willingness to name hard truths and take on problems that others avoid. Without it, a Staff engineer defaults to the visible and the easy.
How does writing design docs relate to avoiding the bottleneck trap?
?
Design docs allow teams to make good architectural decisions without requiring the Staff engineer’s live participation. They encode the reasoning, constraints, and trade-offs that the Staff engineer would otherwise convey in repeated meetings. Writing one good design doc can scale that judgment to every engineer who reads it, breaking the bottleneck dependency.
What does Larson mean by “recharge is work”?
?
Sustainable high-leverage output requires deliberate recovery. When Staff engineers deplete their energy reserves, judgment degrades — they default to snacking, avoid hard conversations, and produce lower-quality work. Treating rest and recovery as part of the job, not a guilty indulgence, is a prerequisite for sustained Staff-level impact.
Summarize the core message of “Work on What Matters” in one sentence.
?
Staff engineers must actively subtract low-leverage work (snacking, preening, chasing ghosts) from their schedules in order to concentrate their finite time, energy, attention, and social capital on existential risks and the work that only they can do.
Total Cards: 26
Review Time: ~18 minutes
Priority: HIGH
Last Updated: 2026-05-30