Creating A Product Development Framework Focused On Customers

Michael Margolis has been a UX research partner at GV (Google Ventures) for nearly 15 years, and through his hands-on work with over 300 startups has developed a unique approach to helping founders identify their “bullseye customer”—the specific subset of their target market who initially is most likely to adopt their product. In our conversation, Michael shares: 🔸 The step-by-step process of running a bullseye customer sprint 🔸 Practical tips for conducting effective customer interviews 🔸 The most common mistakes founders make when picking their first customers 🔸 The power of “watch parties” in aligning teams around customer insights 🔸 How to apply these methods beyond typical tech startups 🔸 Much more Listen now 👇 - YouTube: https://lnkd.in/gwJ6vMfm - Spotify: https://lnkd.in/gpZgzVfc - Apple: https://lnkd.in/g493bRqG Thank you to our wonderful sponsors for supporting the podcast: 🏆 Eppo — Run reliable, impactful experiments: https://www.geteppo.com/ 🏆 Paragon — Ship every SaaS integration your customers want: https://lnkd.in/geirC2qS 🏆 Enterpret — Transform customer feedback into product growth: https://lnkd.in/gjz_mCJt Some key takeaways: 1. Instead of a long, drawn-out research process, you can identify your ideal customer by doing a one-day sprint with your whole team. The process involves five qualitative interviews with your bullseye customers and watching them as a team in real time. This speeds up learning and ensures that the whole team gets aligned around the same insights. 2. The bullseye customer is more specific than a typical ideal customer profile (ICP). It’s an even more narrow subset of your target market most likely to initially adopt your product. Focusing on this narrow group helps you prioritize product development, align teams, and accelerate learning. 3. When validating your ideas, don’t get stuck on perfecting a single prototype. Instead, create at least three different versions to test. This helps you see what resonates most with your bullseye customer and allows your team to avoid getting too attached to one concept. 4. One of the biggest advantages of doing the bullseye sprint is learning how to recognize rejection early. Pay attention to signs of indifference during customer interviews. When you hear, “Oh yeah, I guess that would be nice,” or something similarly noncommittal, that’s your cue to move on. You’re looking for customers who are ready to say, “Take my money—where do I sign up?” 5. The way you approach customer research should differ from sales. Practice humble inquiry—ask questions as if you’re learning, not selling. Be vulnerable and embrace the fact that you don’t know everything. Your goal should be to learn, not to pitch. 6. Before diving into interviews, get everyone to predict what they think they’re going to learn.

