running-effective-1-1s

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 intervention Suggests reports own the 1:1 agenda; manager provides support for their success, not status updates Flags common pitfalls: status-update theater, always advising, skipping career conversations, ignoring wellbeing, and manager-driven agendas

INSTALLATION
npx skills add https://github.com/refoundai/lenny-skills --skill running-effective-1-1s
Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$2a

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
BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card