I spent 4 years in Japan learning how to build systems. It took me 6 months in India to learn how to break them.

At Rakuten, process was everything. You document it, you follow it, you refine it. Every meeting had an agenda. Every project had a playbook. If the process said step 7 comes after step 6, you did not skip to step 8.

And honestly? It was beautiful. The predictability, the precision, the way nothing fell through the cracks.

When I moved back to India to work on Emoneeds, I thought I'd bring that same energy. I created process docs. SOPs. Workflow guides. The whole thing.

Nobody read them.

I would write a detailed documentation, share it with the team, and watch it collect digital dust.

I remember thinking, "Without process, everything will fall apart."

It didn't.

Somehow, things got done. Not the way they were planned. Not through the steps that were outlined. But the results showed up. I call it "systematic chaos"

Features shipped. Targets hit. Results achieved.

India doesn't run on process. It runs on missions.

If your team understands what you're trying to do and (more importantly) why it matters, they will find a way.

Limited resources, limited context, but full passion.

The determination fills in the gaps that documentation was supposed to cover.

Japan taught me the power of structure. India taught me the power of trust.

In Japan, the process carries the work forward. In India, relationships and shared purpose carry it forward.

Neither is better or worse. They're just different operating systems.

The real skill is knowing which one the moment calls for. Sometimes you need the playbook. Sometimes you need to look your team in the eye, explain the mission, and get out of their way.

Four years in Tokyo gave me discipline. Six months in Delhi gave me faith.

I'll take both.