Choose synchronous, asynchronous, one-to-one, or no action from the required interaction, authority, urgency, and coordination cost. 제공할 내용: Problem and required outcome, People, authority, and interaction, Available channels and costs. 예상 결과: A justified communication choice with prerequisites, alternative workflow, and meeting brief if needed.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Decide whether the stated problem truly needs a meeting.
Facts, decision/question, urgency, consequences, blockers, and resolved state:
[problem]
Knowledge, authority, affected people, conflict, time zones, accessibility, and real-time interaction need:
[people]
Async channels, documents, response windows, meeting/attendance cost, prior attempts, confidentiality, and follow-up:
[options]
Separate information broadcast, feedback collection, collaborative sense-making, negotiation, relationship repair, rapid incident coordination, and authorized decision. A meeting is justified only when synchronous interaction adds material value that a document, form, recorded update, direct message, or decision memo cannot provide within the real deadline. Check whether the problem is actually missing an owner, decision rule, evidence, or prepared proposal; a meeting does not repair those gaps by itself. Compare meeting, asynchronous, one-to-one, and no-action options on required participants, latency, interaction value, record quality, inclusion, privacy, preparation, and total participant-hours. Return: recommendation and confidence; decisive reasons; missing prerequisites; lowest-cost viable workflow; escalation trigger; and, only if a meeting is warranted, purpose, invitees, authority, pre-work, duration, outputs, cancellation rule, and follow-up record.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Problem and required outcome
Product operations wants input on a draft naming convention for 18 dashboard metrics before publishing next Friday. A six-page document contains definitions, examples, and three highlighted questions. The required outcome is comments from Analytics, Finance, and Support, then a final choice by product operations. No active incident or relationship conflict. Current blocker: no one has reviewed the draft. 'Resolved' means all three functions respond or explicitly decline and the owner records final names/rationale by Thursday.
People, authority, and interaction
Analytics and Finance each have one subject-matter reviewer; Support has two possible reviewers but one response is sufficient. Product operations owner Lina decides. Teams are in Shanghai, London, and Toronto. Reviewers need quiet reading and may consult colleagues; no issue requires immediate back-and-forth. One reviewer uses a screen reader. Names are internal but not confidential.
Available channels and costs
SharePoint supports comments and accessible Word export. Teams channel can notify. A 45-minute meeting with six people would cost 4.5 participant-hours and is hard across time zones. No async request has been sent. Proposed response window is three business days. If comments conflict materially, Lina can ask a targeted question or schedule a 20-minute decision call with only relevant reviewers.
예시 출력
Recommendation: do not schedule a meeting yet; use an asynchronous review with high confidence. The work is document-centered, reviewers need independent reading, Lina already has decision authority, the three questions are explicit, and there is a three-business-day window. A six-person call adds 4.5 participant-hours and worsens time-zone/accessibility conditions without solving the present blocker, which is simply that the request has not been sent.
Lowest-cost workflow: Lina posts the accessible Word document and one Teams message stating the decision, the three questions, comment format, and deadline. Assign one named reviewer each for Analytics and Finance and one Support responder; ask every function to mark Complete, No comment, or Decline so silence is not treated as agreement. Reviewers comment in the document, preserving one source of record. Lina groups comments, resolves nonmaterial wording, and records final names and rationale by Thursday.
Escalation: if two functions propose incompatible definitions or a comment reveals an unresolved authority/policy issue that cannot be clarified in one targeted thread by Wednesday noon, schedule a 20-minute call with Lina and only affected reviewers. Required pre-work is the conflict table and two options. Cancel if the conflict resolves asynchronously. Output is a documented decision, dissent, and follow-up owner—not another general review.
효과가 있는 이유
1
Classifying the interaction needed distinguishes a decision conversation from information that merely needs distribution.
2
Participant-hour comparison makes recurring coordination cost visible beside response speed.
결과 확인
Is synchronous interaction linked to a concrete value such as negotiation, rapid coordination, or live decision authority?
Were missing evidence, owner, proposal, or decision rule treated as prerequisites rather than agenda items by default?
Does the chosen workflow minimize participant cost while preserving inclusion, privacy, speed, and an auditable record?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Decide whether a problem needs a meeting”?
For “Decide whether a problem needs a meeting,” prepare Problem and required outcome, People, authority, and interaction, and Available channels and costs. 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 “Decide whether a problem needs a meeting” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A justified communication choice with prerequisites, alternative workflow, and meeting brief if needed—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 “Decide whether a problem needs a meeting”?
The published test record for “Decide whether a problem needs a meeting” 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
