Monday, November 16, 2026

Experience before Acceptance: A 1681 Lesson for Today’s Buying Decisions

 

I want to share a revelation came to me while I was reading “Dasbodh” a book written by Shri Samartha Ramadas Swami in the year 1681. One of the fundamental principles of today’s Customer Experience Management was clearly articulated more than three centuries ago. This book is written to guide common man to live his/her life meaningfully. There are teachings around what to do, how to do, when to do, what not to do, etc.

Author clearly says that “do not accept the teaching because I say, experience yourself and then accept them”. There is one subchapter (8th Sub Chapter(samas) from 10th Chapter (Dashak) titled as “Prachiti Nirupan” which means “Exposition of Experience”) dedicated to this thought. It tells us that one should not accept the information because someone has shared it with you nor you should accept it because someone is recommending it to you but you should first experience it and make your own judgement about acceptance.  

Accepting recommendations and follow them in a personal scenario described three hundred years ago is very similar to Buying a product/service from a company in the today’s business context. It is important to visualize the benefits as well as assess the risks by experiencing it. Experience provides pros and cons and builds confidence to make the decision of accepting the recommendation or buying/using a product. The similarity is interesting and clarity comes through various examples given in the verses which definitely have parallels in the today’s customer buying paradigm

There are 34 verses in the subchapter and let us examine a few verses (verses are in language “Marathi”, followed by Marathi words written in English to enable reading followed by translation in English in the brackets to understand meaning (from English translation of Dasbodh by Shri W G Tambwekar)). It is followed by description on what they reveal about experience once we transpose acceptance of teaching to accepting of product/services

Verse 2

नाना रत्नें नाना नाणीं ।Nana Ratne nana Nani (Many Jewels and many coins)

परीक्षून न घेतां हानी ।Parikshun na gheta hani (One suffers loss, if they are taken without examination)

प्रचित न येतां निरुपणीं ।Prachit nay eta nirupani (If one does not get experience in the discourse)

बैसोंच नये ॥ २ ॥Baishochi naye (One should not attend the sermon)

Transposition to Today’s Customer Buying Paradigm: Unless a customer gets the right experience or proof of quality, he/she should not buy the product or service. Customer should get an opportunity to examine the product for its value, which could be through product trial, product demonstration, free subscription to make determination of its suitability before making a buy decision. There are chances that if customer does not get an opportunity to play with the product, customer may not buy the product; so it is critical for the supplier to create these opportunities and make them available to customer. Whenever such opportunities are not possible, then at lease customer reference or cases studies should be created to provide secondary experience.    

Verse 4

बीज उगवेलसें पाहावें ।Beej ugavalese pahave (Ensure that the seed grows)

तरी मग द्रव्य घालून घ्यावें ।Tari mag Dravya ghalun ghyave (Then only pay money and procure)

प्रचित आलियां ऐकावें ।Prachit alia aaikave (If one gets actual experience)

निरुपण ॥ ४ ॥Nirupan (then only listen to the delivery)     

Transposition to Today’s Customer Buying Paradigm: Invest in to any product / Service once it is established that it solves the problem correctly, it addresses the needs completely. Customer is able to validate the outcome before the investment decision is made. Customer may not be comfortable to make a buy a software or any other product just based on polished sales presentation unless they get the confidence that it is really going to address their requirements.

Verse 6

प्रचितीविण औषध घेणेंPrachitivin Aushadh ghene (Taking medicine without experiencing relief)

तरी मग धडचि विघडणे ।Tari mag dhadachi bighadane (Then even healthy one gets sick)

अनुमानें जें कार्य करणें ।Anumane je karya karane (Whatever work is performed on Guesswork)

तेंचि मूर्खपण ॥ ६ ॥Techi murkhapan (That is sheer foolishness)

Transposition to Today’s Customer Buying Paradigm: It has a two-way message

For customers: Do not make your buying decision on assumptions or guesswork; look for proof / evidence (experience) before making your decision.

For Suppliers: Do not assume that customers will buy the product simply because company believes it is good. Many times, Companies design products based on their understanding of customer needs. They invest in development, marketing, sales without adequately validating whether customer actually experiences the need that product intends to fulfill. The right Product-Market fit is critical for successful product. There were not many tools available in 17th century to assess needs of customer, but now we have several tools available. “Differentiated Needs Pyramid” is one such tool created by me to understand the stated and unstated needs of customer, which can be used by companies before they finalize the design of the product. https://www.amazon.com/dp/8195052657

There are many verses which give other examples to get the understanding of the principle of “getting Experience is Critical to buying process” and can be read to get further clarity.

