Analyse the root cause with the team

Find out with the team why a problem happens, before jumping to a solution.

The task in figures

Gives you back
It does not recur every month
Elmira today
On the way
Frequency
Per project
Who does it today
Engineer, Senior
How it is done today

What hurts today.

  • People jump to a solution without knowing the cause.

  • The analysis stays on a flip chart nobody looks at again.

  • It depends on an expert facilitator being available.

With the problem defined with data, the team looks for its possible causes, with an Ishikawa diagram or by asking why until it reaches the bottom, and checks with data which one is the root. It is the step most often skipped, and that is why problems come back.

Done today with

  • Expert
  • In-person meeting
  • Paper and whiteboard
  • Spreadsheet
  • Email and chat
  • Slides
  • Statistics software
With Elmira

Each step, today and with Elmira.

Not yet. With the Value Office, the app structures it in the Problem playbook, with AI help in the editor.

StepTodayWith Elmira
Bring together the people who know the processEmail and chat, In-person meeting15 min – 30 minStill by hand
List the possible causes with the team (Ishikawa)In-person meeting, Paper and whiteboard30 min – 1 hComes with the value office
Ask why until reaching the root (5 whys)Expert, In-person meeting30 min – 1 hComes with the value office
Check the cause with dataSpreadsheet, Statistics software30 min – 2 hStill by hand
Write up and share the analysisSlides15 min – 45 minComes with the value office

The conversation

No example conversation: the Obeyaka web app does it, or it comes later.