What Kalahandi Taught Me About Resilience
Resilience is not a personality trait. Kalahandi taught me it is an operational capacity, built, not born.
Founder, Majhi Group & Majhi OS
There was a flood in Kalahandi when I was young, I do not remember the year precisely, only the aftermath. The Indravati had risen. Several families in the lower areas had lost what they had stored. Within a week, those families were being helped by neighbors who did not have much more than they did.
What I observed was not resilience as a trait. It was resilience as a community system, something built into the way the place operated, not something any individual had developed through the right practices.
The word resilience has become so common in professional contexts that it has lost almost all of its weight. What I want to describe is what the thing actually looks like when it works, not as a mindset, but as a structure.
Resilience is not toughness. It is the ability to re-engage after absorbing a loss.
Kalahandi gave me a different definition.
Not because growing up near it was uniquely hard, there are harder places to be from, and I am not interested in comparative suffering as a framework. But because proximity to a place that had absorbed genuine and sustained institutional failure, and was still running, still producing, still organizing economic and social life, made something observable that is usually invisible: resilience is not a trait. It is an operational capacity. It has components. The components can be identified. They are built over time by doing specific things.
What I watched
My father worked at the Junagarh NAC. Our family had agricultural land on the outskirts of town, eighteen acres, some of it disputed for years before it was settled. I grew up around people who farmed and around the conversations about farming: what had come in, what hadn't, what the rains had done this season, what the next season was likely to require.
Kalahandi's agricultural conditions are what economists describe as high-variance. Rainfall is irregular. Market access is poor. Input financing, fertilizer, seed, equipment, is often expensive or unavailable at the right time. I remember one particular year when the monsoon arrived late, then came too hard, then stopped. Three families in the surrounding area that had staked everything on a single cash crop lost most of it. The families that had planted two or three different crops lost part of it. The difference in what that year cost them was not luck. It was structure.
What I watched was not people failing under these conditions. What I watched was people building systems with more redundancy than you would need in a more forgiving environment. Diversified crops, not monocultures. Informal credit networks that bent rather than broke when a crop failed. Social obligations that distributed loss across communities rather than concentrating it in individual households.
These were not strategies anyone designed. They were adaptations that had survived, the practices that remained when the brittle ones collapsed. The result was not comfort. The result was persistence. The capacity to keep operating when conditions were not cooperative.
The operational definition
Resilience, properly understood, is the ability to absorb shock without losing the capacity to function. Not without cost, absorbing shock has cost. But without losing function. The thing keeps running.
What makes that possible is not mental toughness. It is architecture. Redundancy: when one channel fails, another carries the load. Distributed risk: when failure happens, it doesn't take the whole system down. Recovery protocols: learned responses to specific failure modes, developed through experience with those failures.
Kalahandi had built these into its agricultural and community systems because the alternative, single points of failure, concentrated risk, no recovery protocol, had been tried and had not survived. The resilient architecture was what was left.
What I carried into my work
When I started building companies, I encountered a common trap: optimizing for the best case. Lean operations, no redundancy, everything synchronized to work when conditions cooperate. The efficiency gains are real. The fragility is a hidden tax, paid only when something goes wrong.
The Kalahandi instinct runs in the other direction. Build for the bad year, not the good one. Maintain relationships that carry no immediate return, because they are the backup channel when primary channels fail. Distribute decision-making so that no single point of pressure can paralyze the whole system.
This is not pessimism. It is the operational consequence of having watched what actually survives. The efficient systems that were not built for variance did not survive the variance. The redundant, slower, harder-to-optimize systems kept functioning.
Resilience is built, not born
The people I watched growing up near Kalahandi were not born resilient. The capacity was built, through decades of working in difficult conditions, through collective adaptation to specific failure modes, through the transmission of practice from one generation to the next.
What this means is that resilience is acquirable. It is not a fixed trait you have or lack. It is an architecture you build, deliberately or, more often, through being forced to build it by circumstances that punish fragility.
The lesson from Kalahandi is not that hard places produce hard people. It is that when conditions are genuinely variable and institutional backstops are weak, you either build systems that absorb variance or you do not survive long enough to be observed.
I was not from the hardest place. But I was close enough to watch what survived and what didn't. That observation shaped how I build.
The lesson from Kalahandi is not that hard places produce hard people. It is that when conditions are genuinely variable and institutional backstops are weak, you either build systems that absorb variance or you do not survive long enough to be observed.
Manas Majhi grew up in Junagarh, Kalahandi, Odisha. He writes about opportunity, development, and the systems that fail to distribute either equitably. He is the founder of Majhi Group and Majhi OS.
See also: Kalahandi and the Opportunity Gap, Lessons From Rural India That Apply Globally, What Kalahandi Taught Me About Human Nature
Sources
Nassim Nicholas Taleb: Antifragile: Things That Gain from Disorder
Harvard Business Review: Building Resilience
McKinsey Global Institute: India's Turning Point: An Economic Agenda for the Decade
Frequently Asked Questions
What is the operational definition of resilience vs the trait definition?
The trait definition treats resilience as a personality characteristic, toughness, grit, the ability to push through. The operational definition is more precise: resilience is the ability to absorb shock without losing the capacity to function. Not without cost, absorbing shock has cost. But without losing function. The thing keeps running. What makes that possible is not mental toughness but architecture: redundancy (when one channel fails, another carries the load), distributed risk (when failure happens, it doesn't take the whole system down), and recovery protocols (learned responses to specific failure modes, developed through experience with those failures). Resilience, understood this way, is acquirable. It's not a fixed trait you have or lack. It's an architecture you build, deliberately or, more often, through being forced to build it by circumstances that punish fragility.
What did Kalahandi's agricultural systems demonstrate about how resilience gets built?
High-variance conditions, irregular rainfall, poor market access, expensive or unavailable inputs, produced a specific adaptation: systems with more redundancy than forgiving environments would require. Diversified crops, not monocultures. Informal credit networks that bent rather than broke when a crop failed. Social obligations that distributed loss across communities rather than concentrating it in individual households. These were not strategies anyone designed. They were adaptations that had survived, the practices that remained when the brittle ones collapsed. One specific year: monsoon arrived late, came too hard, then stopped. Families that had staked everything on a single cash crop lost most of it. Families that had planted two or three different crops lost part of it. The difference wasn't luck. It was structure. The resilient architecture was what was left after the single-point-of-failure approaches had been eliminated by experience.
How did the Kalahandi instinct about resilience translate into how Manas builds companies?
The common trap in company building is optimizing for the best case: lean operations, no redundancy, everything synchronized to work when conditions cooperate. The efficiency gains are real. The fragility is a hidden tax, paid only when something goes wrong. The Kalahandi instinct runs in the other direction: build for the bad year, not the good one. Maintain relationships that carry no immediate return, because they're the backup channel when primary channels fail. Distribute decision-making so no single point of pressure can paralyze the whole system. This is not pessimism. It's the operational consequence of having watched what actually survives. The efficient systems that weren't built for variance didn't survive the variance. The redundant, slower, harder-to-optimize systems kept functioning.
Did this land? Push back? Add something I missed?
Reply to Manas →Continue Reading
Related writing
What Kalahandi Taught Me About Opportunity
Opportunity is not a place or a thing. It is a condition. Kalahandi made that visible before I had the language for it.
Why Places Like Kalahandi Produce Determined People
Not because hardship builds character. But because certain environments select for a specific kind of operational capacity.
Lessons From Rural India That Apply Globally
The lessons from building in a constrained environment are not sentimental, they are structural. Resource scarcity forces prioritisation. Weak infrastructure forces self-reliance. Unreliable systems force redundancy thinking. These are the same capabilities that make companies resilient under pressure. They are just harder to develop when everything works.