managing-up

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill managing-up
0 commentsdiscussion
summary

Strategies for working effectively with managers and executives drawn from 35 product leaders.

  • Proactively communicate upward with regular updates on priorities, blockers, and progress rather than waiting to be asked, using consistent formats like weekly emails
  • Bring recommendations and point of view to your manager instead of just problems, reducing their cognitive load and positioning yourself as an ally
  • Understand your manager's priorities and two levels up to tailor communication
skill.md

Managing Up

Help the user work effectively with their manager and executives using strategies from 35 product leaders.

How to Help

When the user asks for help managing up:

  1. Understand the relationship - Ask about their manager's style, what they care about, and where the friction or challenge is
  2. Diagnose the gap - Determine if this is a communication issue, alignment issue, trust issue, or visibility issue
  3. Apply the right approach - Help them choose between proactive updates, reframing conversations, building trust through wins, or direct feedback conversations
  4. Build sustainable habits - Guide them toward ongoing practices rather than one-time fixes

Core Principles

Your manager is a resource to leverage, not an obstacle

Boz: "The advice I give more frequently than any other is for people to more directly leverage their leaders." Your primary job is to achieve results. Your manager has tools and authority to clear paths. Ask for help to bulldoze blockers rather than trying to solve everything yourself.

Proactively communicate before they have to ask

Casey Winters: "People just way under communicate upward. Then they complain that executives are out of touch when they aren't telling executives what they need to know." Send weekly "state of" emails with priorities, blockers, and thoughts. Frame updates as "no response required" to keep leaders informed without creating burden.

Understand two levels up

Fareed Mosavat: "You should understand your boss's priorities and your boss's boss's priorities. Eventually, that means you have to know what the board is thinking." Build a mental model of how your work creates leverage in the larger system. Tailor communication to address senior leadership's specific concerns.

Bring recommendations, not just problems

Wes Kao: "When you ask 'Hey manager, what should we do?' you're putting a lot of cognitive load on them. Instead say 'Hey manager, here's what I think we should do.'" Present a point of view even if it's just an initial hunch. Provide insights and takeaways, not just raw data.

Use structured update formats

Boz: "We used HPM - Highlight, People, Me. Every manager at Facebook would send this to their manager." Use consistent formats. Ask your manager: "How do you like to get information about me?" Consider weekly emails with priorities, blockers, and general thoughts.

Position yourself as an ally who reduces burden

Ethan Evans: "Management can be a lonely job. Having an ally is a huge weight off people's shoulders." Recognize managers are overwhelmed. Move from asking "How can I help?" to suggesting specific solutions. Keep them in the loop by proactively fixing problems before they ask.

Start with Chapter 1 when talking to execs

Casey Winters: "You have to start with chapter one, which is what part of the company strategy are you working on? What metrics are you trying to improve? What assumptions are you making?" Find the last point that's obvious to the audience and build from there. Don't dive into "Chapter 6" details without the strategic context.

Use concrete artifacts, not abstract ideas

Dylan Field: "The more concrete an artifact is or the more you can debate something, the better. I ask for examples a lot." Present designs and docs rather than abstract ideas. If you lack data for a follow-up question, pause to find the answer rather than guessing.

Run experiments to challenge strong opinions

Itamar Gilad: "If you run a secret experiment and come back with data, either they get extremely mad at you... or more commonly, they're pleasantly surprised." Use evidence to flip a leader's perspective rather than engaging in a battle of opinions.

Understand the spirit, then offer better options

Jiaona Zhang: "It's understanding the spirit of what they're trying to achieve. Being able to go back with 'I understand the spirit, but here's a better way to achieve it.'" Align on the underlying goal first. Present automated or scalable alternatives rather than just saying no.

Use the U-curve for founder involvement

Noah Weiss: "High involvement at the start for strategy and at the end for quality, with autonomy in the middle." Involve founders early for strategic buy-in on goals. Bring them back at the end to ensure the product meets quality standards.

Say what you'll do, say you're doing it, say you did it

Peter Deng: "Say you're going to do the thing, say that you're doing the thing, and then say that you did it." This repetitive communication ensures alignment and provides opportunities for course correction.

Questions to Help Users

  • "What does your manager care most about right now? What's keeping them up at night?"
  • "How does your manager prefer to receive information - email, Slack, meetings?"
  • "Do they know what you're working on this week without having to ask?"
  • "When you bring problems to them, are you also bringing recommendations?"
  • "What does success look like for your team from your manager's perspective?"
  • "Have you asked your manager directly how they'd like you to communicate?"

Common Mistakes to Flag

  • Under-communicating - If your manager has to ask what's going on, you're not communicating enough. Proactive updates build trust
  • Bringing problems without recommendations - This puts cognitive load on your manager. Always come with a point of view
  • Starting with details, not strategy - Executives need context. Start with "Chapter 1" (strategy) before "Chapter 6" (details)
  • Trying to solve everything alone - Your manager has tools and authority you don't. Leverage them to clear blockers
  • Waiting to be managed - The most senior people got there by being great at managing up. It's a proactive skill, not resentment

Deep Dive

For all 50 insights from 35 guests, see references/guest-insights.md

Related Skills

  • Running Effective 1:1s
  • Having Difficult Conversations
  • Stakeholder Alignment
  • Written Communication
how to use managing-up

How to use managing-up on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add managing-up
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill managing-up

The skills CLI fetches managing-up from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/managing-up

Reload or restart Cursor to activate managing-up. Access the skill through slash commands (e.g., /managing-up) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.741 reviews
  • Omar Abbas· Dec 20, 2024

    Registry listing for managing-up matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Meera Ramirez· Dec 16, 2024

    Solid pick for teams standardizing on skills: managing-up is focused, and the summary matches what you get after install.

  • Meera Sanchez· Dec 16, 2024

    managing-up fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Diya Bansal· Dec 12, 2024

    Useful defaults in managing-up — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Henry Sethi· Nov 7, 2024

    I recommend managing-up for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Meera Ndlovu· Nov 7, 2024

    We added managing-up from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mia Rao· Oct 26, 2024

    Keeps context tight: managing-up is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Meera Khanna· Oct 26, 2024

    managing-up reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Oshnikdeep· Sep 21, 2024

    Keeps context tight: managing-up is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Arya Perez· Sep 9, 2024

    Solid pick for teams standardizing on skills: managing-up is focused, and the summary matches what you get after install.

showing 1-10 of 41

1 / 5