By Phil La Duke
“Break down barriers between departments. People in research, design, sales, and production must work as a team, to foresee problems of production and in use that may be encountered with the product or service..”—W. Edward Deming’s 9th Point.0
It’s been a couple of weeks since I continued my series on how W. Edward Deming’s points apply to safety. Deming’s ninth point, “Break down barriers between departments. People in research, design, sales, and production must work as a team, to foresee problems of production and in use that may be encountered with the product or service” is another one of Deming’s points that really doesn’t take much imagination to connect it to safety. (My take on the previous points can be found on this and my personal blog—yes, it’s a gimmick to read both, but if you give it a chance I think you will glean useful material from both sites).
Safety has to be about more than just not getting injured, it has to be about making the workplace better WITHOUT sacrificing safety and that takes teamwork. For far too long the safety department has seen itself as somehow removed from the core business and with every consultant on the planet screaming for Operations leadership to cut cost and concentrate on its core business such think is more than just wrong-headed, it is practically suicide.
“Us Versus Them” Conflict
One of the chief sources of destructive conflicts in organizations is the “us versus them” view of the workplace. Nowhere is the better evidence than in the on-going battle between Safety and Production, Safety versus Engineering, or Safety and Continuous Improvement. Safety has been the policeman for so many decades that it is tough for other areas of the company to see them as any thing but obstructionist. Safety for its part, often sees the other departments as recklessly pursuing profit with little regard for the safety of the workers. It’s a faux dichotomy; nobody really wants to jeopardize lives in favor of profit, and safety doesn’t want to shut down the company to eliminate injuries. But “us versus them” conflict has deep roots and can be difficult to over come.
In many organizations, the Safety function grew out of Human Resources (HR), which in turn, has its roots in personnel. For many years, HR was the rules and write-up department. Operations made the money and HR was always mucking about with new rules. Human resources has evolved into a highly functioning partner in most companies success but for some people the memories of HR throwing up roadblocks without offering alternative solutions run deep. Fairly or unfairly, Safety has been tarred with that same brush, and needs to do something about it.
Safety often has little love for Operations, which it sees, as too willing to take reckless chances and put people at risk. It is seldom that Safety sees Operations as evil or as having malicious intent; it’s just that it sees Operations as less than realistic about the likelihood of an injury.
The rift between Safety and Engineering can run almost as deep. Engineering changes to a process that is in production tend to be costly and difficult to implement, and even the most carefully designed processes often need to be tweaked after they have been built and installed. Safety professionals rightly expect Engineering to design a safe and capable process, but Engineers aren’t always able to “engineer-out” every hazard. Engineering often see Safety professionals as showing up with objections without solutions—Safety professionals tell Engineering what they CAN’T do without offering viable, safer, alternatives. For their parts, Safety professionals counter that an unsafe design is an unsafe design and it is not their responsibility to design a safe system, rather its job is to identify issues and provide guidance as to whether or not a system is safe.
Perhaps the most bitter—and surprising—rivalry is between Safety and Continuous Improvement. This conflict is part “us versus them” and part “territoriality”. It’s not surprising that there would be considerable overlap between the two groups. Both functions can rightly claim that activities like 5S (6S to the masters of the obvious who realize that “safety” also begins with an “S” and have renamed the activity); it’s little things like this that make the Continuous Improvement professionals roll their eyes when the Safety professionals open their mouths. Safety, on the other hand, resent the CI team referring to them as “non-value added” activity. Many Continuous Improvement groups eye Safety greedily and whisper in the ear of Operations leadership that Safety should reside within the umbrella of CI. Safety, views CI as working too hard to make process improvements without considering the impact changes can have downstream in the process.
Can’t We All Just Get Along?
As Deming points out, all activities must work as a team, to “foresee problems of production and in use that may be encountered with the product or service”. If worker injuries, over exposure that causes industrial illnesses, or fatalities don’t represent a problem that will interfere with production, it is difficult to envision one that would. But how can an organization break down these barriers? Sometimes the simplest solutions are the best:
- Co-located Teams. Conventional wisdom holds that functions should sit together, after all, doesn’t it make sense that everyone in a functional department would sit together. Unfortunately, teams that aren’t housed together (in some organizations, an individual might never have met his or her program manager in person, interacting only on conference calls and via email.) Co-located teams (those where members are seated with their project teams instead of their functions) tend to be more cohesive and higher functioning than other teams.
- Goal-Based Compensation. It may surprise some to learn that many team members are compensated dramatically different than their colleagues from different functions. As long as one function can be successful while the other fails there is a strong danger of creating destructive competition and conflict. Cross-functional teams should be given a common goal and compensated according to how effectively they achieved it.
- Cross-Training and Interdisciplinary Rotations. The best way to understand and value a teammate’s contribution to the team is to walk the proverbial mile his or her shoes. A greater understanding of how each function operates is key to closer working relationships. Cross training or a rotation to a different function can greatly improve the level of cooperation between groups.
Not every Safety function is at odds with other functions (this is the kind of disclaimer I have to put in because despite my earnest belief that my readers are smart enough to distinguish between me identifying a problem and not weaseling it up by qualifying each statement with a “many” “few” or similar verbal marshmallows some half-wit inevitably stumbles across my post and hammers out a frothy “I hate you” email) but those who fail to reach a high degree of collaboration with traditional rivals will likely go the way of the dinosaur.






















