Most conversations about AI are either too technical for business leaders or too generic to be useful. What Comes Next with Arun fills that gap. Each episode translates real-world data and AI strategy into the language of competitive advantage — drawing on Arun’s 20+ years inside the world’s most complex enterprises, six years as a Microsoft Data & AI Executive, and his experience building Tipsora into a platform serving more than 95,000 professionals worldwide. This is not a podcast about AI tools. It is a podcast about building the organizational intelligence that makes tools matter.
Most organizations bought the AI. What they skipped was the thinking required to make it matter.
In this solo episode, Arunansu Pattanayak sets aside the frameworks and tells one story — the moment, after 20+ years inside Merrill Lynch, Citibank, Credit Suisse, JP Morgan, TD Bank, and Microsoft, when he finally understood what actually breaks in transformation. It was never the technology.
He unpacks why technically excellent systems fail to change anything: people keep using old workarounds no one asked about, leadership announces "data-driven decisions" while the culture keeps making the same instinct-driven calls, and departments quietly guard their own version of the truth because controlling the data means controlling influence. None of those are technology problems. They're organizational behavior problems wearing a technology costume.
The episode closes on the realization that reshaped how Arun works: intelligence architecture isn't a technical framework — it's a sequencing philosophy. Governance, culture, and decision-making readiness, built deliberately in the right order, alongside the technical build rather than bolted on after.
This week's action item is inside.
Subscribe and leave a 5-star review if this shifted how you think about AI in your organization.
Most organizations bought the AI. What they're missing is the thinking required to make it matter. I am Arnand Sapatnaik, ex-Microsoft Data and AI executive, CEO of Tipsora, and your host. This is What Comes Next, the podcast where we talk about building the kind of organization that actually wins in an intelligence-driven economy. Let's get into it. No framework, no five-point model, just a story. A story about one moment after years inside some of the most complex organizations in the world, when I finally understood what was actually breaking transformation. It wasn't the technology, it was never the technology. Twenty plus years inside Enterprise Data and AI, it started at a small consulting firm. Then the big financial institutions, Maryland, Citibank, Credit Suisse, Jeppy Morgan, and most recently, TD Bank. I like to think of organizations as houses and departments as rooms. Throughout my career, I worked in every one of those rooms. Every single time I was brought in to fix what everyone called a technology problem. New systems, new platforms, new AI capability always framed the same way a technical challenge, needing a technical solution. And early in my career, I believed that framing. I thought if I brought the right architecture, the right data model, the right tool, the transformation would just happen. And here is the thing, I was good at the technical work. I built systems that ran exactly as designed. And again and again I watched those technically excellent systems fail to transform anything. At EY, I learned how regulated risk-averse organizations think about change. How the right technical answer gets stuck, not because it's wrong, but because no one built the organizational trust to adopt it. At Merrill Lynch and Citibank, I saw something else. How deeply legacy decision-making habits survive even the most sophisticated systems we installed around them. People kept making decisions the old way, using new tools as expensive decoration. At Credit Suisse, I watched a technically sound data initiative struggle for years, not because the architecture was flawed, because no one had done the organizational work getting different departments to agree on what the data even meant. And at Microsoft, at the center of the AI ecosystem itself, I saw the pattern repeat. At a scale and a speed that made it undeniable. The technology was getting better and better, faster than organizations could figure out how to use it well. Across every one of those environments, the failure rhymed. A new system goes live, the people meant to use it differently keep using their old workarounds. Because no one asked why those workarounds exist in the first place. Leadership announces a data-driven decision culture, then keeps making the same instinct-driven calls they always made. Because changing how decisions get made means changing how power and accountability work. And that's a much harder conversation than buying a new software. Departments protect their own version of the truth because in a lot of organizations, controlling the data is also a way of controlling influence. None of those are technology problems. They are organizational behavior problems wearing a technology costume. So what did the organizations that actually succeed have in common? Across every industry I have worked in, they never treated transformation as a single project with an end date. They treated it as a capability they were always building. They were willing to have the uncomfortable conversation about why people resisted change instead of assuming resistance just meant more training. They built real cross-functional trust before they built cross-functional systems. Because no data architecture, how elegant, survives departments that don't trust each other's intentions. And they were honest about the hardest truth of all. The technical work was the easy part. The human work underneath, it was always the hard part. I can point to the exact moment this clicked for me. I was sitting in a room after yet another technically successful, organizationally stalled initiative. And it hit me. I had been thinking about this backwards. My entire career, I had been building the intelligence infrastructure first and hoping the culture and the decision making would catch up. It never did. Not reliably, not at scale. That's the moment intelligence architecture actually emerged for me. Not as a technical framework, as a sequencing philosophy. Governance, culture, decision making readiness, built deliberately in the right order alongside the technical architecture. Not bolted on after the technology is already live. Everything I teach on this show, every framework I bring you traces back to that one realization. Technology was never the bottleneck we were. The action item this week, pick one transformation initiative from your organization's recent history, one that failed or stalled, and ask yourself honestly, was the actual problem the technology or was it organizational behavior, wearing a technology costume? I think you already know the answer. Most of us do, once we are willing to look. If this episode shifted how you think about AI in your organization, send it to one person who needs to hear it. And if you are ready to act, visit tipsora.com to get certified or reach me directly at urnansupertank.com. The intelligence economy is already here, though the question is whether you are building for it. That's a wrap on today's episode of What Comes Next. If this conversation gave you a new way to think about AI strategy, share it with someone who needs it. You can find everything I'm building at tipsora.com, including AI certifications for you and your team. Connect with me on LinkedIn by looking up my name, Arunan Sipatnaik. Until next time, build the architecture. The advantage follows.
