What Your Business Problems Are Actually Telling You
Most operators I work with come in with a solution already in mind. They have identified the tool, sketched the budget, maybe even shortlisted vendors. What they are looking for is someone to confirm the direction and help them execute.
That is the moment I have learned to slow down.
Not because the instinct is wrong. Usually the person in the room has good instincts, built over years of running the business. But the instinct points at a symptom, and the symptom points at a solution, and somewhere in that chain the actual problem never gets named.
Ear with a thread
Problems Have Something to Say
There is a temptation in business, especially when growth is the constant pressure, to treat every problem as a defect to patch. Something is leaking, so you seal it. Something is slow, so you speed it up. Something is missing, so you buy it.
What gets lost in that reflex is the signal.
Every gap between what your business intends and what your business actually does is a form of honest feedback. The leakage is not random. The slowdown is not arbitrary. The missing piece points somewhere. Underneath it is usually a tension between what the organization says it values and what its operations actually reward.
That is worth pausing for. Not forever. But long enough to ask: what is this problem trying to tell us?
Data Is a Starting Point, Not a Destination
I believe most business problems show up in data first. Declining retention, rising cost-to-serve, flat conversion, team throughput that does not match headcount. The data surfaces the signal before the leadership team has language for it.
Hence the first question is almost never "what tool do we need." It is closer to: what is the data showing us, and what does that mean for how this business actually operates?
The answer to that question is rarely a single thing. I have sat with operators who came in certain they had a technology gap, and what surfaced instead was a pricing structure that quietly punished their best customers. I have worked with businesses that thought they needed better analytics and discovered the real constraint was a legal exposure no one had connected to the data yet. I have seen marketing problems that turned out to be organizational, where the numbers were fine and the friction was in how decisions were made between two departments that did not share the same definition of a customer.
None of those answers are what the operator came in expecting. All of them were more useful than the original solution would have been.
Looking glass
What a Real Diagnostic Actually Does
A diagnostic is not an audit. An audit looks for variance from a standard. A diagnostic looks for what the variance is pointing to.
In practice, that means starting with the data, but not stopping there. It means asking what decisions this business makes, where those decisions break down, and whether the breakdown is a data problem, a process problem, a people problem, or something in the structure of the business itself. Sometimes it is all four in sequence, and the data problem is the last one, not the first.
With that said, this is not an argument for slow. Clarity does not require a six-month engagement. It requires the right questions asked in the right order, before anyone is committed to a solution. The cost of clarity upfront is almost always lower than the cost of ripping out a tool that addressed the wrong thing.
Tree trunk
The Most Practical Thing You Can Do Before You Spend
If you are facing a problem that feels stubborn, that has resisted prior attempts, or that keeps returning after you thought it was resolved, consider this before you move to a solution: what is the problem actually costing you, and what is it costing you to have it?
Those are not the same question. The first is about the symptom. The second is about what the problem is protecting, which is usually where the real answer lives.
I am not suggesting that technology is the wrong answer. Often it is the right one, and often it gets to a result faster than any alternative. What I am suggesting is that the problem itself will tell you which answer is right, if you give it a moment to speak.
That is where every engagement I take starts: not with a solution in search of a problem, but with a problem in search of the truth.Text here
Elias Kruger, MBA, is the Managing Principal of Long-Range AI Consulting LLC, where he provides advanced analytics strategy and AI-powered business transformations tailored for midmarket sectors, including community banks, credit unions, and fintechs. His career spans over 22 years of continuous reinvention across finance, data science, and enterprise AI leadership, notably serving as a Vice President at Wells Fargo where he co-led an internal analytics consulting program of over 60 analysts. As a diagnostic-first practitioner, Elias designs customized human-empowering AI-enabled solutions ranging from multi-agent orchestration, RAG-powered workflows to predictive modeling that drives operational efficiency and valuation increases. He is a frequent speaker at major industry conferences like Finnovate.