
Managing Up
Apply Lenny’s Podcast guest tactics for managing executives, stakeholders, and power asymmetry while you ship as a solo or small-team builder.
Overview
Managing Up is a journey-wide agent skill that surfaces Lenny’s Podcast guest playbooks for influencing leaders and surviving power asymmetry—usable whenever a solo builder needs to align upward before committing to a pl
Install
npx skills add https://github.com/refoundai/lenny-skills --skill managing-upWhat is this skill?
- 35 Lenny’s Podcast guests consolidated with 50 cited mentions in the skill header
- Tactical frames: organizational kayfabe, disconfirming evidence, and parallel ‘hot takes’ docs for CEOs
- Guest-sourced quotes with timestamps for traceable context
- Onboarding-oriented advice such as quarterly provocative strategy memos
- Insight + tactical advice structure for quick agent retrieval
- 35 podcast guests aggregated in the skill header
- 50 guest mentions indexed in the skill header
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 see strategic risks or misaligned narratives but fear that challenging your boss or client will mark you as ‘not performing.’
Who is it for?
Builders and tech leads who work with founders, PMs, or enterprise buyers and want quotable, podcast-sourced managing-up language in agent-assisted prep.
Skip if: Pure IC contributors with no stakeholder layer, or teams that need executable HR/legal escalation procedures instead of advisory patterns.
When should I use this skill?
You need evidence-based tactics for influencing managers, CEOs, or executive sponsors, especially around onboarding, strategy disagreements, or organizational dysfunction.
What do I get? / Deliverables
You leave sessions with concrete tactics—hot-take memos, safer disconfirming evidence, kayfabe-aware framing—to steer decisions without publicly embarrassing decision-makers.
- Stakeholder-ready talking points grounded in named guest insights
- Structured insight + tactical advice summaries for 1:1 or review meetings
- Optional ‘hot takes’ or parallel strategy note outlines
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Draft a 1:1 brief that introduces disconfirming data without making your director ‘look dumb’ in front of peers.
Frame a provocative but safe scope memo when an executive’s public narrative overshoots what you can ship solo.
Align on who owns the external launch story before your agent schedules posts or changelog copy.
Navigate post-incident reviews when leadership prefers kayfabe over blunt root-cause language.
How it compares
Curated leadership research packaged as a skill—not a task runner like Jira integration or a code review checker.
Common Questions / FAQ
Who is managing-up for?
Solo and indie builders who still manage relationships with bosses, clients, or executive sponsors and want Lenny’s Podcast-derived tactics loaded into their agent.
When should I use managing-up?
Use it in build PM when prepping exec reviews; during validate scope conversations when a sponsor narrows the idea; at launch distribution when leadership owns the public story; and during grow or operate phases whenever power asymmetry blocks honest feedback.
Is managing-up safe to install?
It is read-only advisory content with no shell or network requirements in the excerpt; still review the Security Audits panel on this Prism page before installing any skill from the catalog.
SKILL.md
READMESKILL.md - Managing Up
# Managing Up - All Guest Insights *35 guests, 50 mentions* --- ## Alex Komoroske *Alex Komoroske* > "The underlying dynamic that must be true in any organization on a fundamental basis is you can't make your boss look dumb because if you do, they're the person who decides, 'Oh, this person's not performing,' or whatever. And that one little asymmetry, that one little fact... is what leads to the systemic compounding thing where you get these really weird dysfunctional emergent things that everybody hates." **Insight:** Organizational dysfunction often stems from the simple power asymmetry where subordinates feel they cannot challenge a leader's public narrative without personal risk. **Tactical advice:** - Acknowledge 'organizational kayfabe'—the things everyone pretends are true—to navigate the system without being 'knocked out of the game.' - Find ways to introduce disconfirming evidence that doesn't feel like an existential threat to leadership. *Timestamp: 00:29:12* ## Ami Vora *Ami Vora* > "With Max, I also wrote a parallel document of hot takes. So once a quarter or so for the first year, I'd write a document that was just like, hey, for sake of provocation, if we wanted to fundamentally change a few things, here's ideas on what we could fundamentally change." **Insight:** Build a high-trust relationship with a CEO by proactively sharing provocative strategic observations. **Tactical advice:** - During onboarding, write a list of themes and observations to build credibility. - Create a 'hot takes' document to spark discussion on fundamental changes with the executive team. *Timestamp: 01:09:09* ## Anneka Gupta *Anneka Gupta* > "As having a founder that can effectively operate in founder mode means that I can go and have a conversation with the CEO and say, "Hey, look, we have this huge opportunity and these are the things that aren't working, and I need your help to help figure out how we can move the needle more substantially in the direction that we need to go."" **Insight:** A product leader can leverage a founder's unique power as a resource to unblock major initiatives and drive organizational change. **Tactical advice:** - Activate the CEO as an ally to push initiatives that require high-level power to move the needle. - When a founder pushes a 'pet project,' identify the underlying objective and suggest alternative options that meet that goal more effectively. *Timestamp: 00:11:23* ## Bangaly Kaba *Bangaly Kaba* > "A lot of times I think there is a big disconnect between an IC focusing on their discrete area and try to optimize for local maxima, versus understanding, okay, my manager's thinking about these things and this is how I fit in, and understanding maybe they have a gap to understanding why your area is important." **Insight:** Effective managing up requires understanding your manager's broader objectives and showing how your work supports those goals. **Tactical advice:** - Identify what your manager is currently optimizing for and find synergies with your own remit. - Take on adjacent tasks that are on your manager's plate to alleviate their burden and increase your scope. *Timestamp: 00:18:28* ## Boz *Boz* > "The advice I find I have to give more frequently than any other in my career, as a manager, a board member, an advisor and a friend, is for people to more directly leverage their leaders." **Insight:** Your primary job is to achieve results, and your manager is a resource with tools and authority that can clear paths and accelerate your work. **Tactical advice:** - Ask for help to bulldoze blockers rather than trying to solve everything yourself. - Frame updates as 'no response required' to keep leaders informed without creating a burden. - Provide a 'heartbeat' or 'ping' to your manager so they have a mental model of your progress. *Timestamp: 00:13:40* --- > "We actually used to have a format for that we called HPMs. Highlight, people, me. And every manager at Fa