Using the 5 WHYs to determine why your SAP Major Incident really happened

23
Use the 5 WHYs to determine why your last SAP Major Incident really happened * Without making your brain bleed *

description

Use the '5 Whys' methodology to get to the root cause of your SAP Major Incident.

Transcript of Using the 5 WHYs to determine why your SAP Major Incident really happened

Page 1: Using the 5 WHYs to determine why your SAP Major Incident really happened

Use the 5 WHYs to determine why your last

SAP Major Incident really happened

*

Without making your brain bleed *

Page 2: Using the 5 WHYs to determine why your SAP Major Incident really happened

First, pretend you’re a kid again and ask…

Page 3: Using the 5 WHYs to determine why your SAP Major Incident really happened

WHY?

WHY? WHY?

WHY? WHY?

WHY?

WHY?

Page 4: Using the 5 WHYs to determine why your SAP Major Incident really happened

We know, it’s extremely annoying.

Page 5: Using the 5 WHYs to determine why your SAP Major Incident really happened

But after a Major SAP Incident,

it’s crucial to get down to the REAL

root cause of the issue…

Page 6: Using the 5 WHYs to determine why your SAP Major Incident really happened

But after a Major SAP Incident,

it’s crucial to get down to the REAL

root cause of the issue…

If you don’t do this, you’ll never be able to

fix the underlying problem...

Page 7: Using the 5 WHYs to determine why your SAP Major Incident really happened

But after a Major SAP Incident,

it’s crucial to get down to the REAL

root cause of the issue…

If you don’t do this, you’ll never be able to

fix the underlying problem...

Which means the Major Incident will

happen again

Page 8: Using the 5 WHYs to determine why your SAP Major Incident really happened

So you need to ask

Page 9: Using the 5 WHYs to determine why your SAP Major Incident really happened

5 TIMES

So you need to ask

Page 10: Using the 5 WHYs to determine why your SAP Major Incident really happened

Only then will you get down to the root cause responsible for the pain of your Major Incident.

Page 11: Using the 5 WHYs to determine why your SAP Major Incident really happened

Like toothache, SAP Major Incidents really hurt.

Page 12: Using the 5 WHYs to determine why your SAP Major Incident really happened

Take this example…

OUR INTERFACE

HAS FAILED!

Page 13: Using the 5 WHYs to determine why your SAP Major Incident really happened

WHY

Page 14: Using the 5 WHYs to determine why your SAP Major Incident really happened

Why did the interface fail?

BECAUSE THERE WAS AN IDoc ERROR

Page 15: Using the 5 WHYs to determine why your SAP Major Incident really happened

Why did the interface fail?

BECAUSE THERE WAS AN IDoc ERROR

Why was there an IDoc error?

BECAUSE A LEGACY SYSTEM SENT THE WRONG DATA

Page 16: Using the 5 WHYs to determine why your SAP Major Incident really happened

Why did the interface fail?

BECAUSE THERE WAS AN IDoc ERROR

Why did a legacy system send the wrong data?

BECAUSE THERE WAS NO VALIDATION ON A DATA INPUT SCREEN

Why was there an IDoc error?

BECAUSE A LEGACY SYSTEM SENT THE WRONG DATA

Page 17: Using the 5 WHYs to determine why your SAP Major Incident really happened

Why did the interface fail?

BECAUSE THERE WAS AN IDoc ERROR

Why did a legacy system send the wrong data?

BECAUSE THERE WAS NO VALIDATION ON A DATA INPUT SCREEN

Why was there no validation?

BECAUSE IT WASN’T IN THE SPEC

Why was there an IDoc error?

BECAUSE A LEGACY SYSTEM SENT THE WRONG DATA

Page 18: Using the 5 WHYs to determine why your SAP Major Incident really happened

Why did the interface fail?

BECAUSE THERE WAS AN IDoc ERROR

Why did a legacy system send the wrong data?

BECAUSE THERE WAS NO VALIDATION ON A DATA INPUT SCREEN

Why was there no validation?

BECAUSE IT WASN’T IN THE SPEC

Why wasn’t it in the spec?

BECAUSE OUR REQUIREMENTS SPECIFCATION DOESN’T MANDATE THAT VALIDATION MUST BE DESIGNED IN TO SYSTEM CHANGES

Why was there an IDoc error?

BECAUSE A LEGACY SYSTEM SENT THE WRONG DATA

Page 19: Using the 5 WHYs to determine why your SAP Major Incident really happened

BINGO! BECAUSE OUR

REQUIREMENTS SPECIFCATION DOESN’T

MANDATE THAT VALIDATION MUST BE

DESIGNED IN TO SYSTEM CHANGES

Now here’s your real underlying root cause

Page 20: Using the 5 WHYs to determine why your SAP Major Incident really happened

And more importantly, You’ve identified something you can actually fix

BECAUSE OUR REQUIREMENTS

SPECIFCATION DOESN’T MANDATE THAT

VALIDATION MUST BE DESIGNED IN TO SYSTEM

CHANGES

Page 21: Using the 5 WHYs to determine why your SAP Major Incident really happened

You’ve now found a way to stop similar incidents like this disrupting your

business operations again in the future

Page 22: Using the 5 WHYs to determine why your SAP Major Incident really happened

You’ve now found a way to stop similar incidents like this disrupting your

business operations again in the future

And you can go back and identify other validation issues that may cause

interfaces to fail.