Contextual Intelligence: The Competency That Doesn't Appear in Competency Models

Aparajita Sihag
Apr 22
8 min read

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

I started this series with a story about an LMS that succeeded technically and failed politically. Over the five pieces that followed, I traced a pattern across five organizational archetypes: an offshore consulting firm, a Maharatna PSU, a central government ministry, a domestic consulting practice, and a PE-backed multinational mid-merger.

Each organization taught me something that the previous one couldn't. And each lesson, when carried uncritically into the next context, became a liability rather than an asset.

Delivery excellence became a blind spot at the PSU. Social capital awareness became insufficient at the ministry. Diplomatic stakeholder management became a cloak of invisibility at the consulting firm. And the instinct for comprehensive, polished design became a tempo mismatch at the PE-backed company.

The through-line across all of these transitions is not that I lacked competence. In each organization, the technical skill was there. What was missing, and what took years of painful recalibration to develop, was the ability to read the organizational context I was in and adjust my approach before the mismatch produced damage.

I've been calling this contextual intelligence. This final piece is my attempt to move from narrative to framework: to articulate what contextual intelligence actually is, how it can be diagnosed, and why it deserves a place in how we develop HR leaders.

What contextual intelligence is not

It helps to start with what I don't mean.

Contextual intelligence is not adaptability. Adaptability is a disposition, a willingness to adjust. Most competency frameworks include some version of it: "responds effectively to changing circumstances," "demonstrates flexibility." These are fine as descriptors, but they don't tell you what to adapt to, how to diagnose what needs adapting, or when you've read the context accurately enough to act. Adaptability without diagnosis is just reactive flexibility. It helps you survive. It doesn't help you calibrate.

Contextual intelligence is not cultural awareness. Cultural awareness, in the way most organizations use the term, refers to sensitivity to differences in norms, communication styles, and values. This is necessary but insufficient. Two organizations can have similar cultures (collegial, informal, innovation-oriented) and still operate on completely different logics. A consulting firm and a startup might feel culturally similar, but the operating currency in one is expertise and in the other is speed. Cultural awareness might help you fit in. Contextual intelligence helps you figure out how to be effective.

Contextual intelligence is not political savvy. Political savvy is the ability to read power dynamics, identify key influencers, and navigate organizational politics. It's a subset of contextual intelligence, but only a subset. My failure at the PSU wasn't primarily a failure of political savvy. It was a failure of recognizing that the entire coordination system ran on social capital rather than technical output. Political savvy might have helped me avoid specific missteps. Contextual intelligence would have helped me see that the game itself was different.

What contextual intelligence is

Contextual intelligence, as I've come to understand it through these five transitions, is the ability to diagnose the operating logic of an organizational system and recalibrate your approach before the mismatch between your playbook and the system's requirements produces irreversible damage.

Three things are embedded in that definition.

First, diagnose. This is an active, deliberate process. Not intuition. Not "getting a feel for the place." It requires asking specific questions, observing specific signals, and testing specific hypotheses about how the organization actually works as opposed to how it says it works.
Second, recalibrate. This is harder than it sounds. Recalibration doesn't mean adding a new skill to your toolkit. It means suppressing instincts that have been validated by years of success. The instinct for comprehensive design. The instinct for independent delivery. The instinct for consensus-building. These aren't bad instincts. They are context-dependent instincts, and contextual intelligence requires you to recognize when your strongest instinct is the wrong one.
Third, before the mismatch produces irreversible damage. This is the time dimension. At the PSU, I understood the system's operating logic only after I had left. The learning crystallized in retrospect. The cost of that delayed diagnosis was two and a half years of diminished effectiveness and relational damage that couldn't be repaired. Contextual intelligence, to be useful, has to operate faster than that. Not instantly, because some learning requires immersion. But faster than the organization's patience for your miscalibration.

A diagnostic framework

Across the five archetypes, five diagnostic dimensions emerged. Each corresponds to a question you should be asking in your first ninety days, and each has a range of answers that reveal fundamentally different operating logics.

Diagnostic Question	What it reveals	How to read it
What is the operating currency of credibility?	Whether the system rewards expertise, relationships, fairness, visible impact, or speed	Listen to how the organization praises people and work it respects. The language of praise reveals the currency.
Who is the real client?	The gap between who the org chart says you serve and whose satisfaction actually determines your effectiveness	Your formal client and your functional client are almost never the same. Identify the functional one first.
What does "good" look like here?	Whether the system values polish, consensus, defensibility, visibility, or implementability	Look at the last three people who were promoted or publicly recognized in your function. What they did and how they did it tells you what "good" means here.
What is the cost of moving too fast vs. too slow?	The organization's implicit tempo and its tolerance for speed vs. delay	In institutional environments, delay is cheap and speed is expensive. In high-velocity environments, the reverse. Most HR leaders default to one tempo and don't realize it's a choice.
How does information flow?	Where actual power and coordination live, as distinct from the org chart	Map who gets consulted before decisions are announced, who hears things first, whose opinion is sought even when their role doesn't require it. This tells you more than any values statement.

