Agency Client Discovery Interview Guide: Uncover Goals, Constraints and Decision Criteria

An agency client discovery interview guide helps an agency understand the problem before proposing the answer. Good discovery clarifies the current situation, desired outcomes, stakeholders, users, evidence, constraints, decision criteria and unresolved uncertainty. It can also reveal that the proposed project is premature or not a fit.

Discovery does not authorize the agency to promise scope, timing, results or specialist conclusions. Treat the interview as evidence gathering and alignment, then route commitments through the agreed proposal and approval process.

Define the discovery decision

State what the interview will inform: whether to proceed, what further research is needed, the shape of a possible brief or which stakeholders must join next. Do not tell participants the meeting will “finalize scope” if important technical, operational or commercial evidence is absent.

Name the agency interview lead, recorder, client sponsor, subject-matter participants and decision owner. Clarify who may recommend, approve or reject the next step. Define the topics outside scope, such as legal advice, final pricing or a technical guarantee.

The consulting discovery questions guide provides broader prompts for advisory contexts. Select only questions relevant to this client rather than performing a questionnaire at them.

Prepare a focused evidence brief

Review the authorized request, existing brief, public context, prior correspondence and relevant artifacts. Write what appears known, what is inferred and what must be verified. This prevents repeated questions while making assumptions visible.

Send the purpose, attendees, topics, duration, capture method and expected output in advance. Ask the client to bring representative evidence such as current workflow examples, baseline measures, decision criteria or known constraints, but avoid requesting sensitive data before secure handling is established.

Prepare a hypothesis map with competing explanations. Discovery should test assumptions, not simply collect statements that support the agency’s preferred service.

Copy this agency client discovery interview guide

AGENCY CLIENT DISCOVERY INTERVIEW

Client / date / interview lead / recorder:
Purpose / authorized capture / intended output:

1. CONTEXT AND TRIGGER
- What is happening now, and what prompted action?
- Who experiences the issue or opportunity directly?

2. DESIRED OUTCOME
- What needs to be different, for whom and by when?
- How would you recognize meaningful progress?

3. CURRENT STATE AND EVIDENCE
- How does the process work today?
- What data, examples or observations support the diagnosis?

4. PRIOR ATTEMPTS AND ALTERNATIVES
- What has been tried? What helped or failed, and in what context?
- What happens if no project starts now?

5. STAKEHOLDERS AND DECISIONS
- Who uses, influences, reviews, approves and can block the work?
- What criteria and evidence will govern the decision?

6. CONSTRAINTS AND RISKS
- What is fixed? What is flexible?
- Which access, data, policy, capability or dependency limits matter?

7. NEXT STEP
- What remains unknown?
- Action / owner / due date / evidence / escalation route:

Leave time to summarize what you heard and invite corrections. Do not end with an implied commitment.

Start with context, trigger and affected people

Ask the client to describe what is happening now and what prompted the conversation. Probe for a specific recent example. Determine who experiences the issue, who performs the current work and who feels downstream effects.

Separate symptoms from the underlying situation. “We need a new website” is a proposed solution. The relevant need may involve unclear positioning, difficult publishing, inaccessible journeys or weak conversion evidence. Ask what led them to the proposed answer without dismissing their expertise.

Use neutral follow-ups: “What makes that important now?”, “Can you walk me through the last occurrence?” and “Who sees it differently?” These reveal context without leading toward your service.

Clarify outcomes and success evidence

Ask what should be different after the work and why that difference matters. Identify the affected audience, observable behavior, quality condition or operational result. Separate outcomes from deliverables: a campaign, brand system or application is an output unless its intended effect is defined.

Explore baseline, measurement method, review period, data owner and limitations. Do not invent quantitative targets to make a proposal look precise. If the client has no baseline, recommend a responsible discovery or measurement step rather than guaranteeing improvement.

The SMART goals examples can help refine an outcome, but the agency and client still need to test whether a metric represents genuine value.

Map the current workflow and evidence

