31.01.2021

Free Trial
trustkey - the template cloud
Latest posts

We support you in your cloud transformation. 

8D-Report template: the 8 disciplines for improvement

8D-report template

Using the 8D-Report template in trustkey, we explain the procedure of the 8D method.

The 8D method is used for the controlled determination of error causes and the measures to be taken in the case of non-conforming results. The 8D method on which the 8D report is based is fact, cause and team oriented. It is a method that is worked on together in teams of between 3 and 5 members.

Content:

  1. Discipline 1: Organize a small group of people as a team.
  2. Discipline 2: Develop specific problem description.
  3. Discipline 3: Define, verify and validate immediate actions.
  4. Discipline 4: Identify and verify root cause(s).
  5. Discipline 5: Established corrections and corrective actions.
  6. Discipline 6: Implement corrections and corrective actions.
  7. Discipline 7: Measures to prevent recurrence of the problem.
  8. Discipline 8: Verification of the effectiveness of the measures introduced.
  9. How does trustkey provide support?

The 8D report is a methodology for systematically identifying the causes of errors and the actions taken within the team

8D-report template in trustkey

Discipline 1: Organize a small group of people as a team

This step involves determining the team members.

The team should preferably consist of 3 to 5 members (not too large) and have the time, authority and competence to solve the problem and implement corrective actions.

Discipline 2: Develop specific problem description

This step is about describing the problem as accurately as possible. This often sounds easier than done.

The following questions should be answered when describing the problem:

  • Which object shows the error?
  • What is the deviation?
  • Where on the product, where in the process did the problem occur?
  • When did the problem occur (timing / pattern): continuous or steady, sudden, periodic / cyclic, random or first day deviation?
  • How often did the problem occur (number / frequency / pattern)?

Then, What?, Where?, When? and How often? are combined into a simple and precise statement about the object and the deviation (without knowing the cause).

Discipline 3: Define, verify and validate immediate actions

Immediate actions are used for immediate mitigation and are based on the specific changes (software, services, hardware, etc.).

Examples are:

  • Delivery block
  • Block stock
  • Check warehouse stock
  • Revert to previous version of software
  • Reset password
  • Block access
  • etc.

Discipline 4: Identify and verify root cause(s)

To identify root cause(s), for example, it is a good idea to use the 5W(hy?) method, where one is not satisfied with the first “why”.

Discipline 5: Established corrections and corrective actions

It is important here not only to identify and document the corrective measures. The measures must also be communicated. For this purpose, an implementation plan, action plan, or plan of action can be used, for example. This can also be implemented very easily in trustkey.

Discipline 6: Implement corrections and corrective actions

In addition to confirming that the measures have been implemented, this step requires validation of the measures.

Examples of validation are:

  • History diagram
  • Log files, dumps, traces
  • Machine/process capabilities
  • Interaction analyses
  • Process performance indicators
  • Functional safety assessment
  • Security assessment (access security – security)

After successful validation of the corrective and remedial actions, the immediate actions are no longer needed. Continuing the immediate measures would consume important resources (cause unnecessary costs).

Discipline 7: Measures to prevent recurrence of the problem

Now the problem is viewed from the overarching systemic perspective. That is, the question is answered, what practices and procedures in the system allowed the error and its non-detection?

Identify sustainable, overarching, preventive measures to:

  • Prevent the problem in the current system (prevention, product/process related): update of Failure Mode and Effects Analysis (FMEA)
    • Product control plan
    • Inspection plan
    • Work instructions
    • etc.
  • Prevention of similar problems in other systems (cross-product and cross-process knowledge transfer): Recommendations for systemic improvements
    • Processes
    • Instructions
    • Guidelines
    • Forms
    • etc.

In trustkey, this is quite easy, as you can very quickly implement and introduce the results in a new digital version of the respective template.

Discipline 8: Verification of the effectiveness of the measures introduced

And “Last but not least”: Recognition for the team and individuals. Feedback to team members regarding their cooperation (praise and criticism).

How does trustkey provide support?

trustkey is the #1 template system that unifies template management with powerful workflow and collaboration features.

In trustkey you create, manage, edit and optimize activities and workflows with the support of smart templates. In addition, trustkey offers a wide range of pre-built templates (such as this 8D report) that can be accessed and used immediately.

Efficient. Individual and modern.

Weitere Informationen zu trustkey finden Sie unter: trustkey – the template-cloud for better collaboration.

Not a customer yet?

You can test trustkey free of charge for 14 days: https://www.trustkey.eu/view/public/register.

We are happy to assist you. You can book a live demo in German or English at the following link: https://www.ibodigital.com/en/cloud-solutions/trustkey/live-demo/. Or write an email to support@ibodigital.com or use our contact form.

We look forward to showing you the power of trustkey.

Latest posts
Top