Dec 15, 2020 · 29m · we-live-to-build
Why Dogfooding Your Own Product Exposes What All Your Data Misses
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Host Sean Weisbrot and consultant Peter van Eyprin examine the transformative power of operational minimalism in business, demonstrating how eliminating feature bloat, practicing internal dogfooding, and providing strategic context to engineering teams fuels sustainable company growth.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Sean holds 30.5% of the talking time here. How this is scored →
Sean as informed peer 4.6 Guest teaching 4.1 Guest disagreement 1.4 Sean pushing back 1.0
speaking balance: gold is Sean, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 9:35 Guest dismisses agile throw-it-at-the-wall mentality
Peter rejects the premise of passively testing features, calling unpromoted feature drops 'magical thinking' and shouting into an internet black hole.
Hardest push from Sean ▶ 12:08 Host challenges hypothetical scenario of missing replacement featuresSean refuses to accept Peter's assumption that every company has an offsetting feature ready, pushing him on what to do when no ideas are available.
Biggest teaching moment ▶ 20:17 Guest defines dogfooding and mocks disconnected executivesAfter Sean admits he does not know what dogfooding means, Peter defines the industry concept and explains how executives look ridiculous when unable to use their own product.
Sean holds their own ▶ 23:30 Host details his operational leadership overhaul at SidekickSean demonstrates practical startup management expertise by detailing how he revamped his company's internal roadmap and product story after COO employee interviews.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Sean as informed peer | Guest teaching | Guest disagreement | Sean pushing back | Why |
|---|---|---|---|---|---|---|
| Core Competency and Eliminating Enterprise Distractions | 5 | 3 | 1 | 1 | Sean shares his personal philosophy on minimalist living and relates it to business product discipline. Peter agrees and elaborates on how early startups clutter their roadmaps with useless features like unused review systems. | |
| Customer Experience and Hidden Feature Maintenance Overhead | 4 | 4 | 1 | 1 | Peter draws on customer experience tech consulting, noting the hidden operational cost of maintaining legacy features for vocal minorities. Sean listens and sets up a practical question about sunsetting features. | |
| Data-Driven Sunsetting and Weighted Feature Trade-Offs | 5 | 5 | 1 | 1 | Sean references Google's habit of abruptly killing products to prompt Peter on how to sunset features gracefully. Peter explains weighted feature trade-offs and using user data to justify cuts. | |
| Feature Validation Timelines and Active Promotion Strategies | 3 | 6 | 3 | 1 | When Sean asks how long to wait before cutting a feature, Peter bluntly replies 'instantly' and critiques the magical thinking of founders who silently deploy features into a void without active marketing. | |
| Leveraging Strategic Offsets and Bundled Announcements | 5 | 4 | 2 | 3 | Sean challenges Peter's premise by asking what an entrepreneur should do if they lack an alternative feature ready to bundle with bad news. Peter reframes features as any positive operational tweak like pricing cuts. | |
| Pruning MVP Roadmaps and Incremental Vertical Expansion | 6 | 5 | 2 | 1 | Sean shares specific details about trimming his own MVP roadmap for investors before asking when profitable companies should diversify. Peter details Amazon's incremental expansion model versus failed acquisitions. | |
| Defining Dogfooding and Overcoming Executive Disconnect | 2 | 7 | 2 | 0 | Sean asks for clarification on the term 'dogfooding', prompting Peter to explain the concept and describe embarrassing situations where company executives cannot navigate their own software. | |
| Radical Production Transparency and User Demographics | 7 | 3 | 1 | 1 | Peter illustrates demographic awareness with a story about unreadable UX designs for elderly users. Sean follows up with a comprehensive explanation of how his COO revamped internal developer transparency at Sidekick. | |
| Comprehensive Project Scoping Versus Fragmented Development | 6 | 3 | 1 | 1 | Peter advocates for comprehensive 10-15 page project briefs over fragmented agile tasks. Sean explains his structured approach using GitLab milestones and detailed sprint tickets. | |
| Episode Conclusion and Continuous Operational Refinement | 3 | 1 | 0 | 0 | Sean asks a standard closing question about ongoing learning and wraps up the interview with his podcast sign-off motto. |
Statements from this episode (12)
Van Eyprin: Successful Entrepreneurs Must Solve Exactly One Core Problem
“And the truth is to really be a successful entrepreneur, you need to find one problem or pain point that you solve for people and go after it. And all the rest of the stuff is just noise.”
Weisbrot: Business Minimalism Is Hard Because Founders Try to Please Everyone
“Professionally, minimalism is a little bit harder to do, I think, because it's so common for people to want to do as many different things as they possibly can in order to provide as much value for as many potential customers.”
Van Eyprin: Founders Often Keep Costly, Zero-Revenue Features to Appease Complainers
“And most business owners are going to give into that. And I see that often, even giving into it at the point where It's an expense for them to maintain it. And there's literally no revenue left from having this feature. They just want to quote unquote, keep th…”
Weisbrot: Google Builds Useless Products Only to Abruptly Cut Them
“Google does a great job of building useless crap and then throws it out there and then suddenly cuts it after they've got, you know, tens of thousands or hundreds of thousands of people using it.”
Van Eyprin: Soften Feature Deprecation by Announcing Desirable New Features
“We like to put it as a feature trade-off, and we try to make a weighted trade-off, is what we call it. So, on the one hand, you're losing this thing that you love every day. On the other hand, We're going to announce that the same time that we're adding this o…”
Van Eyprin: Maintaining low-usage features creates an unspoken focus penalty
“There's always an unspoken expense here of focus, both on the businesses side and on the customer side.”
Van Eyprin: Aggressive Promotion Quickly Reveals if a Feature Has Real Value
“If you're really promoting the heck out of this feature, it becomes really Quickly obvious from both a budget standpoint of the money you're spending promoting this feature and the return you're getting, whether this feature has value or not.”
Van Eyprin: Big swings into new verticals rarely succeed anymore
“I feel like companies that tend to take big swings into other verticals, the conglomerations, they don't really work that well often anymore.”
Van Eyprin: Teams Must Dogfood Software to Understand True User Pain
“Dogfooding is the concept of everyone has to use your own product. You need to understand the pain points of the software you're developing. Right. And so likewise, if you're never your own customer, you don't know what your customer's going through. You don't…”
Van Eyprin: Developers Need Full Transparency on Business and Customer Demographics
“A developer should know what you're doing well as a business and not, and your customer base, because without knowledge, without transparency, and without that shared communication The more and more often you guys are going to be shooting blind at each other a…”
Weisbrot: COO Found No Sidekick Employees Knew What They Were Building
“After I hired my COO, he came in and he did a very deep review of the company from many different angles. Interviewing every single one of the employees, you know, to see what their experience has been thus far. And one of the questions he asked them was, do y…”
Weisbrot: Long-Term Release Context Makes Engineering Teams Emotionally Invested
“And so once we did that, it became much easier for them to become emotionally invested in what we were doing, even though before that, you know, they were enjoying the development and they liked the company culture and all that.”