Build a neutral question path that uncovers workflow, impact, evidence, alternatives, and decision process. 제공할 내용: Customer and meeting context, Offer and qualification boundaries, Meeting design. 예상 결과: A sequenced discovery guide with rationale, follow-ups, skip logic, evidence capture, and timeboxes.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Prepare a neutral, time-boxed discovery question guide from the supplied context.
Verified facts, participants, trigger, interactions, stated needs, unknowns, and sensitivities:
[context]
Capabilities, limits, fit and exclusion criteria, evidence, implementation, and price context:
[offer]
Duration, stage, goal, roles, next decision, tone, recording, and prohibited topics:
[meeting]
Separate confirmed facts from hypotheses. Sequence a small number of open questions through reason for meeting, current workflow, concrete recent example, frequency and consequence, current alternatives, desired outcome and evidence, stakeholders and decision process, constraints and risks, and mutually chosen next step. Do not assume pain, urgency, budget, authority, dissatisfaction, or purchase intent. Avoid leading, compound, manipulative, or interrogative wording. For each primary question state purpose, evidence to capture, neutral follow-ups, red flags, and skip logic. Include permission before sensitive commercial or operational questions and do not solicit unnecessary personal data. Fit all questions and listening time into the duration. Add a note-taking schema that distinguishes direct statement, observed example, inference, commitment, and unknown. End with disqualification and no-next-step conditions.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Customer and meeting context
20-minute first call with Operations Director and Project Lead at a 42-person design agency. They requested follow-up after our handoff webinar. No stated problem, budget, authority, or current tool. Public facts: remote coordinators and brand/web projects. Avoid implying office expansion caused pain.
Offer and qualification boundaries
Workflow product maps requester, owner, accepter, evidence, and escalation; Slack and Teams, no email-only or on-premise support. Best fit is recurring cross-role work. Single agency case exists but must not be used as a guarantee. Pricing starts around GBP 4,800/year but seat count affects it.
Meeting design
Goal: decide whether a 45-minute workflow review is useful. Two sellers attend; one leads, one notes. Ask permission before pricing. No recording. Warm, concise. Leave 3 minutes for next-step choice.
예시 출력
0-2 min — Confirm purpose: “What from the webinar or checklist made this conversation worth scheduling?” Capture their words as a direct statement; do not translate engagement into purchase intent.
2-7 — Current workflow: “Could you walk us through one recent, recurring project handoff from request to acceptance?” Follow with “Who declares it ready?” and “What tells the receiver it is acceptable?” Skip generic problem questions if the example already supplies evidence.
7-11 — Consequence and frequency: “How often does a handoff like that occur?” “When it does not move as expected, what happens next?” Ask for an example or existing measure; do not offer a cost estimate.
11-14 — Alternatives and desired evidence: “How is this handled today?” “What would need to be observably different for a change to be worthwhile?” If the current method works and change has no priority, do not manufacture dissatisfaction.
14-17 — Constraints and process: “Which channels or deployment requirements are non-negotiable?” “Who else would need to assess workflow, security, or commercial fit?” Then ask: “Would it be useful to discuss the rough price range now?” If yes, explain the starting context and seat dependency.
17-20 — Choice: summarize only confirmed points and ask whether a 45-minute review, a resource, or no next step is most useful.
Notes columns: exact statement; recent example; evidence or measure; seller inference; unknown; participant commitment. Disqualify if on-premise or email-only is mandatory. Do not schedule a review if no recurring handoff, no desired change, or participants prefer no next step.
효과가 있는 이유
1
Concrete-example questions replace generic pain statements with inspectable workflow evidence.
2
Skip logic and listening time keep discovery conversational rather than exhaustive.
결과 확인
Are questions open, single-purpose, and free of assumed pain or intent?
Does the guide leave enough time to listen and clarify?
Are direct evidence, inference, commitment, and unknown recorded separately?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Prepare discovery questions from customer context”?
For “Prepare discovery questions from customer context,” prepare Customer and meeting context, Offer and qualification boundaries, and Meeting design. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Prepare discovery questions from customer context” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A sequenced discovery guide with rationale, follow-ups, skip logic, evidence capture, and timeboxes—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Prepare discovery questions from customer context”?
The published test record for “Prepare discovery questions from customer context” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
