Some time ago, a client of mine had a ridiculously long Issues List that was getting out of control. They never seemed to be making progress on resolving their issues - in fact, their issues seemed to be exploding!

EOS^® promises to help you solve your company's issues for good. Over time, you should be seeing fewer issues and gaining new ground as an organization. But what if your Issues List isn't working? It seems like you're rehashing the same issues over and over again, and frankly the Issues List seems to grow rather than shrink.

You've got Issues List Fatigue.

Imagine you arrive at the office one Monday morning. You flip on your laptop, go get a cup of coffee, and come back to your desk – only to discover the blue screen of death. Your laptop is completely unresponsive and you can't do a thing because your operating system (OS) has crashed.

Without an OS, your laptop can't function. And without an operating system for your company, your organization can't function, either. Like your computer, your business needs an operating system to organize the way the organization functions. An OS ensures smooth communication between your leadership team and all your employees.

After your senior leadership team has mastered the Entrepreneurial Operating System^®, there comes an exciting – and maybe slightly scary – milestone in your implementation of EOS: it’s time to teach the rest of the company how to do it. We call this the “rollout,” and it begins when your leadership team works together to help next level leaders, managers and supervisors begin using EOS foundational tools in their departments or teams.

Whether you do your rollout to one layer of management at a time or to everyone all at once, there are a few things you can do to make sure the process goes as smoothly and successfully as possible.

Most companies end up structured in a way that is very unintentional. Recently I told a new client that many companies end up with an organizational structure that looks much more like a platypus than the stallion your company needs. They got a chuckle out of this. I soon learned that the nervous laughter was because they had created a very haphazard, platypus-like structure and they knew they had work to do.

I was on a phone call earlier this week with a client who has 40 employees. He told me about the sudden resignation of one his long-time managers. Here’s the story he shared with me.

“Last week at our quarterly management meeting, one of my key operations managers turned in his resignation. As we discussed the issue, he said all the extra pressure was too much for him to handle. I was thinking to myself, we haven’t even given him any more work to do. All we did was clarify expectations and improve our communication...