AI 프롬프트: 워크플로우 최적화

Here's my current workflow for [process name]:

[Describe each step, who does it, and how long it takes]

The pain points I notice: [list frustrations]
Deadline pressure: [how often things are late]

Analyze this workflow and give me:
1. The single biggest bottleneck and why it's slowing everything down
2. Three process changes to eliminate or reduce it
3. Which steps can run in parallel instead of sequentially
4. A redesigned workflow with estimated time savings
5. Metrics to track so I know the optimization is working

I need to document this process that currently exists only in people's heads:

Process: [name and purpose]
People involved: [roles]
Tools used: [software/apps]
Frequency: [how often this process runs]

Create:
1. A step-by-step process document with clear ownership at each step
2. Decision points (if X, then do Y; if Z, then do W)
3. A simple flowchart in text/ASCII format
4. Time estimates for each step
5. The "tribal knowledge" questions I should ask the team to fill gaps
6. A checklist version someone new could follow on day one

Here are the recurring meetings on my team's calendar:

[List each meeting: name, frequency, duration, attendees, stated purpose]

Team size: [number]
Primary communication tools: [Slack, email, etc.]

For each meeting, tell me:
1. Keep, shorten, merge, or kill — with specific reasoning
2. What async alternative could replace it (and exact format)
3. If kept: optimal duration, frequency, and attendee list
4. A meeting-free block schedule for deep work
5. Templates for async standups and status updates
6. How to handle the political fallout of canceling someone's meeting

Work gets stuck or lost when it moves between these stages/people:

From [person/team A] to [person/team B]:
- What's handed off: [description]
- Current method: [email, Slack, shared doc, etc.]
- What goes wrong: [common failures]

Design a handoff system that includes:
1. A standardized handoff template with required fields
2. A checklist the sender completes before passing work
3. An acceptance criteria the receiver checks
4. Notification rules (who gets pinged, when, how)
5. An escalation path when handoffs stall
6. A weekly metric to track handoff quality

Here are all the tools/apps my team uses:

[List each tool: name, purpose, cost/month, who uses it, how often]

Pain points: [what's frustrating about current tools]
Budget: [monthly tool budget]
Team size: [number]

Give me:
1. Overlap analysis — which tools do the same thing
2. Consolidation recommendations (fewer tools, same capabilities)
3. Missing tools — gaps that are costing you time
4. A migration plan for switching tools with minimal disruption
5. Cost comparison: current stack vs. optimized stack
6. Integration opportunities between remaining tools

I need an SOP for: [process name]

Who performs this: [role/title]
Frequency: [how often]
Current documentation: [none / outdated doc / tribal knowledge]
Risk if done wrong: [consequences of errors]

Build a complete SOP that includes:
1. Purpose and scope (when to use this SOP)
2. Prerequisites and required access/tools
3. Step-by-step instructions with screenshots placeholders
4. Common mistakes and how to avoid them
5. Troubleshooting section for the top 5 failure scenarios
6. Version history table and review schedule