RSS

Tag Archives: #AITransformation

Why Most AI POCs Stall and How to Build an AI Operating Model That Works

Why Most AI POCs Stall and How to Build an AI Operating Model That Works

A few months ago, I was speaking with a leadership team that had invested heavily in Generative AI. They had done everything right, at least on paper. They hosted hackathons, launched AI innovation days, encouraged teams to experiment with tools like ChatGPT, Cursor, Claude, and Gemini, and generated dozens of exciting proof of concepts (POCs). The demos were impressive. The excitement was real. Then I asked a simple question: “How many of these solutions are actually running in production and creating measurable business value?” The room went quiet.

If you have been involved in AI initiatives, you have probably seen the same pattern. Teams produce innovative AI prototypes, leadership gets excited, and everyone talks about transformation. Yet months later, very few of those ideas become dependable, secure, and widely adopted business solutions.

The problem isn’t the technology. Today’s AI models are incredibly capable. The problem is that most organizations are trying to scale AI without building the operational framework needed to support it. In my experience, the companies that successfully scale AI don’t necessarily have the best models. They have the best operating model.

One of the first challenges organizations encounter is what I call the “happy path” problem. Most AI POCs are built using clean data, predictable scenarios, and carefully controlled environments. Real-world systems rarely behave that way. Customers enter incomplete information, business rules change, systems fail, and unexpected edge cases appear. Many teams react by trying to perfect the solution before launch, spending months solving hypothetical problems. However, I believe that the smarter approach is the simpler one: release a focused solution to a targeted audience, gather feedback, learn from real-world usage, and improve iteratively. The fastest way to build a production ready AI product is to get real users into the loop as early as possible, not to spend months and years to perfect a solution.

Even when organizations overcome that hurdle, they often run into a second challenge: data and integration issues. Most AI failures are not actually AI failures. They are data failures, process failures, or integration failures. A POC can operate on a carefully curated dataset, but production systems need secure data pipelines, governance controls, monitoring, observability, auditability, and integration with existing business workflows. I have seen organizations spend months debating which model to use while completely overlooking the fact that their underlying data ecosystem wasn’t ready. Thus, companies should invest in building a stronger data pipeline, improving their integration testing capabilities, and creating an operational framework that can accelerate pace of innovation. After all, the AI isn’t the problem, the foundation is.

Another common trap is measuring activity rather than outcomes. These days, organizations proudly report the number of tokens used, experiments conducted, prompts executed, or AI tools adopted. Those metrics may indicate engagement, but they don’t necessarily indicate value. The questions leaders should be asking are much simpler: Did customer satisfaction improve? Did operational costs decrease? Did revenue increase? Did employee productivity improve? AI creates value only when it is connected to measurable business outcomes. Everything else is experimentation. That’s why I recommend that organizations regularly review AI adoption, engagement, and ROI through existing governance forums such as Monthly Product Reviews (MPRs), Monthly Business Reviews (MBRs), Engineering Operations Reviews, and Level 10 (L10) meetings. These forums help connect AI initiatives to measurable business outcomes, making it easier to understand what’s creating value, what’s falling short, and where organizations should focus their next investments.

As organizations mature, AI governance becomes increasingly important. Unfortunately, AI governance has developed a bad reputation and is often viewed as the enemy of innovation, since AI models are evolving at an unprecedented pace, heavyweight governance processes often struggle to keep up. In reality, governance is what allows innovation to scale safely. Whether it’s privacy, security, compliance, responsible AI, or human oversight, organizations need clear and repeatable processes that help teams move quickly while managing risk responsibly. The Air Canada chatbot incident serves as a reminder that companies remain accountable for what their AI systems do, regardless of how autonomous those systems may appear. Thus, I recommend that organizations rethink their decade-old governance models. Since AI is evolving rapidly, innovators should not have to navigate multiple approvals and disconnected stakeholders just to get an AI use case reviewed. Instead, organizations should establish a centralized governance forum where teams can bring ideas, ask questions, receive timely guidance, and understand the rationale behind governance decisions. The goal is not to reduce oversight, but to streamline it. By creating a transparent, well-socialized, and operationalized governance framework with regular follow-ups and clear communication, organizations can strengthen governance while simultaneously accelerating the pace of innovation.

Another common mistake organizations make is failing to invest in their people. Like any major transformation, AI augmentation is ultimately a transformation of how people work. Simply providing access to AI models or GenAI tools does not guarantee success. Organizations need to invest heavily in AI literacy, change management, coaching, upskilling, and adoption strategies, just as they would for any other enterprise-wide transformation. Leaders cannot assume that because AI tools are available, employees will automatically use them effectively or that productivity will magically improve. Without the right training, guidance, and support, most employees will either underutilize AI or use it only for basic tasks. Employees need to understand where AI can help, where it cannot, and how to integrate it into their daily workflows responsibly and effectively. After all, if people continue to view AI as nothing more than a chatbot, the vision of building AI-powered assistants, autonomous workflows, and agentic AI solutions will remain out of reach. This is why leaders must build an operating model that reinforces the right behaviors, creates opportunities for learning, and encourages adoption through the right incentives. Ultimately, AI transformation is not a technology transformation. It is a people transformation.

