• Main website
  • Case Studies Home
  • Case Studies
    • Green Belt
      • Example Green Belt Projects-Health Care
      • Example Green Belt Projects-Manufacturing
      • Example Green Belt Projects-Services
    • Black Belt
      • Example Black Belt Projects-Health Care
      • Example Black Belt Projects-Manufacturing
      • Example Black Belt Projects-Services
    • Master Black Belt
    • Lean Success Stories
  • Articles
    • LSS topics of common interest
    • Insights for Green Belts
    • Green Belt tool application examples
    • Insights for Black Belts
    • Black Belt Tool Application Examples
    • Lean Insights
    • Lean Six Sigma Leadership
    • For Master Black Belts
    • New to Lean Six Sigma
      • Lean Expert Basics
      • Six Sigma Basics
    • Leisure and Fun
  • Blog

Build a Visual Dashboard in 10 Steps

 

Build a Visual Dashboard in 10 StepsThe process improvement team at Ball Corporation (the company known for its glass canning jars) started a visual factory programme three years after implementing Lean Six Sigma. This project aimed to create visual dashboard for plant floors that would not only direct workers on where to concentrate their efforts, but also represent the company’s health. The Yellow, Green, and Black Belt projects will be guided by these visual cues. These should not only point to areas where changes can be made, but also to the effectiveness of those that have already been made. The team set out with the aim of creating the ultimate dashboard.

 

1st Step: Ask Questions

Some of the questions that were posed and heard were as follows:

  • How does the dashboard appear?
  • How many indicators should be used in the dashboard?
  • How can the data be interpreted in a way that allows various levels of the company to easily customise it?
  • Who is going to make use of the dashboard?

2nd Step: Tool Selection

Lean does not imply squandering a lot of time and resources on new systems. It’s perfectly acceptable to start with a manual dashboard. Create metrics and update them once a day on a whiteboard. Ball was aiming for the effect of the indicators rather than the flash of a flashy product. Ball was already using a Cyberscience reporting system, and because the system included a dashboard tool, the Cyberscience dashboard was chosen.

 

3rd Step: Dashboard Design Basics

A good dashboard should:

  • Be able to be seen on a single one-page display screen (no scrolling required).
  • Include three to seven metrics in your presentation.
  • Data that is as similar to real-time as possible is presented.
  • Include metrics that one of the target audiences will influence.
  • With minimal text, keep it short and easy to read.
  • Remove the need for paper reports.

A good dashboard does not include the following features:

  • Be all things to all people.
  • There should be more than seven metrics.
  • The key metrics must be viewed through scrolling.
  • There is a lot of text in this document.
  • There is no longer a need for detailed studies.

4th Step:  Determine the Audience

The team began by identifying the metrics for the dashboard, but quickly realised that the audience needed to be identified first. Who should take action based on the dashboard information? The greatest value of visible metrics, according to Ball, will be on the production floor. Employees on the production floor will be able to use the dashboard data to push and realise changes on the tracks.

 

5th Step: Develop the metrics

After determining the target group, the next move was to determine the three to seven metrics that would be most effective in driving manufacturing floor improvements. Over the course of several weeks, personnel from different management levels at both the corporate and plant levels weighed in on the choices. The following is a list of the final metrics:

  • Safety
  • Defective material produced and held (dollars)
  • Inventory (dollars)
  • Line spoilage (percentage)
  • Line efficiency (percentage)
  • Customer complaints (number)
  • Maintenance and repair costs (dollars)

6th Step: Determine the Levels of Data

The next move was to figure out what data levels were needed, which meant going back to the target audience. The dashboard was developed specifically to help drive manufacturing floor improvement programmes. The data must be grasped by the workers on those plant floors at the end of the day, otherwise the dashboard would fail.

To make it more difficult, there are several factories, each with its own department, and each department has its own set of production lines. To guide the right behaviour on the factory floor, the indicators must be able to drill down to the line stage. The Cyberscience dashboard, fortunately for Ball, helps users to navigate a variety of data levels. Start with the level of metric that the main audience can function on or affect while creating a manual dashboard – in this case, line-level data.

 

7th Step: Designing the Display – Visual Management

At the top of each individual metric box, the target is labelled and shown. The period-to-date value (1.61) is the amount in the centre. It’s green because it’s a better option than the target. The deviation to the previous time (0.41) is the number at the right. It’s red here, with a red arrow pointing up, because, although this process is outperforming the target, it’s not performing as well as it was in the previous era.

 

Figure 1: Sample of Metric Display Format

 

 

 

 

 

 

 

 

 

8th Step: Delivering the Dashboard

Creating the dashboard is, in some respects, the easy part. Choosing the best way to deliver the dashboard is one of the more difficult tasks in this phase. The process improvement team desired a dashboard that was visible, interactive, and accessible to a large number of people. Tablets, large screens, individual workstations, terminals, and other display options were available.

 

9th Step: Training

Webinars were used as the primary training tool since the dashboard shows easy-to-understand metrics. Ball found webinars to be perfect for educating multiple people in multiple places, with 13 plants across North America. A short training guide was also developed by the team, which was made available to all. Additionally, members of the process management team conducted one-on-one phone follow-ups with customers to help them feel more comfortable with the tool.  The dashboard’s adoption proved to be more difficult than the training.

 

10th Step: Feedback

Feedback is beneficial, but proceed with caution. Initially, some of the feedback Ball received suggested that the dashboard should be all things to all people. A dashboard isn’t designed to do that. All comprehensive reports will not be replaced by a dashboard. Those reports will be required in the future, but hopefully they will only be used to better understand the item that is being improved.

See full story on isixsigma.com

April 7, 2014   Benchmark Six Sigma
Articles, LSS topics of common interest
×

  • Supplement FMEA with a Risk Priority Matrix
  • 5 trends reshaping the Lean landscape

Categories

  • Articles
    • Black Belt Tool Application Examples
    • For Master Black Belts
    • Green Belt tool application examples
    • Insights for Black Belts
    • Insights for Green Belts
    • Lean Insights
    • Lean Six Sigma Leadership
    • Leisure and Fun
    • LSS topics of common interest
    • New to Lean Six Sigma
      • Lean Expert Basics
      • Six Sigma Basics
  • Case Studies
    • Black Belt Qualified
      • Example Black Belt Projects-Health Care
      • Example Black Belt Projects-Manufacturing
      • Example Black Belt Projects-Services
    • Green Belt Qualified
      • Example Green Belt Projects-Health Care
      • Example Green Belt Projects-Manufacturing
      • Example Green Belt Projects-Services
    • Master Black Belt
  • Featured Articles
  • Lean Qualified
    • Lean Success Stories
  • Project Management Articles
  • Uncategorized

Archives

  • April 2021
  • November 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • February 2012
  • March 2011
Copyright © 2023 Benchmark Six Sigma