Sanjay Mohindroo

Sanjay Mohindroo

What can Hindu philosophy teach us about AI ethics, consciousness, accountability, and building a sustainable Human-AI equilibrium?

What Ancient Indian Philosophy Can Teach Us About AI

A few years ago, an AI conversation would have been about algorithms, data, chips, and computing power.

Today, one of the world's leading AI companies is reportedly flying a Hindu monk to San Francisco to discuss morality, consciousness, and how an AI system should behave.

That should make every CEO and board member pause.

Anthropic, the company behind Claude, invited Swami Sarvapriyananda, a Vedanta monk, to its headquarters for private discussions on AI ethics, morality, consciousness, and Claude's training. According to NDTV, the discussions also brought together thinkers from other religious traditions and specialists in areas such as mental health.

The obvious reaction is to ask: Why Hindu philosophy?

I think that is the wrong first question.

The better question is: 

What can a 2,000-year-old philosophical tradition contribute to a problem that Silicon Valley cannot solve with engineering alone?

And that question takes us somewhere much more interesting.

The conventional wisdom is wrong

The conventional wisdom says AI alignment is primarily a technology problem.

Make the model safer. Add guardrails. Improve testing. Control the agents. Monitor the outputs. Keep a human in the loop.

All of that matters.

But none of it answers the most fundamental question:

Aligned to what?

Humanity doesn't have one universally accepted definition of morality, purpose, responsibility, or even consciousness.

AI is therefore exposing a problem that technology has largely avoided: we have become very good at building powerful tools without reaching agreement about what those tools should ultimately serve.

That is why philosophy has suddenly become relevant to the AI conversation.

And this is where Indian philosophical traditions deserve a closer look.

Not because they are "more advanced" than other religions.

Not because ancient India secretly possessed modern science.

And certainly not because Hindu philosophy has all the answers.

The reason is simpler.

Some Indian philosophical traditions spent extraordinary intellectual effort examining questions about consciousness, selfhood, knowledge, perception, action, responsibility, and the purpose of human existence.

Those happen to be precisely the questions AI is now forcing back onto the boardroom table.

Don't confuse philosophy with technology

There is a dangerous leap that should be avoided.

Ancient India made important contributions to mathematics, astronomy, linguistics, medicine, and other fields. Classical Indian philosophical traditions also developed sophisticated theories of knowledge and cognition. The Stanford Encyclopedia of Philosophy describes Indian epistemology as a rich tradition spanning almost twenty centuries, with competing schools developing detailed theories of how knowledge is generated and justified.

That is historical fact.

It does not mean ancient India had artificial intelligence, modern physics, aviation, or nuclear technology.

Claims like that require evidence, not cultural pride.

The more interesting proposition is different:

A civilization does not need to have invented modern technology for its philosophy to become relevant to modern technology.

That distinction matters.

Why consciousness changes the conversation

Consider the question Anthropic reportedly explored with religious and philosophical thinkers:

Could increasingly sophisticated AI systems become conscious?

We do not have a settled scientific answer.

And intelligence is not the same thing as consciousness.

A system can produce extraordinary language, reason through complex problems, recognize patterns, and behave as though it understands something without establishing that it possesses subjective experience.

Advaita Vedanta offers a radically different starting point.

In Advaita, consciousness is not simply a property attached to a physical organism. The tradition identifies the deepest self, Atman, with Brahman, ultimate reality, and treats consciousness as fundamental to what a person is.

You don't have to accept that metaphysics to see its relevance.

It forces a question modern AI discussions sometimes skip:

Are we assuming that intelligence and consciousness are the same thing?

If they are different, then building increasingly intelligent machines does not automatically bring us closer to building conscious machines.

That distinction could become enormously important.

The first principle: Dharma, not delegation

For business leaders, one of the most useful concepts is dharma, broadly understood as duty, responsibility, and right conduct, although its meaning varies considerably across Indian traditions and contexts.

AI is rapidly changing who performs work.

That does not answer who owns the outcome.

Imagine an enterprise workflow in which:

1.   One AI agent researches.

2.   Another analyzes.

3.   A third recommends.

4.   A fourth executes.

The workflow can be almost completely autonomous.

But accountability cannot be autonomous.

Someone still has to own the consequence.

