AI 提示詞： 工作流程優化

**Role:** You are a process improvement consultant specializing in constraint analysis.

**My Workflow:**
[Describe each step: what happens, who does it, how long it takes, and who it passes to next]

**Pain Points I Notice:** [list frustrations]
**How Often Things Are Late:** [frequency]
**Team Size:** [number of people involved]

**Analyze My Workflow:**
1. **The Bottleneck:** The single biggest constraint and why it's slowing everything downstream — with evidence from the workflow you described
2. **Root Cause:** Why this bottleneck exists (capacity? skill? dependency? approval queue?)
3. **Three Fixes:** Process changes to eliminate or reduce the bottleneck, ranked by impact and effort
4. **Parallel Opportunities:** Steps currently running sequentially that could run simultaneously
5. **Redesigned Workflow:** A streamlined version with estimated time savings per cycle
6. **Tracking Metrics:** 2-3 specific numbers to measure weekly so you know the optimization is working

**Role:** You are a process documentation specialist converting informal knowledge into structured docs.

**Process:** [name and purpose]
**People Involved:** [roles, not names]
**Tools Used:** [software/apps at each step]
**Frequency:** [how often this process runs]
**Current Documentation:** [none / outdated doc / in someone's head]

**Create Process Documentation:**
1. **Step-by-Step Procedure:** Numbered steps with clear ownership, inputs, outputs, and tools at each step
2. **Decision Trees:** If/then branches for common variations (if X, do Y; if Z, do W)
3. **Flowchart (Text):** An ASCII or markdown-table flowchart showing the process visually
4. **Time Estimates:** How long each step should take, and total process cycle time
5. **Tribal Knowledge Questions:** The 10 questions to ask the team to fill gaps in your documentation
6. **Day-One Checklist:** A simplified version a new hire could follow on their first day without asking questions

**Role:** You are a meeting efficiency consultant who isn't afraid to recommend canceling things.

**My Team's Recurring Meetings:**
[List each: name, frequency, duration, number of attendees, stated purpose]

**Team Size:** [number]
**Communication Tools:** [Slack, email, project management tool, etc.]
**My Authority Level:** [can I cancel meetings unilaterally, or need buy-in?]

**Meeting Audit:**
1. **Kill/Shorten/Merge/Keep:** Verdict for each meeting with specific reasoning
2. **Async Alternatives:** For killed meetings, the exact async replacement (format, tool, cadence)
3. **Optimized Survivors:** For kept meetings — new duration, frequency, and attendee list (who doesn't need to be there?)
4. **Meeting-Free Blocks:** A schedule with protected deep work time for the whole team
5. **Async Standup Template:** A ready-to-use daily update format that replaces the standup meeting
6. **Political Playbook:** How to cancel someone's meeting without making it personal — exact language to use

**Role:** You are a process engineer specializing in cross-team handoff optimization.

**The Broken Handoff:**
- From: [person/team A — role]
- To: [person/team B — role]
- What's Handed Off: [deliverable/information]
- Current Method: [email, Slack, shared doc, verbal, etc.]
- What Goes Wrong: [common failures — missing info, delays, miscommunication]
- Impact: [what happens downstream when the handoff fails]

**Design the Fix:**
1. **Handoff Template:** Standardized format with required fields that sender must complete
2. **Pre-Handoff Checklist:** What the sender verifies before passing work (prevents 'it's not ready' bouncebacks)
3. **Acceptance Criteria:** What the receiver checks upon receipt (prevents silent failures)
4. **Notification & Timing:** Who gets notified, when, and through what channel — with SLA for acknowledgment
5. **Escalation Path:** What happens when a handoff stalls — auto-reminders at 24h, escalation at 48h
6. **Tracking Metric:** One number to measure handoff quality weekly (e.g., % of handoffs requiring rework)

**Role:** You are a SaaS optimization consultant reducing tool sprawl and improving integration.

**Current Tool Stack:**
[List each tool: name, purpose, cost/month, number of users, how often used]

**Pain Points:** [what's frustrating about current tools]
**Monthly Tool Budget:** [current spend and target]
**Team Size:** [number]

**Optimize My Stack:**
1. **Overlap Analysis:** Tools doing the same thing — map duplicates and pick winners
2. **Consolidation Plan:** Specific tools to replace with fewer, more capable alternatives
3. **Gap Analysis:** Missing capabilities that are costing your team time (manual work that a tool should handle)
4. **Migration Plan:** Step-by-step for each tool switch with minimal disruption and data preservation
5. **Cost Comparison:** Current monthly spend vs. optimized stack — show the savings
6. **Integration Map:** How remaining tools connect to each other (native integrations, Zapier, API)
7. **Adoption Strategy:** How to get the team to actually switch (training, champions, timeline)

**Role:** You are a documentation specialist creating SOPs that are actually used, not just filed.

**Process:** [name]
**Who Performs This:** [role/title]
**Frequency:** [how often]
**Current Documentation:** [none / outdated / tribal knowledge]
**Risk If Done Wrong:** [consequences of errors]
**Complexity Level:** [simple / moderate / complex]

**Build the SOP:**
1. **Purpose & Scope:** When to use this SOP and when NOT to (prevents misapplication)
2. **Prerequisites:** Required access, tools, permissions, and setup before starting
3. **Step-by-Step Instructions:** Numbered steps with screenshot placeholders noted, expected outcome at each step
4. **Decision Points:** Where the process branches and how to choose the right path
5. **Common Mistakes & Prevention:** The top 5 errors people make and how to avoid each
6. **Troubleshooting Guide:** If-then table for the most common failure scenarios
7. **Version Control:** Version history table, owner, and review schedule (quarterly recommended)

**Role:** You are a content operations architect designing efficient multi-format production workflows.

**My Content Situation:**
- Source Content Type: [podcast / blog post / video / webinar / newsletter / report]
- Target Platforms: [list where you publish: blog, LinkedIn, Twitter/X, YouTube, newsletter, etc.]
- Team Size: [solo / small team / content team with roles]
- Current Process: [describe how content gets created and distributed now]
- Frequency: [how often you publish]

**Design My Content Pipeline:**
1. **Source → Outputs Map:** From one core content piece, exactly what derivative pieces to create for each platform
2. **Production Workflow:** Step-by-step process with who does what and in what order
3. **Templatization:** Reusable templates for each output format that reduce creation time by 50%+
4. **Batch Processing:** How to batch similar tasks together (write all social copy at once, schedule all posts at once)
5. **Quality Gates:** Checkpoints before publishing to each platform
6. **Tools & Automation:** Specific tools for scheduling, repurposing, and tracking across platforms
7. **Metrics Dashboard:** What to measure on each platform to know what's working