Finally, organizations need to answer one critical question: When AI fails, who is accountable? As tools like Claude, Gemini, Cursor, and GitHub Copilot become part of everyday software development, accountability can quickly become blurred. My view is straightforward. AI can generate content, code, and recommendations, but it cannot own responsibility. The engineer who deploys the code remains accountable for its quality. The product manager who launches the feature remains accountable for its business impact. Human ownership must remain intact, regardless of how much AI contributed to the solution.

The biggest obstacle preventing companies from realizing value from AI isn’t model performance or innovation. It’s the absence of an AI operating system that connects governance, measurement, accountability, data readiness, and talent development into a repeatable framework. AI doesn’t reduce our need for leadership, governance, operational excellence, or execution discipline. It increases it.

 

Tags: , , , , , , , , , , , , , , , , , , ,

Beyond the AI buzz: Delivering measurable results through real-world examples

Beyond the AI buzz: Delivering measurable results through real-world examples

I still remember working on an AI initiative 5-6 years ago for a healthcare company that wanted to transform the patient experience. At that time, AI wasn’t readily accessible to everyone. There were no consumer grade AI assistants generating content on demand. There were no established implementation playbooks. Organizations that pursued AI were often entering relatively uncharted territory.

We were building what felt like a first-of-its-kind platform designed to simplify interactions between patients and healthcare providers using AI. While the vision was exciting, the project was filled with uncertainty. Questions such as how to train the model, how frequently retraining should occur, what datasets should be used, what level of accuracy was acceptable, and what operational costs would look like remained largely unanswered. Every decision felt like an experiment.

Today, most of those technical barriers have been significantly reduced. Powerful AI models are available through cloud providers and APIs. Organizations can now build capabilities in weeks that previously would have taken years. But while many technical challenges have become easier, business challenges have become significantly harder.

The challenge today is no longer whether AI works. The challenge is whether companies understand the operational, financial, and governance implications of deploying AI at scale.

One of the most overlooked aspects of AI adoption is cost predictability. Historically, organizations planned budgets around relatively stable variables such as labor, infrastructure, licensing, and operational expenses. Financial forecasts could be created quarterly and adjusted annually with reasonable confidence.

AI is changing that equation. A company’s AI consumption could fluctuate dramatically based on customer adoption and usage patterns. An application might consume 100,000 tokens on one day and 10 Million tokens the next. A highly successful AI-powered feature can introduce operational costs that were never anticipated during planning.

For technology giants such as Microsoft, Apple, Google, Amazon, and Nvidia, these fluctuations can often be absorbed because of their scale and ability to invest heavily in AI infrastructure. For most organizations, however, especially those dependent on product revenue and operating within tighter margins, this new consumption driven model introduces uncertainty that many finance teams have never had to manage before. Thus, today’s companies should shift their focus from “Can we build it?” to “Can we sustainably support it?” That is where organizations need a different approach. 

So, let me provide you some pointers through which you can implement AI sustainably in your organization.

1. Use AI as a Tool, Not a Strategy: 

One of the most common mistakes organizations make is treating AI as a technology initiative instead of a business initiative. AI should never be implemented simply because it is available or because a competitor is using it. If you want to be successful in this AI race, then you need to  identify a specific business outcome and then determine whether AI is the right tool to achieve that outcome.

Instead of asking: “How can we use AI?”, you should ask: “What business problem are we trying to solve?”. The answers should be measurable and meaningful, not just some buzz words. For example, AI will reduce customer service costs by X%, or it will improve employee productivity by Y%, or it will increase customer retention by Z%, etc.

In one Fortune 500, I was called to coach the team in launching an AI chatbot because competitors had announced similar initiatives. But after several workshops, I identified the underlying problem. The real issue turned out to be the excessive amount of time employees spent searching for information across disconnected systems to help their customers. So, rather than building a flashy external facing solution, we implemented an AI-powered knowledge search platform for internal users. Adoption was immediate, employee productivity improved by 20%, and the ROI justified the costs of tokens. Thus, I recommend that you should also focus on outcomes first and technology second.

2. Start With High-Value Use Cases

