D6: Operational Impact

Core Question: How does this problem affect how we work?

Operational impact is often the most pervasive dimension — inefficiencies and bottlenecks compound daily, creating invisible drag on every other dimension.

Primary Cascade: Operational → Quality (80% of cases)

Observable Signals

Don't wait for systems to crash. Look for early warning signals in your systems:

Signal Type	Observable	Data Source	Detection Speed
Immediate	System downtime	Monitoring/APM	Minutes
Behavioral	Manual workarounds	Process documentation	Weeks
Bottleneck	Queue length increase	Workflow systems	Days
Cycle	Processing time up	Metrics dashboards	Days
Resource	Contention/Conflicts	Project management	Days
Capacity	Utilization spike	Resource planning	Days
Silent	Shadow processes	Interviews, observation	Months
Integration	Handoff failures	Cross-team metrics	Weeks

Trigger Keywords

Language patterns indicate severity. Train your team to flag these:

High Urgency (Sound = 8-10)

"system down"           "outage"                  "critical failure"
"data loss"             "cannot operate"          "business stopped"
"disaster recovery"     "incident"                "P1/Sev1"

Action: Incident commander assigned within minutes. Executive notification.

Medium Urgency (Sound = 4-7)

"workaround"            "manual process"          "bottleneck"
"waiting on"            "blocked by"              "delayed"
"capacity issue"        "resource conflict"       "slow"

Action: Manager review within 24 hours.

Low Urgency / Early Warning (Sound = 1-3)

"inefficient"           "could be better"         "nice to have"
"tech debt"             "legacy system"           "someday"
"minor friction"        "slight delay"            "process improvement"

Action: Track pattern over time. Add to backlog.

Metrics

Track both leading (predictive) and lagging (historical) indicators:

Metric Type	Metric Name	Calculation	Target	Alert Threshold
Leading	System uptime	Available time / Total time	>99.9%	<99.5%
Leading	Cycle time	Time from start to completion	Decreasing	Increasing trend
Leading	Queue depth	Items waiting / Processing rate	<2× normal	>3× normal
Leading	Resource utilization	Allocated / Available	70-85%	>90% or <50%
Lagging	Incidents per period	Count of P1/P2 incidents	Decreasing	Increasing trend
Lagging	Mean time to recovery	Avg incident resolution time	Decreasing	Increasing trend
Lagging	Process efficiency	Value-add time / Total time	>70%	<50%

Example Dashboard Query

-- Queue depth anomaly alert
SELECT
  queue_name,
  COUNT(*) as current_depth,
  AVG(COUNT(*)) OVER (
    PARTITION BY queue_name
    ORDER BY date
    ROWS BETWEEN 30 PRECEDING AND 1 PRECEDING
  ) as baseline_30d,
  COUNT(*) / NULLIF(AVG(COUNT(*)) OVER (
    PARTITION BY queue_name
    ORDER BY date
    ROWS BETWEEN 30 PRECEDING AND 1 PRECEDING
  ), 0) as depth_ratio
FROM queue_metrics
WHERE timestamp >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY queue_name, DATE(timestamp)
HAVING depth_ratio > 3  -- Alert at 3× baseline

Cascade Pathways

Operational impact multiplies across multiple dimensions simultaneously:

Cascade Probabilities

Cascade Path	Probability	Severity if Occurs
Operational → Quality	80%	High
Operational → Employee	75%	High
Operational → Revenue	60%	Medium-High

Why Quality Cascade is Most Common:

1. Time pressure forces shortcuts (testing skipped, reviews rushed)
2. Resource constraints limit thoroughness (fewer QA cycles)
3. Workarounds become permanent (technical debt accumulates)
4. Focus shifts to "getting it done" vs "getting it right" (quality culture erodes)

Multiplier Factors

Not all operational issues cascade equally. The multiplier depends on:

Factor	Low (1.5×)	Medium (3×)	High (6×+)
System Criticality	Support system	Core business	Revenue-generating
Dependency Chain	Standalone	Some dependencies	Highly interconnected
Recovery Options	Quick failover	Manual recovery	No backup
Business Timing	Off-peak	Normal operations	Peak/Critical period
Automation Level	Highly automated	Partially automated	Manual processes

Example Calculation

