Document triggers, inputs, decisions, controls, exceptions, and handoffs before considering automation. 제공할 내용: Current recurring work, Rules and variation, Target process. 예상 결과: A runnable standard process with checklist, exception paths, controls, and improvement measures.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Turn the recurring work into a reusable, human-runnable process.
Trigger, frequency, purpose, people, current steps, tools, time, and outputs:
[work]
Input standards, decisions, exceptions, errors, approvals, sensitive data, and escalation:
[variation]
Quality, turnaround, ownership, audit, allowed tools, and improvement target:
[target]
Map the current process before proposing changes. Separate deterministic steps, judgment, approval, waiting, rework, and exceptions. Return: purpose and trigger; entry criteria; inputs and source of truth; numbered steps with owner, tool, output, control, and expected time only when supplied; decision table; exception/escalation paths; completion definition; handoff and audit record; compact checklist; measures for quality, time, and failure demand; and a small pilot. Identify duplication, bottlenecks, unsafe manual copying, and candidates for templating or automation, but do not automate judgment, approval, credentials, or sensitive-data movement without explicit authorization and controls.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Current recurring work
Every Monday a coordinator prepares the prior week's training attendance report for six department heads. They export CSVs from the learning system, copy rows into a workbook, remove test accounts, map department codes, calculate completion, email a PDF, and archive it. It takes 2–3 hours; only one coordinator knows all steps.
Rules and variation
EmployeeID is sensitive. The learning system is source of truth for attendance; HR directory is source for department. Duplicate enrollments occur. Test accounts have AccountType=Test. Completion means attended required minutes, but late corrections arrive through Wednesday. Department heads may dispute records. Only HR may change department mapping. The coordinator may correct obvious CSV formatting but not attendance facts.
Target process
Report by Monday 14:00 with totals reconciling to source exports and a visible late-correction note. A backup coordinator should run it. Use approved Excel and shared drive only; no new external automation. Keep export filenames and an exception log for audit. Pilot with one backup next week.
예시 출력
Trigger: Monday after the learning-system export is available. Entry criteria: prior-week date range confirmed; learning and HR exports saved read-only with timestamped filenames in the restricted shared folder.
Coordinator records filenames, extraction time, date range, and row counts in RunLog. 2. Import both files into separate Excel Tables; never paste EmployeeID into email/PDF. 3. filter AccountType=Test and record excluded count. 4. Identify duplicate enrollment keys; use the approved rule—currently missing—rather than deleting arbitrarily. 5. Look up department from the HR source; unmatched IDs go to ExceptionLog, not a guessed department. 6. Calculate completion from required minutes; reconcile included+test+exceptions to source rows and record duplicates separately. 7. Produce department summary and late-correction notice. 8. Second-person check verifies period, totals, exception count, and no EmployeeID in PDF. 9. Send PDF by 14:00 and archive PDF, workbook, RunLog, sources, and email evidence.
Decision table: department dispute→log and refer mapping to HR; attendance dispute→retain source fact and request learning-system correction; formatting-only issue→coordinator may normalize and record it; post-Monday corrections→reissue or Wednesday addendum requires owner decision. Pilot: backup runs one week from the checklist while primary observes; measure elapsed time, reconciliation difference, questions, rework, and exceptions. Blocker: approve duplicate rule and correction publication rule before claiming the process is complete.
효과가 있는 이유
1
Mapping judgment and exceptions prevents a happy-path checklist from failing in ordinary cases.
2
Controls and source-of-truth fields make reuse safer than copying an experienced person's undocumented habits.
결과 확인
Can a trained colleague run the process using the stated inputs, decisions, and exception paths?
Are approvals, judgment, sensitive data, and automation boundaries explicit?
Do completion evidence and measures reveal errors and rework?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Turn repetitive work into a reusable process”?
For “Turn repetitive work into a reusable process,” prepare Current recurring work, Rules and variation, and Target process. 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 “Turn repetitive work into a reusable process” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A runnable standard process with checklist, exception paths, controls, and improvement measures—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 “Turn repetitive work into a reusable process”?
The published test record for “Turn repetitive work into a reusable process” 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
