Skip to main content
The Rework Podcast

Eat your own dog food

21 min episode · 2 min read
·

Episode

21 min

Read time

2 min

Topics

Startups, Design & UX, Software Development

AI-Generated Summary

Key Takeaways

  • Real data requirement: Teams must use products with actual work data, not test scenarios or lorem ipsum placeholders, to expose edge cases like image cropping issues and flow problems that only surface under genuine usage conditions.
  • Early uncomfortable adoption: Start internal usage before features feel ready, layering in more users gradually while everyone tolerates incomplete functionality. This discomfort drives learning about what's missing and what works better than existing solutions being replaced.
  • Designer autonomy through code: Designers work directly in running software rather than Figma mockups, making micro-decisions about flows and features they encounter daily. This proximity to problems produces better solutions than top-down specifications covering every screen in advance.
  • Neglected flows expose gaps: Sign-up processes and other infrequently used features degrade because teams don't encounter them regularly. Force quarterly reviews of these critical first-impression touchpoints to maintain quality standards across the entire product experience.

What It Covers

37signals cofounders Jason Fried and David Heinemeier Hansson explain their dogfooding practice of using products internally with real data before public release, driving feature decisions and product quality through direct team experience.

Key Questions Answered

  • Real data requirement: Teams must use products with actual work data, not test scenarios or lorem ipsum placeholders, to expose edge cases like image cropping issues and flow problems that only surface under genuine usage conditions.
  • Early uncomfortable adoption: Start internal usage before features feel ready, layering in more users gradually while everyone tolerates incomplete functionality. This discomfort drives learning about what's missing and what works better than existing solutions being replaced.
  • Designer autonomy through code: Designers work directly in running software rather than Figma mockups, making micro-decisions about flows and features they encounter daily. This proximity to problems produces better solutions than top-down specifications covering every screen in advance.
  • Neglected flows expose gaps: Sign-up processes and other infrequently used features degrade because teams don't encounter them regularly. Force quarterly reviews of these critical first-impression touchpoints to maintain quality standards across the entire product experience.

Notable Moment

The team abandoned Highrise 2 development despite strong market demand because neither founders nor staff actively manage customer relationships anymore. Two decades without client work left them unable to dogfood CRM software effectively or authentically.

Know someone who'd find this useful?

Episode Transcript

Welcome to Rework, a podcast by thirty seven Signals about the better way to work and run your business. I'm Kimberly Rhodes joined by the cofounders of thirty seven Signals, Jason Fried and David Heinemeier Hanssen. This week, we're gonna talk a little bit about a term called dogfooding, which is basically in software using your own product to test it out before you are sharing it with customers. We do this internally at thirty seven signals, so I thought we would talk a little bit about the who, what, when, where, why we actually do this. So let's start first with the why. I think that's pretty simple, but when you guys wanna jump in, why do we actually dog food before we release something publicly? I mean, there's there's so many reasons. One reason is to know what to build next. As we've talked about in previous episodes, we we don't know the next six months worth of work. We don't know what it's gonna be. We know what we're doing now, and then we build it, and we use the thing we're building while we're building it. This is for new products specifically. And then we go, this is missing, or this is lacking, or this is good enough, or we really need this. And then you build something and you use it and you go, that didn't really do it. What else could we do? You just don't know. And that's the whole point. You don't know going into it. You have an idea of where you wanna go. You get into it, and then you don't know until you use it, and then you feel it out and the whole thing. So there's that. There's also the sense of this is the best way to figure out if it's any good, and you typically are putting it up against something else you're already doing because everyone's already doing something. Like, we're currently make we've talked about this. You know, we're making, like, a a bug issue tracking sort of thing, And we've done this in other ways. We've used to do list. We've used Kanban, card table in Basecamp. We've done it in other ways. Everyone's doing something in some way already. So what's nice about building something that and using it as you're building it is to go, is this better than the other way? Are we getting somewhere? Is there something interesting here? And then there's a point at which in when you're first starting, you're probably not gonna surpass what you're doing. But there's a point where you wanna get to where it feels like it clicks beyond, and you go, now we're better than what we had. There's something else here that's special. And you can't know that until you use it because you're using the other thing, so you've gotta compare the two things. And then also just it sparks ideas, and there's no better feeling than using the thing …

Get the full transcript (4,343 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Rework Podcast transcripts →

You just read a 3-minute summary of a 18-minute episode.

Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.

Tools

  • Designers work directly in running software rather than Figma mockups, making micro-decisions about flows and features they encounter daily.

Products

  • by 37signals

    The team abandoned Highrise 2 development despite strong market demand because neither founders nor staff actively manage customer relationships anymore.

More from The Rework Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The Rework Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime