Getting Oriented: Why This Matter Right Now

• Tell me briefly what specific adoption or usability concern brought you to consider an external user research pilot today.
• When did this issue first show up after a release, redesign, or other product change? Options: Within 2 weeks, 2 to 8 weeks, 2 to 3 months, Longer than 3 months, Unsure
• Walk me through the last time a customer reported difficulty completing the target task, what happened, and how your team responded.
• Which metrics are you tracking today that would tell you the problem is improving or getting worse? Options: Activation rate, Feature usage per user, Time on task, Support tickets, Churn for the cohort, Other
• If nothing changes in the next quarter, which concrete metric outcome would make you stop pursuing this research path?

Where The Product Falls Short For Real Users

• Which specific user flow or screen do you suspect hides the largest dropoff or confusion, even if dashboards do not show it clearly?
• Describe a recent support ticket, churn conversation, or customer interview that pointed to a usability failure in that flow.
• On a typical sprint, how often do designers or engineers push changes to the flow without an observation of an actual user performing the task? Options: Always, Often, Sometimes, Rarely, Never
• Who on your team currently interprets usability signals from analytics, and what do they usually recommend doing next?
• Which outcome from a small pilot (for example reduced time-to-complete or higher success rate) would convince you to expand research into additional flows? Options: 10% lift in completion, 25% lift, Cut in support volume for the flow, Qualitative evidence of a known blocker, Other

Stakeholders, Budgets, and Decision Power

• If a two-week pilot demonstrated a clear lift in the metric you care about, who could approve funding or scope expansion within your organization and on what timeline?
• Name the roles that must be engaged for a pilot to run smoothly, for example product owner, engineering lead, or data owner. Options: Product lead, Design lead, Engineering lead, Research lead, Legal/compliance, Customer success, Other
• How much budget has already been tentatively allocated to validate usability fixes this quarter, if any? Options: Dedicated budget exists, Contingent on a pilot, No budget yet, needs approval, Unsure
• What internal objections do you expect when researchers recommend changes that shift roadmap priorities?
• Who would need to sign acceptance criteria for the pilot at completion, and what happens if they disagree with the findings?

The Evidence That Changes Minds

• What pattern of results from short usability sessions would prompt engineering or leadership to change an active roadmap item immediately?
• Which deliverable format convinces your designers and engineers to act fastest, annotated designs, video highlights, or prioritized task lists? Options: Annotated design recommendations, Short highlight videos, Prioritized issue backlog, Executive summary with metrics, Other
• Describe a past research finding that was ignored, and why it failed to influence the team.
• To what extent does your engineering cadence allow for design changes within a two-week sprint cycle? Options: Fully supports fast changes, Usually supports some changes, Rarely supports changes, Not possible within current cadence
• Assuming the pilot proves the expected lift, what single organizational step would accelerate contract or scope approval the fastest?

What Could Stop This — Obstacles We Must Face

• Which constraint would make you pause or cancel a usability pilot: recruitment misses, no product test accounts, or leadership blocking time? Options: Recruitment misses, Lack of test accounts, Leadership bandwidth, Security or compliance gating, Other
• How often have recruitment attempts for your target persona failed in the past, and what was the usual cause? Options: Never failed, Rarely, Sometimes, Often, Always failed
• Who owns participant recruitment and screening today, and who will own it during the pilot? Options: Buyer handles recruitment, Seller handles recruitment, Shared ownership, Undecided
• Where would a data privacy or compliance review most likely stall this work? Options: Product access, Participant consent, Internal legal review, Third-party data sharing, Not applicable
• What single readiness gap would stop the engagement from starting on your desired timeline?

Competitive Landscape and Alternatives You Are Considering

• Which of the following options are you actively evaluating as alternatives to hiring an external research partner? Options: In-house research, Existing vendor you're under contract with, Do nothing and monitor metrics, Design sprint without research, Consulting agency focused on strategy, Other
• If you were to stay with your current approach, what evidence would need to be true to justify that decision?
• Has anyone proposed building or expanding your internal research capability instead of running a paid pilot with an external team? Options: Yes, being planned, Yes, proposed but not approved, No one has proposed that, Unsure
• What would have to go wrong with the external pilot for you to prefer the internal option instead?
• Which vendor attributes matter most in your selection, ranked by priority? Options: Speed to recruit, Depth of observation methods, Design-ready recommendations, Price, Cultural fit with engineers, Training handoff

