The Case for Staying: When Not to Switch Jobs

The short version

There is a version of this conversation that stays at the level of frameworks, and a version that deals with what actually happens on a Tuesday afternoon. This is the second kind.

Start with the constraint rather than the ambition. In most Indian organisations the binding constraint is not talent or budget — it is the absence of a clear owner. Once a named person carries the outcome, the sequencing question tends to answer itself.

Where teams get it wrong

Scale changes the answer. What works for a fifty-person team fails at five hundred, not because the idea was wrong but because the coordination cost grew faster than the benefit.

Evidence beats opinion, but only if the evidence is collected before the decision. Retrospective justification is the most common failure mode, and it is very hard to spot from the inside.

A practical approach

Start with the constraint rather than the ambition. In most Indian organisations the binding constraint is not talent or budget — it is the absence of a clear owner. Once a named person carries the outcome, the sequencing question tends to answer itself.

Finally, there is the question of who pays and who benefits. When those are different groups, adoption stalls regardless of how good the design is. Aligning them is unglamorous work and it is usually the work that matters.

What to do next

Scale changes the answer. What works for a fifty-person team fails at five hundred, not because the idea was wrong but because the coordination cost grew faster than the benefit.