3.2: 6 Principles for a 60-Min Discovery Call | Lessons from Apple Mentors for AI-Project Managers.

─────────────────────────────────── Find Full Course :    • AI-Technical Project Manager Course: Build...   ─────────────────────────────────── You've sent the agenda. The client pre-filled the worksheet or didn't. The call starts in 60 seconds. Now what? Topic 3.2 is the live protocol the exact framework for running a discovery call from the opening minute to the close. Six principles before the first question is asked. And four signals most TPMs miss completely mid-call. In this video, Shamir joins the call as a real client stakeholder so you can watch every principle applied in a live discovery session, not just described. ───────────────────────────── Timestamps ───────────────────────────── 0:00 — Introduction & Learning Objectives 0:29 — Principle 1: Emotional Intelligence & Building Trust 1:24 — Principle 2: Structured Meeting Facilitation & Agenda Alignment 1:43 — Principle 3: Active Listening & Making Clients Feel Heard 2:09 — Principle 4: Collaborative Discovery & Stakeholder Participation 2:34 — Principle 5: Requirement Validation & Clarification 3:00 — Principle 6: Clear Next Steps & Action-Oriented Closure 3:48 — Live Discovery Call Begins (Shamir joins as client stakeholder) 4:28 — Industry Research Presentation: Competitors & AI Trends 8:50 — Handling Stakeholder Questions Through Active Listening 9:16 — Clarifying Customer Communication Channels 12:26 — Buy vs. Build: Validating the Business Decision Live 13:03 — Budget, Timeline & MVP Framing 20:34 — Co-Creating the Complaint Management Workflow 28:32 — Exploring Return & Replacement Scenarios Together 31:46 — Validating Return Policies & Automation Logic 33:11 — Architecture Direction & Next Action Items 34:35 — Capturing Missed Scope: Phone Calls as a Primary Channel 37:24 — Final Feedback & Discovery Session Close ───────────────────────────── 🧠 PART 1 — Six Principles Before the First Question ───────────────────────────── How you open determines how honestly clients answer. Run these six in sequence trust before structure, structure before questions: 01 Emotional Intelligence — Lower their guard first Acknowledge their time. Reference something specific from their pre-fill. Rapport is not small talk. It is the first requirement. 02 · Structured Execution — Show the shape of the hour Walk the client through the agenda in 60 seconds at the top. Name the sections and time slots. Clients relax when they see a plan. 03 · Active Listening — Make them feel heard Don't interrupt to show you know things. Pause after each answer, then acknowledge specifically. Silence after a complex answer often produces the most useful information. 04 · Collaborative Communication — Co-work, don't interview Frame the session as shared working space not a form they fill out for you. The call should feel like a design session, not an audit. 05 · Requirement Validation — Confirm, never assume After each substantive answer, paraphrase it back: "So what I'm hearing is…" An assumption left unchecked in discovery becomes a change request in month three. 06 · Next Steps & Owners — Clear ownership on close Close every open item with a named owner and a date — not "we'll follow up." Ambiguity on ownership is a project risk. ───────────────────────────── 🎤 PART 2 — What Happened in the Live Call ───────────────────────────── Key moments from the discovery call with Shamir: → Buy vs. Build — Shamir confirmed a 3-month timeline and $25K budget on the call. The right framing led to a decision on the spot: start with out-of-the-box, build phase two. → The Complaint Workflow — Shamir walked through the full in-store process unprompted. Listening without interrupting produced more detail than any question could have. → The Missed Scope — Phone calls handle nearly 50% of complaints. It only surfaced because the session ended with: "Is there anything I haven't covered?" That one question changed the entire product scope. → Shipping Labels, Triage, 24hr Updates — all emerged from one open-ended scenario: "Imagine the ideal system from first touchpoint to resolution." ───────────────────────────── 💡 The Rule That Ties It All Together ───────────────────────────── By the end of the call, your annotated running sheet is your first-draft requirements log — not meeting notes. The difference is everything. ▶️ Next: Topic 3.3 — Post-Call Extraction: Transcript → Structured Requirements ───────────────────────────── 🎓 AI-Native TPM Curriculum by Sahas Pokhrel | Module 3 · Topic 2 of 3 #TPM #DiscoveryCall #TechnicalProjectManager #SPINFramework #ClientMeeting #ProjectManagement #ActiveListening #OtterAI #RequirementsGathering #TPMTips