Ask the participant to walk through a recent real case from trigger to completion. Identify roles, systems, handoffs, decisions, wait states, workarounds and failure points. Request representative artifacts where appropriate instead of relying only on generalized descriptions.

Distinguish policy from actual practice. A documented process may not describe how work happens under pressure. Invite the client to explain variation across teams, markets or customer groups.

Record evidence sources and owners. If statements conflict, preserve both and assign verification rather than choosing the version most convenient for the proposal. The agency should not copy confidential client material into unapproved tools.

Explore prior attempts and alternatives

Ask what the client has already tried, what was expected, what happened and what context affected the result. This reduces repeated mistakes and may reveal assets worth preserving. Avoid framing previous providers or internal teams as incompetent based on one account.

Discuss alternatives, including internal delivery, a narrower intervention, a different partner, further research and doing nothing for now. Ask what makes each option credible or difficult. Discovery is stronger when it can identify a non-agency answer.

The win-loss interview questions offer useful patterns for exploring decision criteria without turning the interview into a defense of past choices.

Identify stakeholders and decision criteria

Map users, beneficiaries, operational owners, subject-matter experts, approvers, budget owners, procurement, security, privacy, brand and other relevant reviewers. Ask who is absent from the interview and whose perspective could materially change scope.

For each material decision, record the owner, criteria, required evidence, process and useful deadline. Separate influence from formal authority. A senior attendee’s enthusiasm may not equal procurement, technical or budget approval.

Use a decision log template once choices begin. Do not treat an exploratory comment as consent to a deliverable, schedule or commercial term.

Surface constraints, dependencies and risks

Ask what is fixed and what can move. Cover timing drivers, internal capacity, access, data quality, technology, integrations, localization, accessibility, brand, review cycles, procurement and other project-specific dependencies. Financial detail should come from authorized owners and should not be improvised in interview notes.

For each constraint, record evidence, owner, deadline and consequence. Distinguish a true boundary from a preference and an assumption. Route security, legal or specialist questions to qualified reviewers rather than issuing an agency verdict.

Define escalation triggers for unavailable stakeholders, missing data, expanding scope, conflicting approvals and feasibility concerns. A proposal should make unresolved dependencies visible.

Synthesize without overclaiming

At the end, summarize the situation, desired outcome, evidence, constraints and unknowns in neutral language. Ask participants what is inaccurate or missing. Preserve meaningful disagreement rather than forcing one neat problem statement.

After the session, separate observed facts, client statements, agency interpretations and recommendations. Each recommendation should show the evidence and assumptions behind it. Consider a no-go or smaller next step when essential evidence is absent.

Use qualitative interview coding when several stakeholder interviews must be compared systematically. Do not count repeated opinions as independent proof when participants share the same source.

Capture responsibly and require human review

Discovery can reveal strategy, personal information, customer data and security-sensitive details. Record only when authorized and necessary, with clear notice, appropriate agreement, access controls and retention. Establish a secure route for artifacts before asking the client to share them.

For an authorized discovery interview with visible, consented capture, Kuno can help draft notes, themes and actions for responsible human review. It does not determine scope, feasibility, price or contractual commitments. Explore Kuno

Review AI-assisted notes against the source. Correct names, terminology, commitments and negation errors, and remove sensitive details that the next audience does not need.

Assign next actions, escalation and final QA

Close with explicit actions: missing evidence, stakeholder interviews, feasibility checks, proposal inputs and decision dates. Give each action one owner, a due date and a required output. State the escalation route if an input does not arrive.

Before sharing the discovery summary, verify the client identity, purpose, source links, factual claims, quotes, assumptions, confidentiality markings, scope boundaries and decision authority. Have the interview lead and an appropriate delivery reviewer challenge feasibility; ask the client sponsor to correct the summary.

Use meeting follow-up practices to maintain one reviewed version. The next step should be an explicit decision, not momentum created by ambiguous notes.

Turn an authorized client conversation into a reviewable discovery record. Kuno supports capture and structured drafting while agency leaders, specialists and client decision owners retain final judgment. See Kuno