There is a saying in marketing that most leaders have heard: good marketing helps a great product soar. But the other side of that truth is the part no one wants to talk about.
Good marketing helps a bad product fail more quickly.
Technology works exactly the same way.
In this episode of the Leaders Rising Podcast, recorded live at the Rising Launch Event, Steve Perky unpacks one of the most consistent and costly patterns inside scaling organizations: the instinct to solve a people problem with a process solution.
The Pattern That Keeps Repeating
Here is how it usually unfolds.
Something is not working. Collaboration is harder than it should be. Execution has slowed. Decisions are taking too long. Leaders are exhausted trying to keep everything aligned. So leadership does what feels responsible. They go looking for a solution.
They evaluate platforms. They bring in a consultant. They build a rollout plan. And then they implement the upgrade.
And then the original problem gets worse.
The natural response is to blame the technology or the company that sold it. But that diagnosis misses the actual issue.
Technology is an amplifier. It does not create new conditions inside your organization. It intensifies the ones that already exist. If your teams are aligned, communicating clearly, and executing with shared direction, technology accelerates all of that. If your teams are misaligned, siloed, or operating without clear rhythms, technology accelerates that too.
The tool is not the problem. The operating system is.
What We Mean by Organizational Operating System
When Steve talks about an operating system, he is not referring to Windows or MacOS. He is talking about the cultural and structural foundation that determines how your organization actually functions.
Every organization runs on one, whether they have built it intentionally or not. It shows up in how decisions get made, how communication flows (or does not), how leaders are developed, and how accountability is held. It is the architecture underneath everything else.
Most growing organizations have not stopped to evaluate theirs. They are too busy scaling. But scaling on top of a weak operating system does not buy time. It accelerates the breakdown.
The diagnostic question Steve poses is a powerful one: Is the operating system you have today intentional and powerful enough to set your people, your teams, and your organization up for success? Or are you running the organizational equivalent of Windows XP in a world that demands something far more capable?
What a Healthy Operating System Looks Like
Aaron Lee frames the answer using LRN’s core framework: Organizational Identity (ORG ID) at the center, with vision, mission, values, goals, rhythms, and people systems built around it.
This is not a diagram you hang on the wall and forget. It is the load-bearing architecture that determines whether every tool, initiative, or hire you bring in will actually hold.
When the ORG ID is clear and shared, technology serves it. When it is absent or vague, technology exposes the gap.
Rhythms are particularly important here. When teams do not have consistent structures for communication, alignment, and accountability, every new implementation creates more noise and more coordination debt. Leaders spend their time managing the chaos the initiative created rather than gaining the clarity they hoped for.
Role ID is the other critical piece. When leaders and team members do not have clarity about what they own, what success looks like in their role, and how they connect to the larger organizational vision, they default to busyness over productivity. Adding a new tool to that environment guarantees confusion.
The Harder Question Leaders Need to Ask
Most organizations ask: what should we implement?
The harder and more honest question is: what is actually running underneath everything we are trying to build?
That question requires leaders to slow down before they speed up. It requires them to diagnose before they prescribe. And it requires the humility to acknowledge that the next initiative may not be the answer if the foundation is not ready to hold it.
This does not mean organizations should stop investing in tools or technology. It means they should invest in the operating system first.
When your ORG ID is clear, when your rhythms are built, when your leaders have Role ID, when your culture has language and shared values, then the tools you add will amplify something worth amplifying.
One Bold Move for This Month
Before your next technology decision or major initiative, run a quick organizational health check with your leadership team. Ask each person to rate your organization on clarity, alignment, rhythms, and role clarity. Look at where the scores land. That is where to invest your next dollar.
Not in the platform. In the foundation.
To hear the full conversation with Steve, listen to the Leaders Rising Podcast:
