Simplicity as an argument?

Simplicity. Whether it’s stripping away the layers of processes or starting a new project with a goal of minimal steps, the more simplified we make things the more convincing is required throughout an organization. Last night I was thinking about that- about why. I've concluded that it’s easy to poke holes in simplicity, easy to bring up the occasional issues that may or may not happen. It’s easy to debate the need for every contingency. Why? Seriously, why?

How about this; reversing the process. Instead of arguing for more simplicity- state a simple position and ask others to argue for its complexity. Have them rationalize the need for more process, more rules, more stuff. Perhaps when you are forced to argue your points- you’re forced to fully understand them. And when those points are for more and more, instead of less and less- then maybe an inflection point begins to take shape. Maybe, simplicity takes hold, efficiency takes over and ease of business happens.

There is no need for more and more rules, procedures and regulations. There is no need for every contingency to be taken into account prior to launching anything. Smart people will find a way to solve them, but smart people can’t always find a way around complicated rules imposed for too many reasons by too many people.

No comments: