RCA+ Problem MapperNegative effect

Baggage intake misses oversized items

An operations example where a physically larger item improves handling resilience but reduces detection quality at intake.

1. Frame the problem

Move from symptom to a clear map anchor

2. Add a cause or effect

Capture structure, not just a list

3. Review the structure

Node outline

6 nodes

Selected node

Edit notation and wording

Summary

Plain-English reading of the map

Main problem

RFID intake misses oversized baggage during handoff to sorting

Key negative effects

RFID intake misses oversized baggage during handoff to sorting; Large rigid bag shells improve physical stability in transit; Oversized shells block consistent tag exposure to the reader field; Portal geometry is fixed around standard baggage dimensions; Manual exception routing starts only after the missed read is discovered

Key positive effects

Bags stack cleanly and are less likely to collapse in transfer

Contradiction sources

Large rigid bag shells improve physical stability in transit

Most central contradiction

Large rigid bag shells improve physical stability in transit

Next analysis focus

Test the hypothetical causes with evidence so the map reflects what is real versus assumed.

Main problem: RFID intake misses oversized baggage during handoff to sorting. Key negative effects and causes: RFID intake misses oversized baggage during handoff to sorting; Large rigid bag shells improve physical stability in transit; Oversized shells block consistent tag exposure to the reader field; Portal geometry is fixed around standard baggage dimensions; Manual exception routing starts only after the missed read is discovered. Key positive effects: Bags stack cleanly and are less likely to collapse in transfer. Contradiction sources: Large rigid bag shells improve physical stability in transit. Most central contradiction: Large rigid bag shells improve physical stability in transit. Next analysis focus: Test the hypothetical causes with evidence so the map reflects what is real versus assumed.

Export

Take the map into a deck, brief, or workshop

Live diagramAND / OR connectorsContradiction-aware
React Flow mini map

How to use the map

Compact, workshop-ready workflow

Start with the visible symptom, then add the causes that directly create it.

Use `AND` when several causes must be present together. Use `OR` when any one path could be sufficient.

Promote a cause to a contradiction source when it also creates a useful outcome that the system wants to keep.

Notation

Actual negative effect / cause
Hypothetical negative effect / cause
Immutable cause
Contradiction source
Positive effect