Operational Readiness and Integration Constraints

• Which technical or access requirements must be satisfied before fieldwork can begin, for example test accounts, staging access, or API keys? Options: Test accounts, Staging environment access, API credentials, Feature flags enabled, None required
• Who controls those access points and how quickly can they grant them?
• Are there regulatory, security, or vendor agreements that require legal review before participants can test your product? Options: Yes, legal review required, Yes, security review required, Both, None
• How clean and available is the data that supports recruitment, such as lists of active users or customer segments? Options: Immediately available, Available with effort, Fragmented and slow to access, Not available
• If access or compliance blockers cannot be resolved within two weeks, would you postpone, narrow scope, or cancel the pilot? Options: Postpone, Narrow scope, Cancel, Other
• Which internal owner will be the single point of contact for operational questions during the pilot?

Defining a Practical Pilot Scope

• Which target persona should we prioritize for the pilot based on business impact? Options: New users, Power users, Trial users, Customer success contacts, Admin users, Other
• How many participants do you consider sufficient for a sprint-aligned usability pilot on one flow? Options: 6-8, 10-12, 15-20, Depends on segmentation
• What timeline do you need from kickoff to first findings to keep pace with your roadmap? Options: 1 week, 2 weeks, 3-4 weeks, Longer than 4 weeks
• Which deliverables will make the pilot useful to you: annotated tasks, prioritized backlog tickets, design-ready comps, or recorded sessions? Options: Annotated tasks with screenshots, Prioritized backlog tickets, Design-ready recommendations, Session highlight reel, Executive findings brief
• What acceptance criteria must be met for you to consider the pilot finished and trigger payment or next-phase approval?

Risks, Tradeoffs, and How You Want Them Resolved

• Which tradeoff would you accept for faster results: smaller sample, narrower tasks, or fewer deliverable artifacts? Options: Smaller sample, Narrower tasks, Fewer artifacts, No tradeoffs accepted
• Describe a scenario where findings would be too ambiguous to act on and how you expect the seller to address that.
• Who will be responsible for converting research recommendations into tickets and tracking implementation? Options: Design team, Product manager, Engineering, Shared responsibility, Undecided
• If the pilot finds a critical usability issue that requires roadmap rework, how quickly can you commit to scheduling fixes? Options: Next sprint, Within a month, Next quarter, Depends on severity
• What single unresolved risk would cause you to halt the engagement immediately?

Decision Timing, Procurement, and Next Steps

• Realistically, when do you expect to decide on a partner for this pilot? Options: Within 1 week, 1-2 weeks, 3-4 weeks, Longer than a month
• What procurement or contracting steps must occur before work can begin, and who owns them on your side?
• If the pilot meets the agreed acceptance criteria, what is the fastest timeline in which you would sign for follow-on work? Options: Same week, Within 2 weeks, Within a month, Longer
• Which communications and meeting cadences do you prefer during a pilot: daily standup, twice weekly sync, weekly wrap, or as-needed? Options: Daily standup, Twice weekly sync, Weekly wrap, As-needed
• Who should be the point person we follow up with to finalize scope, timeline, and a pilot statement of work?

• Solution Experience Session

• Confirm the current state and its cost to your team
• You confirm the demonstrated sprint workflow eliminates the post-launch rework you described.
• Deliver a tailored pilot study scope and timeline mapped to the discussed scenario within three business days.
• You confirm the delivered artifacts will be design-ready and mapped to acceptance criteria for immediate sprint planning.
• Walk through the sprint-aligned research flow using your scenario
• Provide the prioritized user scenario, target personas, and any available usage metrics or funnel drop-off data for that flow.
• Confirm the pilot acceptance criteria and success metrics for the study (adoption lift, task completion, qualitative user objections to resolve).
• You agree that the recruitment timeline and sample size meet your expectations for the pilot.
• Prove the design-ready recommendation artifact
• Show how work hands off into your sprint without slowing delivery
• You agree on the remaining evidence required to make a buying decision and the next decision milestone.
• Schedule a decision review with the buying committee within two weeks of receiving the pilot scope.
• Validate alignment explicitly
• Agree next steps and decision criteria

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Pilot Usability Test (Single Product Flow)
• Moderated Remote Usability Sessions
• Unmoderated Prototype Usability Testing
• Target Persona Participant Recruitment
• Customer Discovery Interviews
• Diary Study (Multi‑day Behavioral Logs)
• Card Sorting for Information Architecture
• Tree Testing for Navigation Validation
• Embedded Researcher Support in Sprint
• Annotated Design Recommendations Report
• Prioritized Insight Backlog with Tasks
• Client Training on Lightweight Research Methods

