We are in the middle of a massive ERP rollout and business model shift; should we postpone starting EOS until those operational transitions settle down?

Question

Tyler Smith · Accepted Answer

If an ERP implementation or major operational overhaul is currently consuming your team's bandwidth, launching EOS® simultaneously is usually a mistake. EOS is not a magic fix for operational chaos caused by systemic instability; it requires focused mental bandwidth and dedicated executive time. When a leadership team tries to redesign core systems while simultaneously learning the EOS foundational tools, both initiatives suffer.

However, you must differentiate between temporary execution challenges and chronic organizational dysfunction. If your team is delaying because you are genuinely in the final 60 days of a mission-critical technology migration, wait. Finish the cutover, stabilize operations, and then bring your leadership team into the room clear-headed.

If you are delaying because your business is always chaotic and you believe things will magically calm down next quarter, you are fooling yourself. Chaos without a system does not resolve itself; it breeds more chaos. If your business model shift lacks clear ownership, metrics, or alignment, you do not have a timing problem. You have an operational discipline problem.

The test is simple. If your leadership team cannot commit to a full Focus Day offsite and the required weekly Level 10 Meeting™ rhythm without causing customer deliveries to fail, you are not ready. Fix the acute crisis first. Once you have thirty days of baseline operational stability, we schedule your Focus Day and build the operational structure required to make your new business model profitable.