Training Expectations

The podcast discusses the limitations and realistic outcomes of short training sessions, particularly in the context of complex skills like continuous product discovery and managing up. It emphasizes that while one-hour talks or brief workshops can inspire and introduce high-level concepts, they cannot instill deep expertise or lasting behavioral change. Continuous discovery, for example, involves mastering 13 distinct habits that require ongoing practice, repetition, and a supportive environment - elements that cannot be achieved through a single session.

The discussion also highlights common misconceptions among teams and organizations about what training can deliver. Many request training without fully understanding their skill gaps, leading to mismatched expectations. Short sessions may offer awareness or motivation for small behavior changes, but they cannot replace long-term coaching or address systemic barriers such as lack of leadership alignment or access to customers. To be effective, training must be part of a broader, structured learning journey that includes practice, feedback, and organizational support.

• What if you ran a 30-minute discovery audit with 3 team members before your next client talk?

  • Move: Reach out to 3 key team members (product, dev, UX) and schedule 20 - 30 minute 1:1 discovery calls using a simple script: "What's one thing slowing you down in building the right product?"
  • Why Now?: Most training fails because it's based on assumptions; real pain points surface only through direct, lightweight conversations - before you commit to a talk or workshop.
  • Expected Upside: You'll uncover 1 - 2 concrete blockers (e.g., no customer access, stakeholder mandates) and tailor your talk to address real needs, increasing engagement and perceived value.

• What if you redesigned your next 1-hour talk to end with 30 minutes of facilitated Q&A?

  • Move: Structure your talk as 30 minutes of content + 30 minutes of moderated Q&A, and ask the client to assign a facilitator to collect and prioritize audience questions in real time.
  • Why Now?: Q&A exposes systemic issues (e.g., "We can't talk to customers") that reveal whether discovery training is even feasible - letting you pivot to consulting or pre-work instead of generic advice.
  • Expected Upside: You'll convert a passive session into a diagnostic tool, positioning yourself as a problem-solver and opening doors to deeper, paid engagements.

• What if you packaged a single continuous discovery habit into a 7-day micro-challenge for solo developers?

  • Move: Create a self-guided email sequence or Notion template that walks a solo dev through one habit (e.g., "Run 1 customer interview this week") with templates, outreach scripts, and reflection prompts.
  • Why Now?: Most devs are overwhelmed by "13 habits" - focusing on one actionable behavior lowers the barrier to entry and builds momentum without requiring team buy-in.
  • Expected Upside: You'll generate a low-cost, scalable offer that demonstrates value quickly, builds trust, and converts users into paying customers for deeper training or tools.

• Schedule short discovery calls with 3 team members before any training or speaking engagement to identify real pain points and tailor your approach accordingly.
• Structure all presentations with a 1:1 ratio of content to Q&A time (e.g., 30 minutes talk, 30 minutes Q&A) to surface organizational blockers and increase practical impact.
• Offer a single, narrowly focused habit from continuous discovery (e.g., conducting one customer interview per week) rather than promising full mastery, making adoption achievable for solo practitioners.
• Clearly communicate the limitations of short sessions by providing a written summary of what can and cannot be achieved in one hour, setting realistic expectations with clients.
• Design follow-up micro-practices (e.g., a 5-day email sequence with one actionable step per day) to reinforce habit formation after a talk, bridging the gap between inspiration and skill development.