Pilot Usability Test (Single Product Flow)

• For the pilot, which single product flow should we test (for example: signup flow, onboarding checklist, first-time project creation, billing checkout)? Options: Signup / onboarding, First-time project creation, Billing / checkout, Other
• Which success metrics from your analytics should we measure for the pilot (for example: time-to-complete for 'setup_wizard', task completion rate for 'create_project', first-click accuracy on 'billing_page')? Options: Time-to-complete, Task completion rate, First-click accuracy, Error rate
• How many completed moderated sessions do you expect for a meaningful pilot on that flow (typical ranges: 4-6, 8-10, 11-15)? Options: 4-6, 8-10, 11-15, Other
• When must pilot findings be delivered relative to the sprint that owns the flow (for example, by end of the sprint that implements the change, within one sprint after fieldwork)? Options: By end of current sprint (2 weeks), Within 1 sprint (2-4 weeks), Before planned release
• Who will sign off on pilot success and what evidence will they require (for example: 80% task completion on 'create_project', recruitment of N=8 target admins, or validated redesign for the onboarding checklist)?

Moderated Remote Usability Sessions

• Describe your preferred session length and structure for moderated remote sessions (for example: 30-minute task-only, 45-minute task-plus-debrief, 60-minute depth interview plus tasks). Options: 30 minutes, 45 minutes, 60 minutes
• List which internal roles should observe sessions live (product manager, designer, engineer) and whether observers need recording access. Options: Product manager, Designer, Engineer, Customer success
• Do you require live transcription, time-stamped screen recording, or both for each moderated session? Options: Live transcription, Screen recording, Both, None
• Are there specific analytics events we should correlate with session observations (for example: 'signup_complete', 'billing_submit', 'cancel_subscription')?
• Provide any existing moderator guides, task scripts, or example support tickets we should reuse for consistency with your current research artifacts (attach Figma/Docs links).

Unmoderated Prototype Usability Testing

• Include the prototype fidelity we will test (for example: clickable Figma prototype, HTML staging build behind feature flag, or production A/B variant). Options: Clickable Figma prototype, HTML staging build, Feature-flagged staging, Production A/B variant
• Specify the number of unmoderated completions you expect per task to reach statistical confidence for the flow (for example: 20, 50, 100). Options: 20, 50, 100, Other
• Select the device and browser mix to recruit for unmoderated testing (for example: desktop Chrome, iOS Safari, Android Chrome, tablet). Options: Desktop Chrome, iOS Safari, Android Chrome, Tablet Safari/Chrome
• Estimate when unmoderated tasks should be published relative to your sprint demo or release cutoff (for example: 3 days before demo, 1 week before release). Options: 3 days before demo, 1 week before release, Asynchronous, no scheduled deadline
• Identify whether unmoderated results need automated tagging by task outcome (success/fail) and association to analytics events (for example: tag failures to 'checkout_error'). Options: Yes, tag by outcome, No tagging required

Target Persona Participant Recruitment

• List the target persona(s) by job role and product usage for recruitment (for example: enterprise admin who configures org settings, end user who submits invoices weekly).
• Which account-level qualifiers define the target sample (for example: plan tier such as Enterprise, number of seats, active in last 30 days)? Options: Free/Trial, Pro, Enterprise, Other
• Specify mandatory screener criteria we must enforce (for example: performed the target task at least once in last 30 days, has admin privileges, uses feature X).
• How soon do you require the first recruited participants after kickoff (for example: within 3 business days, within 1 week)? Options: Within 3 business days, Within 1 week, Within 2 weeks
• Provide allowed incentive types under your procurement and compliance rules (for example: $50 gift card, service credit, no monetary incentive). Options: $50 gift card, $100 gift card, Service credit, No monetary incentive

Customer Discovery Interviews

• Identify which customer segments to prioritize for discovery interviews (for example: churned customers who cancelled in last 90 days, power users, recent signups). Options: Churned customers, Power users, Recent signups, Support escalations
• Choose the target interview count for discovery (for example: 6-8 exploratory, 9-12 reliable thematic coverage). Options: 6-8, 9-12, 13-20, Other
• Share any artifacts we should use to ground interviews (for example: recent cancellation survey responses, top support tickets, NPS verbatim comments).
• Who on your team will approve the final interview guide and participant list (role, for example: Head of Product, Research Lead)?
• State whether you require interview synthesis to include verbatim quotes mapped to specific product feature requests and exported as a CSV for your roadmap tool. Options: Yes, include CSV of quotes, No, summary only

