Accountability - understand-culture

Accountability Runs to a Person, Not a Role

When you take on a piece of work in an Indian team, the real question isn’t what’s in your job description — it’s whose work this is and who you answer to. You are accountable to your manager as a person, not to an abstract scope you own. That relationship runs two ways: a good boss takes personal interest in you, and in return you give loyalty and effort. The practical upshot is that the consequences of doing well or badly are mostly relational — you gain or lose your manager’s trust, protection, and goodwill rather than triggering a formal procedure. A strong personal relationship, or a good connection (sifarish), will shield you when something goes wrong far more than a clean paper trail will. To work well here, invest in the relationship with whoever you answer to; that bond is the operating system.

Credit Rises to the Top

Watch where credit lands when a project goes well, and you’ll see it flow upward. The manager, the senior, the head of the unit is treated as the owner of the win — they present it, they’re congratulated for it, and they decide how much recognition to pass back down. This usually isn’t resented; it’s how seniority works, and a generous senior who shares credit earns deep loyalty. If you’re junior, expect your contribution to be visible mainly to your immediate boss rather than broadcast upward in your name — making sure that one person knows what you did matters more than a company-wide announcement. If you’re the senior, remember that people notice whether you hoard the credit or distribute it; passing it down is one of the most powerful things you can do to keep a team committed.

When Things Go Wrong, Blame Moves Sideways or Out

Here’s the honest reality of how failure plays out: blame is rarely picked up and held by one named person. It gets deflected to circumstances (“the requirements changed,” “the vendor let us down,” “conditions were against us”), diffused across the group so no single owner stands out, or quietly attributed to factors outside anyone’s control. The language itself helps — people say “a mistake happened” rather than “I made a mistake.” If you’re expecting a colleague to openly say “that was my fault,” you’ll usually wait a long time; as they see it, that isn’t evasion, it’s simply how responsibility is handled. To get to the real cause without triggering defensiveness, frame it as fixing the situation together rather than finding who is at fault — the moment it feels like blame-assignment, the shutters come down.

People Defer Upward and Hold Back Bad News

Rank is respected, and that shapes what gets said out loud. A junior colleague is unlikely to openly contradict a senior, push back on an instruction, or be the one to deliver bad news upward — doing so risks embarrassing the senior and looking out of line. So you will often hear “yes, sir,” “it’ll be done,” and “no problem” even when there are real doubts, and problems tend to surface late, once they are hard to hide. This isn’t dishonesty; it’s deference, and an assumption that the senior shouldn’t be put in an awkward spot. If you’re the senior and you want early warning of trouble, you have to actively create permission for it: ask direct questions, make it safe to speak, and never punish the messenger — otherwise the bad news simply won’t reach you in time to act.

Failure Is Handled Quietly to Protect Face

Reputation — izzat, “what will people say” — is taken seriously, and it governs how the accounting actually happens. Praise and success are made public; criticism and failure are handled privately and indirectly. You rarely see someone’s mistake named in front of the whole team, because that causes a loss of face that damages both the relationship and the person’s standing. A senior will more often signal displeasure through a quiet word, a cooler tone, or an intermediary than through open rebuke. The practical lesson for anyone managing here: never correct or criticize someone in front of others if you want it to land well. Take it offline, keep it discreet, and let the person keep their dignity. A public dressing-down doesn’t read as accountability — it reads as an attack, and it tends to backfire and harden resistance.

Among Peers, Ownership Is Shared and Often Blurry

At the level of the team itself, individual ownership of a specific deliverable is often soft. Work is taken on collectively — “we’ll handle it,” “it’ll get done” — without one person clearly on the hook, and afterward it can be genuinely hard to say who owned which piece. This has two faces. On the upside, the group closes ranks and absorbs the load together, and colleagues pitch in across boundaries without being asked. On the downside, when something slips, the diffuse ownership means no single person feels it was theirs to catch, and tasks fall between the cracks with everyone assuming someone else had it. If you need something owned cleanly, don’t rely on it being implied: name the specific person, have them accept it out loud, and write it down — because shared ownership easily becomes no one’s ownership.

The Ideal of Clear Ownership and “Owning Your Outcomes” (Aspirational)

Important: this pattern describes what the culture teaches and admires, not how people typically behave. India has a large and growing language of personal accountability — corporate values posters, leadership books, management training, and celebrated moments such as a cricket captain publicly “taking accountability” for a loss. These are held up as ideals precisely because they stand out against the everyday norm; the fact that a leader openly owning a failure becomes a notable story tells you it is not the default. So when an organization describes itself as having a strong “ownership culture,” treat that as a sincere aspiration and a statement of values — genuinely useful for knowing what people respect and reward — but don’t assume it predicts behavior. On the ground, the relational, face-protective patterns above usually govern what actually happens when work succeeds or fails.