Quality Is Whatever the Person Checking Will Accept
In India, the real test of whether work is good enough is usually “will the person who checks this accept it?” — not an abstract internal standard a worker carries in their head. The bar moves with who is judging: a demanding client, a particular boss, an examiner, an inspector, an honoured guest. This is why “export quality” is a genuine, everyday category — work meant for a foreign or important client is held to a visibly higher standard than the same work destined for internal use. If you want a particular level of finish from an Indian colleague, don’t assume a universal standard is understood. Be the clear, named judge of the work and state exactly what “acceptable” looks like to you. Once colleagues know whose eyes the work has to pass, they will calibrate to that very precisely.
“Chalta Hai” — Good Enough to Work Is Good Enough
“Chalta hai” — literally “it goes / it’ll do” — captures an everyday working threshold where something that functions, even if rough or unpolished, is treated as finished. Under time and resource pressure, “it works and it passes” is often genuinely considered good enough, and small visible imperfections get let go rather than chased down. This is not laziness; it is a practical tolerance for adequacy when perfecting something wouldn’t change whether it works. If polish actually matters for your task — pixel-level finish, zero-defect output, exact formatting — you have to say so explicitly and explain why, because it will not be assumed. Framing it as “this goes straight to the client and they will reject anything less than perfect” works far better than just asking for “high quality,” which can quietly collapse back into “good enough to pass.”
Jugaad — Making It Work With What You Have Is Itself Good Work
“Jugaad” is the prized skill of making something work with whatever is at hand — a clever workaround, a frugal fix, a result delivered despite missing tools, budget, or time. Among Indian colleagues this resourcefulness is genuinely admired: the person who “manages” a solution under constraint is often respected more than someone who simply followed the proper procedure. The upside is speed and ingenuity; the trade-off is that jugaad solutions can be improvised rather than robust or documented. If you need durability, repeatability, or auditability, ask for it directly — say the fix has to survive without the person who built it, or be reproducible by someone else. And when a colleague pulls off a clever workaround, recognise it; brushing jugaad aside as “unprofessional” reads as not valuing real competence, and you will lose goodwill quickly.
Visible Effort and Sincerity Count as Part of the Work
In Indian workplaces, how someone’s work is judged includes how much sincere effort they are seen to put in — not just the finished output. The word “sincere” is high praise here; visible diligence, putting in the hours, and earnest good faith all count toward being regarded as a good worker, and they buy latitude when something falls short. Practically, this means a colleague who clearly worked hard may expect that effort to be acknowledged even if the result needs fixing, and purely output-focused, effort-blind criticism can land as cold or unfair. Lead with recognition of the effort, then address the gap. It also means you can’t read quality off busyness alone — visible hard work signals commitment, not necessarily a finished, correct result, so still check the output on its own terms.
Quality Gets Reached by Sending It Back, Not by Getting It Right First Time
Expect quality to be reached through rounds of correction rather than delivered perfect on the first pass. The normal rhythm is: someone produces a draft, a senior person reviews it and sends it back, it gets redone — and that loop, not first-time precision, is how the standard is met. People often submit work knowing it will be checked and returned, so a rough first version is not a sign of carelessness; it is the expected opening move. To make this work for you, build review cycles into your timeline and give corrections clearly and specifically, because that is the channel through which standards actually travel. If you truly need it right the first time, say so explicitly and allow extra time up front — but understand you are working against a deeply ingrained submit-review-redo habit, so plan the iterations rather than fighting them.
The Senior Person Owns the Standard
Standards in Indian work settings are usually owned from the top, not negotiated among peers. The team lead or senior person defines what “good” means and signs off on it; colleagues generally don’t police each other’s quality or overrule a senior’s call, and a junior is unlikely to tell a senior the work isn’t good enough. So if you want a quality standard to actually hold, it needs to be set and visibly backed by whoever has seniority — peer-to-peer expectations alone tend not to stick. When you are the outsider or the client, be clear about your standard and route it through the lead; once the senior person owns it, the team will align behind it. And don’t expect a junior to volunteer that something is wrong upstream — you usually have to ask directly and make it safe to answer honestly.
“Is It Done?” — Quality as a Finish Line, Not a Degree of Finish
A lot of quality judgment in India runs on “is it done?” — a finish line you have crossed or not — rather than a sliding scale of how refined the work is. Completion markers carry the weight: the task is “closed,” the sign-off is given, the certificate or degree is in hand, the marks are scored. The risk for you is that “done” can mean “the box is ticked” rather than “finished to the level you imagined,” so “it’s done” and “it’s good” are not the same claim. When you hand off work, define what “done” actually includes — the specific conditions that make it complete, not merely that it exists — and confirm against those conditions rather than the word “done.” Spelling out a clear definition of finished turns a vague yes into something you can rely on.