That gives boards a simple principle:

AI can inherit execution. It cannot inherit accountability.

This becomes especially important as agentic AI moves into underwriting, finance, healthcare, security, procurement, compliance, and customer decisions.

The question for the board should not simply be, "Can the agent perform the task?"

It should be:

"Who is accountable when the agent is wrong?"

That is a dharma question expressed in modern corporate language.

The second principle: Karma means looking beyond the KPI

Karma is frequently reduced to the phrase "what goes around comes around."

The deeper idea is about action and consequence.

That has enormous relevance to AI economics.

A company deploys AI and cuts operating costs by 20 percent.

The spreadsheet looks excellent.

But what happened underneath?

Did the company also lose experienced employees?

Did institutional knowledge walk out the door?

Did junior employees lose opportunities to learn?

Did managers become dependent on systems they don't understand?

Did customers receive faster service but less human judgment?

Did the organization become more efficient and less resilient at the same time?

The immediate financial result is one part of the story.

The second-order consequences are the other part.

So, a board should add another question to every major AI investment:

What consequences are we creating that aren't appearing in the ROI calculation?

That is a very different way of measuring transformation.

The third principle: Ahimsa and the hidden cost of efficiency

Ahimsa, commonly associated with non-harming, provides another useful lens.

The obvious interpretation is physical harm.

For AI governance, the broader interpretation is more interesting.

What if harm is cognitive?

What happens when people stop remembering because AI remembers for them?

What happens when employees stop learning because AI produces the answer?

What happens when executives stop challenging assumptions because the dashboard looks authoritative?

What happens when organizations eliminate entry-level roles and then discover five years later that they no longer have a pipeline of experienced professionals?

These are not necessarily AI failures.

They are AI deployment failures.

Technology can make a process more efficient while making the organization weaker.

That is why the right objective isn't maximum automation.

It is optimal augmentation.

The fourth principle: Aparigraha and the question of "enough"

This may be the most uncomfortable idea for the technology industry.

Aparigraha, often translated as non-possessiveness or restraint in accumulation, challenges the assumption that more is always better.

AI strategy currently rewards more:

More automation.

More agents.

More data.

More compute.

More intelligence.

More processes automated.

But should a company automate everything it can?

No.

The relevant question is:

What should we automate?

Some activities are repetitive and should probably disappear.

Others develop judgment, institutional knowledge, relationships, creativity, and leadership.

Those may need to remain human even when AI could technically perform them.

The objective should therefore not be:

"How many humans can we remove?"

It should be:

"How much human capability can we create?"

That is a radically different AI strategy.

The fifth principle: Viveka, the discipline of discernment

There may be no more important human capability in the AI era than discernment.

AI can produce an answer in seconds.

That does not make the answer true.

Classical Indian philosophy developed extensive debates around pramāṇa, or legitimate means of knowledge, asking how cognition becomes justified and how genuine knowledge can be distinguished from error. Nyāya, in particular, developed detailed theories concerning perception, inference, testimony, and false cognition.

That is remarkably relevant to generative AI.

We are entering a world where machines can produce plausible explanations faster than humans can verify them.

The scarce resource will not be information.

It will be judgment about information.

Boards should therefore ask a different question when evaluating AI adoption:

Are we increasing the organization's intelligence, or merely increasing the volume of machine-generated information?

Those are not the same thing.

The sixth principle: Loka Sangraha and the purpose of automation

There is another idea worth bringing into the conversation: loka sangraha, broadly associated with sustaining social order and acting for the welfare of the larger community.

This creates a useful challenge to purely cost-driven AI transformation.

Suppose two companies achieve the same financial benefit.

Company A uses AI primarily to eliminate labor costs.

Company B uses AI to increase employee productivity, retrain its workforce, and redirect people toward higher-value activities.

The financial spreadsheets may look similar.

The societal consequences are not.

For boards, the question becomes:

Does our AI strategy strengthen the system in which our company operates?

Employees are part of that system.

Customers are part of it.

Communities are part of it.

Suppliers are part of it.

The workforce we are training today may be the leadership pipeline we need tomorrow.

A practical framework for boards

None of this requires a board to become a scholar of Vedanta.

The ideas can be converted into six practical questions.

1. Dharma: Who owns the outcome?

