Dogfooding

Name: Dogfooding
Author: refoundai

refoundai/lenny-skills

1.5k installs
1.2k repo stars
Updated July 16, 2026
refoundai/lenny-skills

Help users implement effective dogfooding practices. Use when someone is trying to get their team to use their own product, designing internal usage programs, or building user empathy through personal

About

The dogfooding skill Help users implement effective dogfooding practices. Use when someone is trying to get their team to use their own product, designing internal usage programs, or building user empathy through personal product use. Documentation covers workflows, commands, and guardrails agents should follow when users invoke this capability. Key documented areas include **Assess current state** - Determine how much the team currently uses their own product; **Identify the gap** - Find where team members lack firsthand experience with user pain points; **Design the program** - Help create systems that make dogfooding natural and required; **Measure impact** - Track how dogfooding improves product decisions. Use when developers or agents need structured guidance for dogfooding tasks with evidence grounded in the bundled SKILL.md rather than generic advice. **Assess current state** - Determine how much the team currently uses their own product **Identify the gap** - Find where team members lack firsthand experience with user pain points **Design the program** - Help create systems that make dogfooding natural and required **Measure impact**

**Assess current state** - Determine how much the team currently uses their own product
**Identify the gap** - Find where team members lack firsthand experience with user pain points
**Design the program** - Help create systems that make dogfooding natural and required
**Measure impact** - Track how dogfooding improves product decisions
"How often does each team member actually use the product as a real user?"

Dogfooding by the numbers

1,538 all-time installs (skills.sh)
+1 installs in the week ending Aug 5, 2026 (Skillselion tracking)
Ranked #388 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
Security screen: MEDIUM risk (skills.sh audit)
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

dogfooding capabilities & compatibility

Capabilities: **assess current state** determine how much th · **identify the gap** find where team members l · **design the program** help create systems tha · **measure impact** track how dogfooding improv · "how often does each team member actually use th

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

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/refoundai/lenny-skills/dogfooding.svg)](https://skillselion.com/skills/refoundai/lenny-skills/dogfooding)

Installs	1.5k
repo stars	★ 1.2k
Security audit	3 / 3 scanners passed
Last updated	July 16, 2026
Repository	refoundai/lenny-skills ↗

How do I handle dogfooding tasks with agent guidance?

Who is it for?

Teams needing documented dogfooding workflows.

Skip if: Teams needing quantitative analytics pipelines or formal user research interview scripts instead of internal usage philosophy.

When should I use this skill?

What you get

Structured workflow from dogfooding documentation applied to the user request.

By the numbers

Draws from 2 Lenny Podcast guests with 2 total mentions

Files

SKILL.mdMarkdownGitHub ↗

Dogfooding

Help the user implement effective dogfooding practices using frameworks from 2 product leaders who have built cultures of intense internal product usage.

How to Help

When the user asks for help with dogfooding:

1. Assess current state - Determine how much the team currently uses their own product 2. Identify the gap - Find where team members lack firsthand experience with user pain points 3. Design the program - Help create systems that make dogfooding natural and required 4. Measure impact - Track how dogfooding improves product decisions

Core Principles

Require team members to become users

Maya Prohovnik: "I am constantly yelling at my product team who do not have podcasts and being like, I really don't think that you can build the right things. If they talk to users all the time, they see the data, but all of them, once they finally start doing their podcast, they're like, I get it." Force the entire team to become creators/users to deeply understand user pain points.

Use the tool intensely every day

Michael Truell: "From the very start, our product development process was really about dogfooding, and using the tool intensely every day. And we never wanted to ship anything that wasn't useful to us." 'Intense' daily use provides the realism needed to build useful features, especially for AI products.

Questions to Help Users

"How often does each team member actually use the product as a real user?"
"What's preventing your team from being heavy users of your own product?"
"What would it take to make internal usage feel natural rather than forced?"
"Are you learning different things from dogfooding vs. customer feedback?"
"How quickly do you feel the pain of bugs or friction when using your own product?"

Common Mistakes to Flag

Superficial testing - Using the product only in demo mode, not for real work
Delegating to QA - Relying on testers instead of requiring team members to be real users
Ignoring non-obvious use cases - Only testing the happy path rather than edge cases
Not acting on findings - Dogfooding without a process to fix discovered issues
Excluding non-product roles - Only having engineers dogfood when designers and PMs should too