Charles Wilson

Ever launch a new product feature that seemed solid—until a small, overlooked detail broke everything? In this episode, Teresa Torres and Petra Wille share their real-world experiences wrangling global invoicing and taxes while running small, international businesses. What starts as a rant about EU tax compliance turns into a sharp product lesson: how failing to map the entire path to customer value—down to the tiniest regulatory requirement—can kill your product’s usefulness. Whether you’re shipping code or selling courses, this conversation will remind you that sweating the details isn’t about perfectionism—it’s about ensuring your product actually delivers value at the moment that matters. In this episode: - The nightmare of global invoicing for small online businesses - Why even big platforms (like Squarespace and Teachable) miss the mark on EU tax compliance - How Petra and Teresa navigated invoicing across borders with Ableify and LearnWorlds - The key difference between meeting regulations and meeting customer needs - What product teams can learn from regulatory edge cases - How missing a single detail can block the “moment of value creation” - Why story mapping is critical for finding gaps between “we shipped it” and “customers got value” Key takeaways: - Customers define value, not your compliance checklist. - Regulatory work still requires discovery—you can’t skip understanding user needs. - The path to value doesn’t end when your feature works; it ends when your customer succeeds. - “Sweating the details” isn’t micromanagement—it’s good product management. Memorable quotes: “If you don’t sweat the details, people choose other platforms.” — Petra Wille “It’s not a little detail when your client won’t pay the invoice.” — Teresa Torres Watch or listen to this episode: YouTube: buff.ly/DRVEfiJ Apple Podcasts: buff.ly/x24rdd7 Spotify: buff.ly/7nkwwSJ

"Discovery doesn't come at the expense of delivery. Both activities should happen in tandem to achieve the best results." 🔄 Explore the 7 most common reasons product teams struggle to make time for discovery: 1. Too focused on delivery activities 📊 2. Excessive stakeholder management 👥 3. Constant cross-team coordination 🤝 4. Overwhelmed by product support tasks 🆘 5. Trapped in endless meetings ⏰ 6. Discovery not valued by the organization 🏢 7. Discovery process itself takes too long 🐌 Learn practical tips to overcome these challenges and integrate discovery into your workflow. Watch the video or read the transcript: buff.ly/CpcndG2 🤔 Which of these reasons resonates most with your team's experience? Share your thoughts in the comments below.