Stakeholder Interviews for AI Discovery Sprints: A Fixed-Fee Week-1 Plan

A fixed-fee AI discovery sprint rarely breaks because the interview guide is weak. It breaks because six senior stakeholders fill the calendar, frontline reality arrives too late, and Friday becomes a choice between rushed synthesis and unpaid work. Week-one capacity determines the credibility of the entire sprint.

Why Calendar-First Stakeholder Interviews Fail

Most teams schedule whoever is easiest to reach: the sponsor, several department heads, and one helpful technical lead. That produces a polished account of the organization’s AI ambitions, not evidence of how work, data, and informal AI use actually operate.

The second failure is arithmetic. One researcher can usually run five or six useful stakeholder interviews in a week after scheduling, preparation, note cleanup, and internal check-ins. Manual synthesis then adds several days—or weeks if recordings and notes sit untouched while delivery work continues.

This is the common failure mode: a small research team books eight interviews, but rescheduling and a security review whittle that down to five completed sessions and a Friday transcript backlog. The resulting read overstates leadership’s automation priority, because only one frontline operator ever got heard.

That is the broader stakeholder interview overflow problem in a sold AI readiness audit: scope is fixed before the real number of necessary voices becomes visible. A full calendar is not representative coverage.

Interview Decision Layers, Not Just Departments

I divide stakeholders by the evidence they hold. Leadership explains strategic intent and investment constraints; frontline staff reveal actual workflows and workarounds; IT and data owners establish what is technically available, permitted, reliable, and governable.

A credible week-one sample

• Leadership: 3 interviews. Include the executive sponsor, one business-unit owner, and one risk, finance, or operations leader who can challenge the sponsor’s assumptions.
• Frontline staff: 6–10 interviews. Select people performing high-volume, judgment-heavy, or document-intensive work across at least two teams.
• IT and data owners: 3–5 interviews. Cover architecture, security or compliance, and the owner of the data behind the most promising workflows.

Six interviews can support a narrow diagnostic: two leaders, three frontline staff, and one IT or data owner. It cannot credibly represent a multi-function organization. For a normal fixed-fee sprint, I target 12–18 stakeholders and expand further when roles, regions, or business units differ materially.

Do not sample frontline staff solely through their managers. Ask leaders for nominations, then add people identified through workflow dependencies and interview referrals; otherwise, you get articulate champions while quiet skeptics and workaround-heavy teams remain invisible.

The Interview Order Should Challenge the Brief by Wednesday

The wrong sequence leaves all technical constraints until Thursday or lets executive language shape every later question. Start with intent, test feasibility immediately, then investigate work.

A practical five-day sequence

1. Monday: Run two leadership interviews, define the decisions the sprint must support, and map candidate workflows, affected roles, data dependencies, and known risks.
2. Tuesday: Interview one or two IT/data owners and two frontline staff. Use technical evidence to test whether leadership’s priority workflows are accessible and safe enough to pursue.
3. Wednesday: Concentrate on four to six frontline interviews. Follow repeated handoffs, duplicate entry, review loops, undocumented tools, and moments where judgment overrides the official process.
4. Thursday: Fill evidence gaps with remaining frontline, security, compliance, or data interviews. Begin structured analysis rather than waiting for every session to finish.
5. Friday: Triangulate findings, score opportunities, document disagreements, and prepare a decision-focused playback with explicit confidence levels.

At hand-run capacity, this schedule compresses quickly: five or six sessions consume most of the week before synthesis starts. I use AI-moderated interviews through Usercall when broader coverage is necessary, while retaining researcher control over the guide, probes, audience, and analysis framework. This is how Usercall runs AI readiness interviews with stakeholders.

Every Session Must Produce Workflow Evidence, Not AI Opinions

Asking “Where could AI help?” invites speculative wish lists. I ask stakeholders to reconstruct a recent piece of work, show where information entered and changed hands, and explain the last exception that forced human judgment.

A 35-minute stakeholder interview structure

1. Role and accountability, 3 minutes: What outcomes does this person own, and what failure would reach their manager or customer?
2. Recent workflow, 10 minutes: Reconstruct one real case from trigger to completion, including systems, handoffs, waiting, and rework.
3. Current AI use, 7 minutes: Ask what tools were used in the last 30 days, for which tasks, with what inputs, and whether usage was approved.
4. Constraints and risk, 8 minutes: Probe data quality, permissions, sensitive information, review requirements, and consequences of an incorrect output.
5. Opportunity and proof, 5 minutes: Identify one change worth testing and the metric or observable behavior that would demonstrate value.
6. Referral, 2 minutes: Ask who sees the workflow differently and which artifact would verify the account.

Behavior beats sentiment. “Our team is enthusiastic about copilots” is weak evidence; “seven analysts paste public filings into an approved model, then spend 20 minutes checking every citation” is usable discovery data.

Synthesis Must Preserve Disagreement Instead of Averaging It Away

A theme count alone is not research-grade synthesis. Ten mentions of “data access” may describe ten different problems: missing permissions, inaccessible formats, uncertain ownership, poor quality, or a policy nobody understands.

The five fields I synthesize for every finding

• Claim: The precise workflow condition or behavior observed.
• Evidence: Quotes, reconstructed examples, artifacts, and relevant product or operational data.
• Coverage: Which roles, teams, and business units reported it—and which did not.
• Contradiction: Where leadership, frontline, and technical accounts conflict.
• Decision implication: Invest, test, educate, govern, sequence later, or stop.

I then score opportunities on business value, workflow frequency, data readiness, adoption friction, and risk. The output should distinguish high-confidence actions from hypotheses requiring a prototype, data audit, or additional interviews.

Usercall once ran 100 interviews with internal stakeholders at a financial consulting firm to assess how AI was actually being used across the organization. The practical constraint was breadth: usage varied across roles, and investment decisions had to cover both tools and education; once interview volume was no longer the bottleneck, the firm could base priorities on organization-wide evidence rather than a handful of confident voices.

Fixed Fees Should Cap Decisions, Not the Number of Voices

The cleanest sprint contract defines the decisions, deliverables, research window, and included synthesis—not an artificially tiny interview count. Five conversations may surface hypotheses, but dozens of voices create legitimacy when leaders must fund tools, change workflows, or enforce new controls.

My week-one standard is simple: hear all three decision layers, challenge the brief by Wednesday, synthesize continuously, and expand capacity before representation becomes the hidden compromise. That works whether you lead a boutique consultancy or are driving AI readiness inside your own company.

Related: When the sold AI readiness audit needs more stakeholder interviews than your team can run by hand that week · stakeholder interviews for organizational diagnostics

Usercall runs AI-moderated user interviews that collect qualitative insights at scale, with deep researcher controls and the depth of a real conversation—without the overhead of a research agency. Use it to expand stakeholder coverage, analyze qualitative evidence at research-grade depth, and intercept people at key analytic moments to explain the “why” behind operational metrics.