Every so often, I hear it: “That’s not EOS® Pure.”
And I have to take a deep breath and get ready for a longer discussion. This typically happens in reference to a feature we have built or a customization we allow within our EOS® features and it’s almost always from a long time EOS Implementer™.
I get it. EOS is meant to be followed very closely, especially in the beginning (which is typically when EOS Implementers™ are engaged). They don’t want organizations changing a proven model and they are 100% right. But I think there are nuances here and that’s what this blog is all about…. sharing my perspective / rebuttal to the inevitable “that’s not EOS pure” comment about a feature or a setting we have built in Strety.
For background and context, I’ve been running on EOS for almost ten years now across three companies (with and without Implementers). And over the past two years I have seen thousands of companies use Strety to run on EOS. So here’s my perspective on it!
Truth #1: Eventually, All Purists Flex the Tools
We see this every single day with our customers. After a while, even the most purity-minded integrators start massaging the tools to fit their organization.
It’s not that they change the core; you won’t see anyone taking the Vision/Traction Organizer and renaming it the Traction Vision Organizer. But maybe a 10-Year Target doesn’t resonate with their team anymore, so they use a 5-Year Target instead. Small shifts like that seem to make the framework more believable and therefore more actionable.
That’s a small example but we’ve seen bigger flexes from “EOS pure” people, like including Project Updates as an agenda item in L10 meeting agendas (that happens a lot with Strety Projects now). Before you reach for the trash bin to vomit, let me explain more!
Integrators who would start adding Project Updates to L10 agendas are almost always from long-time EOS-run organizations, or what EOS Implementers would call Graduated organizations. And I think it’s pretty awesome to keep EOS relevant to an organization after you have the essential tools down pat (even just to keep things fresh). Ultimately EOS is a framework, not a manual or a rulebook. Frameworks imply flexibility and since every business is unique, there’s no way a single model will fit every company perfectly.
Truth #2: Even Implementers Disagree on “EOS Pure” sometimes
I’ve personally had countless one-on-one conversations with EOS Implementers about features to build and how to improve Strety. And I can’t tell you how many times I have heard one Implementer say “we need this, it’s EOS Pure” and another will say the opposite. I don’t have the heart to argue with them and it’s never about the most fundamental things (like running Meeting Pulse). So I know it’s just up to us to decide on what’s the best functionality for the companies running on EOS.
Btw, I do think the difference in opinion comes from (1) the length of time and Implementer has been coaching clients and (2) that each Implementer brings a unique flavor to how they teach, facilitate, and guide.
Those two points above really lead to my last point… which is that every software platform is built by people with a point of view.
Truth #3: We’re Integrators at Heart with a Long History Running EOS
We are definitely customer #1 for Strety after our years of running EOS ourselves. We build our platform with that lens first and foremost. And we do have some varying experiences too, not to worry! I’ve used EOS in a tiny software startup (here), at a fast growing 40 person software company, and in a 30 year old services business with 70 employees. So I’ve seen a wide range of usage which certainly impacts my point of view quite a bit. For better or for worse of course.
More simply put, our point of view is that EOS software should help you work on the business and in the business, in one place. We build with operators and integrators in mind, because that’s who we are.
Fortunately it’s been resonating… one of my favorite quotes came recently from a well known financial consultant:
“The fact that you clearly use EOS in your business while building Strety for others using EOS really shows. Continue to appreciate the ‘little things’ that show up in the usability of the software that communicate, ‘oh yeah, these folks actually USE their own software.’ Keep it up!”
That’s exactly our ethos.
EOS Pure + (a.k.a. EOS+)
So yes, you can run EOS Pure with Strety. But when you start flexing, we’re right there with you as well. That’s why we sometimes refer to ourselves as EOS Pure + (or just EOS+). Because you can do more than just EOS pure with Strety…and how awesome is that to do more with less software!
At the end of the day, I’ve realized my job isn’t to chase purity, it’s to help you and I get results with software and EOS®. I think it’s the right approach. If you think differently, let me know!