Prioritize tasks by impact, urgency, and effort

작성자: AILesson5 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Rank work with transparent evidence, dependencies, deadlines, and uncertainty instead of a false universal score. 제공할 내용: Tasks and evidence, Capacity and planning horizon, Priority rules. 예상 결과: A justified priority order, do-now set, sequencing map, and information gaps.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Tasks and evidenceCapacity and planning horizonPriority rules

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Prioritize the task list using impact, urgency, effort, and the supplied rules.

Tasks, outcomes, stakeholders, deadline sources, consequences, dependencies, estimates, and confidence:
[tasks]

Available people/time, fixed work, skills, energy, and horizon:
[capacity]

Impact, urgency, effort, risk, obligation, weighting, and tie-break rules:
[criteria]

Normalize task descriptions before ranking. Distinguish true deadlines and obligations from requested or self-imposed dates. Score only dimensions supported by the inputs; label unknowns and show rationale rather than inventing precision. Account for dependencies, cost of delay, risk reduction, opportunity enablement, and task size. Return a comparison table, priority tiers, recommended sequence within actual capacity, quick wins that do not displace higher-consequence work, tasks to clarify/defer/decline, sensitivity to uncertain estimates, and the first physical action for the top three. Do not let a short low-value task outrank necessary enabling work merely because it is easy.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Tasks and evidence: A Submit statutory filing, hard deadline Fri 17:00, penalty if late, 90 min, data ready. B Fix broken checkout for 6% of mobile sessions, live now, estimate 2–5 h, engineer needed. C Make board slides prettier, requested Thursday, no decision impact stated, 3 h. D Approve supplier renewal by Wednesday to avoid service lapse Friday, 30 min after Legal review. E Ask Legal to finish renewal review, no due date from Legal, 10-min request; D depends on it. F Clear 20 low-priority emails, 45 min. G Analyze cancellation spike, potential revenue impact unknown, 4 h, data extraction first 30 min.
Capacity and planning horizon: One manager has 5 hours today and 4 tomorrow. Engineer has 3 hours today. Legal capacity unknown. Horizon through Friday. Manager cannot fix checkout but can prepare reproduction evidence.
Priority rules: Regulatory or service-continuity obligations outrank convenience. Then active customer harm and material decisions. Use qualitative High/Medium/Low for impact and urgency; effort ranges stay ranges. Tie-break by dependency enablement and earliest cost of delay.

예시 출력

Tier 1: E then D—service continuity. E is a 10-minute enabling request; its urgency is high despite low effort because D cannot proceed without Legal. Confirm Legal's completion date and escalate through the stated process if one exists. B—active harm to 6% of mobile sessions; impact/urgency high, engineering estimate uncertain. Engineer spends the available three hours on reproduction and fix; manager supplies evidence and defines rollback, but completion may require more capacity. A—regulatory, hard Friday deadline, high impact but data-ready and 90 minutes; protect a Wednesday block rather than letting it drift.

Tier 2: G—potentially material but impact unknown; spend only 30 minutes extracting data first, then reprioritize based on magnitude. Tier 3: C—requested date but no decision consequence; clarify minimum useful slide changes or defer. F—low impact; batch only in leftover shallow time.

Today's sequence: send E; manager creates checkout reproduction evidence while engineer starts B; reserve 90 minutes for A; extract G data; use remaining manager capacity for D if Legal returns or for checkout coordination. Sensitivity: if B exceeds three hours, customer-harm mitigation/rollback decision becomes the priority rather than pretending the fix will finish. First actions: E—send a request naming service-lapse date; B—capture affected device/session reproduction; A—open filing checklist and verify submission credentials.

효과가 있는 이유

1
Deadline-source and evidence fields prevent loud requests from masquerading as objective urgency.
2
Dependency-aware sequencing recognizes enabling work that simple score sorting misses.

결과 확인

Are impact, urgency, and effort rationales tied to supplied evidence?
Were real deadlines, requested dates, dependencies, and unknowns distinguished?
Does the proposed sequence fit actual capacity and honor enabling work?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Prioritize tasks by impact, urgency, and effort”?

For “Prioritize tasks by impact, urgency, and effort,” prepare Tasks and evidence, Capacity and planning horizon, and Priority rules. 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 “Prioritize tasks by impact, urgency, and effort” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A justified priority order, do-now set, sequencing map, and information gaps—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 “Prioritize tasks by impact, urgency, and effort”?

The published test record for “Prioritize tasks by impact, urgency, and effort” 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.

더 많은 탐색 방법