Document Type: Framework
Status: Canon
Version: v1.0
Authority: Operations Brain
Applies To: All MWMS workflows and execution environments
Parent: Operations Brain Canon
Last Reviewed: 2026-04-15
Purpose
Operational Bottleneck Detection Framework defines how MWMS identifies execution slow points, friction surfaces, and structural constraints that reduce system efficiency.
Bottlenecks limit throughput.
Throughput limits scaling speed.
Hidden bottlenecks create:
execution delays
workflow congestion
repeated manual effort
task accumulation
handoff waiting states
scaling inefficiency
Bottleneck visibility improves execution flow stability.
Early detection improves system adaptability.
Scope
This framework applies to:
multi-step workflows
approval chains
content creation pipelines
build environments
testing environments
handoff sequences
decision preparation flows
documentation-dependent workflows
Bottlenecks may occur across operational, structural, or knowledge layers.
This framework governs detection of execution constraints.
It does not govern:
strategic prioritisation decisions
risk severity classification
experiment statistical design
capital allocation decisions
Those remain governed by:
Strategy Brain
Risk Brain
Experimentation Brain
Finance Brain
Operations Brain governs workflow efficiency visibility.
Core Principle
Throughput limitations often occur before they become visible.
Slow steps create accumulation pressure.
Accumulation pressure reduces execution responsiveness.
Reduced responsiveness slows optimisation cycles.
Faster feedback improves system learning speed.
Bottleneck visibility improves scaling readiness.
Bottleneck Definition
A bottleneck is any step that:
limits throughput
creates waiting states
requires repeated clarification
requires repeated manual correction
accumulates unfinished tasks
increases execution cycle time
Bottlenecks reduce system responsiveness.
Responsiveness improves scaling adaptability.
Bottleneck Categories
Process Bottlenecks
steps requiring repeated clarification
unclear instruction surfaces
high dependency on interpretation
complex decision sequences
Process friction increases cycle time.
Approval Bottlenecks
approval queues
unclear authority boundaries
multi-stage approval chains
decision waiting states
Approval congestion reduces workflow velocity.
Knowledge Bottlenecks
information difficult to locate
fragmented documentation
unclear instruction location
dependency on specific individual knowledge
Knowledge friction increases execution delay.
Tool Bottlenecks
software limitations
manual data transfer
unreliable integrations
configuration complexity
Tool friction increases maintenance burden.
Dependency Bottlenecks
dependency on upstream task completion
waiting for prerequisite actions
blocked workflow sequences
dependency visibility gaps
Dependency congestion slows execution progress.
Capacity Bottlenecks
limited execution bandwidth
excessive workload concentration
resource imbalance
repeated task accumulation
Capacity imbalance reduces system throughput.
Bottleneck Detection Signals
Indicators of bottleneck presence include:
repeated waiting states
repeated clarification requests
growing task backlog
increasing cycle completion time
repeated manual intervention
repeated workflow interruption
frequent blocking conditions
frequent dependency delays
Detection signals indicate structural friction surfaces.
Bottleneck Impact Dimensions
Each bottleneck must be evaluated for:
throughput limitation severity
impact on learning speed
impact on workflow continuity
impact on execution reliability
impact on scaling readiness
High-impact bottlenecks require prioritised visibility.
Throughput Visibility Model
Each workflow should evaluate:
step completion time
handoff delay duration
dependency waiting frequency
manual effort repetition
workflow interruption frequency
Throughput visibility improves system responsiveness.
Relationship to Other Frameworks
Process Stability Framework
ensures steps remain consistent
Workflow Continuity Framework
ensures handoffs preserve context
Execution Reliability Framework
ensures outputs remain predictable
Documentation Integrity Framework
reduces knowledge friction
Risk Brain Operational Fragility signals
identify structural instability exposure
Bottleneck visibility improves operational resilience.
Failure Modes Prevented
hidden workflow congestion
repeated manual intervention
slow execution cycles
delayed optimisation loops
knowledge retrieval friction
dependency congestion
maintenance overload
Bottleneck visibility prevents silent scaling constraints.
Drift Protection
The system must prevent:
workflow congestion increasing without visibility
repeated manual friction accumulating
hidden capacity limitations expanding
knowledge retrieval difficulty increasing
dependency congestion being ignored
execution cycle time increasing silently
Bottleneck visibility must remain continuous.
Architectural Intent
Operational bottleneck detection ensures MWMS execution remains responsive as complexity increases.
Responsive execution improves learning speed.
Faster learning improves optimisation cycles.
Improved optimisation cycles increase scaling adaptability.
Bottleneck visibility strengthens operational resilience.
Final Rule
If bottlenecks are not visible, execution speed decreases silently.
Reduced execution speed slows optimisation.
Slower optimisation reduces scaling durability.
Bottleneck visibility must remain continuous.
Change Log
Version: v1.0
Date: 2026-04-15
Author: HeadOffice
Change:
Initial creation of Operations Brain Operational Bottleneck Detection Framework defining structural model for identifying throughput constraints across MWMS workflows.
END OPERATIONS BRAIN OPERATIONAL BOTTLENECK DETECTION FRAMEWORK v1.0