
On Wall Street, millions of transactions move within a minute. Decisions happen at a speed that leaves no room for ambiguity. Wrong data gives wrong information. Wrong information leads to wrong decisions. Wrong decisions lead to disruptions in the business and the loss of trust within the industry. Vasa Krishnan watched this play out in real time early in his career, and it changed the trajectory of everything that followed.
Vasa krishnan began his career as a Systems Engineer and evolved into a C-suite technology executive, building a career defined by continuous learning, bold transformation, and strategic leadership. His journey from hands-on engineering to enterprise leadership reflects a unique ability to bridge technology and business strategy, challenge conventional thinking, and translate innovation into measurable business outcomes and let his passion for technology drive every decision after that. What Wall Street gave him, and what he has carried through years of building systems inside major financial institutions, was a fundamental conviction about data strategy that no platform or certification could have produced. Speed of execution becomes a liability rather than an advantage when the data underneath it cannot be relied upon. That conviction sits at the center of everything he does today as Chief Information and Technology Officer at Lüt, the payment brand of Fin Results, where he is building a payment platform from the ground up with AI, security, and governance at its core.
The shift from systems architecture to leading data teams was not accidental. Vasa recognized something most technology organizations still struggle to articulate. Data is not an output of the systems you build. It is the fuel that drives the business, drives the business strategy, drives the decisions about where to invest, and how to grow. Without that fuel, the engine runs on guesswork. He made a deliberate choice to move into the data world because he could see that data was the centralized piece of the puzzle for everything an organization does, and that the fastest systems in the world produced nothing of value when the data running through them could not be trusted.
That reframe, data as fuel rather than data as infrastructure, is the lens through which Vasa approaches every engagement. It is the lens through which he advises boards, builds platforms, and evaluates AI investments. The technology changes. The principle does not.
One principle consistently shapes Vasa’s advisory approach: Business strategy and data strategy are inseparable. They are not parallel initiatives or independently managed priorities they are two dimensions of the same strategic agenda. When organizations disconnect the two, they risk building sophisticated data ecosystems that deliver technical capabilities but fail to create meaningful business value. Data strategy must be driven by business ambition, not technology ambition.
When Vasa sits down with boards and senior leadership at Fortune-level institutions, his first question is always the same. What is your business strategy? Not the technology roadmap. Not the current platform. The business strategy. Once that is clear, the data strategy becomes a translation exercise. You understand where the business is trying to go, and you design the data ecosystem to make that journey possible. Without that clarity, even a well-funded and technically impressive data program ends up solving for the wrong destination.
One of the most revealing exercises Vasa has run in steering committees carries no technology at all. He hands everyone in the room a sticky pad, writes a single word on the board, and asks each person to write down what it means. The word is price. Every single person writes something different. Same company. Same meeting. same strategic context. Completely different definitions.
This illustrates how inconsistent business definitions can create data quality, reconciliation and communication problems across the organization. If the organization has not agreed on what its most fundamental business terms mean, every system recording and processing that data is recording a different version of reality. Reconciliation becomes a permanent operational condition rather than an exception. Decisions get delayed because leadership cannot agree on which number to trust. The data strategy that was supposed to accelerate the business ends up producing the confusion it was supposed to eliminate.
Standardizing business taxonomy is not a technology project. It is a governance decision the business has to make deliberately. Once it is made, the technical work of enforcing it across the data ecosystem becomes straightforward. Until it is made, no amount of platform modernization resolves the underlying inconsistency.
Vasa advises organizations across a wide range of data maturity stages, and he is clear that the advice has to match where an organization actually is, not where it aspires to be. Some institutions have never started their data strategy journey. Some have started and stalled. Some are well advanced and want to understand what the next leap looks like.
For those who have never started, the work begins with a practical, outcome oriented plan. A data strategy session is not a thirty-minute exercise. It takes time to understand the business goals, define the target state, and lay out a phased plan that gives leadership visible results before the full program is complete. Five years without demonstrable output is not a strategy. It is a risk that leadership will not sustain.
For those who started and failed, the conversation is more complex. They have already experienced something not working, and that experience shapes how they approach the next attempt. The job in those situations is to understand what broke, peel back the layers, and fix the foundation before building again. He points to issues such as wrong strategic steps, incomplete planning and gaps in the right talent as factors that can derail a transformation. None of them are primarily technology problems.
Vasa has lived through several major technology transitions. Mainframes gave way to distributed processing. Distributed processing gave way to service oriented architecture and microservices. The internet changed how businesses reached their customers entirely. In each case, the same questions circulated. Is this relevant? Will it last? And in each case the organizations that asked those questions alongside how this serves our business strategy ended up ahead of those that chased the technology itself.
AI is the same. Another transformation phase. The technology is more sophisticated than what came before, but the principle that governs whether the investment delivers is identical. How can AI help you in the context of your business strategy? What are the outcomes you are looking for? What are the suitable use cases, and can you prove value from a pilot before scaling the investment? These questions have not changed since the days of mainframes. They will not change when the next transformation arrives.
At Lüt, Vasa describes AI-driven fraud detection as a use case that delivered meaningful improvement after continued model training and tuning. The result did not come from selecting the most sophisticated model available. It came from getting three things right simultaneously. The first was trusted data. The work relied on trusted data and transaction history used to train and continuously tune the models. The second was operational integration. The AI outputs were connected to the actual processes the fraud operations team used, not running as a separate experimental system. The third was the right team. Experienced people who understood both the fraud patterns and the AI outputs and could tune the models based on what they observed in production.
The result depended on more than the AI model itself. Trusted data, operational integration and the team all had to work together. All three are organizational decisions. The model was capable. What made it produce results was the foundation beneath it. Organizations that try to shortcut the data quality or skip the operational integration consistently find that the AI produces outputs nobody trusts enough to act on. The technology is rarely a limiting factor. The conditions required to use it reliably almost always are.
The traditional CIO role was primarily technology-oriented, but today the role requires both business and technology understanding. The role that exists today requires something different. Boards do not follow architecture diagrams. They have one question that matters, how are you adding value to my business? Technology knowledge gets you in the room. The ability to answer that question in business terms gets you the investment.
A data strategy that lives only in the technology function will always struggle for budget and credibility. A data strategy that is understood and owned by business leadership, connected to specific revenue and growth outcomes, and measured by the decisions it enables rather than the systems it deploys, is a strategy that earns sustained organizational commitment. That is the version Vasa Krishnan has spent years learning to build.
For more conversations with technology and data leaders shaping the future of enterprise AI, follow The Executive Outlook.