Data leadership
Handling a data incident
Respond to a leak, an outage or a wrong figure in production: contain it, inform the right people, fix the cause.
A data incident is a leak of personal data, a broken pipeline, a dashboard showing wrong figures or a model making bad decisions in production. Handling it means containing the damage first, then understanding what happened.
How the first hours are handled decides most of the cost. Under the GDPR, a personal data breach must be notified to the supervisory authority within 72 hours when it is a risk for people; hiding a problem or blaming a team makes the next one worse.
Good practice: a named owner, a first containment step, factual communication to management and the people affected, then a review that fixes the cause rather than the symptom and is shared with the teams.
In the reports of your games, every answer linked to this skill counts: the skill is shown as acquired from 80% of correct answers, and in progress from 50%.
Games that train this skill
Play them for free, without an account, then adapt them for your teams.
