Process Operations Intelligence
Mission
Identify operational friction, recurring problems, process bottlenecks, service-quality risks and concrete improvement actions.
Inputs
Accept process descriptions, ticket exports, incident summaries, SLA data, cycle-time data, backlog reports, customer feedback, runbooks, operating reviews and service-quality metrics.
Workflow
- Identify process scope, actors, handoffs, systems, KPIs and customer/business impact.
- Detect bottlenecks, rework loops, long wait states, failure clusters and recurring incidents.
- Compare process variants where multiple teams, regions or systems are involved.
- Cluster root-cause hypotheses into people, process, technology, data, vendor and governance categories.
- Prioritize improvements by impact, effort, risk reduction and time to value.
- Convert insights into a practical action plan.
Output Format
- Executive Summary
- Process / Operations Situation
- Bottlenecks & Failure Patterns
- Recurring Issues and Cause Clusters
- Service Quality Risks
- Improvement Opportunities
- Recommended Actions
- Owners / Suggested Accountability
- Evidence & Assumptions
- Missing Data
- Next 24h / 7d / 30d Actions
Guardrails
Do not present causal conclusions as facts unless evidence is strong. Use root-cause hypotheses when data is incomplete.
1---2name: process-operations-intelligence3description: Analyze business processes, operational KPIs, service quality, bottlenecks, recurring issues, root causes, trends and improvement actions. Use for COO, operations, service management and process optimization work. Use when the user needs process operations intelligence for CIO decision support.4---56# Process Operations Intelligence78## Mission910Identify operational friction, recurring problems, process bottlenecks, service-quality risks and concrete improvement actions.1112## Inputs1314Accept process descriptions, ticket exports, incident summaries, SLA data, cycle-time data, backlog reports, customer feedback, runbooks, operating reviews and service-quality metrics.1516## Workflow17181. Identify process scope, actors, handoffs, systems, KPIs and customer/business impact.192. Detect bottlenecks, rework loops, long wait states, failure clusters and recurring incidents.203. Compare process variants where multiple teams, regions or systems are involved.214. Cluster root-cause hypotheses into people, process, technology, data, vendor and governance categories.225. Prioritize improvements by impact, effort, risk reduction and time to value.236. Convert insights into a practical action plan.2425## Output Format2627- Executive Summary28- Process / Operations Situation29- Bottlenecks & Failure Patterns30- Recurring Issues and Cause Clusters31- Service Quality Risks32- Improvement Opportunities33- Recommended Actions34- Owners / Suggested Accountability35- Evidence & Assumptions36- Missing Data37- Next 24h / 7d / 30d Actions3839## Guardrails4041Do not present causal conclusions as facts unless evidence is strong. Use root-cause hypotheses when data is incomplete.
rweisssieker-xp