For every autonomous AI process, identify the human executive accountable for the result.

2. Karma: What are the second-order consequences?

Measure not only cost savings, but workforce, customer, knowledge, resilience, and reputational effects.

3. Ahimsa: What capabilities could we unintentionally damage?

Identify cognitive, organizational, and human harms created by excessive automation.

4. Aparigraha: What is enough automation?

Do not automate simply because technology makes automation possible.

5. Viveka: How will humans challenge machine-generated knowledge?

Build verification and judgment into critical decisions rather than treating AI output as authority.

6. Loka Sangraha: Does AI strengthen the larger ecosystem?

Evaluate whether the transformation builds sustainable organizational and societal capability.

This is not a religious governance framework.

It is a human governance framework inspired by philosophical ideas.

Does this prove ancient India was scientifically more advanced?

No.

And we should resist that temptation.

Ancient India undeniably produced major intellectual achievements. Indian traditions contributed to mathematics, astronomy, linguistics, medicine, and philosophy, and the historical development of science on the subcontinent is well documented.

But saying that ancient Indian thinkers developed sophisticated theories of consciousness does not prove that they anticipated modern neuroscience.

Likewise, recognizing the sophistication of Indian mathematics does not mean ancient India possessed modern physics.

The stronger argument is more subtle.

Ancient Indian intellectual traditions may have explored some dimensions of the human mind and human conduct with a depth that modern technological civilization has not always prioritized.

And AI is forcing those dimensions back into the conversation.

The real opportunity

The future of AI will not be decided only by engineers.

It will be shaped by philosophers, psychologists, economists, ethicists, religious thinkers, policymakers, executives, and ultimately society.

That is why Anthropic's reported engagement with religious and philosophical thinkers matters. It suggests that the AI industry is beginning to recognize a fundamental limitation of pure engineering: you can build an extraordinarily capable machine without answering what that capability should ultimately serve.

Hindu philosophy does not have the answer.

Neither does Christianity.

Neither does Buddhism.

Neither does Western philosophy.

No single tradition does.

But perhaps the future requires us to stop looking for one answer.

Instead, we should build a global conversation around the oldest questions humanity has asked about consciousness, responsibility, knowledge, restraint, purpose, and the good society.

That is the real opportunity.

The objective should not be to make machines more human.

Nor should it be to make humans more machine-like.

The objective should be to build a society in which machines amplify human capability without eroding human agency, judgment, responsibility, and purpose.

That is what I would call Human-AI equilibrium.

And perhaps the irony of the AI revolution is this:

The more intelligent our machines become, the more seriously we may have to ask what it actually means to be human.

Do you believe ancient philosophical traditions have a meaningful role to play in shaping the future of AI, or should we leave questions of AI ethics entirely to modern science and technology?

If this perspective resonates, subscribe to TechnologyTrends or share your experience in the comments.

Sanjay Mohindroo

AI ROI is not just headcount reduction. Learn how boards can measure the capacity, growth, resilience, and capability AI creates across the enterprise.

The AI Cost Paradox.

 Why Cutting Headcount Is the Wrong Measure of AI Success

A company invests $100 million in AI and cuts $150 million from annual workforce costs.

On paper, that looks like a triumph. In the boardroom, it may be the beginning of a much more expensive mistake.

The conventional wisdom I want to challenge is simple: if AI can do the work, the quickest way to prove ROI is to remove the people who used to do it.

That logic is financially neat, operationally dangerous, and strategically incomplete.

The real question is not how much work AI can eliminate. It is how much additional economic capacity AI can create, and whether the enterprise can convert that capacity into growth, resilience, better decisions, faster execution, and stronger competitive advantage.

That is the AI cost paradox.

The Easiest AI ROI Is Often the Narrowest

Boards are right to ask where the return is.

AI investment is no longer experimental. Companies are spending heavily on infrastructure, models, cloud capacity, data platforms, applications, talent, and increasingly autonomous agents. At some point, the expenditure has to translate into measurable business value.

The problem is that the easiest value to measure is usually labor cost.

If AI allows a process to be run by six people instead of ten, the arithmetic is immediate. Four salaries disappear. The savings drop into the cost base. The business case becomes visible.

But the balance sheet does not capture what may have disappeared with those four people.

