Quick Snapshot — What's on the Table?

• What's the one product launch, flow, or decision that brought you here today?
• Who will be the primary sponsor and final decision-maker for this work? Options: VP Product, VP Design, Head of UX/Research, Product Manager, CRO/Head of Customer, CEO/COO, Other
• Which outcome from that launch most clearly missed expectations? Options: Activation, Feature adoption, Retention/churn, Conversion, Time-to-value, Support volume, Qualitative satisfaction (NPS/CSAT), Other
• How long ago did that launch or change go live? Options: Last 2 weeks, Last month, 1–3 months, 3–6 months, More than 6 months, Not launched yet
• Who on your team would be working with researchers day-to-day (names/roles)?
• If you had to describe in one sentence why you need research now, what would you say?

If This Keeps Happening, What Will Break?

• If you ship another release that fails to gain traction, what will the real cost be to the product and the organization over the next 6–12 months?
• Which internal story is gaining traction about why adoption failed? Options: Market fit, Pricing/packaging, Technical bugs, Poor onboarding, Usability/UX assumptions, Data/analytics gaps, Other
• How does engineering typically respond when research shows the roadmap needs changing? Options: They adapt quickly, They ask for more evidence, They deprioritize research, They push back due to timelines, It causes friction but eventually adapts, Other
• Tell me about a recent decision where evidence lost to 'known' assumptions—what happened and what was the fallout?
• Beyond metrics, how does this problem make you feel about your product's future? Options: Anxious/urgent, Frustrated, Confident we can fix it, Resigned, Other

Who Exactly Are We Trying to Win Over?

• What if the person you think is the decisive user isn't the one actually choosing to adopt—how would that change your priorities?
• List the top 3–5 personas you believe drive successful adoption (include titles, responsibilities, and decision power).
• Which single persona showed the largest gap between expectation and behavior? Options: New/trial user, Power user, Admin/account owner, IT/Integrator, Finance/approver, Customer success contact, Other
• How do those personas typically discover, evaluate, and start using this product or feature?
• Which persona is the hardest to recruit or observe in studies and why?
• When was the last time you directly observed a target persona using the product in their real environment? Options: This week, This month, 1–3 months ago, 3–6 months ago, Longer than 6 months, Never

Tell Me the Real Launch Story

