Example Inputs
Process
Publishing new category pages across content, design, dev, and QA
Pain
Work waits too long between review steps
Constraint
No dedicated project manager
Analyze a workflow and identify where delays, handoff issues, or confusion are slowing execution.
This prompt helps you diagnose why a process feels slower or messier than it should. It is useful when teams sense friction but have not yet translated it into concrete bottlenecks or fixes.
Copy-And-Paste Prompt
Works well in ChatGPT, Claude, Gemini. Replace any bracketed variables before you run it.
Variables to customize
Act as an operations analyst diagnosing workflow bottlenecks. Your task is to analyze my process and identify likely bottlenecks, handoff issues, delays, and practical improvement ideas. Use these inputs when available: - [Current Process Steps] - [People or Teams Involved] - [Where It Feels Slow or Messy] - [Any Capacity or Tool Constraints] Requirements: - Spot likely bottlenecks and explain why they happen. - Separate structural problems from one-off mistakes. - Recommend realistic improvements. - Keep the analysis tied to the actual workflow described. Return the answer in this format: 1. Likely bottlenecks 2. Why each bottleneck exists 3. Improvement ideas and sequencing Tone and style: diagnostic and practical Ask me concise follow-up questions only if a missing detail would materially change the quality of the final answer.
Process
Publishing new category pages across content, design, dev, and QA
Pain
Work waits too long between review steps
Constraint
No dedicated project manager
Likely bottleneck: the handoff between content approval and implementation is too implicit, so work sits in a gray area where everyone assumes someone else owns the next move. Improvement: define a single ready-for-build signal and owner.
This is a mock example only. Your result should change based on the variables, context, and constraints you provide.
The structure of this prompt is meant to make the AI do more than generate a loose first pass. It frames the model with a role, directs it toward a concrete goal, forces relevant inputs into the request, and asks for a usable output format instead of an open-ended answer.
That combination usually makes the result easier to review, edit, and reuse inside a real workflow. If the first output is still too generic, your best move is usually to add more context rather than abandon the prompt entirely.
These related calculators and guides add more depth when you want to connect this productivity prompt to real numbers, strategy, or supporting tools.
Browse more copy-and-paste prompts that fit the same workflow, adjacent use case, or decision context.
Turn a messy task list into a focused daily plan with priorities, sequencing, and time blocks.
Good For
Summarize meeting notes into decisions, action items, blockers, and follow-up.
Good For
Create clearer delegation briefs so teammates or freelancers know what to do and why.
Good For
Review the week, identify wins and misses, and plan the next week with more intention.
Good For
Straight answers to the questions readers usually have before using these prompts.
Replace the bracketed variables with your own context, then add any constraints that matter for your audience, offer, or workflow. The more specific you are about goals, tone, and output format, the stronger the result will usually be.
Yes. The prompt is written in plain English so it works well across major AI assistants. If one model gives an answer that is too short or generic, paste the same prompt back in with an extra sentence telling the model to be more specific.