Omar was dejected. He had just spent his annual training budget on a re-engineering consultant. His rationale had been that re-engineering would require a reasonable amount of training to be effective.

Happy at the beginning, the biggest bottlenecks in the plant had been at the top of the agenda. In the re-engineering meetings, everyone was excited and enthusiastic. It was only now, after the project had been shut down and the consultant sent packing that the truth began to emerge.

Omar had intended this process to bring the team together, to create trust, cooperation. Tackling the toughest workflow issues seemed admirable. Only now, he began to learn of the different agendas within the team, hidden agendas, mistrust, turf skirmishes and blaming behavior. That was the buzz. Things were worse now than before.

For Pete’s sake (or Omar’s sake). Why would you take a team and try to solve the most difficult problem on the planet (floor)?

START SMALL. Build trust by having team members report on small successes for the week. Try solving a small problem. Everything the team does sets a precedent for the next team event. If the team tries to solve a difficult problem and fails, they are more likely to fail on the second problem. If the team solves even a simple problem and succeeds, the likelihood for future success (and trust) increases.

START SMALL. Build on strength. -TF