Stack Tool Confusion Signs

Nobody wants to be the one who questions the tool the last person bought before they left.

That stack was bought before the problem was defined, and there are four tells. I hear them in the first hour of most platform reviews:

1. The tool has no owner. Somebody championed the purchase, then moved on or left. It still runs, and the licence renews itself every year without a conversation.
2. Nobody can name the metric it was supposed to move. “Faster dashboards” was the whole spec: no named dashboard, no target, no user. That wasn’t measured before, so it can’t be measured now.
3. The old system is still running. The migration reached 80%, the last 20% was political, and you now pay for both.
4. The vendor’s reference architecture is your architecture. Every box exists because it was in the diagram, sized for the reference customer’s problems rather than yours.

None of these make the tool wrong. Snowflake, Databricks and Fabric are all good at what they do. The waste is in the parts you bought for a problem nobody stated.

The defusing question is cheap before a purchase and awkward after: what specifically gets better, for whom, and how will we know in 90 days?

How many of the four would your current stack score?