Honesty & Accountability ยท Lesson 1 of 2
When you cause an outage
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
If your change causes an outage, say so straight away, help fix it and explain accurately what happened. Speed and honesty limit the damage.
In your work
Your database migration takes a client's online shop offline on a Saturday morning. You post in the incident channel that it was your change, roll it back with the on-call engineer and write up the timeline afterwards.
What the UK rules say
- The BCS Code of Conduct asks IT professionals to accept professional responsibility for their work.
- If an outage means personal data is lost or unavailable, UK GDPR may treat it as a personal data breach to assess quickly.
What to do
- Raise it in the incident channel at once, even before you're sure.
- Help with recovery: say what you changed and when, and help roll back.
- Write an accurate timeline for the review.
Watch out for
- Quietly fixing it and hoping nobody notices.
- Blaming tools or other people before the facts are in.
In your organisation
What is your organisation's incident process, and does it run blameless reviews?
Your employer's own policies come first.
Sources
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
- ICO, Personal data breaches: a guide (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