Many Fortune 500 companies are attempting AI transformation through large, organization-wide initiatives. While it might work for 20% of the top tech companies, I believe that other Orgs should identify use cases that are easy to measure and relatively low risk, before heavily investing into AI transformation. In some of the companies where I have recently consulted, I often see AI augmentation opportunities within internal knowledge management, customer support automation, document summarization, meeting intelligence, workflow automation, and sales enablement.

For example, in one of the largest companies, we introduced AI-generated meeting summaries for their sales calls. While this initiative sounds relatively small compared to larger transformation, the productivity gains and lead conversion rates were transformational for the company. SDRs and BDRs had all the insights about their clients on their fingertips and they spent less time in refreshing their memories and more time in converting the lead into an actual sale. 

Thus, I believe that AI should be used in these targeted initiatives to provide immediate value and actual ROI. This approach isn’t flashy, but it works. Small wins create confidence, confidence creates momentum, and momentum enables scale.

3. Build Guardrails Before Scaling

Once organizations begin seeing success, there is a natural temptation to expand AI rapidly. After all, C-Suites are pushed by their stakeholders to show big wins through AI quickly. 

However, I believe that AI adoption without governance can quickly become expensive, inconsistent, and difficult to manage. I strongly believe that all the Orgs should establish guardrails before broad deployment. This includes monitoring usage trends, creating cost management controls, setting spending thresholds, defining approval processes, implementing security standards, and establishing performance monitoring frameworks.

Recently, I was coaching this S&P 500 company that had seen situations where individual departments adopted multiple AI solutions independently. Marketing purchased one platform, operations implemented another, and customer support selected a third. While each decision appeared reasonable in isolation, the organization eventually found itself managing overlapping vendors, inconsistent security controls, and rapidly increasing costs. Thus, I strongly recommend you to think through your AI strategy and implement internal support systems for building guardrails and governance before everything goes out of hand.

In the end, the organizations that succeed with AI over the next decade will not necessarily be those spending the most money or tokens. They will be the companies that approach AI with discipline. They will understand the difference between experimentation and strategy. They will balance innovation with governance, ambition with financial accountability, and opportunity with measurable outcomes. Most importantly, they will stop asking: “How can we say we are using AI?” And instead ask: “Where can AI create sustainable business value?” That distinction may seem small, but it changes everything.

The future will not belong to companies that can simply claim they use AI. It will belong to companies that can clearly demonstrate why they use AI, how they govern it, and the value it delivers. Because in the end, AI should be more than a buzzword. It should be an impact multiplier.  

 

Tags: , , , , , , , , , , , , , , , , , , ,

How AI Transforms Program Management: From Reporting to Strategic Partnership

How AI Transforms Program Management: From Reporting to Strategic Partnership

Early in my career at a couple of Fortune 500s, program management excellence often meant one thing: being able to produce a clean, defensible status report. Green boxes built credibility. Red ones triggered escalation. The irony was that by the time something turned red, everyone already felt the pain, the report simply made it official.

Fast forward to today, use of AI often exposes an uncomfortable truth: much of what we call program management has been information movement, not decision support. Startups figured this out long ago. They don’t have the luxury of formal status cycles; they rely on shared situational awareness. AI finally allows large organizations to do the same without collapsing under scale.

What changes is not visibility, but interpretation. AI is extremely good at synthesizing fragmented signals into a coherent story. That’s something PMOs have historically tried to do manually, often under time pressure and political constraints.

In most of these big tech giants, I have often seen programs where risk doesn’t emerge explosively, it creeps. A dependency slips a sprint. A scope assumption quietly changes. A team compensates heroically. None of this is “red,” but all of it matters. AI excels at spotting these slow burn patterns precisely because it doesn’t get tired, defensive, or distracted by hierarchy.

Thus, I have been extensively using AI into my day-to-day activities by replacing weekly status decks with weekly sense‑making narratives. Instead of asking teams to explain why something is red or green, I have been using Rovo and Cursor to ask questions like: What’s drifting from plan but not yet obvious? What commitments are most vulnerable if nothing changes? These questions provoke far better conversations, provide helpful insights to the leadership team, and help the core project team to maneuver challenges.

The practical change required to implement this workflow is surprisingly small. You just need to enable Rovo agent in JIRA, work with your teams to fix JIRA hygiene challenges, and connect Cursor with your Atlassian suite. Once you do the groundwork, you can then feed AI your existing artifacts like Jira updates, roadmap changes, sprint notes, and ask it to generate insights rather than summaries. You can then review these insights and share it with your teams. This workflow and its visibility will fundamentally change how your teams operate. Over time, teams will stop optimizing for optics and start optimizing for coherence.

So, I strongly believe that AI won’t make program managers irrelevant, but it will make them more like strategists and less like couriers. The PMO of the future won’t be judged by how accurate its reports are, but by how early it helps leaders see reality and help them win through data driven decision making.

 

Tags: , , , , , , , , , , , , , , ,