Even in the year 1681, it was customer experience, which was advocated to be key for a customer buy-in and same is true today. It is important for companies now to determine how do we get our customers to experience the product to create their own experience or how to create a secondary experience through examples and entice them to make a decision or we use another method to start the process. Some approaches companies can follow to create opportunity for experience are:

Direct Experience                          Free Trials, Demonstrations, Product Samples

Controlled Experience                   POC, Pilot Projects

Indirect Experience                       Customer testimonials, Case Studies, References

Simulated Experience                   Product Simulation, Interactive Demonstration

Outcome based Experience          Business value Assessment, ROI Demonstration

Not every product / service could be experienced beforehand; in such cases company should try and create secondary experiences, indirect experiences to ensure customer gets a feel of how their needs will get satisfied.

Virtuous Cycle of Product and Customer Success:


The success for customer, which is determined by the experience, is driven by great product and success for Product is determined by Customer loyalty, which is dependent on customer experience. This virtuous cycle, explained in the picture. Once in motion, it can drive great success to both Product company and Customers. Off course, it requires effective implementation, onboarding, support, usability and ability to deliver promised outcomes along with the great product to make it successful but once Companies find a way to kickstart this cycle through first experience, it can continue on and on.

Conclusion

Principle of “Experience before Acceptance” was true in 17th century and is true even now. Now we have support of multiple tools like “Differentiated Needs Pyramid”, to understand needs and measure outcomes which can help us create better products and give better experience to customers and run the virtuous cycle of Product and Customer Success

Saturday, September 26, 2026

Revenue Acceleration Perpetual Cycle

 

Revenue Acceleration is critical for every business to succeed. The organizations which are able to find ways to increase its revenue on continuous basis, are able to provide value to their stakeholders. Organizations are in search of a structure and process which, if adopted, gives them a clear roadmap for Revenue Acceleration.

I am sharing a set of three videos, which explain the Framework of Differentiated Needs Pyramid and Processes around it. Once Organizations adopt this structured framework and processes around it, they can continuously produce strategies for accelerating the revenue.

Part 1- Talks about relationship between Customer Experience Improvement and Revenue Increase and core reasons for a disconnect

https://lnkd.in/p/gGAT_qZh

 

Part 2 – Talks about the core model “Differentiated Needs Pyramid” which describes impact on Revenue from stratification of needs and their satisfaction

https://lnkd.in/p/dZujTTij

 

Part 3 – which brings all the things together and guides how to create revenue acceleration plan

https://lnkd.in/p/ggM-dYAB

 

Share your feedback and experiences.

Wednesday, September 23, 2026

AI Needs a Theory of Constraints: How Do Governments & Enterprises Can Create Higher Societal Value from AI?

      AI is advancing at an extraordinary pace.

Hundreds of billions of dollars are being invested across the AI ecosystem, and the demand for more investment continues to grow. AI is becoming pervasive, touching almost every aspect of our personal and professional lives.

Competition is intense. Development cycles are accelerating. At the same time, some industry leaders and policymakers are increasingly calling for appropriate safeguards and regulatory frameworks.

But there is another question that deserves more attention:

Are we getting proportional societal value from the enormous investment and effort going into AI?

I believe there may be a systemic reason why the answer is not always yes.

AI is a chain, not a single technology

Investment is happening across the entire AI value chain covering Data centers, storage and cloud infrastructure, Energy and communications, Chips and semiconductors, Foundation models, Data infrastructure, Engineering and coding, Cybersecurity, Robotics and industrial AI, Autonomous systems, Business-specific applications, AI skills and capability building, and Governance and regulatory frameworks

A significant proportion of investment is currently concentrated in infrastructure and foundational capabilities.

Yet, at the same time, we repeatedly encounter situations such as:

  • AI is hungry, but the grid isn't ready.
  • The pilot is successful, but the data isn't ready.
  • The AI agent is ready, but cybersecurity and guardrails aren't ready.
  • The capital is available, but the required compute or chips aren't available.
  • The application is ready, but the regulatory framework isn't ready.
  • The technology is ready, but the organization isn't ready to redesign its processes around it.

Each of these represents a mismatch somewhere in the AI value chain. And that mismatch can limit the value that the entire system can deliver.

Could this be a Theory of Constraints problem?

The Theory of Constraints (TOC) by Goldratt is based on a relatively simple principle: The throughput of a system is constrained by its most limiting constraint.

Instead of trying to optimize every component independently, TOC asks us to identify the constraint that is limiting the overall system, make the best use of that constrained resource, align the rest of the system around it, and then elevate the constraint.

Once the constraint moves, we identify the next one.

I believe this thinking can be applied to the AI ecosystem.

But there is one important difference. A manufacturing system typically optimizes throughput for a business. For AI, the ultimate objective should be broader i.e. Maximize value AI creates for humanity

Applying TOC to AI

Classic TOC-- AI ecosystem interpretation

