When things go wrong - and they will - do your teams know how to respond? If not, team members can grow frustrated, issues will go unreported or not properly diagnosed, and quality will suffer. A defined process provides a path for team members to follow, lets them know expected behavior, and helps teams navigate issues from root-cause analysis to resolution and improvement.

Define the triggers

Understanding what constitutes an issue is the first step. These are easily understood when defined by a trigger - e.g. X minutes of equipment downtime. It's useful to involve the Team in defining these triggers, so they they feel ownership of any issue they encounter. The triggers should be specific with an agreed criteria for escalations. These could be agreed separately for different categories: Safety, Environment, Quality, Productivity, Cost or People issues. They could be either equipment, process or behavior related - depending on the application and the culture the Team are striving for. They could even be specific to a challenge the Team is working towards. The main thing here is that the triggers are understood and signed up to.

Make it easy

Whether it's instant and on the spot, recorded and addressed later on, or in a regular Team meeting - there needs to be zero barriers to raising the incident. The barriers come in many forms - pure self-doubt, disengagement, a lack of clarity on expectations, not wanting to show up a problem caused by others, a lack of basic understanding on the issue, or a perceived (or real) lack of support if the incident is raised. The list of possible barriers is long. If the incident is not raised there can only be 2 explanations - there are no problems, or there are too many barriers stopping people. We've all got problems, so develop a psychologically safe culture and enable the Team. Just make it simple.

Act quickly

The Team's goals are clear, their expectations of each other are defined, all barriers to raising an incident have been removed. The Team leader's role is now all about support - with speed. It's not about taking the issue from the Team member, asking them to resume work and then solving it for them. Support means developing the team member so that they can resolve it. The first level of support may be just an extra set of hands to get through the immediate required actions. Next, it’s about working with the Team member to determine the root causes of an issue or refining an improvement idea. From here this could then turn into a coaching opportunity to improve the Team member’s knowledge or skill. Engage their creativity to find a better way, or develop their confidence and leadership to work with others to resolve the issue. Whatever the support, it needs to be immediate or the moment will be lost.

Give recognition

When sincere efforts are made, there should be open recognition and the person that raised the issue should be personally thanked.  After all, they overcame many potential barriers to raise the alarm - let them know they are safe to do it again. What you openly reward and recognize is as good as a broadcast message defining your Team's cultural norms, and provides muscle memory for when they are met with their next opportunity.

TeamAssurance is an Operational Excellence Management System designed on principles that build a healthy and resilient operations culture. Contact us to find out more.