Spot the Bottlenecks That Will Break Your AI Agent
Expose unclear decisions, missing data, hidden exceptions, and risky handoffs before automation begins.
Prompt Overview
Featured AI Partner
Tips For You
If experienced employees cannot agree on the correct output for the same input, the agent cannot be evaluated reliably yet.
From Operations TeamNexusAi TechnologyProblem It Solves
Teams frequently automate an undocumented process and discover too late that it depends on tribal knowledge, inconsistent inputs, inaccessible systems, or exceptions that humans resolve informally.
Ambiguity Audit
Finds hidden judgement and undefined quality standards.
Exception Inventory
Separates agent-handled and human-handled exceptions.
Data Readiness Check
Tests availability, quality, access, and privacy.
Readiness Verdict
Shows whether the process is safe to design now.
AI Prompt Instructions
Act as a business process analyst and AI agent failure-prevention specialist. Audit one workflow before it is automated.
Inputs:
- Process name and objective: [insert]
- Trigger and completion condition: [insert]
- Current steps: [paste]
- People and systems involved: [list]
- Inputs, outputs, rules, and known exceptions: [paste]
- Current performance problems: [insert]
Produce:
1. Current-State Process Map: trigger, steps, decisions, handoffs, systems, waiting points, and output.
2. Ambiguity Audit: undocumented judgement, inconsistent rules, unclear ownership, subjective quality standards, and missing definitions.
3. Data Readiness Check: required data, source, format, quality, access, freshness, privacy, and failure behaviour.
4. Exception Inventory: exception, frequency, detection signal, current response, severity, and whether the agent or a human should handle it.
5. Integration Bottlenecks: missing APIs, manual exports, authentication, rate limits, duplicate records, and write-access concerns.
6. Failure Impact Map: customer, financial, operational, security, and reputational consequences.
7. Fix-Before-Build Checklist: process changes, data cleanup, policy decisions, system access, approval rules, and success criteria.
8. Automation Readiness Verdict: ready, conditionally ready, or not ready, with reasons.
Do not hide process weaknesses behind an AI layer. Make every unresolved dependency explicit.
Expected Outcome
A current-state process map, ambiguity audit, data check, exception inventory, integration bottlenecks, failure map, and readiness verdict.
Implementation Journey
Audit the current workflow
Paste the promptText and current process notes into Claude, ChatGPT, or Gemini. Expect a structured bottleneck and readiness report.
15–25 minutesConfirm real exceptions
Review the exception inventory with process owners in Notion AI and validate data access and integration constraints with technical owners.
45–90 minutesResolve build blockers
Turn the fix-before-build checklist into assigned tasks in Notion, Jira, or the team's project system before creating the agent specification.
1–10 days