Identify the constraint-- Find what is currently preventing AI from creating more societal value

Exploit the constraint-- Get maximum utilization from the existing scarce capacity

Subordinate everything else-- Align other resources and activities around the constraint

Elevate the constraint-- Invest, innovate or change policy to increase the constraint's capacity

Repeat-- Once the constraint moves, identify the next constraint

What could the constraints be?

The constraints can exist at different points in the AI ecosystem.

  • Capital: Is there sufficient financing for infrastructure, applications and deployment?
  • Compute: Are sufficient GPUs, accelerators and computing resources available?
  • Energy: Can electricity generation and availability keep pace with AI infrastructure?
  • Physical infrastructure: Are data centers, grids, cooling systems and networks available?
  • Data: Is the required data available, accessible, high-quality and usable?
  • Talent: Do we have enough AI engineers and domain experts?
  • Organizational capacity: Can organizations redesign processes quickly enough to take advantage of AI?
  • Economics: Does the cost of AI deployment make economic sense relative to the benefits?
  • Human adoption: Do employees, customers and citizens have the capability and willingness to use AI effectively?
  • Problem selection: Are we applying enormous AI capabilities to the problems that can create the greatest value?

The constraint doesn't have to be technological.

In fact, the most important constraint may sometimes be organizational, economic, regulatory or human.

Let's consider two examples

1. Electricity availability

Imagine that the AI industry can build 100 GW of additional compute capacity, but the power system can support only 60 GW.

The additional 40 GW of compute cannot generate its expected value until the energy constraint is addressed.

In this situation:

Compute is not the binding constraint; Electricity availability is.

Investing more money in compute without addressing the energy constraint would therefore increase capacity without proportionally increasing societal throughput.

The same principle applies to data centers.

A data center may be constructed in 2–3 years, while energy generation, transmission and grid connection can require substantially longer planning and development cycles.

Therefore:

Building more data centers does not necessarily solve an AI capacity problem if the energy system cannot support them.

2. Capital allocation

Consider a hypothetical situation in which there are 10,000 potentially valuable AI applications, but only 1,000 have access to adequate capital.

Capital becomes a constraint.

But simply adding more capital isn't necessarily the answer. The more important question becomes:

Where will the next dollar of capital create the greatest increase in societal AI throughput?

Should it go toward: another foundation model or AI infrastructure or energy infrastructure or healthcare AI or education AI or cybersecurity or industrial AI or AI agents?

The answer should depend on which investment removes a binding constraint and enables the greatest additional societal value.

The multiplier effect of constraint removal

Some constraints may be more important than others because removing one constraint can unlock several others.

For example: Energy infrastructure enables Data-center capacity which enables Compute availability which enables AI applications which enables Enterprise adoption which creates economic and social value

In such a situation, investment in the original constraint can have a multiplying effect throughout the system.

This leads to an interesting question:

Should we measure investments not only by their direct return, but also by the additional AI capacity and societal value they unlock elsewhere in the system? I believe we should.

Constraint prioritization becomes critical

The AI ecosystem will almost certainly have multiple constraints simultaneously. Therefore, we need to prioritize them.

One possible approach is to evaluate each constraint based on:

  • How much additional throughput will its removal create?
  • How early is it in the AI value chain?
  • How many downstream constraints will it unlock?
  • How much investment is required to remove it?
  • How quickly can it be removed?

And the constraint will keep moving

This may be one of the most important aspects of applying TOC to AI.

Today's constraint may be Compute, tomorrow it could be Energy then it could be Talent. Therefore, AI policy & action cannot be a one-time exercise. Constraint identification & removal needs to become a continuous process.

What role should governments and enterprises play?

I believe both have an important but different role.

Governments and Policy institutions

Governments can address constraints that affect entire ecosystems through:

  • Infrastructure investment
  • Energy and grid policy
  • Education and workforce development
  • Incentives
  • Data policy
  • Standards
  • Regulatory frameworks
  • Public-private partnerships
  • Research and development
  • International cooperation

The objective should not necessarily be for governments to pick individual AI winners. Instead, governments can help identify and remove systemic constraints that affect many participants simultaneously.

Enterprises

Enterprises should apply the same thinking internally.

Their constraints may be:

  • Data availability
  • Legacy systems
  • Talent
  • Capital
  • Process design
  • Integration
  • Cybersecurity
  • Change management
  • AI governance
  • Employee adoption

The question becomes:

What is the single most important constraint preventing our organization from obtaining more value from AI?

Rather than implementing AI everywhere simultaneously, organizations could focus their transformation efforts around that constraint.

The bigger question

AI capability may not ultimately be limited by the intelligence of the models.

It may be limited by our ability to build the infrastructure, energy systems, data ecosystems, organizations, skills, policies and human capabilities needed to convert that intelligence into value.

