Your Leadership Playbook is Context-Dependent. You Probably Don't Know It Yet.

Part 1 of a series on what working across five radically different organizations taught me about the real competency behind leadership effectiveness.

Within six months of joining a large Indian PSU, I designed and launched their first-ever learning management system. The organization had been trying to build one for years. Multiple attempts, multiple stalls. I came in, mapped the requirements, found the gaps, built the thing, and shipped it. By any conventional measure of functional delivery, it was a win.

It led to one of the most embittered factional standoffs I've witnessed in my career.

Two HR teams, who had until then coexisted in an uneasy truce, turned openly hostile. The team that hadn't been involved felt overstepped, outshined, and excluded. The quality of what I'd built was never questioned. Nobody said the LMS was bad. Nobody said it wasn't needed. What they said, in corridors and in meetings with senior leadership, was that it had been done wrong. That they hadn't been consulted. That I had moved too fast, too independently, without building the consensus the system required.

I remember the disorientation of that period vividly. My first instinct was to question - where had I gone wrong? I had done exactly what had made me successful in my previous role at an offshore consulting firm: identify a problem, design an intervention, deliver with precision and speed. That playbook had earned me credibility, stretch assignments, recognition. My next instinct was to blame the environment - they don't value innovation; they don't support initiative; they're being defensive; it's dirty politics; they have a personal vendetta. It's somewhat sad to admit that the realization that I was villainizing them unjustly came only after I moved from that role. It took a different organisation, a different operating logic, and a different set of mistakes to see that I hadn't used the wrong playbook - I had used the right playbook in the wrong game. It was like I was answering questions in a literature exam using mathematical equations.

That was the first time I understood something that I've since come to believe is the most underrated insight in leadership: what makes you effective is not transferable across organizations. Not automatically. Not without significant recalibration. And most dangerously, not without you realizing it needs recalibrating at all.

The assumption nobody questions

There is a quiet assumption that runs through most leadership development. It goes something like this: as you accumulate experience across organizations, you build a toolkit. Competency frameworks, change management models, stakeholder engagement techniques, learning design principles, talent review processes. The toolkit grows, you get better, your value compounds.

This assumption is embedded in how we train leaders, how we write job descriptions for senior roles, and how we evaluate candidates. We look for breadth of experience as though it automatically produces depth of judgment. We assume that someone who has "done" process delivery or functional leadership in three organizations knows it better than someone who has done it in one.

I've worked in five fundamentally different organizations over twelve years. An offshore consulting firm serving US clients. A Maharatna PSU with operations across India. A central government ministry shaping policy for public enterprises. A domestic consulting firm with hands-on client delivery. And a PE-backed multinational navigating the chaos of thirteen companies merging into one.

If the toolkit assumption were true, I should have arrived at each successive organization more prepared than the last. In some ways I did. But in the ways that mattered most for the first six to twelve months, I arrived miscalibrated. Not incompetent. Miscalibrated. Which is, in many ways, harder to diagnose because everything you're doing feels right. The feedback that it isn't right arrives late, indirectly, and often in the form of political damage you didn't see coming.

Five organizations, five different games

What I've come to understand, looking back across these five organizations, is that each one was operating on a fundamentally different logic. Not just different industries or different sizes, but different rules for what "good" looks like, how credibility is built, who the real client is, and what impact actually means.

Let me lay these out, because the specifics matter.

1. The offshore consulting firm ran on practitioner expertise and delivery precision. Your value was measured by the quality and timeliness of your output. Clients were remote. Colleagues were the daily interface. The unspoken rule was: be so good at the work that your work speaks for you. Politics existed, but competence was the dominant currency. If you could design a sharp framework, manage your team's bandwidth, and produce a polished deliverable on deadline, you were respected. End of story.

   
   

2. The PSU operated on an entirely different logic. Competence earned you a seat. But the seat didn't come with influence. Influence required network. It required relationships cultivated over time, across functions, with people whose support you would need not for this project but for the next five. Decision-making was collective, not by design but by survival instinct. The institutional memory was long, hierarchies were layered, and anyone who moved too fast without bringing others along was treated not as a high performer but as a threat. The LMS episode taught me this the hard way.

   
   

3. The government ministry added yet another layer. Network and relationships mattered immensely, but the primary skill was something more delicate: the ability to make every stakeholder feel genuinely heard without actually promising alignment. You were shaping policy for 300+ public enterprises, each with their own interests, their own organizational pressures, their own interpretation of what the policy should say. Senior bureaucrats, PSU leaders, think tanks, other ministries - everyone had a view. Your job was to rise above these influences and produce something fair, comprehensive, and defensible, without alienating the people who would need to implement it. You could not appear subservient to any single stakeholder, but you absolutely could not afford to antagonize them either. The tolerance for ambiguity was extraordinarily high. The tolerance for perceived bias was zero.

   
   

