Is your operating system actually working?
Bloom Growth
Is your operating system actually working?
Summary
Find out if your operating system is running your business or just sitting in a shared drive. A system that works shows up in behavior. Decisions get made, priorities stay visible, and the same obstacles stop reappearing week after week. A system that has stalled still produces meetings and documents, but nothing downstream changes. Below you'll find a six-question checkup you can run with your leadership team this week, the warning signs worth watching, the four reasons systems usually stall, and a practical way to fix what you find without scrapping everything and starting over.
Index
- Having a system is not the same as running one
- The six-question checkup
- Warning signs your system has stalled
- Four reasons systems stall
- The sunk cost trap
- How to restart without starting over
- When switching systems actually makes sense
- What "working" looks like
- Where to go from here
1. Having a system is not the same as running one
Most leadership teams do the hard part first. They block the offsite session, write the vision, name the quarterly priorities, and add a weekly meeting to the calendar. Then a big client escalates. A key person resigns. A quarter gets away from them.
Six months later the artifacts are still there. The behavior is not.
That gap is the whole issue because the framework you follow is not a document or software. An operating system is a set of habits that repeat until they become how your company thinks. When those habits hold, the documents stay useful. When the habits slip, the documents become archaeology.
In Flourish, Todd Smart describes looking under the hood at companies from $5 million to $200 million in revenue and finding duct-tape foundations behind polished exteriors. His conclusion is worth holding onto before you start this checkup: messy is normal. Every business has gaps. The real question is whether your system surfaces them and moves them, or whether it just files them.
2. The six-question checkup
Run this with your leadership team, but run it the way Flourish recommends for its self-assessment exercise: have each leader answer privately first, then compare. Collaborating in the moment produces polite consensus instead of useful information.
Can each leader name this quarter's priorities without opening a document? If the answer is no, the priorities exist but they aren't operating. Visible priorities change decisions. Filed priorities don't.
Does your weekly leadership meeting end with owned decisions? The Bloom Weekly is built around this. It's a 90-minute meeting that dedicates a full hour to opportunities and obstacles, and it uses a method called 3D, or Discover, Discuss, Decide. Discover the root cause, discuss the desired outcome, and make a permanent decision.
Are your KPIs predictive, or do results still surprise you? Flourish frames the weakest version of this clearly: outcomes are often a surprise. Strong KPIs measure the weekly activities that produce your quarterly and annual goals, so you see trouble early instead of at close.
Do issues get solved once, or do they keep coming back? Recurring items on your list are the single most reliable signal. A system that works retires issues permanently. A system that has stalled recycles them.
Has anything in the system changed in the last six months? This one catches problems the others miss. A living system gets adjusted because the team noticed something wasn't serving them. If nothing has changed, either your fit is perfect or nobody is paying attention. Usually it's the second one.
Does anyone below the leadership team know the system exists? Leadership teams typically need three to six months to learn the system well enough to teach it. After that, the cadence should be spreading. If it has stayed at the top for a year, adoption stopped.
🧠 Bloom tip: Decisions become to-dos with owners, due at the next weekly. If your meetings end in shared understanding rather than assigned action, that's the leak.
3. Warning signs your system has stalled
Beyond the six questions, a few patterns show up consistently in teams whose systems have quietly gone dormant.
- The weekly meeting gets shortened or moved whenever the week gets busy.
- Quarterly priorities get set, then reviewed at the end of the quarter rather than every week.
- One person, usually the CEO, is the only one who references the framework.
- Team members describe the system as reporting rather than as how work gets done.
- The written plan is current, but nobody can point to a decision it changed.
- New hires learn the tools without learning the reasoning behind them.
None of these is fatal on its own. Three or more together usually mean the system has become a ritual.
4. Four reasons systems stall
Partial adoption
Teams take the parts that feel comfortable and skip the parts that create friction. Unfortunately, the uncomfortable parts are often the ones doing the work. Skipping the issues portion of a weekly meeting keeps the meeting pleasant and keeps the business stuck.
Leadership doesn't model it
Culture flows downhill. When leaders arrive unprepared, treat priorities as suggestions, or skip the cadence during a busy stretch, everyone else reads that as permission.
Wrong fit for your stage or culture
A framework designed for a 200-person manufacturer will feel like overhead at 30 people. A framework designed for a 15-person startup will break at 100. Rigid systems make this worse, because the terminology and structure can't bend toward how your team already works.
No support after launch
This is the most common one, and the least discussed. A two-day kickoff builds enthusiasm, not habit. The Bloom Growth Journey is structured as a multi-year, coach-guided path for exactly this reason, with full-day sessions at Bloom Days 1, 30, 60, and 90, then quarterly planning and annual reviews after that. The cadence is the point. Momentum comes from returning to the work, not from launching it well.
5. The sunk cost trap
Here's where a lot of leadership teams get stuck. You've spent real money on training, licenses, and offsites. You've spent something scarcer, too: your team's patience. Admitting the system isn't working feels like admitting the investment was wasted.
So teams keep going, quietly, for another year.
A cleaner way to think about it is to ignore what you've already spent and ask one question instead: If your team were choosing an operating system today, with everything you now know about how your company actually works, would you choose this one?
If the answer is yes, you have an adoption problem, and section six is where to go.
If the answer is no, you have a fit problem, and section seven is where to go.
6. How to restart without starting over
Most struggling systems don't need replacing. They need focus.
Flourish includes an exercise built around this idea. Leaders individually rate the company from 1 to 3 across a set of core areas, where 1 means significant work is needed and 3 means the company is excelling. Ratings stay private until everyone is finished. Then the team combines scores and identifies the three lowest-rated areas, which represent the biggest sources of pent-up potential.
From there, the sequence matters:
- Address the lowest-rated area over the next 90 days.
- Take on the second in the following quarter.
- Handle the third within nine months.
That pace feels slow to ambitious teams. It works because it's survivable. Most businesses see meaningful change by focusing on only two or three of the Bloom 8 Essentials rather than attacking all eight at once. Those eight essentials are: Growth Plan, People, Sales and Marketing, Meetings, Finance and Data, Process, Technology, and Relationships.
If you want one place to start, start with meetings. The weekly cadence is where every other essential either gets reinforced or gets forgotten.
7. When switching systems actually makes sense
Sometimes the fit really is wrong. A few signals point that way rather than toward an adoption fix.
Your framework uses terminology your team quietly refuses to adopt, and you can't change it. Your software doesn't support your methodology, so the team maintains spreadsheets alongside it. Nobody is accountable for helping you implement, so every problem becomes an internal debate. The framework itself hasn't been meaningfully updated in years, while your business has changed considerably.
Worth noting: switching frameworks and switching software are separate decisions. Plenty of companies run EOS, Scaling Up, or Pinnacle successfully and simply need a platform that fits the way they already operate. Bloom Growth's software is growth-system agnostic, with customizable terminology and native support for meetings, priorities, KPIs, and opportunity and obstacle lists. If your methodology is fine and your tooling is the friction, you don't need a new operating system. You need better tools underneath the one you have.
8. What "working" looks like
A functioning system is usually unglamorous. Meetings get shorter. Fewer things fall through. Skepticism fades because results show up before the enthusiasm runs out.
Pam B. at Copado put it this way: "The old way left me frustrated. Now, with Bloom Growth, our team is more productive, stays on track, and finishes on time. No more tangents in what used to be a meeting of tangents. I would have bet my next vacation that this system wouldn't work for us—but it does, and I'm so much happier!"
Stacey C. at Tekton Research described a similar shift: "I love the meeting format—it's made our time together far more effective and productive. Meetings are now half as long, thanks to improved focus and efficiency. Tracking issues alongside action items has streamlined task management completely."
Neither of those is a story about a dramatic transformation. Both are stories about a cadence that finally held.
9. Where to go from here
Take 20 minutes at your next leadership meeting and run the six questions. Answer privately, compare openly, and resist the urge to explain away the low scores. Then pick one area and commit to it for 90 days.
If you'd rather start with an outside read, our business health assessment takes about seven minutes and gives you immediate insight into your business strengths and weaknesses, along with a starting point for the second half of the year.
The second half of the year is still yours. What you do with it depends less on the system you chose than on whether you're willing to use it.
