Four steps to implementing CI from a standing start



Ryan King
08/29/2019

Men rowing a boat

Whether you are aiming to create a long-term culture of continuous improvement or seeking improvements in efficiency or customer service, the operational team ways of working in your business play a huge role in successful delivery regardless of industry.

This blog will help you implement continuous improvement (CI) ways of working within a team using a method which is scaleable across the organisation, sustainable and can be mobilized easily.

STEP 1: DEFINE THE TEAM PURPOSE

This can be achieved through a facilitated session with all members of an operational team. The team should define their purpose and this involves answering questions such as:

  • Why does the team exist?
  • What is the core purpose of the team?
  • What does success look like?

These are simple questions but that may be difficult to answer and different team members may have different opinions. Ideally a team purpose will be no more than two sentences, preferably one.

An example of a team purpose for an accounts payable team in a finance department might be:

‘To pay suppliers within the agreed payment terms for the goods and services received.’

The whole team should be involved in creating their team purpose and a consensus reached on the definition.

STEP 2: CREATION OF PURPOSEFUL PERFORMANCE MEASURES

This exercise could directly follow step 1 in the same workshop and will also require facilitation. This is the practical creation of the team performance measures and possibly the most crucial step in their CI journey, as from my experience performance measures will strongly influence the focus of the team.

The performance measures will vary greatly depending on the purpose of the team, but ideally will:

  • Be directly linked to the team purpose
  • Show whether performance is improving or declining over a period of time
  • Show clearly current performance against a target or expected outcome
  • Be accessible to measure through available data
  • Help the team to seek improvement / act

An important point here is that we are creating measures which focus on the service delivered, not evaluating any individual’s performance. We are aiming to promote team problem solving, not monitor individuals.

The team should have both lead and lag indicators for each performance measure. A lag indicator measures something that has already happened and a lead indicator is something that will influence the achievement of the lag. The team should be focus more on the lead indicators as they are more likely to influence them.

If we continue the theme of using an accounts payable team as an example a lag indicator might be;

  • % suppliers paid on time

There are likely to be lead indicators that strongly influence whether the organisation pays their supplier on time. These might be:

  • % invoices received on time
  • % goods receipted on time

If the team focuses on improving the two lead indicators, the lag measure logically will also improve.

A range of visuals should be used to bring performance measures to life. This could be line graphs, charts, colour coded data tables et cetera.

STEP 3: DESIGNING PERFORMANCE BOARDS & IMPLEMENTING TEAM HUDDLES

Again a facilitated workshop with the whole team is a the ideal starting point to design a visual performance board which works perfectly for the team.

The board should be visible to all team members and would ideally be a physical board. For teams that are located in multiple locations, digital performance boards can be used effectively.

Ideally the team would create innovative ideas for their board. However the most typical/generic elements for a performance board may include;

  • Team name and purpose
  • Individual status that could be linked to their current workload e.g. amber, green, red (some teams like to have their own fun way of doing it such as selecting emojis)
  • Visual performance measures created in step 2
  • Actions- the recording and reviewing of actions. (These actions should be above standard BAU tasks but more the actions that are linked to identified problems or out of the ordinary tasks)
  • Team successes
  • ‘On the radar’ - keeping the team in the loop of upcoming changes/events
  • Projects status – the projects that affect and/or involve the team and how they are progressing
  • Root-cause problem solving – the key problems currently affecting the team and the stage of resolution
  • Strategic deployment – how the team are tracking against their strategic objectives (more suitable for teams mature with CI)

A Huddle is a session where the team comes together to review performance, plan for the day and progress problem solving activity. 

I would recommend daily huddles of 15 mins for teams with high volume operational work and 30 mins for teams with lower volume work (but no less than two huddles per week). The huddle facilitator should be on a rotational basis. Ideally three roles would be in play including a huddle leader, a timekeeper and a scribe creating actions to go on the board.

Teams benefit greatly from receiving feedback and ongoing coaching to develop their huddles and problem-solving activity over a period of time.

STEP 4: PROBLEM SOLVING

This includes both simple every day problem solving and complex root cause problem solving.

Problem solving naturally follows the steps one to three as teams will easily identify problems that restrict them from achieving their goals which they are monitoring on their visual board and reviewing in their huddles. Actions are created at every huddle with owners and dates assigned and older actions are reviewed and removed when complete. Post-it notes are the most commonly used method for this.

Each team should always have one key problem they are working on, which is likely to involve an element of complexity. This problem may require collaboration with other teams and departments to solve. The team will need to use a root cause problem solving methodology that will help them follow a structure, using different tools and techniques to properly define the problem, identify the root cause and choose & implement an appropriate solution.

An experienced problem solving facilitator is required to support a group through the methodology and tools and ensure discipline is kept to solve root causes rather than just symptoms.

OTHER POINTS TO CONSIDER

Of course there are many other steps in the journey to mature the CI ways of working however these four simple steps applied widely across the whole organisation can really put you on course towards changing behaviours and culture.

There is an investment in time and expertise required (you may have experience in-house) typically with an initial one-day workshop/training session for steps one to three, a separate training session and workshop facilitation for step four and coaching support periodically thereafter. E-learning can also be useful prior to the workshops and training sessions to introduce the CI concepts.

I will leave you with three further tips to making these four steps a success;

  1. If possible, initially take each team to see a successful board from another team/organisation, this can help them see what is possible and put things into practical context
  2. Create a maturity assessment that will help the organisation track progress of each team over a period of time and identify the required coaching support and best practice teams
  3. Senior Leaders must be engaged and regularly visit teams, asking questions and offering support. The principle of transparency needs to be role-modelled to allow teams to feel safe to display problems and true performance

Good luck on your CI journey and be sure to let me know how it goes!

 

RECOMMENDED