product-operations

refoundai/lenny-skills

Build and scale product operations functions to enable product teams without creating bureaucracy.

What is product-operations?

Product operations bridges product teams and organizational operations, creating systems and processes that enable product managers to focus on core product work. Use this when scaling a product team, improving cross-functional coordination, standardizing processes, or ensuring insights reach product teams effectively.

Define product ops scope and ownership boundaries to avoid duplication with PM work
Design standardized processes for roadmaps, user research, and data insights across the organization
Create systems that enable product teams to scale velocity without adding bureaucracy
Identify and eliminate operational tasks that distract PMs from strategic product work
Bridge communication and coordination gaps between product and other functions like sales, support, and operations

How to install product-operations

npx skills add https://github.com/refoundai/lenny-skills --skill product-operations

Claude Code

Cursor

Windsurf

Cline

How to use product-operations

1.Assess your current pain points by identifying what operational tasks are distracting PMs from product work
2.Determine if your product organization is at the scale where dedicated product ops makes sense
3.Define the scope of product ops ownership versus PM responsibilities to avoid duplication
4.Design standardized systems for roadmaps, user research, and insights distribution
5.Establish clear reporting structure and physical/cultural proximity between product ops and product teams

Use cases

Good for

Scaling a product team from 3-4 PMs to 10+ and needing operational infrastructure
Standardizing how user research and customer insights flow to product teams across multiple locations
Reducing coordination friction between product, engineering, sales, and operations functions
Establishing consistent roadmap formats, review cadences, and decision-making processes
Enabling product teams to ship faster by offloading release management and enablement work

Who it's for

VP or Head of Product building out organizational structure
Product Operations leaders designing new functions
Product managers struggling with operational overhead
Scaling startups transitioning from founder-led to structured product organizations
Organizations with distributed product teams needing standardization

product-operations FAQ

When is the right time to hire a product operations function?

Product ops makes sense when you have enough product managers and complexity that operational tasks are distracting PMs from core product work. Too early investment wastes resources; too late creates scaling bottlenecks.

Should product operations make product decisions?

No. Product operations informs product decisions through insights and infrastructure but decision-making authority remains with product managers. Product ops enables, not decides.

What's the difference between product ops and product management?

Product managers own product strategy and decisions. Product operations owns the systems, processes, and operational work that enable PMs to do their best work without distraction.

How do you avoid product ops becoming a bureaucratic bottleneck?

Focus on enabling and scaling, not process for process's sake. Standardize outputs and check-ins, but avoid creating approval gates or slowing down product teams.

Where should product operations report organizationally?

Product ops should report into operations for accountability but sit physically and culturally with product teams to understand their needs and maintain close collaboration.

Full instructions (SKILL.md)

Source of truth, from refoundai/lenny-skills.

name: product-operations description: Help users build and scale product operations functions. Use when someone is scaling a product team, struggling with cross-functional coordination, needs to standardize product processes, or wants to improve how insights reach product teams.

Product Operations

Help the user build and scale product operations functions using frameworks from 5 product leaders.

How to Help

When the user asks for help with product operations:

Understand the pain points - Ask what's breaking down in their current product processes
Assess organizational scale - Determine if they're at the stage where dedicated product ops makes sense
Define the scope - Help them clarify what product ops should own vs. what PMs should retain
Design the systems - Create processes that enable product teams without creating bureaucracy

Core Principles

Product ops bridges product and operations

Brian Tolkin: "One solution to that problem, our solution at the time was to start up a new function called product operations who had accountability and reported into operations but physically sat with and operated much like a member of the product team." Product ops originated as a bridge between centralized product teams and distributed operations, ensuring product decisions account for operational reality.

Product ops creates systems for product teams to thrive

Christine Itwaru: "Product operations for a VP or a head of product or a product manager is the creation of some system that allows you to thrive or allows your team to thrive in product management." The function is about building systems that enable product management, not doing product management itself.

Product ops enables scaling velocity

Geoff Charles: "We invested early on in product operations... they basically are tasked with a lot of the work that needs to get done to continue shipping products and scaling product development." Product ops handles release management, enablement, and operational tasks that would otherwise distract PMs from their core work.

Product ops informs, not decides

Melissa Perri + Denise Tilles: "Product operations does not take away decision making rights from the product manager. It's there to inform them." Product ops provides insights and infrastructure but doesn't make product decisions - that remains with PMs.

Product ops helps with standardization and insights at scale

Melissa Perri: "Product management at scale is really hard, and that's where product operations comes in. So what it does is it helps you get the right insights to the team, and then help standardize those outputs and those check-ins." The function focuses on standardizing roadmaps, scaling user research, and surfacing data insights across the organization.

Questions to Help Users

"What operational tasks are currently taking PMs away from product work?"
"How do insights from sales, support, and operations currently reach product teams?"
"What would be different if every PM had standardized processes and tools?"
"Where are the biggest coordination gaps between product and other functions?"
"At what point did your product org start struggling with scale?"

Common Mistakes to Flag

Product ops as PM work - Asking product ops to make product decisions instead of enabling PMs
Too early investment - Building a product ops function before the product org is large enough to need it
Process for process's sake - Creating standardization that slows teams down rather than enabling them
Siloed from product - Product ops reporting into operations without close connection to product teams
Unclear ownership - Ambiguity about what product ops owns vs. what PMs own