Process Runs Through Relationships, Not Paper
When you need something done in India, the fastest route is usually a person, not a procedure. Work moves because someone knows someone — the right colleague, the manager who can call ahead, the contact inside the department. People talk about having an “approach” or a “source,” and getting things done often depends on who you can reach rather than which form you file. For you, this means investing in relationships before you need them: a warm introduction, a senior who vouches for you, or a colleague who owns the relationship with a client or office will accomplish in a day what a cold, by-the-book request takes weeks to do. Don’t read this as corruption or as cutting corners — it is how the system is wired. Map the relationships around a task and you will understand how it will actually flow.
Jugaad — The Workaround as the Normal Route to the Result
“Jugaad” is the everyday art of reaching the result by an improvised route when the official path is blocked, missing, or too slow. Your Indian colleagues will frequently hit the goal in a way that wasn’t in the plan — substituting a resource, bending a step, assembling a fix from whatever is at hand. This is admired, not hidden; resourcefulness under constraint is a point of pride. What it means for you: expect the outcome to be delivered even when the prescribed steps were not followed exactly, and don’t assume that a deviation signals failure — often it is the thing that saved the deadline. The flip side is that improvised solutions can be fragile or undocumented, so if consistency and repeatability matter to you, say so explicitly and ask how the result was achieved, rather than assuming the textbook process was run end to end.
The Sequence Waits on the Senior
Action in India is gated by hierarchy. Most steps in a task pause until the senior person sanctions them, and people are reluctant to deviate from what a superior expects without that person’s blessing. This shapes timing: things move quickly once the boss is engaged and stall when they are not, so the real bottleneck is often access to the decision-maker, not the work itself. It also shapes how problems travel. Obstacles and bad news tend to surface late and indirectly — a “yes” or “it’ll be done” can mean “I heard you,” not “I have committed” — because contradicting or alarming a senior is uncomfortable. When something goes wrong, the fix is usually a senior intervening in person rather than a change to the system. Practically: identify who must approve, engage them early, and create low-stakes ways for juniors to flag trouble without losing face.
The Real Method Is Carried in People, Not Documents
There is often a gap between the written procedure and how work is truly done. Documentation tends to exist for compliance, audits, and clients, while the working knowledge — the order things really happen in, who to call, where the shortcuts and the landmines are — lives in people’s heads and passes on by watching and word of mouth. A new joiner learns the real process from a senior colleague, not from the manual. For you, this means the document may not tell you what actually happens, and the person who has done it before is your best source. Ask “how is this usually done here?” rather than relying on the written procedure, and if something must be repeatable by others, push to get the tacit knowledge written down — it will not happen on its own. Lose the person and you can lose the process with them.
Chalta Hai — Deviation and Imperfection Are Absorbed, Not Corrected
“Chalta hai” — roughly “it’ll do,” “it runs” — captures a broad tolerance for things not matching the plan exactly. Minor defects, approximate results, and departures from the prescribed sequence are often accommodated and worked around rather than stopped and fixed at the root, and this is usually paired with a confident “no problem, it’ll get done.” The upside is that work keeps flowing under messy, real-world conditions and friction is avoided. The cost is that small deviations can accumulate and root causes go unaddressed because the immediate situation was patched. If precision, exact specifications, or zero-defect output genuinely matter for your work, you cannot assume they will be treated as non-negotiable — you have to name the standard explicitly, explain why it matters, and check against it, rather than expecting deviations to be flagged to you automatically. Stated clearly and verified, high standards are readily met.
Time and Sequence Are Elastic
Time in India stretches. Schedules, deadlines, and the order of steps are treated as flexible and negotiable rather than fixed, and several things often proceed in parallel rather than one neatly after another. A meeting may start well after its stated time, a deadline may be understood as an aspiration, and “I’ll do it now” or “two minutes” can cover a wide range. This is not a signal about how much your work is valued; relationships and the situation in front of someone usually take priority over the clock. Interestingly, some timings are treated as immovable — an auspicious date or hour can hold firm even when everything else slips. What to do: distinguish hard deadlines from soft ones out loud, build in buffer, and confirm timing as you go rather than once at the start. Treat a single stated date as the opening of a conversation, not a lock.
Process Excellence as Professional Self-Image (Aspirational Pattern)
Note: this pattern describes what much of professional India aspires to and teaches as the ideal — not necessarily how work is done day to day. India’s IT and services sector built a strong identity around world-class, rigorously documented process: maturity models, quality certifications, and “process excellence” are sources of genuine professional pride, and you will hear this self-image stated with confidence. Treat it as real and meaningful, but do not assume the certified, documented process is the lived one. In practice the polished procedure often coexists with the relationship-driven, improvised, and orally transmitted ways of actually getting work done described in the behavioral patterns above, and the two can diverge significantly. The useful move is to respect the aspiration — it tells you what your colleagues value and want to be seen as — while verifying, on any given task, how the work will actually flow rather than taking the documented process at face value.