
Delegating Work
Apply Lenny-guest delegation tactics so you stop micromanaging agents, contractors, or early hires and get leverage from their judgment.
Overview
Delegating Work is a journey-wide agent skill that distills Lenny Podcast guest advice on delegation—usable whenever a solo builder needs to hand off ownership without losing momentum.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill delegating-workWhat is this skill?
- 46 curated mentions across 38 Lenny podcast guests on delegation and managerial leverage
- Frames true leverage as reports (or owners) bringing direction, not waiting for your prompts
- Tactical pattern: intentionally 'refuse to rule' when the team faces the right challenges
- Separates low-flexibility 'on assignment' work from high-flexibility ownership areas
- Guest-sourced quotes with timestamps for quick reference while planning roles or agent autonomy
- 38 podcast guests indexed
- 46 mentions of delegating work curated in the skill body
Adoption & trust: 1.3k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are the bottleneck: agents, hires, or partners wait for your direction instead of advancing their slice of the product.
Who is it for?
Founders transitioning from hands-on builder to orchestrator of people or agent workers with ambiguous ownership.
Skip if: Low-level API integration tasks or moment-to-moment debugging where you must personally touch the code.
When should I use this skill?
You need delegation and leverage patterns while handing off roadmap, implementation, or ops to reports, contractors, or agents.
What do I get? / Deliverables
You adopt concrete delegation heuristics—leverage tests, autonomy boundaries, and when to step back—so parallel workstreams move without constant rescuing.
- Delegation heuristics aligned to guest quotes and tactical advice
- Ownership boundaries (high vs low flexibility) you can paste into agent or team briefs
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Split customer-discovery threads between you and a contractor while setting expectations that they bring weekly hypotheses, not status-only updates.
Assign an agent-owned feature lane with explicit 'high flexibility' boundaries so you do not re-plan every commit.
Delegate channel experiments to a teammate with a mandate to propose the next three tests instead of waiting for your playbook.
Coach a support or success owner to drive retention fixes while you only unblock strategic tradeoffs.
Step back during incident follow-ups when the on-call owner is wrestling with the right systemic fixes.
How it compares
Curated leadership research skill—not a task runner, codebase linter, or hiring ATS integration.
Common Questions / FAQ
Who is delegating-work for?
Solo and indie builders who delegate to contractors, early teammates, or autonomous agents and want podcast-grade tactics instead of ad-hoc Slack pep talks.
When should I use delegating-work?
Across the journey: during Validate when scoping who owns discovery; Build when assigning agent or dev workstreams; Ship/Launch when distributing launch tasks; Grow/Operate when scaling support and roadmap without reverting to micromanagement.
Is delegating-work safe to install?
It is reference content with no shell or network requirements by default; still review the Security Audits panel on this Prism page before piping any skill into automated agent runs.
SKILL.md
READMESKILL.md - Delegating Work
# Delegating Work - All Guest Insights *38 guests, 46 mentions* --- ## Ben Horowitz *Ben Horowitz* > "managerial leverage means it is very simple... If I am kind of pushing you to kind of move your organization forward, then that's no leverage. What's leverage is if you're telling me what you should do and how you can push the company forward, that's leverage, then I'm getting more than I'd have if you weren't there" **Insight:** True delegation (leverage) occurs when a report drives their own department's progress without constant prompting from the leader. **Tactical advice:** - Evaluate reports based on whether they are bringing ideas to you or waiting for your direction - Consider a change if you find yourself constantly asking 'why aren't we doing this?' *Timestamp: 00:27:08* ## Boz *Boz* > "One of the most powerful things we do is refuse to rule. Someone will bring me a thing. A lot of times we feel obligated to weigh in and help. I'll be like, 'Nope, but look, I think you've got it. I think the challenges you're facing are the right challenges.'" **Insight:** Effective delegation involves intentionally stepping back when the team is struggling with the 'right' problems to build their autonomy. **Tactical advice:** - Explicitly tell reports when you are 'refusing to rule' to empower their decision-making. - Differentiate between 'on assignment' work (low flexibility) and 'high flexibility' areas. *Timestamp: 00:15:09* --- > "Mark, we joke inside of Meta, to this day, we call it the eye of Sauron. When Mark has determined that the thing that you're working on is the most important thing, there is no detail too small for him to notice." **Insight:** Leaders should oscillate between high-level strategy and deep-detail involvement based on the criticality of the project. **Tactical advice:** - Identify the 'hinge' upon which success or failure happens and go deep into those specific 'weeds'. - Use the 'Eye of Sauron' approach selectively for the company's most vital priorities. *Timestamp: 00:31:17* ## Cam Adams *Cam Adams* > "I run everyone through the culture of Canva. One of those sections is on giving away your Lego, finding joy in the other things of building a team, passing on your experience, helping other people do great writing or great product building or great engineering." **Insight:** Delegation is about finding fulfillment in enabling others to succeed and scale rather than holding onto tasks for personal identity. **Tactical advice:** - View scaling as a multiplier where you must change your own role to handle increased complexity - Pass on experience to help others achieve high-quality output in writing, product, or engineering *Timestamp: 00:00:12* --- > "Finding joy in the other things of building a team, passing on your experience, helping other people do great writing or great product building or great engineering is really what giving away your Lego is about. And we still encourage everyone to do that, to think about those moments where they need to level up in their impact, how they can bring their team along with them, how they can pass on their experience and help everyone really have a tremendous impact with the skills that they have." **Insight:** True leadership growth requires transitioning from individual execution to coaching and system-building. **Tactical advice:** - Identify pivot points where you need to move from a contributor role to a coach role - Focus on building systems and processes that allow the work to scale beyond your own capacity *Timestamp: 00:18:56* ## Camille Fournier *Camille Fournier* > "I also think people don't delegate enough. So, if you don't delegate, then you get overwhelmed because your team doesn't know how to do anything, because you haven't bothered to spend the time delegating, which actually takes more time initially, usually, you have to teach people whatever it is that you're trying to get them to do." **Insight:** Failure to d