Ninety’s Post

View organization page for Ninety

23,213 followers

It’s not the software that makes EOS work. But the wrong tools can absolutely slow it down. That’s the point behind this post from EOS Worldwide Implementer Ken Bogard and it’s one we hear from teams running on Ninety every day. When execution breaks down, it’s usually not the framework. It’s the friction. Scattered tools, lost data, and disconnected conversations make it hard for even strong teams to stay aligned. As one Integrator put it: “Using Ninety makes my job easier. I can’t imagine being in the Integrator role without it.” The comments speak for themselves. Wondering if Ninety is the right tool for your team? Take a look.

View profile for Ken Bogard

Your EOS implementation is failing, and it's not EOS's fault. Some of my most successful clients increase their EOS buy-in across the organization because they use EOS One or 90io. RPRS Leadership teams get fired up about EOS, create a collective Vision, start L10 meetings, create Scorecards... 💪🏻 Then they try to manage it all with spreadsheets, email threads, and whatever random tools they can muster up. What happens next: 🔸 EOS rollout to the next level feels chaotic Mike logs in to 5 different sheets on Tuesday morning for his L10. Sarah tries hers on one choppy Word doc and updates during the L10. Jim forgot his login to that shared drive... again. People’s Rocks are scattered across three different platforms, and nobody knows which version is current. 🔹 Buy-in disappears completely When the system is clunky, people blame the system. "This EOS stuff is too complicated." "I can't find my numbers." "The spreadsheet crashed again." Now your biggest skeptic has ammunition... AND they're not wrong, a big piece of the execution is broken. 🔸 You're giving the 5% an excuse That person who already resists accountability just got handed the perfect out. Technology problems become their shield against real conversations about performance. They blame EOS; others join in. I can understand... EOS software feels like another expense when you've already invested in implementation. The truth... When your team spends 15 minutes or MUCH more trying to organize themselves, you're bleeding productivity and slowly killing the momentum that got you excited about EOS Worldwide in the first place. The investment alone will save your teams time. The software doesn’t make EOS work. But bad tools will ABSOLUTELY make it fail at the next levels. Software isn’t the end-all be-all for EOS success. But it is a HUGE crutch to help keep rollouts nice and tight. So what's it gonna be? Really commit to a system you know and love, or keep watching your team check out one broken spreadsheet at a time? Agree? Disagree? What disasters have you seen trying to run EOS without proper software? *95% of my 70 clients run on some EOS-type software.

  • No alternative text description for this image

To view or add a comment, sign in

Explore content categories