Scenario: Payment processing system down during Black Friday, no failover, highly interconnected with inventory/shipping

Multiplier factors:
- System criticality: High (6×, revenue-generating)
- Dependency chain: High (6×, interconnected)
- Recovery options: High (6×, no backup)
- Business timing: High (6×, peak period)
- Automation level: High (6×, fully automated, no manual option)

Average multiplier: (6 + 6 + 6 + 6 + 6) ÷ 5 = 6×

Impact:

• Direct cost: $100K/hour in lost revenue
• 4-hour outage: $400K
• Multiplied impact: $400K × 6 = $2.4M
• Plus customer cascade: 85% probability of trust erosion → lost lifetime value
• Plus employee cascade: 75% probability of burnout → turnover
• Total risk: $2.4M + cascading customer/employee costs

3D Scoring (Sound × Space × Time)

Apply the Cormorant Foraging lens to operational dimension:

Lens	Score 1-3	Score 4-6	Score 7-10
Sound (Urgency)	Efficiency opportunity	Bottleneck	System down
Space (Scope)	One process	One department	Cross-functional
Time (Trajectory)	Temporary spike	Recurring issue	Chronic condition

Formula: Dimension Score = (Sound × Space × Time) ÷ 10

Example Scoring

Scenario: Deployment process bottleneck affecting all engineering teams, recurring every sprint for 6 months

Sound = 6 (bottleneck, slowing releases)
Space = 8 (all engineering teams)
Time = 7 (chronic, 6+ months)

Operational Impact Score = (6 × 8 × 7) ÷ 10 = 33.6

Interpretation: High urgency (33.6 > 30). Expect cascade to Quality (rushed deployments, insufficient testing), Employee (frustration, overtime), and Revenue (delayed features, lost opportunities).

Detection Strategy

Automated Monitoring

Set up alerts for:

1. System uptime (<99.5% availability)
2. Cycle time increase (>20% vs baseline)
3. Queue depth spike (>3× normal)
4. Resource utilization extremes (>90% or <50%)

Human Intelligence

Train your operations/engineering teams to:

1. Flag language patterns (use trigger keyword lists)
2. Report workarounds (manual processes hiding automation failures)
3. Escalate bottlenecks (blocked work, waiting states)
4. Track handoff failures (cross-team coordination issues)

Real-World Example

The "Waiting On" Signal:

Observable	Data Point	3D Score
Signal	"Waiting on deployment" mentioned in 20+ standup meetings	Sound = 5
Context	Affects all product teams, deployment once per week	Space = 8
Trend	Pattern consistent for 6 months, getting worse	Time = 7
Score	(5 × 8 × 7) ÷ 10 = 28	Medium-High urgency

Cascade Prediction:

• 80% probability → Quality impact (features tested in production, insufficient QA)
• 75% probability → Employee impact (frustration, context switching, overtime)
• 60% probability → Revenue impact (delayed features, missed market windows)
• Multiplier: 3-4× (core business process, cross-functional, recurring)

Action Taken:

1. CI/CD pipeline audit (within 1 week)
2. Deployment automation improvements (within 1 month)
3. Self-service deployment capability (within 2 months)
4. Result: Deployment frequency increased from weekly to daily, cycle time reduced 60%

Industry Variations

B2B SaaS

• Primary metric: Deployment frequency, lead time for changes
• Key signal: Production incidents, rollback rate
• Cascade risk: Operational → Quality → Customer

Healthcare

• Primary metric: Patient wait time, bed turnover rate
• Key signal: Staffing shortages, equipment downtime
• Cascade risk: Operational → Quality → Customer (Patient) → Regulatory

Manufacturing

• Primary metric: Overall Equipment Effectiveness (OEE), cycle time
• Key signal: Machine downtime, changeover time, inventory levels
• Cascade risk: Operational → Quality → Revenue → Customer

Next Steps

📊 D5: Quality Impact — The 80% cascade from operational issues to quality degradation

👥 D2: Employee Impact — How operational bottlenecks burn out teams (75% cascade)

🔄 Cascade Analysis — Map how operational issues multiply

📖 Observable Properties — Complete signal catalog

---

Remember: The bottleneck you ignore becomes the ceiling. The workaround you tolerate becomes the process. Fix both. 🪶