I've seen my fair share of product development processes. JPD's approach stands out as particularly principled and well thought out. Here are the five most important things about how they build product: 𝗙𝗮𝗰𝗲𝘁 𝗢𝗻𝗲 - 𝗧𝗵𝗲 𝗟𝗶𝗴𝗵𝘁𝗵𝗼𝘂𝘀𝗲 𝗣𝗵𝗶𝗹𝗼𝘀𝗼𝗽𝗵𝘆 As Catalin Bridinel, Head of Design, explains: "The product is a ship, and the user is a lighthouse that gives you direction." This is more than a cute metaphor - it's a fundamental operating principle that multiple interviewees brought up. It manifested, for instance, in the early access program stages: Step 1 - Deep dive with 10 carefully selected customers Step 2 - Expand to 100 customers for broader validation Step 3 - Then 1000 and GA And it does in a million little other ways. 𝗙𝗮𝗰𝗲𝘁 𝗧𝘄𝗼 - 𝗧𝗵𝗲 𝗧𝗲𝗮𝗺 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 They have Five Autonomous Squads: 1. PM Experience Squad: Focused on core product manager workflows 2. Admin Experience Squad: Handling the critical but often overlooked admin experience 3. Cross-flow Integration Squad: Making JPD play well with the broader Jira ecosystem 4. Infrastructure Squad: Ensuring performance at scale 5. Growth Squad: Driving adoption and expansion Having each squad own specific components end-to-end has transformed their development process. As Edouard Kaiser, Head of Engineering, put it: "Before, everyone owned everything - which meant no one owned anything." JPD operates with a surprisingly lean team of about 50 people, including just 3 PMs (plus Tanguy). 𝗙𝗮𝗰𝗲𝘁 𝗧𝗵𝗿𝗲𝗲 - 𝗧𝗵𝗲 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗖𝗮𝗱𝗲𝗻𝗰𝗲 Instead of rigid quarterly planning, they've adopted a "nested timeframe" approach: 1. Strategic Planning (Every 6 Months): - Create opportunity solution trees - Define key strategic bets - Align on major initiatives 2. Weekly Rhythm: - Monday: PM Loom updates (3-5 minutes each) - Wednesday: PM sparring sessions - Friday: "Dojo" sessions for deep dives 𝗙𝗮𝗰𝗲𝘁 𝗙𝗼𝘂𝗿 - 𝗧𝗵𝗲 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 𝗘𝗻𝗴𝗶𝗻𝗲 They stay connected. 1. Weekly PM Rotation: - One PM owns all feedback channels - Monitors community posts - Reviews support tickets - Catalogues sales feedback 2. Video-First Customer Understanding: - Every product decision includes customer video clips - Regular customer interview reels - Visual evidence over written summaries This allows PMs to have a near-Tanguy level knowledge and understanding of the product. 𝗙𝗮𝗰𝗲𝘁 𝗙𝗶𝘃𝗲 - 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗶𝗻 𝗣𝘂𝗯𝗹𝗶𝗰 In a delightful bit of dogfooding, JPD uses their own product to manage their development process. Their public roadmap isn't just a marketing tool - it's their actual working document. This transparency creates an interesting dynamic: they're building a product management tool while publicly showing how they manage their own product. It's a level of authenticity that I find refreshing.

Transforming Global Capability Center into World-Class Product Development Center: The Power of Customer Empathy Building a high-performing Global Capability Center (GCC) isn’t just about hiring great talent—it’s about instilling a customer-first mindset and creating a culture of ownership, innovation, and purpose. At Intuit, we turned our GCC into a product innovation powerhouse by embedding customer awareness and empathy into everything we did. Here’s how we bridged the gap between remote teams and real users: 1. Customer Connections Every U.S. visit wasn’t just about meetings. Team members were tasked with meeting real customers, learning their challenges, and sharing their insights with the team back home. These stories ignited empathy and shaped the way we built solutions. 2. Customer Booths in the Office We brought the customer voice directly into the GCC. A customer listening booth allowed employees to hear real call center conversations, making customer challenges tangible and actionable. 3. Purpose-Driven Innovation Our hackathons focused on real customer pain points. Teams picked specific problems and designed impactful solutions, driving a culture of customer-focused creativity. These kinds of initiatives complemented with a clear OKR framework that keeps the focus on outcomes can help you transform a GCC: Objective: Build a GCC that deeply understands customers and solves real-world problems. • Key Result 1: Facilitate N+ direct customer interactions annually for GCC team members. • Key Result 2: Identify and solve 10 top customer pain points through innovation initiatives with delightful solutions. • Key Result 3: Increase customer satisfaction (CSAT) for GCC-developed solutions by 25%. The result? A GCC that doesn’t just support product development—it leads the way, creating impactful, customer-centered solutions that matter. Takeaway: A truly customer-centric GCC doesn’t just deliver—it empathizes, innovates, and takes ownership. When you empower, educate and energize remote teams with customer insights and purpose, you transform outcomes and create products that delight. How are you driving customer awareness and innovation in your GCC? Zinnov Amita Goyal Karthik Padmanabhan Mohammed Faraz Khan ieswariya k Komal Shah Hani Mukhey Sagar Kulkarni Veerendra Baligeri Namita Adavi Dipanwita Ghosh Rohit Nair Amaresh N.