Without a System Nothing was done Wrong

Several incidents lately have helped shape or remind me of an important team principle.

Team friction developed on our team recently. Nothing major, but noticeable. That isn’t unusual on teams. Teams involve imperfect people with differing views and opinions. The best teams will have friction at times. The only way to avoid some it would be to institute a more controlled environment, where opinions don’t matter. But, then friction really isn’t eliminated. It’s just silenced. For a time.

Our friction resulted from:

• Miscommunication
• Unclear expectations
• Unknown objectives

Ever seen that on a team?

We all have. Those are common reasons for friction.

Here’s the principle that emerged:

Apart from a system nothing was done “wrong”.

Here’s what I mean.

Sure, the friction was wrong. Sure the miscommunication, unclear expectations, unknown objectives…all wrong. All of those, however, are natural occurrences when there is no system in place to address those concerns. Or when the system isn’t good enough. People were performing under the current systems…or lack thereof…the best they knew how.

And, systems are important:

• If you want something repeated and done well you systematize it.
• If you want something done better…you create better systems.

And, every system should continually be: 

• Evaluated
• Reconstructed
• Refined

Systems drive progress and if you want better progress keep getting better at your systems.

So, back to our friction. As a leader, it’s important for me to realize and remind people: No one did anything wrong. We were making decisions the best we knew how under the current systems. And in the process, unnecessary friction developed. Totally natural.

What is important now is to learn and write a system. Or a better system. To keep that type of friction to a minimum.

Sometimes, as a leader, you can calm the friction on your team by:

• Releasing people of a sense of guilt…which only causes them to be defensive…resulting in even more friction.
• Identifying the need for improved systems.
• Leading the process to create or develop better systems.

Here’s to writing better systems.