More Thoughts on Dogfooding
Published: ....
Last modified: ....
Share this post on BlueskySee discussion on Bluesky
After posting about Dogfooding the other week (which if you haven't read yet I recommend doing so now, it's really a short read), one of my favorite development focused podcast shows covered the same exact topic while reviewing another blog post on the topic.
After both listening to the above episode and also talking with Scott Kaye about the topic, there were a number of interesting takeaways that I had:
New Customers
Dogfooding is great at improving the product for existing customers, but what about attracting and improving the conversion for new customers?
Scott got me thinking about this more.
Dogfooding can still be a useful exercise for attracting new users, see for example the note from my original post on how Graphite forces their employees to go back through the account creation flow every so often by deleting their account on a scheduled basis.
Famously also, I think either Stripe or Shopify have shared that they have new hires build some kind of product using their offering (usually focusing on a specific part of their offering). They then have these new hires feed back in improvements and fixes to make their feature better for others and also improved documentation.
The key insight I think is to make sure to play the role of a new user as part of the dogfooding - often this means having you start fresh without an account, but it could involve other aspects too!
In combination with user feedback
From the episode, they talked about collecting user feedback - while I talked briefly about this in the previous post as well - I wanted to re-iterate that dogfooding alone won't magically make your product/feature better across all axes.
One pitfall of only dogfooding and not listening to real customers is that you may end up building a bit of a monoculture or a single solution to a subset of the problems that your customers may have. Sure the resulting product may fit all your needs, but you may also have greatly reduced the percentage of potential users in the process.
I believe that you should do both - dogfood actively but also listen to and act on customer feedback. While sometimes it can be difficult to actually understand what users may want (speech is a lossy medium after all), but none the less it's still worth capturing and listening to.
Tags:
Related Posts
Development
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
Is it a good or a bad thing to offload writing code to AI agents and Large Language Models?
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
How to generate a custom Ghostty theme based on any iterm2 theme!
Published: ....
A rough mental model for how you should be leveraging AI as a tool for your own growth
Published: ....
The secret to excellent product teams is using your own product, and often!
Published: ....
(Ab)using Git as yet another tool for thought!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
Published: ....
I've been using a variety of AI tools as of late, I figured I'd document the ones I'm primarily using!
Published: ....
I've started to use Cloudflare to manage my domains for several side projects, have had to jump through the same hooks multiple times that I figured I should document them here!
Published: ....
Revising my previous blog post on React Error Boundaries and my preferred go-to implementation!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
When did semver major changes become so scary?
Published: ....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few quick thoughts on burn out and taking a break