Business Process Bottleneck Analyzer Skill

Operational inefficiencies and hidden delays stall business growth, yet identifying the exact friction points in a messy workflow is difficult without manual auditing. This skill converts raw process data into a structured bottleneck analysis, mapping every handoff and dependency to find the root cause of delays.

What it does

• Process Mapping creates a step-by-step sequence of owners, inputs, and outputs based on provided data.
• Bottleneck Detection flags specific stages where queues form, approvals stall, or rework loops occur.
• Handoff Analysis identifies friction points between teams and external dependencies that risk project timelines.
• Root-Cause Hypothesis develops evidence-backed theories for why specific steps are failing or lagging.
• Prioritized Planning generates an action roadmap categorized by effort, impact, and implementation speed.

How it works

1. Supply a description of a business process, including steps, owners, and any known timing or volume data.
2. The agent normalizes the workflow and maps the flow including waiting points and approval loops.
3. Review the generated tables for bottleneck evidence, repetitive work signals, and dependency risks.
4. Use the prioritized action plan to address immediate, near-term, and long-term process improvements.

Frameworks & tools

This tool works with standard operations analysis methods and requires no specific software stack. It processes text-based workflow descriptions, log exports, or manual process interviews.

Why this beats prompting it yourself

General LLMs often invent performance metrics or suggest generic automation for every problem. This skill is hard-coded to distinguish facts from hypotheses, strictly avoiding fabricated savings while focusing on the specific handoff and dependency logic of your supplied data.

Use cases

• Audit a messy customer onboarding flow to reduce time-to-value.
• Identify why a software release pipeline consistently stalls at the QA or approval stage.
• Streamline an accounts payable process by finding unnecessary approval layers.
• Map internal procurement workflows to highlight external vendor dependencies.

Known limitations

Requires specific process details like owners or step sequences to be effective. It cannot calculate ROI or cycle times if the user does not provide raw timing data.