GTMGO TO MARKETPLAYBOOKS
← All playbooksDiscovery · Field guide

Problem discovery call

Run discovery that produces testable evidence instead of a tour of generic pain points.

When to use this

Use before proposing a solution or building a demo for a new buying situation.

Before the working session

Run the process

01

Contract for the conversation

State the working hypothesis and ask the buyer to correct it. Confirm time, objective, and whether a next step is appropriate.

02

Reconstruct a recent event

Ask: “Walk me through the last time this happened.” Capture trigger, sequence, people, tools, handoffs, duration, workarounds, and where evidence lives.

03

Quantify without leading

Ask what delayed work displaced, how often it recurs, and who feels the consequence. Distinguish a buyer estimate from a measured number.

04

Map the decision

Ask what changed recently, who owns the problem, what alternatives are being considered, what proof is needed, and what would block action. Summarize what you heard and invite correction.

Fictional worked example

Fictional example: A buyer says “reporting is slow.” The operator asks for last Friday’s report: four exports, two manual reconciliations, a missed review deadline, and one operations owner. The agreed next step is to test whether the product can surface the disputed records in a sample file.

Failure checks

Editable workbook and filled example

Establish whether a problem merits a next step by capturing the buyer account of its workflow, consequences and decision process.

Download editable Word workbook ↓

What you will complete

  • Call objective and participant roles
  • Current workflow and trigger
  • Problem in the participant own words
  • Impact and how it could be verified
  • Next decision and authority
  • Agreed next step and permission

Distinguish a direct observation from a statement and a seller inference. Ask before prescribing. Leave impact unknown when it cannot be verified; do not turn an illustrative estimate into a confirmed cost.

Fictional filled evidence record

Observation or statementSource and confidenceFollow-up or contradiction
Fictional analyst copies totals weeklyParticipant statement; not observedAsk for approved workflow demonstration

Fictional action record

Question to resolveEvidence neededBuyer / vendor ownersReview and exit condition
Is copying causing reconciliation errors?Approved walkthrough and error examplesAnalyst / discovery leadClose when actual failure path is understood

Decision and next review

Proceed to one workflow walkthrough, not a solution proposal. The repeated task is described, but neither its error rate nor the buying priority has been established.

Discovery lead confirms permission for an approved walkthrough; buyer analyst supplies a generic workflow. Stop if the problem has no relevant consequence or no owner willing to investigate.

The Word file includes editable response fields and blank tables. These examples are invented and do not represent a real buyer or employer.

See more fictional examples → · Open planning tools →