Resourceful Workarounds With Whatever Is at Hand
When something needs solving, expect your Indian colleagues to reach first for a clever, low-cost workaround using whatever is already available, rather than proposing to rebuild the system properly. This instinct — make it work, get it done, good enough for now — runs deep, and it is genuinely impressive in a pinch: people are remarkably inventive under constraints. But be clear about what it is and is not. It is improvised adaptation, not systematic redesign, and it often leaves the underlying problem in place. If you need a quick fix, this is a real strength to lean on. If you need a durable, re-engineered solution, say so explicitly and protect the time and budget for it, because the default pull will be toward the fast, frugal patch that keeps things running today.
New Ideas Live or Die by a Senior’s Blessing
In practice, a new approach goes nowhere in an Indian team until a respected senior person backs it. The real test an idea faces is usually not a data review or an open debate — it is the judgment, experience, and gut feel of someone with standing. Win that person over, ideally in private first, and the idea gains momentum; skip them and even a strong idea stalls or quietly dies. So if you want something tried, do not just pitch it to the room. Find the senior sponsor, make your case to them directly and respectfully, and let them carry it. Once a trusted senior owns an idea, others get on board quickly. Pushing something over a senior’s head, or expecting it to win purely on merit in a meeting, usually backfires.
Ideas Surface Quietly, and Disagreement Stays Polite
Do not expect people to challenge the boss, or each other, openly in the room. New ideas and doubts tend to surface indirectly — in side conversations, hedged language, or a quiet word afterward — because keeping the relationship smooth and everyone’s dignity intact matters more than blunt directness. Silence in a meeting is not agreement, and a polite “yes, we’ll try” can mean “this won’t work” without ever saying so. To get real input, create low-pressure, private, or one-on-one channels where people can speak without appearing to contradict a senior or embarrass a colleague. Ask in ways that do not force anyone to disagree out loud. If you reward people who push back bluntly in public, you will mostly get quieter, not better, feedback — the honest signal travels through the side door.
Things Move Through Relationships, Not Process
Whether an idea spreads, a fix gets adopted, or anything actually gets done depends heavily on personal relationships and trust, not on official process or documentation. A good practice in one team does not propagate because someone wrote a memo; it spreads because the right people know and trust each other. Getting past a bottleneck often comes down to who you know and the goodwill you have built, not the formal procedure. So invest in relationships before you need them. The time spent on chai, on personal rapport, on the network is not a distraction from the work — it is the infrastructure the work runs on. If you are rolling out a new approach, map who is connected to whom and seed it through trusted people, rather than relying on an announcement to carry it.
Safe Execution Beats Risky Experiments
There is a strong pull toward doing the proven thing well rather than gambling on something new, and a real wariness of visible failure. A failed experiment can feel like a personal and professional risk — to one’s standing, even one’s job security — so people often prefer to execute the known method reliably than to be the one who tried something that flopped. This is not a lack of ability or ambition; it is a rational response to environments where mistakes have been costly. To get genuine experimentation, you have to make failure safe and cheap: frame trials as low-stakes and reversible, make clear that a sensible attempt that does not pan out will not be held against anyone, and, as the senior person, visibly own the risk yourself. Remove the downside and the willingness to try shows up.
Build On the Old, Don’t Replace It
When change does happen, it usually takes the form of absorbing and adapting the new into what already exists, rather than tearing things down and starting fresh. New tools, methods, and ideas get bolted onto established ways and blended in, preserving continuity. A proposal framed as “let’s enhance and extend what we already do” lands far better than “let’s scrap this and replace it,” which can feel disrespectful to the people and the history behind the current way. So position innovation as evolution, not rupture: show how the new approach honors and improves the existing one. You will meet much less resistance and adoption will be smoother. Pushing wholesale replacement — however logical it looks on paper — tends to trigger quiet resistance, because the instinct is to fold the new into the familiar, not to discard the familiar.
The Self-Image of the Bold, Frugal Innovator (Aspirational — what the culture believes about itself, not how colleagues necessarily behave)
This pattern describes an ideal the culture holds and celebrates, not a description of day-to-day behavior — read it that way. India carries a strong, proud self-image as a land of ingenious, frugal innovation: the “jugaad” spirit, the startup nation, doing more with less, lean breakthroughs achieved on shoestring budgets. You will hear this in company values, training material, policy language, and national narrative, and it is sincerely held. Treat it as an aspiration, not as operating reality. On the ground, actual innovation tends to be cautious, channeled through senior authority, relationship-driven, and continuity-preserving — often quite different from the fearless, distributed, break-the-mold creativity the rhetoric implies. The gap itself is useful to you: when colleagues invoke the entrepreneurial, innovative ideal, respect it as a genuine value, but plan around how new approaches actually get made here, not around the slogan.