Building for Bharat: Why I Traded "Move Fast and Break Things" for "Move Slow and Change Lives"

If you are from the tech domain, I am 100% sure you have stared at a government portal at least once and screamed, "Why doesn't this just work like the other apps on my phone?" You probably had a thousand suggestions running through your head on how to fix it. I did too. But then I did something about it. I actually jumped into the trenches to build those very systems.

So let me share my experience and observation, contrasting the two very different worlds that very few get to live.

The Context

I have a type. I love a challenge that requires every ounce of my wit, forces me into a zone of absolute discomfort, and still threatens to remain elusive. It’s a thrill worth chasing, and for the better part of my career, startups were the only place I thought that adrenaline lived.

So, you can imagine the internal "World War III" happening in my head when I received an offer from Samagra, a governance consulting firm.

On one hand, I was a startup guy used to breaking things and moving at light speed. On the other, there was this pull I couldn't ignore. Let me give you a tour of the arguments that were brewing in my mind at that moment.

The Internal Tug-of-War

The "For" Column (The Heart):

• The Hero Factor: I am a die-hard patriot, and that isn't just talk. My worldview was shaped by incredible privileges: being a student of Dr. APJ Abdul Kalam, seeing Mr. Ratan Tata in action, and living and working in Jamshedpur. I idolized these heroes and their service to the nation. I felt I owed it to the system to give back.

• The "Swades" Syndrome: I was basically Mohan Bhargav in my head. I believed that if you have the skills, you should dive head-first into serving the nation.

• The "Average Citizen" Angst: Like everyone else, I had experienced the system (or the lack of it) firsthand. I had ideas, hundreds of them, on how to make things better for an average citizen like myself. I wanted to stop complaining and start fixing.

• The Scale: We aren't talking about "DAUs" in the thousands. We are talking about reach that is surpassed maybe only by Quick-Commerce or OTT giants. It’s a tech dream.

• The Learning Curve: The problems looked terrifyingly beautiful. New sectors, massive scale, unpredictable user behavior, and complex stakeholders. It was a challenge that promised to stretch me thin.

The "Against" Column (The Brain):

• The Pace: My biggest fear? Speed. I was used to sprinting; I didn't want to learn how to crawl.

• The Red Tape: I worried personal agendas would trump actual value-add.

• The "Dream" Alternative: I had another offer from a top-tier consulting firm with significantly better pay. Choosing Samagra meant taking a pay cut to do harder work.

The Mentor’s Verdict

I did what any conflicted professional does. I called my mentor. We debated for an hour. Finally, he cut through the noise with words that still ring in my ears

"Your heart and your brain have conflicting answers. But jitna main tujhe jaanta hu, you had already decided to go with your heart even before calling me. You just wanted to feel like you debated it before taking the call."

That’s the thing about great mentors—they see the "unsaid" crystal clear.

I followed my heart and signed the offer. But the moment I stepped onto the floor on Day 1, I realized that my 'move fast' playbook wasn't just useless here, it was possibly dangerous. I hadn't just changed jobs; I had landed on a different planet.

10 Lessons from the "Build for Bharat" Trenches

If you think building for the government is just "slow startup work," you’re wrong. Here is what I learned:

1. Scale is more than just "No Crashes": I thought scale was a backend engineering problem. I was wrong. Scale means incorporating wildly varied user behaviors into a single flow and making trade-offs that don't leave anyone behind.

2. Speed vs. Weight: A startup can "move fast and break things." A government cannot. If a government system breaks, a citizen might lose their livelihood or healthcare. Decisions are slow because they carry the weight of millions of lives.

3. The "A/B Test" Trap: In a startup, data gives you the green light to experiment. In government, you can’t give two citizens a different experience for the sake of a "test." It’s a fair point, but a nightmare for a product person.

4. The 1% Rule: In a startup, a 1% error rate is a "bug." In a state with 3.5 crore people, 1% is 3.5 lakh people in chaos. Detail orientation isn't a "nice-to-have"; it’s the only way to survive.

5. The Administrative Brilliance: My biases about "bureaucracy" were washed away. I encountered some of the smartest, most dedicated people in the administrative cadre. Massive respect.

6. The Real "99%": It humbled me. I realised that what we consider "default" behavior in tier-1 cities is only the top 1%. The other 99% operates on a completely different logic.

7. Extreme Resilience: Moving a metric often meant solving three other unrelated problems first to "unlock" the lever. It’s frustrating at first, but it makes you a much tougher operator.

8. The "Guard" Strategy: In startups, you build as you discuss. In government, you have to be two steps ahead but keep it guarded. I learned to anticipate the next three requests and have them ready the day they were asked for. This gave my team a "cushion" and me a higher bargaining power.

9. Privacy as a Baseline: In startups, we use any tool that works. In government, citizen data privacy is the starting point. It slowed me down, but it made me feel significantly more secure as a citizen using those very systems.

10. The Party Scene: Let’s just say that how "government folks" let their hair down is... different. Need I say more?

The Final Word

Looking back, that internal conflict was the best thing that happened to me. It forced me to choose between a comfortable career path and an enriching journey that fundamentally changed how I operate as a human and a builder.

I walked in expecting to fix the system, but in many ways, the system fixed me. It taught me patience, it taught me the true meaning of scale, and it taught me that "building for Bharat" is the ultimate product management masterclass.

I love talking product, moonshot ideas, and the wild intersection of government and startup systems. If you're looking to exchange notes on building for the "Next Billion" or just want to chat over a cup of coffee, let’s connect.