If you’ve spent any significant time in the corporate world, you know the drill. A big, exciting transformation is announced. The consultants roll in with their fancy presentations, the leadership team is buzzing, and everyone feels that rush of optimism.
Then, nothing happens. Or worse, it crashes and burns.
I’ve watched this scene play out for over 30 years. I’ve been that consultant. I’ve been that leader. And honestly, I’ve been that frustrated employee wondering why the “big vision” never trickles down to my daily reality . The statistics floating around say that 70% to 95% of digital transformations fail. That’s not just a number; that’s wasted money, lost jobs, and broken trust .
After three decades in tech—from IT administration to building teams at AWS and Airbus—I finally stopped complaining about the problem and started building a solution. That’s why I’m building CapabiliSense.
It’s not just another SaaS tool. It’s my attempt to bring clarity to the chaos, to give leaders an honest mirror, and to make sure that the next big idea doesn’t die on the vine because of politics, confusion, or misalignment.
The Problem with the “How”
We’re pretty good at figuring out the “what” in business. We know we need to go to the cloud, adopt AI, or become more agile. We’re also decent at the “why”—usually to save money or beat the competition.
But the “how”? We stink at the “how.”
I’ve seen the same patterns repeat across continents and industries. It’s rarely the tech that fails. It’s the humans. It’s the lack of a shared understanding. It’s the middle manager who feels left out, or the risk officer who shows up at the last minute to block a project because nobody thought to include them earlier .
Traditional methods treat capability like a software update. You can’t just “install” a new skill or a new process on a human being and expect it to stick.
My “Aha” Moment Wasn’t a Moment
You often hear about founders who had a lightning-bolt epiphany in the shower. Mine wasn’t like that. It was death by a thousand cuts.
There wasn’t a single “aha” moment. It was more like seeing the same movie for the 30th time and finally deciding to walk out of the theater .
I remembered a time when a massive company got sold on the “cloud dream.” The leaders were excited, but the IT teams just stared blankly. They had no idea how this helped them. Meanwhile, an expensive contractor was happy to keep billing hours without actually moving the needle. The project stalled, the vision died, and the company lost millions .
I got tired of being the guy who translates between the “visionaries” and the “doers.” I thought, Why can’t a platform do this? . That question is what started CapabiliSense.
A Real Example: The “Respect the People” Trap
Let me give you a quick story that still makes my blood pressure spike. I once joined an organization where a team had spent three years building a custom tool to do something that a free, ready-made solution from a cloud provider could do instantly.
When I suggested we look at the free alternative, the pushback was immediate. I was told, “You have to respect the people.”
Sounds noble, right? But the result wasn’t respect. It was waste. The in-house tool never worked, internal customers got frustrated and built their own shadow solutions, and the company ended up with a mess of duplicated work and deep silos .
That’s a political deadlock. It’s opinion versus opinion. And you can’t beat opinion with a better opinion. You can only beat it with evidence .
What is Capabilisense? (And Why the Name?)
So, what am I actually building? CapabiliSense is an AI-powered platform designed to be a compass for organizational transformation . The name comes from blending “capability” and “sense-making.” Because my goal is to help organizations make sense of their own strengths and weaknesses .
Think of it as a diagnostic tool for the health of your change initiatives. It analyzes the documents you already have—strategy decks, project plans, emails—and builds an evidence-based map of what’s really going on. It highlights where the gaps are, who’s not aligned, and what the actual risks are .
It’s not about guessing. It’s about knowing.
Here are the three principles CapabiliSense is built on:
Capabilities are Contextual: You can’t copy-paste a winning formula from one company to another. What works in a stable environment breaks in a crisis. We need to assess skills against real challenges .
Growth Requires Sensing: You need to know where you are before you can figure out where you’re going. CapabiliSense helps teams reflect on their actions and interpret feedback so they can adjust in real time .
Systems Shape Behavior: You can train people until you’re blue in the face, but if the incentive structure or company culture undermines that training, nothing will change .
It’s About People, Not Just Processes
Look, I’m building a tech platform, but my heart is in the human side of this equation. When a transformation fails, real people lose their jobs. Real families feel the stress. Real careers get derailed .
I want to build something that protects people from that. By giving everyone—from the C-suite to the front lines—a clear view of the roadmap, we build trust. When people understand “what am I actually supposed to do to help with that big vision?” they stop resisting and start contributing .
Actionable Steps: How to Think About Capability Today
You don’t need to wait for a platform to start changing how you think about growth. Here are a few practical tips I’ve learned the hard way. You can start using these tomorrow:
Start with the “Crux,” Not the Buzzwords
Don’t start by saying, “We need to implement AI.” Start by asking, “What is the single most critical obstacle to our success right now?” Richard Rumelt calls this the “Crux.” . Identify that one thing before you do anything else.
Change the Questions You Ask
Stop asking, “Did you meet your target?” Start asking questions that prompt real thinking . For example:
What assumptions did you make about the customer this week?
Where did your team disagree, and how did you handle it?
If you had to do that project over, what would you change?
These questions build metacognition—the ability to think about your own thinking. And that’s the hallmark of a truly adaptable person .
Map Your Challenges
Sit down with your team and map out 2-3 recurring obstacles. Is it cross-department communication? Is it slow decision-making? Once you identify the pain point, you can diagnose whether it’s a skill gap or a system gap .
| Do This | Don’t Do This |
|---|---|
| Start with real, current challenges your team faces. | Launch training programs based on abstract industry trends. |
| Encourage experimentation and treat failures as data. | Punish people for mistakes made while trying new things. |
| Observe behavioral changes to measure progress. | Rely only on course completion certificates. |
| Let teams help design their own development paths. | Impose a top-down curriculum without input. |
Where We Go From Here
I’m not going to pretend this journey is easy. My co-founder Alex and I have had to make hard calls—including pausing active development recently to re-focus and listen to the market again . That’s the reality of building a startup. You pivot. You learn. You get back up.
But the mission isn’t dead. It’s just getting sharper .
I believe we’re entering an era where technical skills become obsolete faster than ever, but the demand for judgment, resilience, and collaboration explodes . We need tools that help us navigate that ambiguity.
That’s why I’m building CapabiliSense. To arm brave leaders with the reality they need to cut through the politics and make good things happen .
Let’s Build This Together
I’m sharing this journey publicly—the wins and the losses—because I think we can all learn from each other. If any of this resonates with you, if you’ve got your own “battle scars” from a failed transformation, or if you just want to follow along, I’d love to connect.
Drop a comment below, share this post with someone who needs to read it, or [subscribe to the newsletter] to follow the real, unfiltered story of building CapabiliSense.
Let’s make the next transformation the one that actually works.
