Ignoring These Org Smells Puts Your Culture at Risk

How to identify eight common org smells.

I’ve spent a great deal of time with software engineers. They’re my clients, my former co-workers…I even married one. One of my favorite concepts I learned from them is code smells. Here’s how Martin Fowler describes it, “A code smell is a surface indication that usually corresponds to a deeper problem in the system. The term was first coined by Kent Beck while helping me with my Refactoring book.”

I see something akin to this in my field — the human systems operating inside a business. We have surface indications too. I call them org smells. These org smells indicate a problem in the organizational part of the business. They often arise as leaders navigate organizational friction. Sometimes we get a whiff of a problem but struggle to identify the root. We tend to look to individuals as the cause. Sometimes a person really is causing ripples at a business level and needs to leave. The problem can be with an individual leader. I know plenty of stories of execs who left a company because they weren’t up for the challenge. And, organizational issues can masquerade as individual leader failure.

Sometimes the problem is at the system level. These can be tougher to solve, it’s no wonder we hope the issue just resides in one person. When the…