Diary Study (Multi‑day Behavioral Logs)

• Identify which multi-day behaviors the diary should capture (for example: daily task frequency, steps to generate a recurring report, cross-session workflows).
• Select the diary duration you prefer for behavioral coverage (3 days, 7 days, 14 days, or a custom period). Options: 3 days, 7 days, 14 days, Custom
• Specify the submission medium for diary entries (for example: mobile app journal, web form with screenshot upload, scheduled screen recording). Options: Mobile app journal, Web form, Screen recording, Email log
• Detail how you want diary entries validated against your product data (for example: cross-check time-stamps with analytics event 'report_generated').
• Are there regulatory or compliance constraints we must follow for multi-day logging (for example: GDPR data retention limits, HIPAA constraints)? Options: Yes, No

Card Sorting for Information Architecture

• Identify the information architecture area to study with card sorting (for example: settings taxonomy, help center categories, product features menu). Options: Settings taxonomy, Help center categories, Feature menu, Other
• Which card sort method do you prefer: open card sort, closed card sort against existing labels, or hybrid? Options: Open card sort, Closed card sort, Hybrid
• Specify the target participant count for reliable grouping (for example: 15-20 for initial patterns, 21-30 for stable clusters). Options: 15-20, 21-30, 31+
• What deliverables should accompany the IA recommendations (for example: grouping matrix CSV, recommended navigation labels mapped to menu items, suggested Figma pages)?
• Are we required to align suggested labels to your design system component names or token set before handing off to design? Options: Yes, align to design system, No, separate deliverable

Tree Testing for Navigation Validation

• Identify which navigation paths should be validated with tree testing (for example: top nav to billing page, help center to troubleshooting article, product discovery to feature docs).
• Choose how many tasks per participant you want to run in the tree test (3-5 lightweight, 6-8 thorough). Options: 3-5, 6-8, 9+
• Indicate the success thresholds you consider acceptable for navigation (for example: >70% first-click accuracy to locate billing, <2 clicks on average to reach 'create_project').
• Who will supply the live navigation structure or staging sitemap to use as the test artifact (for example: link to staging sitemap, exported menu JSON)?
• When do you need tree test results available relative to release planning (for example: within 1 week, within 2 weeks, before UI freeze)? Options: Within 1 week, Within 2 weeks, Before UI freeze

Embedded Researcher Support in Sprint

• Select which sprint cadence the embedded researcher will join (for example: 1-week sprint, 2-week sprint, or ad-hoc sprint support). Options: 1-week sprint, 2-week sprint, Ad-hoc
• Assign the percent of researcher capacity you need per sprint (for example: full-time embedded, half-time, or on-call for two days). Options: Full-time, Half-time, On-call (2 days)
• Name the tools we should use for issue capture and handoff while embedded (for example: Jira project key, Confluence page, or shared spreadsheet).
• Share which team member will act as the daily research liaison (role name, for example: Product Designer, Research Lead) to speed decisions and access.
• Detail the onboarding access required for embedding (for example: staging credentials, Figma project, Jira create/edit rights).

Annotated Design Recommendations Report

• For annotated recommendations, what format do you prefer (annotated screenshots, Figma redlines on the affected frames, or a component-level change list with CSS/token notes)? Options: Annotated screenshots, Figma redlines, Component change list / tokens
• Which deliverables are required with the report (for example: one-page executive summary, detailed annotated report, Figma frames ready for implementation)? Options: Executive summary, Annotated detailed report, Figma frames for implementation
• Specify what is explicitly out of scope for the annotated recommendations deliverable (for example: front-end code changes, A/B test implementation, ongoing support after handoff).
• Who must approve the report before it is considered ready for engineering handoff (role, for example: Head of Design, Product Director)?
• Confirm the acceptance evidence required for the report to be marked complete (for example: prioritized tasks imported to your Jira backlog with estimates and attached Figma frames).

Prioritized Insight Backlog with Tasks

