← Case Study

Sensitivity Analysis

Like the healthcare sensitivity page, this version perturbs one structural coefficient at a time and measures how much the chosen GDPR outcome moves. It answers a local robustness question: which direct structural assumptions does this conclusion depend on most?

Why sensitivity analysis matters

Sensitivity answers the planning question: which inputs matter most for this outcome, and by how much? Each score is the interventional effect of a one-standard-deviation shift in the source node, propagated through all downstream paths to the target. Unlike feature importance in black-box models, these scores carry a causal interpretation — they measure the effect of a do(), not a correlation.

Sensitivity analysis guides resource allocation. A high-sensitivity node that is tractable to change is a natural intervention target. A high-sensitivity node that is difficult to change tells you the system is largely outside your influence from the levers currently in the model. The comparison between nodes is only meaningful when inputs are standardized — which is why standard-deviation scaling is essential here.

Start here
  1. Open the recommended scenario for this case
  2. Adjust the three root drivers to describe the organization
  3. Choose the GDPR outcome to stress-test
  4. Change the perturbation percentage to test robustness
  5. Inspect which direct assumptions dominate the tornado chart
Tornado — impact on outcome
weight decreased weight increased