The Plan Belongs to the Senior Person
When you work with Indian colleagues, expect the plan to be owned by the most senior person in the room — the manager, the team lead, the client, the elder. Planning is usually not a flat, everyone-contributes exercise; direction flows downward, and juniors are there to execute it well rather than to redesign it. If you want a plan changed, the productive move is to raise it with whoever holds that authority, not to settle it sideways among peers and assume it sticks. Decisions made without the senior person’s sign-off tend to come undone. This also means a junior colleague going quiet in a planning meeting is usually showing respect, not disengagement — they may share real concerns privately, or once the boss invites them to. Route planning questions upward, and confirm the senior person is genuinely on board.
Plans Are a Direction, Not a Contract
Treat a plan with Indian colleagues as a confident statement of direction rather than a fixed, fully-specified blueprint. Detail is often kept light at the start, with the path worked out as the work unfolds — and revising the plan midway is normal and skilled, not a sign of failure. You’ll hear phrases like “it will get done” or “we’ll manage” that signal commitment to the goal without locking the route. If you need precise interim specs, scope, and dates, ask for them explicitly and revisit them, because they may not be volunteered upfront. Don’t read flexibility as disorganization: the same colleagues can deliver with extraordinary reliability when the target genuinely matters. The practical tip is to agree firmly on the outcome and the deadline, then expect — and leave room for — the method to shift as reality pushes back.
Relationships Are the Backup Plan
When something goes wrong, expect your Indian colleagues to fix it by working their network — calling the right person, pulling a favour, finding someone who knows someone — rather than by reaching for a written contingency procedure. Contingency lives in relationships and trust, not in documents. This is why building genuine personal rapport isn’t just a nicety here; it is the actual mechanism that makes delivery resilient. A colleague who trusts you will move mountains and surface problems early; one who doesn’t will quietly route around you. Practically: invest in the relationship before you need it, learn who is well-connected on the team, and understand that “I know someone who can sort this” is often a more reliable recovery path than escalating through formal channels. The flip side is that purely process-based problem-solving, with no relationship behind it, tends to stall.
Time Is Textured, Not Uniform
With Indian colleagues, time isn’t a flat, interchangeable resource — certain moments carry more weight than others. The start of something significant is often anchored to an auspicious or culturally meaningful date: weddings, openings, big purchases, even the stock exchanges’ special Diwali trading session are timed this way, and a colleague may sincerely prefer to begin a venture on a “good” date. Between those fixed points, day-to-day time tends to be elastic — meetings drift, gatherings begin when people actually arrive, and a stated clock-time can be softer than it looks. Practically: pin down hard deadlines explicitly and confirm they are being treated as hard, build buffer around start dates that may be set by the calendar rather than by your logistics, and don’t assume a time is exact unless it has been handled as exact. Reading which moments are fixed and which are flexible is the key skill.
The Ideal of Systematic, Process-Driven Planning (Aspirational Pattern)
Aspirational pattern — this describes an ideal India holds and teaches about itself, not how colleagues necessarily plan from day to day. India deeply admires rigorous, documented, process-mature planning: it shows up in the prestige of engineering and management training, in the global reputation its software industry built on process certifications, and in a long civic tradition of celebrating “scientific” planning. Colleagues may sincerely present work in this systematic register — detailed plans, formal reviews, best-practice language. Take it seriously as a value, but verify it against behavior: the polished plan on the slide often coexists with much more relational, adaptive, hierarchy-led execution underneath. The useful move is to treat stated process as a genuine aspiration and a point of pride, while checking how planning actually runs in practice — and to recognize that the gap between the two is normal, not hypocrisy.