A position tells you what someone asks for; an interest explains why it matters. We need delivery by Friday may reflect a customer meeting, a crew booking, a reporting deadline, or simple preference. If you negotiate only against the date, you miss options that could satisfy the real need differently.
Good discovery questions are specific, respectful, and connected to decisions. They are not an interrogation or a trick for extracting weakness. The goal is to build a more accurate map of priorities, constraints, risk, and authority so both sides can design workable trades.
Start with purpose and success
Ask what the agreement needs to make possible and how success will be judged. Questions such as What happens after delivery? or Which outcome matters most to your team? reveal the operational purpose behind a term. Listen for audiences, deadlines, measures, and dependencies.
Invite prioritization rather than asking whether everything matters. If we can improve two of speed, customization, and price, which two protect the most value? Ranking questions expose trade space while allowing the other side to explain nuance rather than accept a forced yes-or-no choice.
Explore constraints without challenging legitimacy
Ask which terms are fixed by policy, law, budget cycle, customer promise, or technical limitation, and which are preferred. Follow with Who owns exceptions? and What evidence would they need? This distinguishes a real boundary from a default process that can change with the right case.
Avoid why questions delivered in an accusatory tone. What makes Friday important? often invites more useful detail than Why can't it be Monday? Reflect the answer before proposing a solution, especially if you disagree. People share more when they feel the information will be used accurately.
Map risk and downside
Ask what could make the agreement fail and which risk worries them most. One party may fear late delivery while the other fears uncertain volume. Once risks are visible, terms such as milestones, notice periods, trials, warranties, or shared contingencies can allocate them more intelligently.
Explore past experience carefully: What happened the last time this condition was missing? This can reveal why a seemingly unusual term exists. Do not dismiss historical concern as irrational. Look for a present control that addresses the underlying risk without reproducing an unnecessarily burdensome old solution.
Confirm authority and summarize
Ask how decisions are made, who else must review, and when those people become involved. A productive conversation with someone who lacks approval authority can still help, but you need an agreed path for bringing the package to the actual decision-maker.
Close discovery with a concise summary: It sounds like continuity is first, implementation effort second, and unit price third; legal approval is required for liability changes. Ask them to correct it. A confirmed priority map prevents you from solving the wrong problem during proposal design. Share the summary in writing after the meeting and mark any unverified assumption. That record lets additional approvers correct the map before it hardens into a proposal.
Prepare an eight-question discovery sheet
- Write two questions about the outcome and how success will be used or measured after the agreement.
- Add two ranking questions, two questions about fixed constraints and exception authority, and two questions about failure risk.
- During the conversation, ask one question at a time, take notes, and reflect the answer before advancing your proposal.
- End with a spoken priority-and-authority summary and invite corrections before designing the next package.
Common questions
How many questions are too many?
Ask only questions connected to a decision or proposal. If the other person becomes fatigued, summarize what you have learned and explain why the next question matters.
What if they refuse to share priorities?
Offer transparent hypotheses and conditional packages. Their reaction can reveal preferences, while you continue protecting your own information and avoid inventing motives.
