Create Space for Others
selt leadership sponsorship growth amplification
Status: Notes complete
Overview
Staff engineers are effective multipliers — but only if they resist the instinct to do everything themselves. This section addresses one of the deepest tensions at Staff level: the more you personally solve, the less room others have to grow, and the more the organization depends on you as an individual rather than a developed team.
Creating space for others is not a soft, charitable act. It is the primary mechanism by which Staff engineers achieve organizational leverage rather than merely individual productivity. Larson frames it as a professional discipline: learning to hold back, amplify, and sponsor — and knowing precisely when not to.
Core Concepts
The Staff Engineer’s Paradox — The skills that make you effective at Staff level (fast, high-quality judgment; broad context; deep expertise) are exactly the skills that create a vacuum when you exercise them: others don’t get the chance to develop those same capabilities. Long-term organizational leverage comes from growing others, not from being indispensable.
Sponsorship vs. Mentorship — These are often conflated but are meaningfully different:
- Mentorship is the transfer of knowledge and advice. You speak with someone, share your experience, help them think through problems.
- Sponsorship is action on someone’s behalf. You recommend them for a project, include their name in a leadership conversation, hand them your best work, and stake your credibility on their ability.
Mentorship is valuable but passive. Sponsorship is costly (it involves reputation risk) and correspondingly more powerful. Larson argues that Staff engineers should lean heavily toward sponsorship, especially for engineers they believe are ready for more but are not being seen.
Giving Away Your Best Work — Once you have done a class of work once and mastered it, the highest-leverage move is often to give the next instance of that work to someone who is ready to stretch into it. This:
- Creates growth opportunities for others
- Frees you to take on genuinely novel problems
- Builds organizational capability rather than personal indispensability
The emotional challenge is real: interesting, impactful work is enjoyable. Giving it away requires deliberately prioritizing team development over personal satisfaction.
Amplification — When you speak in a meeting or document, do you absorb credit for ideas or redistribute it? Effective Staff engineers amplify: “Building on what Priya said…” or “This is the approach Maya outlined last week…” Credit explicitly redirected publicly creates compounding goodwill, motivates others to contribute, and signals to leadership that others are doing important thinking.
The Bottleneck Anti-Pattern — A Staff engineer who must review, approve, or weigh in on every significant decision creates an organizational bottleneck: decisions slow down, teams feel disempowered, and the engineer themselves cannot do genuinely high-leverage work. The remedy is to build systems that let teams operate without constant Staff input (documented standards, trained engineers, clear decision frameworks) rather than centralizing judgment in a single person.
The Spectrum: When to Lead Directly vs. Create Space
Larson does not argue for always creating space. There is a spectrum:
| Situation | Right approach |
|---|---|
| Crisis — incident, high-stakes decision, no time | Lead directly. Step in, make the call, handle it. |
| Novel territory — no one else has the context yet | Lead directly, then bring others along as fast as possible. |
| Repeated class of problem you’ve handled before | Hand it to someone ready to stretch. Sponsor them. |
| Routine problem with a capable engineer available | Create space entirely. Don’t insert yourself. |
| High-visibility opportunity | Actively advocate for someone else to take it. |
The discipline is calibrating which situation you’re actually in — not always deferring, not always taking over.
Sponsorship in Practice
Concrete sponsorship actions that Staff engineers can take:
- Recommend someone by name in planning conversations: “Aditi should own the data model redesign — she has the context and is ready for this scope.”
- Include engineers in high-signal rooms: Bring a senior engineer to the architecture review who wouldn’t normally be invited.
- Give credit loudly and in the right rooms: Explicitly name who did the thinking in a leadership update.
- Hand off your best work deliberately: Not with a “let me know if you have questions” approach, but with a genuine handoff: context, stakes, support offer.
- Advocate when the person isn’t present: Proactively mention someone’s capabilities to managers and directors in contexts where decisions about assignments and promotions are made.
Sponsorship is asymmetric by design: the sponsor does the credentialing work that the sponsored person cannot do for themselves.
The Equity Dimension
Who gets space created for them matters. Historically underrepresented engineers — by gender, race, socioeconomic background, or communication style — tend to receive less organic sponsorship. They are passed over for high-visibility assignments, mentioned less often in the rooms that matter, and have fewer “informal” advocates making the case for them.
Staff engineers have the organizational capital to correct this explicitly:
- Be deliberate about who you are sponsoring, not just whether you are sponsoring.
- Examine whether your default network of people you “notice” and advocate for reflects the actual distribution of talent in your organization.
- Sponsorship without equity awareness tends to reinforce existing hierarchies; sponsorship with equity awareness can partially counteract them.
Elevating vs. Enabling
A useful distinction Larson draws:
Enabling — Removing a specific blocker so someone can continue their current work. Answering a question, unblocking a dependency, reviewing a PR. Valuable, but episodic and creates no lasting capability.
Elevating — Investing in someone’s growth so they can operate at a higher level independently going forward. This takes longer and requires more deliberate effort: pairing on how to approach a problem, not just giving them the answer; bringing them into strategic conversations so they build context, not just skills.
The goal is more elevating and less enabling — but enabling is appropriate when the stakes are immediate and the person genuinely needs unblocking.
Creating Space in Meetings
Meeting dynamics are a microcosm of broader space dynamics:
- Wait before speaking. Not being the first to answer gives others room to offer the answer. Often they can.
- Explicitly invite quieter voices. “Soren, you’ve been working closely on this — what’s your read?” normalizes participation from people who wouldn’t push in.
- Resist completing others’ thoughts. If someone is working toward an answer slowly, let them get there.
- Don’t re-explain what someone just said correctly. Restating a colleague’s correct point is credit erasure, even if unintentional.
- Publicly correct credit errors. If someone else’s idea gets credited to you, fix it immediately and in the same forum.
When Creating Space Fails
Failure modes to watch for:
- Abdicating, not delegating: Handing work off without context, support, or genuine care for the outcome. This is abandonment dressed as empowerment.
- Delegating the boring work: Only giving away unglamorous tasks while keeping high-visibility work for yourself. This creates a ceiling, not space.
- Sponsoring selectively: Sponsoring people who are already getting plenty of support while overlooking those who need it most.
- False modesty in meetings: Performatively deferring (“I don’t know, what do others think?”) when you actually have strong views. This is unhelpful — say what you think, then invite others.
- Creating space prematurely: Handing off work the person isn’t ready for, without adequate support, sets them up to fail and damages trust.
Key Takeaways
- The Staff engineer’s paradox: the more you solve personally, the less the organization learns to solve without you. Long-term leverage requires growing others.
- Sponsorship (action on someone’s behalf) is more powerful and more costly than mentorship (advice and knowledge transfer); Staff engineers should lean toward sponsorship.
- Giving away your best work — once you’ve mastered a class of problem — is the primary mechanism for creating genuine growth opportunities.
- Amplification means redistributing credit explicitly and publicly; “building on what X said” is a concrete practice, not just a platitude.
- Becoming a bottleneck (requiring your approval on everything) is not helpfulness — it is an organizational liability.
- Know when not to create space: crises and genuinely novel territory often require direct Staff-level leadership, at least initially.
- Elevating (building someone’s lasting capability) is more valuable than enabling (unblocking them for the immediate task), though both have their place.
- Equity matters: be deliberate about who receives sponsorship, not just whether you sponsor anyone. Default networks tend to reinforce existing hierarchies.
- Meeting-level behaviors (waiting before speaking, inviting quieter voices, correcting credit erasure) compound over time into cultural norms.
- Delegation without context and support is abandonment — genuine space-creation requires investment, not just withdrawal.
Related Resources
- sec02-work-on-what-matters — Giving away your best work only works if you’re reallocating to genuinely high-leverage problems
- sec07-stay-aligned-with-authority — Sponsorship requires organizational capital; staying aligned protects the capital needed to spend on others
- sec09-build-a-network-of-peers — Peer networks are the mechanism by which you discover who needs sponsorship outside your immediate team
- ch04-finishing-what-you-start — Complementary view on delegation and follow-through
- ch07-reuse-patterns — Organizational patterns that create or destroy space for engineers to grow
Last Updated: 2026-05-30