These five dimensions don't operate independently. In any given organization, they form a pattern. At the PSU, the pattern was: credibility through relationships, the real client was the peer network, "good" meant consensual and inclusive, speed was expensive, and information flowed through informal relationship channels. Every element reinforced every other element. If you misread one, you misread the system. If you read the pattern correctly, you know what game you're playing before you make your first move.

The visual below maps each dimension across all five archetypes. Read a column to see the full pattern of one organizational type. Read a row to see how a single dimension shifts across contexts. The mismatch between your previous column and your current column is where miscalibration lives.

	Offshore consulting	PSU	Government ministry	Domestic consulting	PE-backed MNC
Credibility currency	Expertise	Relationships	Independence	Visible impact	Speed
Real client	Onshore team + end client	Peer network	Policy ecosystem	Client + internal leaders	Org's absorptive capacity
What "good" looks like	Polished, on time	Consensual, inclusive	Fair, defensible	Visible, client-endorsed	Fast, implementable
Cost of speed vs. delay	Delay is expensive	Speed is expensive	Both are expensive	Delay is expensive	Delay is very expensive
Information flows through	Delivery checkpoints	Relationship networks	Hierarchical conversations	Partner attention	Whoever is closest to action

The teachable and the unteachable

If I were designing a development intervention around contextual intelligence (and perhaps someday I will), I would split it into two components.

The diagnostic practice is teachable. The five questions above can be learned, practiced, and applied systematically. You can train an HR leader to ask these questions in their first ninety days. You can give them frameworks for interpreting the signals. You can help them build a contextual map that identifies the operating logic before they start deploying their playbook.

What is harder to teach is the disposition that makes the diagnostic practice possible.

The disposition has two parts. The first is patience: the willingness to observe before acting, to sit with uncertainty, to resist the pressure (internal and external) to demonstrate value immediately. Every organization I've worked in created pressure to "hit the ground running." Contextual intelligence requires you to hit the ground watching, which feels uncomfortable and can look like passivity to people who are expecting impact.

The second is something I can only describe as the willingness to be a beginner. Not in the technical sense. You don't lose your functional expertise when you change organizations. But in the contextual sense, you arrive knowing nothing about how this particular system works. And if your identity is built on being the expert (as mine was, coming from consulting), the experience of not knowing is threatening. The instinct is to fall back on what you know rather than sit with what you don't. Contextual intelligence requires overriding that instinct long enough to learn the new system before you start trying to change it.

I don't think patience and the willingness to be a beginner can be taught in a classroom. But I do think they can be cultivated. And I think the most powerful way to cultivate them is exposure to multiple organizational archetypes, because nothing teaches you the limits of your playbook faster than watching it fail in a system it wasn't designed for.

What this series has been

I want to be honest about what writing this series has done for me, because I think the process matters as much as the product.

When I started, I had fragments. Experiences I remembered vividly. Lessons I had absorbed but never articulated. A general sense that my career path, its breadth across very different organizational types, had given me something valuable, but I couldn't name what that something was.

The process of writing, of pairing organizations against each other, of finding the academic frameworks that gave language to lived experience, of tracing the through-line from one transition to the next, has been an act of sensemaking as much as communication. I didn't start with the framework and illustrate it with stories. I started with stories and the framework emerged.

This is, I think, how most practitioner knowledge works. You accumulate experience. You develop instincts. You make decisions that feel right without being able to fully explain why. And then, if you're fortunate enough to have the time and inclination to reflect, you find the structure underneath the instincts and give it a name.

Contextual intelligence is the name I've given to the structure underneath my instincts. It's the competency that explains why I failed at the PSU and succeeded at the ministry, why I was invisible at Deloitte India and effective at Material, why the same skills that made me excellent in one context made me miscalibrated in the next.

The argument, stated plainly

HR effectiveness is not portable. The competencies that make an HR leader successful in one organizational archetype may actively undermine them in another. And the factor that determines whether a leader can bridge that gap is not the size of their toolkit but the quality of their contextual diagnosis.

Most HR development focuses on functional competence: deeper expertise in talent management, compensation, organizational design, learning and development. This is necessary. But it is not sufficient for leaders who will move across organizational archetypes, and in a career landscape where such moves are increasingly common, the gap between functional competence and contextual intelligence is where the most consequential failures happen.

What would it look like if we took contextual intelligence seriously as a development priority? Not as a line item in a competency model ("demonstrates awareness of organizational context") but as a structured diagnostic capability with its own frameworks, its own development pathway, and its own assessment criteria?

I don't have the complete answer. But I have five organizational archetypes, five transitions, five frameworks, and a diagnostic model that emerged from the wreckage of getting it wrong more often than I got it right.

That feels like a place to start.

This series began with a single question: why does HR effectiveness break down when you move between organizations? If you've read all six parts, you now have my answer. But I'm more interested in yours. What has your experience been? Which transitions broke your playbook, and what did you have to unlearn? The framework is only as useful as the conversations it generates. I'd like this to be one of them.