• Choose which backlog tool you want tasks exported to when we hand off insights (for example: Jira project, Trello board, your internal ticketing system). Options: Jira, Trello, Other
• How should tasks be prioritized for your roadmap team (for example: impact x effort scoring, risk-first, compliance-driven)? Options: Impact x Effort, Risk-first, Compliance-driven
• What minimal metadata must each insight task include before handoff (for example: clear acceptance criteria, estimated hours, annotated screenshot link, linked analytics event name)?
• Who on your team will own triage and scheduling of the insight backlog once we hand it over (role, for example: Product Manager, Engineering Lead)?
• What acceptance criteria will confirm the backlog is ready for handoff (for example: each task has an owner, an estimate, and an attached design frame in Figma)?

Client Training on Lightweight Research Methods

• Identify the training audience you want to build capability in (for example: product designers, product managers, customer success, product ops). Options: Product designers, Product managers, Customer success, Product ops
• Select the training format you prefer (for example: hands-on workshop, recorded sessions, or paired shadowing during live sessions). Options: Workshop (live), Recorded sessions, Paired shadowing
• How many people should participate per training cohort to remain interactive and practical (for example: 5-8, 9-15, 16+)? Options: 5-8, 9-15, 16+
• Choose which follow-up artifacts you want delivered after training (for example: a reusable playbook, templated screener, moderator scripts). Options: Playbook, Screener templates, Moderator scripts, All of the above
• Measure how you will judge training success (for example: number of internal lightweight studies run in the next quarter, improved confidence scores on a post-training survey). Options: Number of studies run, Post-training confidence survey, Other

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Order Form & Payment Schedule
• Recruitment & Participant Ownership Agreement
• Data Processing Agreement (DPA) — conditional
• Acceptance & Completion Certificate
• Change Order Agreement

• Go-live health check (Week 1-4)
• First measurement review (Week 4-10)
• Acceptance gate review (Day ~90)
• Ongoing quarterly success review

• Create prioritized implementation tasks for the top three backlog items to be addressed next quarter.
• Produce a documented acceptance record listing pass or fail for each Study Scope criterion and the buying owner's decision.
• Create a remediation and re-test plan for any criteria that did not meet targets, with clear resolution deadlines.
• Ensure the evidence package required for the acceptance record is stored in the shared workspace.
• Publish the acceptance decision record and attach the supporting evidence package to the workspace.
• Create remediation tickets for any failed criteria with re-test conditions and deadlines.
• If acceptance is conditional, document the exact re-test timeline and measurements required for closure.
• Backlog status and completion rate
• Confirm backlog completion rate meets the agreed quarterly target or document reasons and recovery plan.
• Verify feature adoption rate for the studied flow is stable or improving and identify any required follow-up tests.
• Ensure open high-severity usability issues are tracked with clear resolution timelines and owners recorded in the backlog.
• Update the tracked backlog with current status, next milestones, and estimated completion dates.
• Publish the quarterly metrics snapshot showing backlog completion rate, feature adoption rate, and open high-severity issues.
• Re-confirm acceptance criteria and owners
• Deployment environment and test access are validated against Study Scope readiness items.
• Recruitment and onboarding progress is documented and any critical blockers have a remediation task and timeline.
• Owners for each outstanding readiness item are named in the shared workspace and timelines are set.
• Publish the validated deployment checklist and participant onboarding status to the shared workspace.
• Create remediation tasks for each critical blocker with expected resolution dates.
• Confirm and document the recruitment cadence and remaining sample targets recorded in Study Scope.
• Present first outcome data against Study Scope targets
• Determine whether task success rate and average time-on-task are trending toward the Study Scope targets or require remediation.
• Identify top 3 root causes for observed gaps with supporting evidence from sessions.
• Agree a set of corrective actions with completion dates that enable a clear path to the acceptance gate.
• Publish the first-measurement data pack including session excerpts, metric calculations, and diagnosis notes.
• Create discrete remediation tasks for each agreed corrective action with target completion dates.
• Schedule the acceptance gate meeting and confirm the evidence required for each Study Scope acceptance criterion.
• Restate acceptance criteria and numeric targets recorded in Study Scope
• Deployment and environment validation
• Present outcome data against each criterion
• Feature adoption and behavioral metrics
• Root cause diagnosis for any metric gaps
• Open high-severity usability issues
• Agree corrective actions and timeline
• Early adoption and recruitment signals
• Document pass/fail and formal acceptance decision
• Confirm timeline to acceptance gate
• Agree remediation plan for failed or conditional criteria
• Agree next-quarter operational actions
• Blockers and open issues
• Agree immediate remediation actions