Experienced employees carry accumulated knowledge about customers, products, exceptions, workarounds, supplier behavior, regulatory interpretation, system limitations, and the history behind decisions that make little sense when viewed only through current documentation.

That knowledge is rarely stored cleanly in a database.

So, the board should ask a second question before celebrating the savings: what capability did we remove along with the cost?

AI Creates a Capacity Dividend

This is where the economics of AI need to be reframed.

AI value should not be treated as:

AI value = labor cost eliminated

A better boardroom equation is:

AI value = cost eliminated + cost avoided + productivity capacity created + revenue enabled + quality improvement + risk reduction + innovation value, less AI investment, transformation cost, and AI-related risk.

That is a much harder equation to manage.

It is also much closer to the truth.

Suppose AI releases 500,000 hours of human capacity across an enterprise. Those hours are not worth zero because payroll has not fallen.

They may represent additional customer capacity, shorter product cycles, more sales activity, faster research, stronger risk management, better service, and projects that were previously uneconomic.

I call this the capacity dividend.

The strategic question is not whether the dividend exists. It is what management chooses to do with it.

Redeployment Before Reduction

A board should insist that every significant AI automation program answer five questions in sequence.

1. What work is being eliminated?

Be specific. Reporting, reconciliation, data entry, document processing, routine analysis, customer administration, or some other defined activity.

2. How much capacity is being released?

Do not stop at FTEs. Measure hours, cases, transactions, customer interactions, engineering output, projects, product cycles, or sales capacity.

3. Where can that capacity create more value?

This is the critical step. Can the released capacity be directed into growth, innovation, customer acquisition, product development, operational improvement, or risk management?

4. What skills are required for that move?

This turns AI from a technology program into a workforce transformation program.

5. What capacity remains genuinely surplus?

Only now should structural workforce reduction become the default discussion.

The principle is simple: redeployment before reduction.

This is not an argument against reducing headcount. Some roles will become economically unnecessary. Some activities will disappear. Some organizations will genuinely need fewer people.

The point is sequencing.

Workforce reduction should be an outcome of transformation, not the definition of transformation.

The Biggest Hidden Risk Is Capability Debt

There is another reason boards should be cautious about aggressive AI-led downsizing.

AI is entering knowledge work directly.

Entry-level analysts, researchers, coordinators, administrators, and junior professionals spend much of their time gathering information, building spreadsheets, preparing presentations, performing basic analysis, documenting processes, and responding to routine requests.

AI can increasingly perform a significant share of that work.

The productivity upside is obvious.

The less obvious problem is that these tasks have historically been part of the apprenticeship system through which judgment develops.

If AI does the junior work, where do tomorrow's experienced professionals come from?

The same issue appears in middle management.

A large portion of traditional management consists of collecting information, consolidating reports, tracking performance, coordinating teams, preparing presentations, monitoring projects, communicating priorities, and escalating exceptions.

AI and agentic systems can automate more of that coordination layer.

That may allow organizations to operate with fewer managerial layers, which could be a major advantage.

But if companies remove junior roles and middle-management layers without redesigning how expertise is developed, they may optimize today's cost structure at the expense of tomorrow's operating capability.

That is capability debt.

Like technical debt, it is easy to create and difficult to see until the organization needs the capability it has quietly removed.

AI May Make Expertise More Valuable, Not Less

There is a popular assumption that more capable AI automatically reduces the value of experienced people.

I think the opposite may often be true.

The more powerful the machine becomes, the more valuable the people may become who understand when not to trust it.

Experienced employees know which customers matter disproportionately, which process exceptions are normal, which supplier promises should be discounted, which system documentation is wrong, which regulatory interpretations have practical consequences, and which apparently logical recommendation will fail in the real world.

AI can process enormous volumes of information.

Information is not the same as institutional understanding.

This changes the role of expertise.

The future expert may do less manual analysis and more supervision, exception handling, judgment, orchestration, and decision-making. AI does not necessarily remove expertise. It can increase the leverage of expertise.

For senior leaders, that is a far more interesting economic proposition than replacing skilled people with cheaper automation.

The Incentive Problem Most AI Strategies Ignore

There is also a behavioral issue that receives too little board attention.

Imagine an employee discovers that AI can eliminate 40 percent of their workload.

