The Problem Behind the Problem
Many problems are actually process problems. Something isn’t working smoothly in task handling, handovers, decision-making, or the customer journey. But because software is visible and tangible, it quickly gets pointed to as both the cause and the solution.
Before you know it, IT becomes the leading factor. New requirements are evaluated based on what the system can handle. Processes are adjusted to match the capabilities of the tooling. And slowly but surely, everyone forgets what the actual business goal was in the first place.
At that point, IT is no longer a means to an end. It has become the end itself.
A Practical Example
One of our clients had gradually expanded a well-known CRM system. Understandably so: the vendor’s sales team was convincing, the demos were impressive, and the promised ROI looked attractive.
The logical conclusion? Focus even more on that system.
Step by step, the CRM platform was expanded with processes it was never really designed for. What started as a customer management system slowly evolved into something resembling an ERP solution.
At some point, no one was asking the fundamental questions anymore. It had simply become the default assumption that all processes had to run through this one system.
With a lot of effort, the organization managed to make it work for quite some time.
Until the moment it became clear that they had created a monster of a system. Complex, difficult to modify, and nearly impossible to oversee. Changes became risky and slow.
At that point, software had indeed become the problem, but not because the technology itself was bad. The real problem was the series of decisions made along the way.
The Solution: A Helicopter View Without Constraints
Every solution starts with perspective. And the guiding principle should always be the same: Let software follow the process, not the other way around.
Change Your Perspective
Step back and look at what has quietly become “normal” in day-to-day operations. Only then do you often realize how far things have drifted from the original goal.
Build Reflection Into Improvement Processes
Create fixed checkpoints in every improvement initiative. Force the team to zoom out at key moments.
Step into the helicopter and ask: How does what we are doing today contribute to our business goals?
Keep Steps Small
Work in short cycles. Deliver in increments, test, learn, and adjust. Approaches like Scrum or other Agile methodologies almost always work better than spending months “underwater” and launching a big-bang solution at the end.
Don’t Design Around Limitations
When designing your ideal process, don’t start with the limitations of your current systems. Start with what truly works for your organization.
The Role of AI
In the past, designing around software limitations was understandable. Custom software was expensive, complex, and time-consuming. The rule was simple: only build custom solutions if absolutely necessary.
AI has changed that landscape.
Today, much more can be built faster and often at lower cost. As a result, the key question is shifting from:
“Does our process fit inside this standard tool?”
to
“Why would we force our ideal process into the constraints of a standard tool if we can build a flexible solution faster?”
AI makes it possible to put processes back in the driver’s seat, instead of systems.
Software as a Growth Driver
Software should not determine how you work. It should enable what you want to achieve. In the end, it’s not about systems, tools, or even AI. It’s about direction. As long as organizations keep designing their processes around the limitations of their software systems, complexity will continue to grow. But organizations that start with the ideal process and consciously use technology as an accelerator build adaptability instead of dependency. Software should always be (and that’s how I personally see it) a catalyst for growth.
