Key takeaways
- 01
Fix the operating model first
Messaging alone cannot resolve a gap between what employees are promised and what they experience.
- 02
Define ownership precisely
Ask which decisions teams can make, within what boundaries, and with whose support.
- 03
Audit promise against practice
Name the accountable leader and the open gap for every claim before it goes out.
- 04
Make stories carry evidence
Ask employees for the decisions they made, not whether they feel empowered.
Mid-market GCCs in India will build strong brands by giving employees the authority and resources to deliver on their promise. This idea is straightforward and logical, almost Management 101: accountability, authority, and resources go hand in hand. But it is more complex than it appears. Reason: Most GCCs create a contradiction when they promise employees ownership but present the GCC to enterprise stakeholders as a delivery unit, diluting what should be a consistent and compelling organisational identity. Resolving this contradiction requires consistent messaging and providing employees with the decision-making authority, access, and resources to exercise the ownership they are promised. This is a potent combination. It helps support a single, credible identity for employees and enterprise stakeholders alike.
One GCC, two stories
As a CMO, I see Brand-as-a-Service (BaaS) as a strategic capability GCCs can use to bridge the gap between their employer and business reputations. BaaS can create a single organisational identity, driven and maintained by a consistent narrative. (For a deep dive into BaaS: Nimmi Sebastian, "The GCC brand hack: Why brand-as-a-service is a compelling strategy," Adgully, September 18, 2026.)
The challenge of creating a powerful, consistent, and recognisable brand identity raises a demanding question: what must change within the organisation before the two narratives, one aimed at employees and the other at stakeholders, can credibly converge? The answer requires examining the operating model that underpins the brand's claims.
One thing is certain: We cannot resolve an operating model contradiction through messaging alone. The marketing team must recognise this. Instead, the team must sharpen the value proposition, back it with credible evidence, and surface inconsistencies that undermine it. If we recruit people to shape products and services but employ them only to execute specifications, stronger storytelling becomes counterproductive. It makes the existing discrepancy more visible.
We cannot resolve an operating model contradiction through messaging alone.
Consider the word "ownership."
What “ownership” means depends on who is listening
“Responsibility for completing assigned tasks”
Task responsibility“I have influence over product priorities”
Product influence“Accountability for commercial results”
Commercial accountabilityScope of authority implied
All three can leave the conversation believing they agree.
However, these meanings are not interchangeable. Task responsibility focuses on meeting defined requirements. By contrast, product or service influence involves participating in decisions about what gets built, setting priorities, and negotiating trade-offs.
These responsibilities do not necessarily align. A team may own a product or service component without controlling its roadmap. It may engage with customers and understand requirements without having authority to change a feature. It may influence priorities while another business unit remains accountable for revenue. The useful question therefore shifts from "Do our employees have ownership?" to "Which decisions can they make, within what boundaries, and with whose support?"
This is why promises to employees and potential candidates, such as "You will shape the future of a product," sound suspect. The employee can see that product strategy and priorities remain elsewhere. That is why a proposition like "you will own platform reliability and influence quarterly priorities" is more defensible. It is an operational mandate, stated precisely and honestly.
Which decisions can they make, within what boundaries, and with whose support?
A decision comes up
The team settles it, with the access and budget to act.
The team shapes the outcome alongside other functions.
The call stays with enterprise leadership.
Imagine a hypothetical mid-market GCC preparing an innovation-led recruitment campaign. Before approving the campaign, the CMO convenes the GCC head, HR, and functional leaders. They agree to attract candidates by highlighting opportunities to innovate, gain global experience, advance their careers, and take ownership of their work.
Innovation. The claim requires more than an annual ideas hackathon. Employees need protected time to experiment, access to usable data, the right tools, and a path from prototype to production. The engineering leader enables these conditions; the GCC head resolves funding and mandate barriers.
Global exposure. Participating in late-night calls (or any calls) does not create meaningful exposure. Employees should contribute to cross-border decisions, present recommendations, and understand the business context behind requests. Functional leaders and their global counterparts enable that participation.
Career growth. Mentoring, training, and certification opportunities can create growth potential, not prove progression. The workplace experience should include clear role expectations, developmental assignments, feedback, and credible opportunities to advance. HR defines progression frameworks; functional leaders assess readiness and assign work.
Ownership. The evidence is an explicit allocation of decision-making authority: what teams decide independently, what requires consultation, and what must be escalated. The GCC head agrees on the mandate with enterprise leadership, and product and functional leaders translate it into day-to-day authority.
For each claim, the audit asks one question:
Every promise needs evidence, an owner and a test
Protected time to experiment, usable data, the right tools and a path from prototype to production
Enabled by: Engineering leader, with the GCC head clearing funding and mandate barriers
Can a team test an idea without repeatedly seeking permission?
Contributing to cross-border decisions, presenting recommendations and understanding the business context
Enabled by: Functional leaders and their global counterparts
When did an employee’s recommendation last change a decision?
Clear role expectations, developmental assignments, feedback and credible opportunities to advance
Enabled by: HR sets progression frameworks; functional leaders assess readiness
Can employees explain what broader responsibility requires, and point to colleagues who earned it?
An explicit allocation of what teams decide, what needs consultation and what is escalated
Enabled by: GCC head with enterprise leadership; product and functional leaders
Does accountability come with access, budget and discretion?
A claim without supporting evidence
The audit should document each promise, its supporting experience, the accountable leader, and the unresolved gap. A claim without supporting evidence suggests that leaders must first change the experience, narrow the promise (of ownership), or defer it.
I believe we need to be direct: Instead of asking employees whether they feel empowered, we must ask them to list the decisions they made. Which customer problem did they investigate? What constraints shaped their choices? What did they need permission to do? What changed because of their work?
How marketing turns employee stories into proof
Instead of “Do you feel empowered?”
Ask “Which decisions did you make?”
- 01Which customer problem did they investigate?
- 02What constraints shaped their choices?
- 03What did they need permission to do?
- 04What changed because of their work?
Stories that separate contribution from authority, and hold up.
If every story stalls at approval, the next conversation is with operating leaders.
A credible innovation story explains the team's decision, the constraints it addressed and navigated, and the resulting improvement. It also distinguishes contribution from authority. "We recommended a change that global product leadership approved" may be stronger and more accurate than an inflated claim of end-to-end ownership.
As a CMO, I am convinced this approach serves two purposes: it surfaces publishable evidence and reveals recurring organisational friction. If every story stalls at an approval bottleneck, the next discussion should be with operating leaders, not the chief copywriter on the marketing team!
When BaaS is understood and implemented this way, the marketing team's diagnostic contribution becomes strategically valuable.
Brand-as-a-Service, in sequence
- 01Define the promise
- 02Assign responsibility for enabling it
- 03Verify the experience
- 04Then amplify it
A credible brand identity for employees and stakeholders.
The principle is straightforward: define the promise, assign responsibility for enabling it, and verify the experience before amplifying it. For GCCs, that sequence refines an attractive recruitment proposition into a credible brand identity for employees and stakeholders.

About the author
Nimmi Sebastian
Chief Marketing Officer, Embark