If the implied corporate message is, "Thank you, your job is now 40 percent redundant," what incentive does that employee have to identify the next automation opportunity?

Very little.

The rational behavior is to protect the work.

That is exactly the opposite of what an AI transformation requires.

Organizations need a different implicit contract: if you automate low-value work, we will help you move toward higher-value work.

Employees should be rewarded for finding automation opportunities, improving processes, adopting AI, increasing productivity, developing new skills, and creating new business value.

That turns the workforce from a target of automation into a participant in transformation.

It also makes adoption far more likely.

The Board Needs a Different AI Scorecard

If headcount reduction is the main measure of AI success, management will naturally optimize toward headcount reduction.

Boards need a broader scorecard.

I would group it into five categories.

First, financial value: AI investment, run-rate savings, avoided hiring, revenue enabled, margin improvement, and payback period.

Second, productivity: output per employee, cycle time, throughput, hours released, customer capacity, and engineering capacity.

Third, capability: AI proficiency, critical-skill coverage, internal mobility, expert retention, knowledge capture, and succession depth.

Fourth, transformation: processes redesigned, agent autonomy, new products, new services, and new revenue streams.

Fifth, risk: AI incidents, model failures, compliance issues, human override, AI-off resilience, and concentration risk.

This gives the board a more complete view of whether AI is making the enterprise cheaper, more capable, or both.

Those are not the same thing.

The New Executive Equation

A useful way to think about the quality of AI transformation is:

AI Autonomy × Business Value × Human Capability Retention

If autonomy increases but business value does not, the organization has created technological complexity.

If business value rises but human capability collapses, the organization may be consuming its future.

If human capability is preserved but AI adoption remains weak, the organization risks protecting yesterday's operating model.

The goal is the intersection.

This is why the strongest AI strategy is not simply a technology strategy.

It is a capital allocation strategy, an operating model strategy, and a workforce strategy at the same time.

The Counter-Argument.

Surely Some Companies Simply Need Fewer People?

Yes.

Any serious discussion of AI has to acknowledge that some work will disappear and some organizations will require fewer employees.

AI will reduce repetitive administrative work. Some coordination layers will become thinner. Some knowledge-work roles will be redesigned beyond recognition.

There is no strategic virtue in preserving work that no longer creates value.

But that is not the same as assuming that the first visible productivity gain should be converted into layoffs.

The better sequence is:

Automate. Measure. Redeploy. Upskill. Transform. Grow. Then ask what capacity is genuinely surplus.

This sequence forces management to test whether released capacity can produce a higher return somewhere else in the enterprise before treating it as waste.

That is simply disciplined capital allocation.

The Real Competitive Advantage Is Organizational Multiplication

The next phase of AI will separate companies into two broad models.

The first will use AI primarily as labor substitution.

They will automate work, remove roles, reduce cost, and improve short-term operating efficiency.

That can be a valid model.

The second will use AI as capability multiplication.

They will automate low-value work, release human capacity, redeploy people toward higher-value activity, redesign roles, increase productivity, and make new products, services, or markets economically viable.

They may still end up with fewer people.

But the reduction will be a consequence of a more capable operating model, not the objective itself.

That distinction matters because the most powerful enterprise may not be the one with the smallest workforce.

It may be the one where every person has dramatically more capability because of the intelligence working alongside them.

The Board Question That Matters

Perhaps the most useful question a board can ask is this:

If AI gave us 30 percent more organizational capacity without increasing our workforce, what would we do with it?

If the answer is, "reduce the workforce by 30 percent," then AI is being treated primarily as a cost program.

If the answer is, "serve more customers, develop new products, improve quality, accelerate innovation, strengthen resilience, enter new markets, and raise the productivity of our people," then AI is being treated as a transformation platform.

That is the choice.

AI will eliminate work. Some jobs will disappear. Some layers will thin. Some traditional career paths will change permanently.

But eliminating work is not the same as eliminating value.

The people inside an enterprise are not just a cost line. They are accumulated capability.

The objective of AI should not be to make the organization smaller.

It should be to make the organization more capable.

What is your board measuring today: headcount removed, or capability created?

If this is a debate happening inside your organization, subscribe to TechnologyTrends or add your perspective in the comments.