Most large programs don't fail because of poor planning. They fail because the rules felt unfair.

I've run customer engagement programs at a scale that most teams don't get to experience.

BNAT — 10 lakh registrations. 3.6 lakh test takers.

BYJU'S AIM — India's largest mock test series. 1.9 lakh registrations, 90K test takers.

Shiksha Awards — 5,500 schools. 65,000 teachers. One national stage.

And across all three, the most dangerous moments had nothing to do with technology failures or logistical breakdowns.

They came from one thing: participants who felt the system wasn't fair.

At BNAT, an accidental wrong question didn't just create a scoring issue — it created a scholarship contention. Students who had prepared for months suddenly questioning whether they'd been robbed of a life-changing opportunity.

At mock tests, a misalignment with the paper pattern could distort self-assessment entirely — shaking a student's confidence at the worst possible time.

At Shiksha Awards, schools and teachers escalated — not because the program was poorly designed — but because timeframes, regional differences, board variations, subject weightages, and medium of instruction created a perception of unequal ground.

"My school was closed during this period. How could we compete with schools in other parts of the country that were open?"

Here's the part that stayed with me: most of the time, it wasn't actually a problem.

We had already accounted for the discrepancies. The rubric was fair. But it wasn't understood — and that made all the difference.

At scale, perception IS reality.

You can have the most technically correct rulebook and still lose people's trust — because fairness isn't just about what's right. It's about what feels right.

Here's how I solved it:

→ Pressure-test your rules for perceived inequity, not just logical gaps. Invite someone from the most disadvantaged participant segment to find flaws. They will — and that's the point.

→ The value has to be undeniable before the competition begins. Participants who deeply want what you're offering will tolerate friction. Participants who are lukewarm will weaponise ambiguity.

→ Resolve edge cases publicly and fast. A quietly resolved grievance helps one person. A transparently resolved one builds trust with thousands watching.

→ Communication is not a follow-up step. It's part of the design. If your fairness logic isn't understood by your most sceptical participant, it doesn't matter how airtight your rubric is.

Running programs at national scale taught me that operations is really trust architecture.

The logistics are table stakes. The hard part is making 65,000 teachers or 4.5 lakh students feel like the game was worth playing — and that it was played fairly.

Read the original post on LinkedIn →