• When you replay the launch in your head, what assumption failed—what surprised you most?
• What hypothesis were you testing with the launch (expected user goals and behaviors)?
• Which quantitative signals did you monitor immediately after launch? Options: Activation rate, Feature usage depth, Time-to-first-value, Churn/retention, Conversion funnel, Support volume/tickets, Other
• Which qualitative signals or direct user quotes stood out and contradicted your expectations?
• Were there product or technical constraints that limited what users could do (and you couldn't easily change post-launch)? Options: Yes—major constraints, Yes—manageable constraints, No significant constraints, Unsure
• If you could re-run that launch with one different assumption, what would it be?

What's Getting in the Way of Acting on Research?

• Why do solid research findings often fail to move the roadmap—what's the single biggest blocker in your org?
• Which of the following have previously stopped research from being implemented? (select all that apply) Options: Timeline pressure, Leadership skepticism, Recruitment misses target users, Findings delivered as long reports, Lack of design/engineering capacity, Conflicting business KPIs, Procurement/budget hurdles, Other
• How do you prefer research findings to arrive so they get immediate traction? Options: Annotated design recommendations, Short prioritized playbook, Recorded sessions + highlighted clips, Working prototypes/mockups, Backlog-ready tickets, Interactive workshop
• How embedded should researchers be with your squads to ensure handoffs happen smoothly? Options: Full sprint embed (daily), Sprint-attending (planning + demos), Weekly sync, On-demand consultancy, Not embedded—deliverables only
• What would genuinely convince engineering leadership that research speeds rather than slows product velocity?

What Will 'Success' Actually Look Like?

• If a leader asked you to promise one measurable outcome from this engagement, what would you commit to—and what makes that believable?
• Which primary metric(s) must move to call this pilot a success? (select all that matter) Options: Increase activation rate, Improve feature adoption, Reduce churn, Decrease support tickets, Shorten time-to-first-value, Increase conversion, Improve NPS/CSAT
• What percentage or absolute change in those metrics would justify the investment?
• Who needs to sign off on pilot success and what will their acceptance criteria look like? Options: VP Product, VP Design, Head of Eng, Head of Customer Success, CRO/Head of Sales, CEO/COO, Other
• Besides numbers, which qualitative signals will make leadership confident (e.g., specific quotes, recorded task completions, internal alignment)? Options: Convincing user quotes, Observed unblocked task completion, Design-ready recommendations, Cross-functional consensus, Successful integration plan
• How will you validate the metric during the pilot—do you have dashboards, instrumentation, or will we rely on pre/post benchmarks?

Pilot Reality Check — What Would Make This Win?

• What's the smallest, fastest pilot that would either prove research value or prove the current approach is fine?
• Which product flow should the pilot focus on to create the biggest immediate impact? Options: Onboarding/activation, First key task, Billing/upgrade flow, Admin/permissions setup, Core feature X (specify), Other
• What's your ideal pilot length and cadence for two-week cycles versus longer validation? Options: 1 sprint (2 weeks), 2 weeks, 3–4 weeks, 1 month, Multiple 2-week cycles
• Which deliverables would make you able to act within a sprint (select all that apply)? Options: Annotated recommendations mapped to screens, Design-ready mocks/prototypes, Session recordings & highlight clips, Recruitment screener and participant list, Prioritized backlog tickets, Implementation estimate
• Who on your team will be accountable to implement pilot recommendations, and who will be the escalation for tradeoffs?
• What minimum participant mix or sample size would convince stakeholders this pilot is valid?

Money, Timing, and Decision Mechanics

• If the CFO asked you to justify this spend in 30 seconds, what would you say?
• Which commercial model do you prefer for a pilot? Options: Fixed-fee pilot, Time & materials, Outcome-based, Retainer for recurring cycles, Unsure—need guidance
• What internal approval path and budget status should we expect to navigate? Options: Budget already allocated, Requires new budget request, Executive signoff required, Procurement/legal review required, Unsure
• When would you ideally like the work to start? Options: ASAP, In 2 weeks, In 1 month, In 2+ months, Undecided
• Are there legal, security, or privacy constraints that restrict participant recruitment, recordings, or data access? Options: Yes—strict constraints, Yes—manageable with controls, No constraints, Unsure
• Who else should we include in the initial alignment session to avoid rework later (names/roles)? Options: VP Product, VP Design, Head of UX Research, Lead Engineer/Architect, Customer Success Lead, Security/Legal, Other

• Current State & Consequence Alignment
• Pilot Design & Two-week Cycle Workshop
• Solution Experience — Pilot Demo & Validation
• Pilot Decision, Commit & Operational Kickoff

• Recap Preconditions (Current, Consequence, Future)
• Introductions & Meeting Objectives
• Confirm recruitment criteria and contingency plans to meet sample speed and quality targets.
• Define handoff mechanics so recommendations enter engineering sprints as implementable tickets.
• Draft and circulate the pilot protocol (tasks, script, screener, deliverables) for stakeholder review.
• Create the recruitment screener and assign the recruitment owner and timeline.
• Provision staging/test accounts and any feature flags needed for moderated sessions.
• Prepare 2–3 example annotated recommendation artifacts (mock or past) to use in the Solution Experience meeting.
• One-sentence Recap of Preconditions
• Prove that a two-week cycle can deliver prioritized, design-ready recommendations tied to measurable business outcomes.
• Obtain explicit validation from stakeholders that the demonstrated recommendations address the stated consequence.
• Capture required adjustments to the pilot before commit (if any).
• Collect validation responses and record any requested adjustments to the pilot protocol.
• Update deliverable templates and handoff checklist based on feedback from the demo.
• Prepare a short decision memo summarizing the demonstration, validation outcomes, and remaining open items.
• Recap Agreements & Outstanding Items
• Secure formal approval (budget and schedule) to run the pilot.
• Assign and confirm owners for every major pilot activity and handoff point.
• Establish the acceptance criteria and decision gates to measure pilot success and next-phase criteria.
• Complete operational setup so recruitment and session scheduling can begin immediately.
• Execute SOW or purchase order and circulate signed agreements.
• Provision researcher and stakeholder calendars, recording tools, and shared drive with templates.
• Kick off recruitment with the agreed screener and timeline; provide first-week schedule draft.
• Confirm the first sprint integration slot and label which engineering tickets will receive recommended changes for the pilot.
• Produce a single, shared one-sentence current state describing what is broken and who it affects.
• Surface and quantify the business consequence so urgency is explicit.
• Agree on the exact product flow and persona(s) the pilot will exercise.
• Define a one-sentence future state and 2–4 measurable success signals for the pilot.
• Finalize and circulate the one-sentence current state and future state to all participants.
• Provide requested analytics extracts, churn examples, or recordings referenced in the meeting.
• Share staging/test accounts and identify internal product/design/engineering owners for pilot access.
• Confirm target participant list and any off-limits user segments for recruitment.
• Lock down pilot scope, tasks, and explicit success metrics for each two-week cycle.
• Agree the two-week cycle process and the exact artifacts that prove the future state.
• Commercial Terms & Purchase Order
• One-sentence Current State
• Pilot Scope & Core Product Flow Tasks
• Live Walkthrough or Session Replay
• End-to-end Two-week Cycle Example
• Business Consequence & Metrics
• Roles, Responsibilities & RACI
• Two-week Cycle Mechanics
• Concrete Recommendations & Outcome Mapping
• Confirm Target Persona(s) & Product Flow
• Acceptance Criteria & Decision Gates
• Deliverables & Example Artifacts
• Recruitment Criteria & Screener
• Validation Exercise
• Operational Setup: Tools, Calendars, and Channels
• Define Future State (one sentence) & Success Signals
• Pre-work & Data Requests
• Q&A and Edge-case Probing
• Mapping Findings to Consequence
• Confirm Kickoff Date & Immediate Next Steps
• Integration with Engineering Sprints & Decision Gates
• Risks, Dependencies & Contingency Plan

• Moderated Remote Usability Test — Core Flow (5 sessions)
• Unmoderated Task-Based Test with Session Metrics
• Two-Week Remote Diary Study with Daily Entries
• Remote Card Sort with IA Recommendations
• Tree Test for Navigation Paths with Success Rates
• Five In-Depth User Interviews with Thematic Synthesis
• Prototype Validation Sessions with Annotated Fixes
• Annotated Usability Issue Report with Prioritized Fixes
• Sprint-Integrated Two-Week Iterative Usability Cycle
• Customer Journey Map with Behavioral Breakdown
• Design Team Training: Lightweight Usability Methods (Half-Day)
• Prototype Analytics Report with Task Drop-Offs and Heatmaps

Moderated Remote Usability Test — Core Flow (5 sessions)

• Which core product flow should the moderated sessions evaluate (e.g., onboarding, checkout, configuration)?
• What is the primary success metric for the flow being tested? Options: Task success (complete), Time on task, Error rate, Qualitative satisfaction, Other
• Which participant persona(s) should we recruit for these 5 sessions?
• Preferred session length per participant? Options: 30 minutes, 45 minutes, 60 minutes, 90 minutes
• Which artifacts do you require from each session? Options: Video recording, Transcript, Task metrics spreadsheet, Annotated highlights, Raw notes
• Do you need the sessions scheduled to align with a sprint or specific calendar dates? Options: Yes - align to sprint dates, Yes - specific calendar dates, No - flexible within 2 weeks

Unmoderated Task-Based Test with Session Metrics

• How many unique tasks should participants complete in the unmoderated test? Options: 1-3, 4-6, 7-10
• What minimum sample size do you expect for reliable metrics? Options: 20-30, 31-50, 51-100, 100+
• Which metrics are essential to capture (select all that apply)? Options: Completion rate, Time on task, Click path, Success by segment, Drop-off points
• Do you have analytics tooling or device/platform constraints for unmoderated scripts (e.g., mobile only)? Options: Desktop only, Mobile only, Both desktop and mobile, Specific browser/device constraints
• What prototype fidelity will be provided for unmoderated testing? Options: High-fidelity interactive, Mid-fidelity clickable, Screenshots/static
• Do you require automated flagging of failed sessions (e.g., low engagement, rapid abandonment)? Options: Yes, No

Two-Week Remote Diary Study with Daily Entries

• Which participant groups should keep daily entries (power users, new users, churn-risk)?
• What minimum daily entry frequency do you want (per day)? Options: Once per day, Twice per day, Ad-hoc with daily check-in
• What prompts or topics should daily entries cover (pain points, context, screenshots)?
• How will participants submit entries (mobile app, email, web form)? Options: Mobile app, Web form, Email reply, Other
• What incentive model do you prefer to maintain daily compliance? Options: Single completion payment, Tiered completion payments, Gift card per week, Other
• Which deliverables do you expect from the diary study? Options: Daily highlights, Thematic synthesis, Participant quotes & clips, Behavioral timelines

Remote Card Sort with IA Recommendations

• Open or closed card sort? Options: Open (participants create categories), Closed (using your category list), Hybrid
• How many content items or labels will be included in the sort? Options: Under 50, 50-150, 150-300, 300+
• What target sample size do you prefer for reliable IA patterns? Options: 15-20, 21-40, 41-80, 80+
• Do you want card sort outputs mapped into suggested navigation structures (site map & labels)? Options: Yes - site map & labels, Yes - suggested taxonomies only, No - raw results only
• Are there existing IA constraints (legal labels, product categories) we must respect? Options: Yes, No
• What tools or platforms should we use for remote card sorting? Options: OptimalSort, Miro/Manual, Other

Tree Test for Navigation Paths with Success Rates

• Which navigation tasks should we include to validate findability?
• What success rate threshold would indicate acceptable navigation (for you)? Options: >90%, 75-90%, 50-75%, <50%
• How deep is the tree structure (max levels) we will test? Options: 2 levels, 3 levels, 4+ levels
• Do you want segment-based success comparisons (e.g., new vs returning users)? Options: Yes, No
• Which deliverables are required from the tree test? Options: Success rates per task, Time to find, Recommended label changes, Annotated site map
• Any technical constraints for linking the tree test to your prototype or live site?

Five In-Depth User Interviews with Thematic Synthesis

• Which participant profiles should the five interviews represent?
• Preferred interview length per session? Options: 30 minutes, 45 minutes, 60 minutes, 90 minutes
• Which outputs do you expect from the thematic synthesis? Options: Affinity clusters, Top themes and recommendations, Representative quotes, Journey excerpts
• Should interviews be recorded and transcribed for internal reuse? Options: Yes - audio/video with transcript, Yes - audio only, No recordings
• Do you want interview guides or key questions reviewed/approved by your team before fieldwork? Options: Yes, No
• Do you require follow-up affinity mapping sessions with your design team? Options: Yes - facilitated session, No - deliverable only

Prototype Validation Sessions with Annotated Fixes

• What fidelity is the prototype to be validated (static, clickable, coded)? Options: Static screens, Clickable prototype, Partially coded, Fully coded
• How many validation sessions do you want (per prototype)? Options: 3-5, 6-10, 10+
• Which format should annotated fixes take for handoff? Options: Annotated screenshots, JIRA tickets with reproduction steps, Interactive design overlays, All of the above
• Do you require prioritized severity levels on each annotated fix? Options: Yes - severity and effort estimate, Yes - severity only, No
• Should validation sessions be run with product or engineering present for live Q&A? Options: Yes - product present, Yes - engineering present, Prefer observers only
• Do you want a rapid retest after fixes are implemented within the same engagement? Options: Yes - retest within 1 sprint, No - separate engagement

Annotated Usability Issue Report with Prioritized Fixes

• Which prioritization framework should we use (e.g., impact/effort, severity-only)? Options: Impact / Effort, Severity / Frequency, Custom - provide criteria
• What minimum reporting format is required (PDF deck, CSV, JIRA import)? Options: PDF deck, CSV export, JIRA import-ready, Confluence page
• Do you want each issue accompanied by proposed design changes or only problem descriptions? Options: Proposed design changes included, Only problem descriptions, Both where applicable
• How many prioritized fix levels do you want (e.g., critical, high, medium, low)? Options: 3 levels, 4 levels, Simple - Must/Should/Could
• Should we include rough engineering effort estimates for fixes (T-shirt sizing)? Options: Yes - include estimates, No - product will estimate
• Do you need an executive summary with OKR-linked recommendations? Options: Yes - tie to OKRs, No - standard summary

Sprint-Integrated Two-Week Iterative Usability Cycle

• Which sprint framework do you use (e.g., two-week Scrum, Kanban)? Options: Two-week Scrum, One-week sprints, Kanban, Other
• Do you want researchers embedded full-time in the sprint or on a consult basis? Options: Embedded full-time, Consulting engagement per sprint, Hybrid
• How many iterative cycles do you plan to run during the engagement? Options: 1-2 cycles, 3-5 cycles, 5+
• Who will own recruitment coordination each cycle (vendor, client, shared)? Options: Vendor handles recruitment, Client handles recruitment, Shared responsibility
• What integration artifacts are required for engineering handoffs each sprint (JIRA stories, annotated designs)? Options: JIRA stories, Annotated designs, Prototype links, Acceptance criteria
• Do you require a standing demo/review at sprint end to review findings and decide on scope changes? Options: Yes - mandatory, Optional - on request, No

Customer Journey Map with Behavioral Breakdown

• Which persona(s) and lifecycle stages should the journey map cover?
• What channels and touchpoints must be included (web, mobile, email, support)? Options: Web, Mobile, Email, Support, Sales
• Which behavioral metrics should be layered onto the journey (e.g., activation, churn triggers)?
• What level of fidelity do you expect for the journey map deliverable (high-level vs granular step-by-step)? Options: High-level strategic map, Granular step-by-step with moments of truth
• Do you want recommended interventions and metrics tied to each touchpoint? Options: Yes - interventions + metrics, No - journey only
• Who are the primary stakeholders we should interview/engage when building the map?

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Pricing & Payment Schedule
• Acceptance Criteria & Success Metrics
• Responsibilities & RACI
• Integration & Sprint Sync Plan
• Participant Recruitment Agreement
• Data Processing & Security Addendum (DPA)
• Deliverables, IP & Licensing
• Change Order Process
• Decision Gates & Go/No-Go Criteria
• Onboarding & Access Checklist
• Communication & Escalation Plan
• Termination & Transition Agreement
• Renewal & Ongoing Support Agreement

• Outcome Validation Review
• Research Artifacts Handover
• Lightweight Research Training Workshop
• Follow-up Governance & Support Channel Setup

• Opening & Meeting Purpose
• Identify owners and timelines for any remaining actions required for full handover.
• Publish a final outcome report mapping each success signal to evidence (metrics, clips, quotes) and decision.
• List accepted recommendations with owners, priority, and implementation deadlines for engineering/design.
• If not accepted, produce a focused remediation plan with experiments to close gaps within the next cycle.
• Artifact Inventory & Access
• Ensure the client has full access to and understanding of every artifact and how it maps to product decisions.
• Agree on a clear handoff checklist so design and engineering can act directly on recommendations.
• Confirm storage, permissions, and any additional deliverables required post-handover.
• Deliver a single zipped/linked artifact bundle with README mapping each file to the problem it solves.
• Create ticket templates (title, description, acceptance criteria, clips) for designers to convert recommendations into sprint work.
• Provision recording and transcript access for relevant stakeholders and document retention/consent rules.
• One-sentence Future State & Workshop Goals
• Enable a cross-functional team to independently run a rapid two-week usability cycle and produce design-ready recommendations.
• Provide reusable templates (screener, script, synthesis, ticket) and practical experience via practice runs.
• Confirm the first in-house cycle's scope, owner, and timeline with coaching checkpoints.
• Share training materials and templates (screener, moderator script, synthesis sheet, ticket template).
• Assign an internal research lead and schedule the first independent two-week cycle with coaching check-ins.
• Book two 30-minute coaching sessions for the first cycle: mid-cycle observation and post-cycle synthesis review.
• Confirm Channel (Slack/Teams/Email) & Access
• Establish a clear, low-friction channel and protocol for follow-ups so research insights continue to feed product decisions.
• Assign owners for monitoring success signals and define the cadence for progress reviews and decision checkpoints.
• Clarify vendor support boundaries and quick-engagement options for urgent follow-up research needs.
• Create the agreed channel, add stakeholders, and post an onboarding message with governance and triage rules.
• Set up the monitoring dashboard, assign the owner, and schedule recurring review meetings in the calendar.
• Publish the vendor support contact method and retainer/buy-back options with estimated SLAs for future engagements.
• Confirm whether pilot outcomes meet the pre-agreed success signals and produce a formal acceptance decision.
• Surface clear root causes for any shortfalls and agree on remediation or additional validation needed.
• One-sentence Current State
• Current Capability Snapshot
• One-sentence Mapping to Current State & Consequence
• Triage & Escalation Protocol
• Annotated Recommendations Walkthrough
• Monitoring Plan & Dashboard Ownership
• Consequence Recap
• Principles of Rapid Usability Testing
• Review Cadence & Reporting Templates
• Recruitment & Participant Profile Artifacts
• Recruitment & Screener Workshop (hands-on)
• Measured Results vs Success Signals
• Moderation & Observation Techniques (demo + roleplay)
• Vendor Support & Buy-back Options
• Handoff Checklist for Design/Dev
• Gap & Root-cause Analysis
• Commitments, Owners & Close
• Synthesis & Prioritization Template
• Proof of Future State (Concrete Examples)
• Data, Recordings & Consent Storage
• Micro-practice: Run & Synthesize a 30-minute Cycle
• Q&A & Outstanding Clarifications
• Force Validation & Acceptance Questions
• Validation, Feedback & Next Steps
• Decision, Next Steps & Owners