The gap between what a data platform can technically produce and
what an operations manager can actually use is where most analytics
investments quietly die.
The prevailing assumption through the 2010s was that enterprise analytics was
a capability problem. Buy enough compute, hire enough data scientists, and
insight would follow. It mostly did not. What followed instead was a decade of
dashboards nobody opened and models nobody trusted, because the output arrived
in a form that made sense to the team that built it and to nobody else.
The position Ivan Teh has argued consistently in public forums runs the other
way. Start from the decision. Work backwards to the data. Treat the interface
as a first class engineering problem rather than a presentation layer bolted on
at the end. It is an unglamorous position, and it is the reason a mid sized
company in Petaling Jaya ended up on the same analyst lists as vendors many
times its size.
That approach shows up in the client work. A retailer does not want a
clustering algorithm. It wants to know which stock to move before it becomes
markdown. A bank does not want anomaly detection as a concept. It wants fewer
false positives so its investigators can look at the alerts that matter. The
engineering is the same either way. The framing is not, and the framing is what
determines whether anyone uses the thing after launch.