process-bottleneck-detection

Identify and analyze operational bottlenecks in banking processes using Lean and Six Sigma.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wassemgtk/skills-testing --skill process-bottleneck-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-bottleneck-detection
Source: https://github.com/wassemgtk/skills-testing/tree/main/financial-services/banking-ops/process-bottleneck-detection
Command: npx skills add https://github.com/wassemgtk/skills-testing --skill process-bottleneck-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and analyzes operational bottlenecks in banking processes, helping to improve efficiency, reduce cycle times, and increase throughput.

Core Features & Use Cases

  • Bottleneck Identification: Pinpoints the constraint step in a process using data analysis.
  • Root Cause Analysis: Investigates why bottlenecks occur (e.g., capacity, dependencies, systems).
  • Improvement Recommendations: Suggests specific actions based on Lean and Theory of Constraints principles.
  • Use Case: A bank is experiencing long delays in its loan application process. This Skill can analyze the process map, cycle times, and WIP data to identify if underwriting or a specific verification step is the bottleneck, quantify its impact, and recommend solutions like adding staff or automating a manual check.

Quick Start

Use the process-bottleneck-detection skill to analyze the provided loan origination process map and cycle time data to identify the primary bottleneck.

Frequently Asked Questions about process-bottleneck-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify operational bottlenecks in banking processes?▼

To identify operational bottlenecks in banking processes, analyze process maps, cycle time data, and WIP accumulation using Lean and Six Sigma methodologies. This pinpoints the specific constraint step, such as underwriting or manual verification, causing delays in workflows like loan origination.

What data is needed for cycle time analysis and Theory of Constraints application in banking?▼

Cycle time analysis and Theory of Constraints application in banking require process maps, cycle time data, volume data, resource data, quality data, and SLA targets. Supplying these inputs allows for comprehensive constraint identification across lending, payments, and account servicing operations.

How does value stream mapping find WIP accumulation in loan origination?▼

Value stream mapping finds WIP accumulation in loan origination by visualizing the flow of work and highlighting stages where work-in-progress exceeds capacity. Applying Lean principles to this map reveals where applications stall, quantifies the delay's impact, and isolates the root cause.

Can I use Six Sigma methodologies for root cause analysis of payment delays?▼

Yes, you can use Six Sigma methodologies for root cause analysis of payment delays. By analyzing resource data, quality data, and SLA targets, the approach investigates why bottlenecks occur due to capacity limits, system dependencies, or manual checks, and then recommends specific improvements.

What is the best way to reduce cycle times and increase throughput in account servicing?▼

The best way to reduce cycle times and increase throughput in account servicing is applying the Theory of Constraints to identify the limiting step and recommend targeted actions. Suggested solutions based on Lean principles include adding staff or automating manual checks to resolve the bottleneck.