Jun 8, 2021 · 43m · we-live-to-build
Why We Don't Release Features That Don't Get Used Anymore
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
In this episode of 'We Live To Build,' host Sean Weisbrot and Bonjoro founder Matt Barnett explore essential product management principles, focusing on problem-first scoping, iterative feature staging, and empowering autonomous engineering teams.
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 29.1% of the talking time here. How this is scored →
Sean as informed peer 3.6 Guest teaching 4.4 Guest disagreement 1.6 Sean pushing back 0.9
speaking balance: gold is Sean, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 19:55 Direct challenge to monetization timeline
Matt directly challenges Sean's plan to defer charging for a year, asserting that founders should price their offerings immediately to test true value.
Hardest push from Sean ▶ 36:03 Defending visual mockup presentationsSean refuses Matt's framing that presenting mockups biases discussions, arguing visual aids are essential for helping team members envision the product.
Biggest teaching moment ▶ 19:55 Foundational SaaS pricing schoolingMatt educates Sean on the psychological necessity of early billing, value-linked feature tiers, and iterative price testing in B2B SaaS.
Sean holds their own ▶ 37:37 Articulating high-fidelity specification workflowSean demonstrates practical product expertise by detailing how building high-fidelity Figma prototypes concurrently with written specs uncovers missed edge cases.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Sean as informed peer | Guest teaching | Guest disagreement | Sean pushing back | Why |
|---|---|---|---|---|---|---|
| Matt Barnett's Background and Physical vs. Digital Product Design | 2 | 2 | 0 | 0 | Sean opens with a friendly welcome and invites Matt to share his professional trajectory. Matt outlines his transition from industrial hardware design to digital software products in an agreeable, narrative manner. | |
| Focusing on Problems Over Solutions and Rapid Prototyping | 3 | 4 | 1 | 0 | Matt explains the imperative of focusing on user problems rather than prematurely building solutions. Sean demonstrates comprehension by offering an inventor analogy, validating Matt's rapid prototyping methodology. | |
| Upfront Problem Scoping, Team Synergy, and Embracing Mistakes | 4 | 4 | 1 | 0 | Sean candidly discusses past mistakes in sprint planning and introducing product tools like ProdPad. Matt offers measured advice on not over-engineering internal processes or hiring a dedicated product manager too early. | |
| The Three Stages of Feature Conceptualization and Release Strategy | 4 | 4 | 1 | 0 | Matt outlines a three-tier framework spanning core necessity, expanded features, and product delight. Sean asks sharp, practical follow-up questions regarding staged deployment and beta user management. | |
| SaaS Monetization, Value-Based Pricing, and Behavioral Analytics | 3 | 6 | 3 | 1 | When Sean explains his intention to delay monetization for nearly a year due to competition, Matt directly rejects the premise, urging him to charge early. Matt explains value-based tiering, usage models, and behavioral data tracking. | |
| Structuring the Product Team and Early Engineering Collaboration | 4 | 5 | 2 | 1 | Sean shares how his technical CTO avoids product ideation, leaving wireframes to Sean. Matt educates Sean on the necessity of involving technical leadership early in ideation to build team commitment and prevent engineering roadblocks. | |
| Problem Scoping Workflows and Empowering Autonomous Teams | 5 | 6 | 3 | 4 | Matt warns Sean that showing high-fidelity mockups too early biases team discussions. Sean pushes back, detailing his personal workflow with Figma and functional specifications to proactively resolve edge cases before handing work off. |
Statements from this episode (15)
Matt Barnett: Software Builds Monoliths While Physical Design Retires Products
“Maybe the main difference is that if you're building real world tangible products, you are more likely to build Product suites. So you'll be building new products and new products and new products, and the older products will be like ultimately chucked away af…”
Barnett: Startups fail by jumping to solutions instead of exploring alternatives
“It's one of the reasons why a lot of startups fail. It's not that they've got the problem wrong, and the problem is often there, but by jumping to the solution, they've missed more obvious solutions, easier to build solutions, and better solutions.”
Barnett: Spending more time researching upfront gets product out faster
“If you spend more time on the problems initially, and you spend more time scoping, and you spend more time researching and investigating, it actually ultimately gets you stuff out the door faster. Because it means you're not necessarily making mistakes down th…”
Barnett: Startups should not make a product manager their first hire
“Don't go build all the processes in day one. Don't make your product manager your first hire, muddle through. It's like, you don't make your sales go into the first hire.”
Barnett: Delay Delight Features Until Core Functionality Is Validated
“When you first build features and test features, forget the delight factor, because this is like the icing on the cake. When you know it works, and it's going to go ahead, come back and do that as well.”
Barnett: Shipping Two Baseline Features Outvalues Polishing One Feature
“The total value of me doing stages one and two on two features versus doing stage one to three on one is going to be higher for the end user, and therefore they'll stay along when they spend more money and will grow faster.”
Barnett: Founders should charge as early as possible
“Personally, I think you should charge as soon as possible. I've never seen a founder charge too much of a product or charge too early.”
Barnett: Most B2B software products use free trials over freemium
“Most B to B products are not freemium. Most of them have a free trial and then paid.”
Barnett: Bonjoro has changed its pricing roughly nine times
“We've changed our pricing, I think, nine times.”
Barnett: Biteable has 127 custom plans from monthly pricing tests
“I chatted to a company the other day called Biteable, who are a much bigger video platform. They said they have a 127 different custom plans from all the pricing tests they've done over the last three years. And they're like, well, we can't calm it down, but t…”
Barnett: Founders should not run product as startup grows
“Being a founder and running products as you grow is not a good idea. Because one side of the business is going to suffer. You're either going to get not as much time on products or not as much time on, like, you know, stakeholder management and everything else…”
Barnett: Hire first product manager at 5 to 6 team members
“Product management probably starts to come in when your whole product team starts to get to five plus, six plus. Starts to be a good idea to start to think about this.”
Barnett: Showing mock-ups too early biases product conversations
“So if you're already showing the mock-ups, you already bias the conversation”
Barnett: Bonjoro had to rebuild its platform twice early on
“We like rebuilt that platform twice, which I wish we hadn't done.”
Barnett: Founders must solve hard problems at peak mental energy
“Solving problems Is the hardest thing you can do in the company. It takes the most brain power. So if you come in in the morning and you get straight into emails and you get straight into stakeholder management, you get straight into hiring and everything else…”