Building a Reliability Team

Abstract

Dianna and Fred discuss building a reliability team.

Key Points

Join Dianna and Fred as they discuss building a reliability team.

Topics include:

• the difference between being a manager and building/leading a team.


• why a reliability program should not rely on one person.


• the importance of business risk and how to quantify it with input from a team.


• how ad hoc teams can solve problems and create opportunities for continuous improvement.

Plus, find out how a reliability engineer saved a company millions of dollars by building a team to solve a problem.

Enjoy an episode of Speaking of Reliability. Where you can join friends as they discuss reliability topics. Join us as we discuss topics ranging from design for reliability techniques to field data analysis approaches.

Show Notes

Fred and Dianna discuss the differences between being a manager and building a team, noting that simply managing a department is very different from creating a team to solve a specific problem.

They emphasize that a reliability program should not be built around one person, as that program will disappear when that person leaves the organization.

Building a team requires influence, explaining the benefits, and getting people to understand what’s in it for them.

A key element of a team is understanding business risk. The team can assist with putting a dollar amount on the risk to get a project going.

Ad hoc teams can be useful to solve problems, like a customer complaint, or for continuous improvement. The team should include people from different parts of the organization. In one case, a reliability engineer built a team that saved a company millions of dollars by identifying bottlenecks in the prototype process.

There can be reliability lessons in business systems and processes as well.

The post SOR 1046 Building a Reliability Team appeared first on Accendo Reliability.