Vicky Bansal

Thinking

Points of View

Perspectives on the problems that matter — from someone who has spent 18 years solving them. Not thought leadership for its own sake.

The Philosophy

How I think about the work.

I

Build machines, not dependencies

If the operation only works when I am in the room, I have failed. Every system I build is designed to run better after I leave. That is the only measure that matters.

II

AI in production. Not in a deck.

I have deployed GenAI against 100,000 reviews a month, live prospecting pipelines, and real cost targets. If it does not move revenue or cut cost, it is not AI transformation — it is a slide.

III

Strategy is worthless without Tuesday

The gap between what the board decides and what happens on the floor on Tuesday morning is where most companies bleed. I close that gap. Precisely. Every time.

IV

Culture is a number, not a feeling

40% attrition to 12%. That is not HR work — that is operational discipline applied to people. Inclusion is not a programme. It is a performance variable. Treat it like one.

Articles

Six things worth reading.

GCC Strategy

Why Most GCCs Never Become Strategic

"The problem is not the people in India. The problem is the ambition of the people who designed the mandate."

Most Global Capability Centres are built with a cost arbitrage thesis — skilled talent at lower cost, doing work designed and owned elsewhere. It is a rational starting point. It is also a ceiling. The GCCs that become genuinely strategic share one characteristic: they were given — or fought for — ownership of outcomes, not just execution of tasks.

The GDM India GCC started as a support function in 2016. By 2025, it was generating significant revenue, overseeing vendor governance, and contributing to executive strategy. The difference was not talent. It was mandate. And mandate was earned, not given — through a decade of building things that worked and making the results impossible to ignore.

The organisations building truly strategic GCCs in 2026 are the ones asking a different question: not "what can we move to India?" but "what can India own?" Ownership changes everything. It changes how people think, what decisions they make, and what problems they solve.

AI Operations

AI Won't Replace Operations. It Will Redefine It.

"The question is not whether AI will transform operations. The question is whether your operations are structured to absorb the transformation."

Most AI transformation programmes fail not because the technology does not work — but because the operations it is being applied to were never designed to be AI-enabled. Processes built for human judgment, approval chains built for human accountability, and metrics built for human pace do not simply improve when AI is inserted. They need to be redesigned.

The organisations winning with AI are the ones that treat it as an operational architecture question, not a technology procurement question. They are asking: what does this process look like when AI handles 80% of the decisions?

At GDM India, AI was deployed against moderation workflows first — not because it was the easiest, but because it was where the volume was highest and the quality impact was clearest. The result was not just efficiency — it was a new capability. A moderation function that could handle 100,000 reviews a month with the quality consistency of a team ten times its size.

Capability Building

Building New Capabilities Inside Large Organisations

"Large organisations do not lack ideas. They lack the internal architecture to turn ideas into capabilities before someone loses patience."

Building something new inside a large organisation is fundamentally different from building a startup. The resources are theoretically available. The market is already defined. The distribution already exists. The challenge is organisational: navigating approval processes designed for sustaining existing operations, building alignment among stakeholders with competing priorities, and maintaining momentum through the inevitable period when results are not yet visible.

The skill that separates leaders who build new capabilities from those who do not is not strategic vision. It is operational patience combined with the ability to generate early proof points that make the investment obvious before it is fully made. Start small enough to run without approval. Succeed fast enough to earn it.

Marketplace Trust

Scaling Trust in Digital Marketplaces

"At 2,000 reviews a month, trust is a policy. At 100,000 reviews a month, trust is an operating system."

Every digital marketplace eventually faces the same inflection point: the moment when the volume of content exceeds the capacity of human review. This is the moment when trust — the platform's core asset — becomes operationally fragile.

The platforms that maintain trust at scale have something more fundamental — an operational culture where quality is treated as a business outcome, not a compliance requirement. The difference shows up in the numbers: 90% spam reduction is not a technology achievement. It is an operational achievement that required process design, governance structures, incentive alignment and — eventually — AI deployed in production against a baseline that had been measured for years.

Revenue Operations

Revenue Operations Beyond Sales

"The revenue opportunity was always there. It just did not have an owner."

Revenue Operations is typically defined as the alignment of sales, marketing and customer success around shared revenue metrics. This is correct but incomplete. The larger opportunity is the revenue that sits inside operational functions that have never been given commercial accountability.

Prospecting teams that qualify vendor leads. Support teams that manage renewal conversations. Moderation teams that determine which vendors receive premium placement. These are not support functions with accidental commercial exposure. They are revenue functions that have been labelled as operations because nobody gave them a revenue mandate. The Four Intern Experiment was the proof that giving an operations team a commercial mandate — and the resources to pursue it — changes what is possible.

Leadership

What Six Promotions Taught Me About Leadership

"I was never promoted because I asked for it. I was promoted because the business needed someone to own something bigger — and I had already demonstrated I could."

Getting promoted repeatedly is not a function of ambition or self-promotion. It is a function of a pattern, repeated six times: identify what the business needs that nobody owns, build the capability to meet that need, prove the value before asking for resources, scale what works, and earn the mandate to do it again at a higher level.

The lesson is uncomfortable for people who believe careers are built through visibility and advocacy. They are built through outcomes. Visibility is a by-product of outcomes, not a precondition. The leaders who build the most influence are not the ones who manage their careers most aggressively. They are the ones who solve the most important problems most reliably — and trust that the organisation will notice.