Perhaps the next AI challenge isn't simply building more AI.

Perhaps it is identifying and removing the constraints that prevent AI from delivering its full potential to society.

This is a concept I am currently developing, and I would genuinely value perspectives from people working across AI, infrastructure, investment, enterprise transformation, government policy and organizational change.

What do you think is the biggest constraint preventing AI from delivering greater value to society today?

Wednesday, August 5, 2026

The Conversational AI Paradox: Why Great Introductions Are Still Ending in Frustrated Customers

 We have officially entered the era of daily interactions with Conversational AI Agents. They are on the front lines of customer service, evolving rapidly, and each sitting at a different stage of human-like sophistication.

Having interacted with several AI voice agents across Retail, Banking, Telecom, and Insurance over the past few weeks, I’ve experienced a full roller-coaster ride of Customer Experience (CX).

Here is what is working exceptionally well—and where the experience breaks down.

Phase 1: The Good News (Greetings & Identity Verification)

1. The Voice & Opening Greetings The voice quality, natural cadence, and greeting mechanisms are nearly perfected. There is no longer that jarring robotic delay, making the initial connection comfortable for the caller. I will give it an A+ grade

2. Upfront Transparency Most agents immediately state: "I am an AI agent here to assist you." Setting expectations at the beginning which builds trust and establishes a strong CX foundation. I will give it an A Grade

3. Understanding Intent Instead of rigid interactive voice response (IVR) menus ("Press 1 for Account Balance…. "), AI agents ask open questions in natural prose. In 80–85% of my tests, the agent accurately reflected my intent back to me in plain English, adapting effortlessly to my accent and vocabulary. I will rate them at A- grate

4. Frictionless Authentication Identity verification across industries was seamless. In one case, the AI identified me by my phone number, confirmed my name, and thanked me for being a premium club member. At this stage, the CX felt modern, hyper-personalized, and impressive. This is at A+ Grade

Phase 2: Where the Experience Breaks Down

While the beginning of the journey feels seamless, the actual resolution phase reveals critical gaps. I am sharing two cases for better understanding of the challenge

Case 1: Repair Appointment (Hardware /Appliance store) - Scheduling Disconnect

  • The Goal: Book a repair appointment.
  • The Interaction: The AI agent picked up immediately, verified my details, and walked through morning/afternoon options for the next few days. We booked the appointment for tomorrow. Appointment details were sent to me over an e-mail.  I was thrilled.
  • The Flaw: The confirmation email arrived for the day after tomorrow, rather than tomorrow as requested. The whole interaction with agent seemed to be a waste. Driven by urgency, I walked into the physical store directly. To my surprise, there were multiple open slots available for that same day and I could complete my work on the same day. I was now doubting the capability of Agent to bring in right information resulting in to a really bad impression
  • The CX Takeaway: A delightful conversation means nothing if the underlying logic delivers inaccurate outcomes. It leaves the customer questioning the utility of the AI altogether.

Case 2: Obtaining Clarification (Mortgage / Financial Services) - The Infinite Loop & Abrupt Hang-Up

  • The Goal: Seek clarification on a complex notice.
  • The Interaction: Authentication and intent-capture went smoothly. Very Happy
  • The Flaw: After asking about the clarification, the agent forced the conversation into a rigid option-tree loop. When I explicitly said, "I am unable to find the right option, please connect me with a human agent," there was a brief pause—and the line went dead. I was shocked and frustrated
  • The CX Takeaway: Getting stranded without a human fail-safe leaves customers feeling undervalued. It conveys that the organization prioritizes cost reduction over actual service quality.

The Conclusion: Bridging the "Midway" Gap

Conversational AI implementations currently excel at starting a great experience, but often fail to sustain it through resolution. To take AI agents from midway execution to a true human-AI collaboration, organizations should focus on three focus areas:

  1. Train on Complex Edge Cases: Base models must be fine-tuned on real-world, non-standard customer scenarios rather than perfect script flows.
  2. Implement Real-Time Sentiment Analysis & Handoffs: Systems need background monitoring to evaluate call "pulse." If an interaction stalls or sentiment degrades, it should trigger an instant, context-aware escalation to a live human agent or recommend alternative path for conversation to the AI agent. This will help retaining customer faith and their experience stays high
  3. Orchestrate Specialized Agents: Rather than relying on a single generalist AI, deploy specialized sub-agents (e.g., scheduling, billing, complex troubleshooting) that pass context seamlessly behind the scenes.

I remain immensely optimistic about the future of Conversational AI as technology continues to mature.

Over to you: What has your experience been with live AI voice agents recently? Are you seeing smooth resolutions, or hitting similar execution walls? Let’s discuss in the comments below! 👇