4. The domestic consulting firm brought a different set of demands. Everything I'd learned about stakeholder navigation was useful for client relationships, but the primary challenge was visibility and demonstrated impact. In consulting for Indian clients with hands-on delivery, you couldn't hide behind a remote operating model. You were in the room. You were travelling. You were implementing, not just advising. And the measure of your effectiveness was not whether you produced a thoughtful recommendation but whether your client and your Partner could see the change you had driven. Advisory without evidence of impact was just overhead.

   
   

5. The PE-backed multinational threw all the previous calibrations into question. Thirteen companies merging into one. Constantly shifting structure, positioning, go-to-market strategy. The foundational blocks that established organizations take for granted, role clarity, decision rights, cultural norms, a shared understanding of "how we do things here," didn't exist yet. They had to be built - and they had to be built fast. The premium was on speed, not precision. My instinct to produce polished, comprehensive, consultant-grade artifacts was, for the first time in my career, actively slowing me down. What the organization needed was progress: imperfect, directionally correct, shipped-today-and-iterated-tomorrow progress. The playbook that had served me well everywhere else, the one that said rigor and thoroughness earn credibility, was now a liability.

   
   

The accumulation trap

Looking at these five experiences together, a pattern emerges that I don't think gets talked about enough in leadership development.

Each organization required a primary skill that was necessary but insufficient for the next one. Delivery precision at the consulting firm was essential but not enough at the PSU, where network-building was the real game. Network-building was essential but not enough at the ministry, where stakeholder management without alignment was the game. Stakeholder management was essential but not enough at the domestic consulting firm, where visible impact was the game. And visible impact was essential but not enough at the PE-backed company, where speed of progress was the game.

The dangerous part is that each skill remained useful. It wasn't that my delivery precision stopped mattering when I joined the PSU. It still mattered. It just wasn't the thing that determined whether I succeeded or failed. And because it remained useful, it was easy to mistake it for sufficient. To keep leaning into the thing that had worked before, because it was still working, in a limited sense, even as the real determinant of effectiveness was something I hadn't yet developed.

This isn't just a personal development problem. When a senior leader is miscalibrated, the organization pays for it in ways that rarely get attributed to the right cause. The first twelve months in a new context are a credibility window. Stakeholders are forming judgments about whether this person understands how things work here. A miscalibrated leader who is producing excellent work that nobody asked for, or driving change at a pace the system can't absorb, burns through that window without realizing it. By the time the feedback arrives, the ceiling on their influence may already be set. Organizations read this as a "culture fit" problem. It's usually a contextual calibration problem, and the distinction matters because one is fixable and the other is a death sentence.

The calibration is easier to fix at junior levels. At junior levels, your work passes through others who correct the calibration errors you can't yet see. At senior levels, the logics are implicit and you are often the final decision-maker - there is no corrective layer between your instincts and their consequences. This is what I call the accumulation trap. You accumulate competencies across roles and organizations. You genuinely get better at many things. But you also accumulate blind spots, because each success reinforces the playbook that produced it, making it harder to see that the next organization requires a different playbook entirely.

Why the frameworks we use don't catch this

Let's look at the research available to us - the ones that we use to identify different organizational archetypes. Henry Mintzberg's work on organizational configurations identifies fundamentally different structural archetypes: the professional bureaucracy (where expertise drives the operating core), the machine bureaucracy (where standardization and hierarchy dominate), the adhocracy (where innovation and adaptation are the organizing principle). Each configuration has different coordination mechanisms, different power centres, and different definitions of what it means to add value.

My five organizations map almost perfectly onto different Mintzberg configurations. The offshore consulting firm was a professional bureaucracy. The PSU was a machine bureaucracy. The ministry was something closer to what Mintzberg might call a political arena, an organization where influence and negotiation are the primary coordination mechanisms. The domestic consulting firm was a professional bureaucracy with strong adhocratic elements. And the PE-backed company was an adhocracy in crisis, trying to find its shape while simultaneously performing.

Once you see organizations through this lens, the miscalibration problem becomes obvious. A leader who has perfected their craft in a professional bureaucracy will instinctively reach for expertise-based credibility in a machine bureaucracy, where relationship-based credibility is the real currency. They will keep producing excellent work and keep wondering why it doesn't translate into influence.

