Become an Epic Product Engineer

Get five people talking about your product - iterative feedback with Ben Vinegar

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Gathering user feedback from multiple sources and aggregating it over time allows product teams to identify recurring issues and opportunities.
  • Building tools for yourself or mimicking user experiences can help understand and improve the product from the user's perspective.
  • Creating accessible channels for feedback and providing incentives encourage genuine user engagement.
  • Automations and AI should support human judgment and connection, not replace them, especially in customer support and product decision-making.
  • A strong product culture includes direct human interactions, such as support rotations and active listening, to foster empathy and better product decisions.
  • The art of saying no and applying personal taste are crucial skills that can't be fully automated or distilled into algorithms.
  • Getting five users to try your product and soliciting detailed feedback from them can significantly improve your product.
  • Even at scale, maintaining personal contact with users—though challenging—is vital for sustained product success.

Summary

Introduction and Personal Background of Ben Vinegar

The episode begins with host Kent C. Dodds introducing Ben Vinegar, a seasoned startup engineer and product leader, emphasizing his focus on product engineering. They recount how they met at Space City JavaScript conference and discuss their long-standing acquaintance dating back to around 2017. Ben shares his career journey, starting from early roles at FreshBooks and Disqus, through his time at Century where he grew the team from five to 400 employees, and his various leadership roles including head of product engineering and VP of Merchant Technology. He describes his background as a hybrid product engineer handling both UI and backend, with a focus on creating impactful products. Ben also talks about his current project, Modem, which he founded to streamline how product teams capture and act on user feedback. He emphasizes the importance of rapid iteration, collecting feedback from diverse channels like Slack, Discord, GitHub, and support tools, to better understand user pain points and opportunities. The discussion underscores his advocacy for close-loop feedback and active listening to users to inform product decisions.

Modem’s Approach to Feedback and Product Development

Ben explains that Modem aggregates signals from multiple communication platforms such as Slack, Discord, GitHub, and customer support channels to provide a unified view of user feedback. This enables development teams to prioritize issues and features based on historical and real-time data, avoiding the pitfall of missing recurring problems. He shares anecdotes about how the tool surfaces critical feedback, like performance complaints, that can be addressed with quick updates, fostering an iterative development process. The conversation highlights how capturing and analyzing feedback at scale allows teams to respond rapidly and maintain a close connection to user needs. Ben emphasizes that his approach aims to scale the human feedback loop, making it manageable for teams to remain responsive without drowning in noise. He also mentions his personal project, Cody, an AI-oriented MCP server, which is in early testing and benefits immensely from direct user feedback, demonstrating his commitment to continuous improvement and user-informed design.

Strategies for Gaining User Feedback and Engagement

The hosts discuss methods for eliciting meaningful user feedback, with Ben advocating for kindness and making it easy for users to give input. He suggests that building tools for oneself or mimicking user experiences can be effective in understanding customer pain points. Ben emphasizes the importance of incentives and creating safe, accessible avenues for feedback – like welcoming community spaces or direct outreach – to foster genuine engagement. Ben shares specific tactics, such as offering early access for feedback, and the importance of responding to users with tangible outcomes to close the feedback loop. They talk about how automations and AI can facilitate relationships in support channels, but human connections are still vital for insights and innovation. The conversation also delves into the culture of support, citing FreshBooks’ support rotation and the value of direct conversations, and discusses how to keep that human touch alive even as automation and AI become more prevalent.

The Role of Human Judgment vs Automation in Product and Support

A key theme revolves around whether AI and automation might replace human judgment in product development and customer support. Ben argues that AI can accelerate and augment human taste and decision-making but should not eliminate human involvement altogether. He cites his own projects, like Hunk, a terminal diff tool, which was built to improve his own workflow and based on his personal taste, illustrating how individual human judgment shapes successful products. Ben stresses that taste, vision, and the ability to say no are irreplaceable, as AI tends to produce median or average solutions. He supports a balanced approach where automation handles repetitive tasks and data collection, freeing humans to focus on meaningful judgment and strategic decisions. He shares an example of how community-driven open-source projects thrive on individual taste, reinforcing his view that human imperfection and discretion are crucial to creating distinctive, valuable products.

Closing Reflections on Product Culture and Actionable Advice

The episode concludes with a reflection on maintaining a strong product culture that values human connection, particularly in customer interactions. Ben shares his experience at FreshBooks, where customer support was deeply integrated into the company culture—support team members actively engaged with users and rotated through support roles to foster empathy and understanding. Kent and Ben agree that automation should facilitate, not replace, human relationships. Ben advocates for leveraging automation to enable more meaningful communication rather than dilute it. As a practical takeaway, Ben recommends that listeners get five people to try their product and talk to them about their experiences, emphasizing the value of direct conversations for improving product and strengthening relationships.

Sponsors

  • Modem · Modem is a platform that helps product engineers access user feedback from various sources like Slack, Discord, GitHub issues, and support channels to enable rapid iteration.

Show notes

If you ship features and never hear what users actually said, this episode is for you. Kent talks with Ben Vinegar - co-founder of Modem, formerly founding engineer and VPE at Sentry - about aggregating feedback, eliminating adoption barriers, and keeping human judgment in the loop as AI speeds up shipping.

They cover FreshBooks-era product engineering, Modem's approach to capturing feedback across Slack, Discord, GitHub, and support tools, and why five real conversations beat a median LLM opinion.

  • (00:00) - Meet Ben Vinegar
  • (01:29) - Career startup guy
  • (03:48) - What Modem is for
  • (06:59) - Building products for builders
  • (12:58) - Aggregating feedback at scale
  • (15:26) - FreshBooks and early product loops
  • (21:34) - Onboarding and getting users unstuck
  • (25:06) - Emerging technology at Sentry
  • (27:59) - Buy a laundromat - go deep on users
  • (33:56) - Support culture and intentionality
  • (39:35) - Human connection in the feedback loop
  • (42:27) - Hunk and accelerating taste with AI
  • (45:12) - Human judgment vs median products
  • (49:43) - Homework: five people talking

Ben Vinegar calls himself a career startup guy - early at FreshBooks, Disqus, and Sentry (first five people through ~400 employees), then head of product engineering, VPE, and VP of emerging technology. He founded Modem (modem.dev) to give product engineers faster access to what users are saying so they can iterate.

The through-line is closed-loop feedback. Successful products Ben has worked on followed make-a-change, get-it-in-front-of-users, adjust, repeat. Modem aggregates signals from Slack Connect, Discord, GitHub issues, Intercom, Zendesk, and similar channels so teams are not hunting screenshots in five tools.

They talk adoption barriers, FreshBooks' support culture, and why human judgment still differentiates when agents can ship median products. Ben's Hunk terminal diff tool story shows taste accelerating with AI: he built what he needed as a "norm core" Mac user who wanted agents running while he closed the laptop. Extreme product bets rarely come from averaged LLM taste.

Homework from Ben, sharpened by Kent: get five people to try your software - and talk with them about their experience using it.

Homework

  • Pick something you shipped (or are about to ship).
  • Get five people to try it.
  • Talk with those five people about their experience using your software - not just whether they clicked install.

Resources

Guest: Ben Vinegar

Host: Kent C. Dodds

See on Epic Product Engineer

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file