running-effective-1-1s

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 running-effective-1-1s
0 commentsdiscussion
summary

Frameworks for running productive one-on-one meetings drawn from seven product leaders.

  • Emphasizes coaching over advising: shift to curiosity and empower reports to solve problems rather than providing immediate answers
  • Recommends dedicated deep-dive conversations on past (life story), future (dreams), and present (career action plan) to build long-term development
  • Includes monitoring for joy and recovery as performance indicators; treat lack of daily joy as a risk requiring interven
skill.md

Running Effective 1:1s

Help the user run effective one-on-one meetings using frameworks from 7 product leaders.

How to Help

When the user asks for help with 1:1s:

  1. Understand the relationship - Ask about their role, the report's tenure, and current dynamics
  2. Identify the purpose - Determine if the 1:1 needs to focus on tactical work, career development, or emotional support
  3. Suggest structure - Recommend appropriate formats based on the situation
  4. Coach on coaching - Help them shift from advising to empowering their reports

Core Principles

Coach, don't advise

Rachel Lockett: "Great leaders know that when you try to advise and have the answer all the time, you're not actually equipping your team to go solve the hard problems. You're training your team to come to you with all of the hard problems." Shift energy into curiosity when a report brings a hard problem. Avoid the urge to provide the answer immediately.

Dedicate time to deep career conversations

Kim Scott: "I would have three separate 45 minute conversations, so one about their past, one about their future, and one about their present to create a plan." Conduct a "Life Story" conversation to understand motivations, a "Future Dreams" conversation to identify long-term visions, and create a "Career Action Plan" to map current skill-building to those dreams.

Monitor recovery and joy

Hilary Gridley: "In my one on ones... I'm asking them, 'What do you do for joy? Are you doing something every single day that's bringing you joy in your life?' And if they say no, I'm like, 'That's a problem.'" Ask reports directly about what brings them joy outside of work. Treat a lack of daily joy as a performance risk that needs a plan.

Consider cutting standing 1:1s

Howie Liu: "I actually cut my one-on-one roster by default... Just having more standing one-on-ones actually precludes me from engaging in more timely topics." Consider a barbell approach: high-quality, less frequent relationship catch-ups (e.g., monthly walks) vs. urgent topical meetings scheduled as needed.

Use 1:1s for emotional processing after crises

Matt Mochary: "With each and every person on the stay team, you have a one-on-one with their manager for one hour and all the manager does is say, 'I'd like to know your thoughts and feelings,' and the person shares and then all the manager does is make them feel heard." Post-crisis 1:1s should focus entirely on active listening and emotional processing.

The 1:1 belongs to the report

The report should own the agenda. As manager, you're there to support their success, not to get status updates.

Questions to Help Users

  • "When your report brings you a problem, do you tend to give the answer or ask questions?"
  • "When was the last time you had a deep career development conversation (not a performance review)?"
  • "How do you know if your report is recovering well outside of work?"
  • "Does your report own the 1:1 agenda, or do you drive it?"
  • "Are your 1:1s tactical or strategic? What's the right balance?"

Common Mistakes to Flag

  • Status update theater - Using 1:1s for updates that could be async
  • Always advising - Solving problems instead of coaching the report to solve them
  • Skipping career conversations - Only discussing immediate work, never long-term development
  • Ignoring wellbeing - Not noticing when a report is burning out
  • Manager-driven agenda - The manager dictates topics instead of the report owning the time

Deep Dive

For all 10 insights from 7 guests, see references/guest-insights.md

Related Skills

  • running-effective-meetings
  • running-decision-processes
  • post-mortems-retrospectives
how to use running-effective-1-1s

How to use running-effective-1-1s 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 running-effective-1-1s
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 running-effective-1-1s

The skills CLI fetches running-effective-1-1s 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/running-effective-1-1s

Reload or restart Cursor to activate running-effective-1-1s. Access the skill through slash commands (e.g., /running-effective-1-1s) 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.648 reviews
  • Mateo Thompson· Dec 28, 2024

    running-effective-1-1s is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Soo Farah· Dec 16, 2024

    Registry listing for running-effective-1-1s matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kiara Sethi· Dec 12, 2024

    running-effective-1-1s reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Dhruvi Jain· Dec 8, 2024

    I recommend running-effective-1-1s for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Oshnikdeep· Nov 27, 2024

    Useful defaults in running-effective-1-1s — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mateo Shah· Nov 19, 2024

    Keeps context tight: running-effective-1-1s is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Desai· Nov 15, 2024

    Solid pick for teams standardizing on skills: running-effective-1-1s is focused, and the summary matches what you get after install.

  • Jin Yang· Nov 7, 2024

    running-effective-1-1s fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Xiao Ghosh· Nov 3, 2024

    running-effective-1-1s has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Omar Choi· Oct 26, 2024

    running-effective-1-1s is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 48

1 / 5