Ronald Heifetz's distinction between technical and adaptive challenges maps onto this as well. Most professionals are trained to solve technical problems: improve process bottlenecks, strengthen operations, increase revenue, improve bottom-line. These are problems where the solution is knowable and the challenge is execution. But the transitions between organizational archetypes are adaptive challenges. The problem is not that you don't know what to do. The problem is that what you know how to do has changed, and recognizing that fact itself requires a different kind of intelligence altogether.

Contextual intelligence: the competency that doesn't appear in competency models

What I've been circling around has a name, though it doesn't show up in most competency frameworks. It's contextual intelligence: the ability to read the organizational environment you're in, understand what game is actually being played, identify what the dominant currency of credibility is, and recalibrate your approach accordingly.

This is different from adaptability, which is the word most frameworks use. Adaptability suggests flexibility, a willingness to adjust. Contextual intelligence is more demanding than that. It requires you to actively diagnose the system you've entered, question the assumptions that served you well elsewhere, and sometimes suppress instincts that have been validated by years of success.

Consider what contextual intelligence would have looked like at each of my five transitions:

At the PSU, it would have meant recognizing that the LMS was a political object, not just a technical one. That building it well was necessary but that building consensus around it was the actual deliverable. That my speed, which felt like a strength, was being read as a signal of disregard for the institutional process.

At the ministry, it would have meant understanding that "taking everyone along" (which I'd painfully learned at the PSU) was necessary but had to be balanced against the appearance of independence. That the skill wasn't just listening to stakeholders but creating the conditions for fair outcomes without becoming captured by any of them.

At the domestic consulting firm, it would have meant grasping that the credibility I'd built through careful stakeholder navigation wasn't visible in the same way. That consulting in India, with direct client delivery and high-touch implementation, required a different kind of proof: not that I could manage complexity, but that I could show results.

At the PE-backed company, it would have meant accepting that my instinct toward comprehensiveness and polish, the thing every previous organization had rewarded, was now misaligned with what the organization needed most: velocity. That "good enough, shipped today" was more valuable than "excellent, shipped next month."

In each case, contextual intelligence is the thing that would have shortened the miscalibration period. Not eliminated it, because some degree of recalibration is inevitable. But shortened it from months to weeks.

The 2x2 that clarified this for me

As I reflected on these transitions, I kept coming back to a distinction that I think captures the core tension. There are two dimensions that determine a leader's effectiveness in any given organization: their functional expertise (how well they understand the technical craft of their field) and their contextual calibration (how well they've read the organizational logic and adjusted their approach).

	Low Contextual Calibration	High Contextual Calibration
High Functional Expertise	The Misread Expert. Technically excellent but solving the wrong problem or solving it in the wrong way for the environment. Gets things done but generates friction, misses political signals, and confuses their own competence with organizational fit. This was me at the PSU with the LMS.	The Embedded Strategist. Reads the system accurately, deploys technical skill where and how it will land. Builds credibility in the currency the organization actually values. Knows when to push and when to wait.
Low Functional Expertise	The Passenger. Neither equipped nor calibrated. Often survives through organizational inertia or political cover but adds little value.	The Political Navigator. Reads the room well but lacks the technical depth to deliver on what the organization actually needs. Can maintain relationships and avoid missteps but struggles to drive substantive change.

Most leadership development programs focus entirely on the vertical axis: build more functional expertise and you'll be a better leader. The horizontal axis, contextual calibration, is left to experience. Sometimes you develop it. Sometimes you don't. And when you don't, you end up in the top-left quadrant, genuinely excellent at your craft but consistently underperforming relative to your potential because you've misread the environment.

What this means for the rest of this series

I started this piece with a story about an LMS that succeeded technically and failed politically. But that's only one of many stories across these five organizations where the same dynamic played out, sometimes spectacularly, sometimes in ways that were only visible in retrospect.

In the pieces that follow, I want to explore the specific tensions that surface when you move between organizational archetypes. What happens when you carry an expertise-first mindset into an institution that runs on networks? What does it cost you when your instinct for stakeholder consensus collides with an environment that rewards visible, fast, individual impact? What do you lose, and what do you gain, when you finally learn that speed matters more than polish?

Each piece will pair two of these five organizations to surface a specific lesson about contextual intelligence. Not as memoir, but as a way of naming dynamics that most leaders experience but rarely have language for.

What's been your experience of moving between organizational archetypes? Did your playbook transfer cleanly, or did you discover, as I did, that effectiveness has an expiry date the moment the context changes? I'd like to hear about it.

An orange pencil on a black background contrasts with a black pencil on an orange background | Photo by Sóc Năng Động: https://www.pexels.com/photo/orange-and-black-pencils-on-split-background-34511909/