RSS

Tag Archives: #FutureOfWork

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: , , , , , , , , , , , , , , , , , , ,

New Operating Model for Product & Engineering Ops in the World of AI

New Operating Model for Product & Engineering Ops in the World of AI

When I first saw teams experimenting with AI before it became cool, the behavior felt really familiar. It reminded me of how teams treated Agile in the early days, something you “use/follow” rather than something that fundamentally reshapes how work flows. Teams were excited, curious, and well intentioned, but almost everyone was underestimating the change in front of them.

At larger enterprises like GE and Schneider, operations always lived a layer below the visible product surface. Customers never see the spreadsheets, the JIRA workflows, the dependency maps, or executive readouts, but those invisible systems determined whether strategy delivered the outcomes that we were looking for. AI is now inserting itself directly into that invisible layer.

Most teams today are using AI as a chatbot. They paste in meeting notes, ask for summaries, maybe generate a PRD draft or clean up status language. That’s fine, but it’s also like using a high performance engine only to power the radio. The real power shows up when AI becomes part of how decisions get made, not just how words get written.

I saw a version of this contrast clearly when working with startups versus large enterprises. Startups rarely debate whether a process is “ready.” They automate thinking early because speed leaves no alternative. In contrast, large organizations often wait for certainty, governance, and sign‑off, which delays leverage. AI flips this dynamic. For the first time, large companies can gain a startup‑like operational awareness without burning people out.

The biggest mental shift is this: AI is not just another productivity tool, it is an operating layer that sits between data and action. Every organization already has raw inputs: roadmaps, sprint plans, incident logs, metrics, emails, Slack threads. What most lack is synthesis at scale. Humans do this manually, inconsistently, and too late. AI changes that.

One of the most effective early experiments I have seen is when we stop asking AI to “do work” and start asking it to “explain the system.” Thus, I often ask questions like: What changed this week that mattered? Where are we accumulating hidden risk? What assumptions are we acting as if they are true, but haven’t validated recently? These questions help me sharpen my approach and provide insights that I can quickly review and validate with my organization’s strategy.

Another practical way to begin is to deliberately wire AI into your operating cadence. For example, before every weekly program review, I feed my model JIRA updates, dependency map, and roadmap changes. After that I ask it for a narrative and compare it against my overall understanding of the program. This approach has helped me cut down my manual tasks by almost 40%. Recently, I have started providing some additional context to my model and started asking it what tradeoffs it will make based on the information and using that to improve program’s execution. If you follow this approach, then overtime AI will become your partner and help you expedite decision making. 

I believe that the teams that win with AI won’t be the ones who generate content faster. They will be the ones who design systems where insight appears earlier, decisions happen cleaner, and surprises shrink. This isn’t a tooling upgrade, it is an operating model shift.

 

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