When Expertise Is Not Enough: The Relational Intelligence Gap That Quietly Defines Senior IT Careers
There comes a moment in many senior IT careers. Usually, it arrives somewhere between a solid track record and the move into broader leadership, consulting, advisory work, or deeper ecosystem involvement. The rules change quietly, without any announcement.
The very strengths that earned you international assignments, management-level responsibility, and a reputation as the person who delivers complex transformations suddenly start creating friction. You stay focused on outcomes. You speak directly. You insist on merit and results. Yet the feedback that comes back feels strangely disconnected from what you actually did. People call you transactional. Or self-focused. In more polite circles you hear that you are strong-headed or that you always have an original perspective to share. Those last two almost sound like compliments. In a way they are accurate. But they also carry a clear signal: others are experiencing you as operating outside the relational flow of the ecosystem you want to influence.
This is not a flaw in your character. It is not even mainly a failure of communication. It is the gap between deep domain expertise and Relational Intelligence, often called RQ. And it remains one of the least discussed inflection points in the IT industry. In this piece I share five fictitious scenarios that many of you will recognise from your own experience or from people you have worked with.
What Relational Intelligence Actually Is – And Where It Comes From
Relational intelligence is not just a new name for soft skills. It has real intellectual roots. Understanding those roots helps explain why it matters so much in professional ecosystems.
The idea first took shape in France in 1994. Researcher and consultant Valérie Gauthier coined the term savoir-relier, which means knowing how to relate. She developed it as a leadership concept focused on building deliberate relational capacity: reading unspoken protocols, signalling alignment with the right people, and making sure your actions feel like they add to the larger system rather than take from it. The English term relational intelligence came later, but the thinking has been part of European leadership development for over thirty years.
American organisational psychologist Adam Bandelli built on this foundation. His doctoral work at the University of South Florida led to the most structured model available today. It centres on five core skills around discerning relational fit, aligning values, and assessing interpersonal dynamics. Psychotherapist Esther Perel brought the concept into mainstream corporate conversation. She describes relational intelligence as how you establish trust, how you overcome betrayal, how you choose to engage or avoid conflict, and how you manage the interaction itself. She positions it as a real competitive advantage for organisations, not just a personal quality.
In 2025 Stanford’s Social Innovation Review announced that we had entered the era of relational intelligence. The reason was clear. As AI systems grow better at cognitive tasks and even surface-level empathy, the distinctly human ability to navigate trust, repair relationships, and move gracefully inside complex social systems becomes the true differentiator. You simply cannot automate savoir-relier.
For those of us in ITSM and IT service management this feels especially relevant. Our own frameworks have quietly recognised it for years. ITIL 4 lists Relationship Management as one of its 34 core management practices. It sits alongside Risk Management, Strategy Management, and Workforce and Talent Management. ITIL Version 5 keeps it in the same important position. The framework does not treat relationship management as a personality trait or a nice-to-have extra. It treats it as an organisational capability that must be designed, measured, and improved. The same principle applies to us as individuals operating at the higher levels of the profession.
Five Scenarios Where Relational Intelligence Becomes Visible
The following examples are illustrative composites. The patterns come from real transitions in IT service management, consulting, and matrix organisations. If you have spent fifteen years or more in this industry, at least one of them will feel uncomfortably familiar.
Scenario 1: The Expansion That Strengthened the GCC but Weakened the Enterprise
An India-based Global Capability Centre for a European enterprise had become a clear success. Strong SLA performance, steady cost savings, and a growing reputation inside the company made everyone proud. The site leader saw the obvious next step: expand the centre to handle external customer support, which was currently scattered across expensive regional vendors.
The business case looked excellent. Better efficiency, greater scale, and significant cost reduction. Senior leadership approved it quickly.
Not everyone was convinced. The marketing head in Europe raised concerns early on. They were subtle but consistent. Customer experience might suffer. Regional expectations and language sensitivities could get lost. Those signals were noted but mostly interpreted as normal resistance to change rather than genuine caution from someone close to the customers.
The transition moved ahead anyway.
Twelve months later the operational numbers still looked good. SLAs were being met. Costs had come down as planned.
Customer sentiment told a different story. Clients, especially in non-English speaking markets and mid-tier segments, started pulling back. Not because of bad resolution times, but because the conversations themselves felt distant. Nuance disappeared. The familiar tone they were used to was gone. Retention softened in some key markets. Regional leaders began raising red flags.
Nothing was technically broken. But something important no longer worked.
The RQ Gap: The real gap was not in execution. It was in how the decision had been framed from the beginning. The GCC team had optimised for scale and internal efficiency. The wider enterprise needed continuity of customer connection. An internal support model had been stretched into an external world where expectations were fundamentally different.
Those early concerns from the marketing head were never resistance. They were signals from the person closest to the actual customer reality.
The GCC grew stronger. The enterprise quietly absorbed the cost in lost goodwill and retention.
Relational intelligence here was never about delivery excellence. It was about recognising that the success of the whole enterprise must come before the expansion of any single centre. And it was about knowing when to treat a dissenting voice not as an obstacle to overcome, but as a perspective worth genuinely hearing and weighing.
Sometimes a larger GCC is not the better contribution. Sometimes the more strategic move is restraint.
Scenario 2: The Knowledge Transfer That Delivered Everything Except Understanding
A large IT services provider wins a significant outsourcing deal and begins building a new offshore delivery capability. To accelerate the transition, the client offers something generous. Two senior architects will travel to India for eight weeks. The goal is clear: not just to explain the systems, but to make sure the offshore team truly understands the environment, the decisions behind it, and the relationship they are inheriting.
The offshore KT manager designs the programme. The client steps back, assuming the receiving team knows best what it needs.
The resulting programme is structured, comprehensive, and efficient. Sessions run back to back. Documentation is created. Diagrams are walked through. Repositories are populated and indexed. The focus stays sharp: extract and transfer as much knowledge as possible in the available time.
From a process viewpoint it looks exemplary.
Eight weeks later the architects fly home. The transition is formally signed off.
The team now has everything on paper: architecture designs, data flows, operational runbooks, configuration documents. What they do not have is real understanding. They lack the context behind key decisions, why certain choices were made, what constraints shaped them, and what the client had tried and abandoned before. They miss the cultural texture of how this client actually operates: communication preferences, sensitivities, and the informal escalation paths that no diagram can capture. Many team members cannot even explain why the client chose to outsource in the first place or what business pressures and internal politics made the engagement meaningful.
The RQ gap is simple. The knowledge transfer captured information. It did not transfer perspective. It built repositories, not relationships.
The client had invested real proximity. Eight weeks of their most experienced people in the same room, ready for exactly the kind of judgement sharing and relationship building that turns a capable team into a trusted partner. Instead, the programme treated that time as a content extraction exercise. The architects were scheduled, not truly engaged.
In complex delivery work, information enables execution. Understanding enables judgement. The programme delivered the first efficiently. The long-term client relationship needed both.
Scenario 3: The Conversation That Should Never Have Happened in That Room
A technical delivery manager with twelve years in IT services is well respected inside his own business unit. He finds himself in a difficult situation with his line manager. A recent client escalation has highlighted gaps in internal support. Priorities feel misaligned and his contributions seem under-recognised. The frustration has been building for months.
At an internal leadership event he ends up in conversation with a senior VP from an adjacent unit. He has worked with this VP peripherally and respects him a great deal. The conversation feels warm and candid. He shares his situation: the issues with his line manager, the recognition gap, the sense of being sidelined. He is not complaining in bad faith. In his own mind he is simply discussing a professional challenge with a trusted senior voice.
The RQ Gap: The relational intelligence failure was not in the honesty. It was in reading the situation. He did not fully account for the setting.
Within weeks the atmosphere changes. His line manager becomes noticeably more formal. Access to certain conversations narrows. A development opportunity he had been quietly encouraged to pursue suddenly disappears.
Nothing is said directly. Nothing needs to be.
The difference is subtle. In senior careers, subtle is consequential.
Leadership networks in mature organisations are tightly connected. The VP and his line manager are peers who talk regularly. Conversations in that space rarely stay private. They travel, often reframed by the context of ongoing relationships.
In high-context environments, where you raise a concern, with whom, and under what circumstances matters as much as the concern itself. The same conversation held with an external mentor or in a structured HR setting would have been fine. Held in that room with that person, it activated a network he had not mapped.
Scenario 4: The Cyber Advisor Who Built a Pipeline Without Building a Partnership
A cybersecurity consultant with sixteen years of enterprise experience, including ISO 27001 lead assessor roles and former CISO advisory work, starts an independent practice anchored by a retainer with a specialist IT advisory firm. The firm brings him clients, handles commercial aspects, and lends institutional credibility. He delivers the assessments, training, and gap analyses. The arrangement works cleanly for everyone.
His personal reputation spreads faster than expected. Direct enquiries start coming in: a FinTech needing quick ISO readiness support, a healthcare group looking for DPDP compliance advice, a former mentee recommending him to a peer. None of this overlap with active retainer work, so he responds directly and professionally.
The retainer firm later hears about two of these engagements through shared contacts, as often happens in interconnected markets. Nothing is said openly. But over the next quarter the warm introductions slow down. A multi-site ISO rollout he had been informally lined up for goes to someone else. When he asks, the response is polite: “We assumed you were at capacity.”
That sentence had nothing to do with capacity.
The RQ Gap: He had operated as an independent contractor. The firm had expected a partner who keeps them in the loop as a matter of professional courtesy. The distinction is rarely written down, but it is strongly felt. Opportunity quietly moves elsewhere.
Scenario 5: The Leader Who Outgrew the Room — and Chose Not to Show It
A senior operations leader had built something genuinely impressive. Over several years at a fast-growing mid-sized IT services company, he helped scale the delivery organisation from a few hundred people to over a thousand. He put capability frameworks in place, instilled process discipline, and earned a reputation for blending strong execution with real strategic thinking.
Then came a two-year career pause for family reasons. When he returned the company had been acquired by a large multinational. The function he once led now sat under a more senior leader brought in during integration. The organisation was glad to have him back. His knowledge and credibility with the teams still mattered. Yet the role on offer was clearly below his previous level.
He accepted it without visible hesitation or negotiation.
Over the next few years, he worked with quiet consistency. He did not push visibly for promotion or broadcast his ambitions. His impact grew. Relationships deepened across India and into global teams. His strategic perspective started pulling him into conversations his formal grade would not normally allow.
This created unspoken tension. His direct manager, competent in most ways, began showing subtle signs of discomfort with the growing influence beneath him: credit quietly absorbed, ideas presented upward without full attribution, gentle steering away from high-visibility platforms.
The leader had options. He could escalate using his network. He could dial down his contribution. He could let the friction surface on its own.
He chose a different path.
In his annual review, a formal and protected setting, he addressed the dynamic with measured directness. He stated his ambitions clearly, not as a challenge but as an offer of clarity. He was not after his manager’s role. He wanted to contribute at the level he was capable of, with the space required to do so. He tied his own success directly to his manager’s success and the department’s performance.
“Use my strengths for the department’s success. Because if a rift appears where none exists, everyone will notice, and neither of us benefits.”
The words were careful. The intent was collaborative. The loyalty offered was genuine.
The RQ Edge: It required real patience, the kind that tests maturity when you can clearly see an unjust pattern. By removing ambiguity, he gave his manager room to recalibrate without losing face. The insecurity lost its fuel. Professional space opened. Collaboration deepened.
The results went far beyond the immediate team. The function’s improved performance drew global attention. Programmes built on the India model were adopted internationally. Indian thought leadership in the domain received formal recognition at a level the organisation had never achieved before.
None of that would have happened if he had won the smaller, more immediate argument.
This is relational intelligence at its most demanding. Not managing easy relationships, but holding clarity, maturity, and long-term orientation when a relationship is testing all three and repeatedly choosing the response that serves the larger outcome rather than the immediate grievance.
It is not passivity. It is one of the hardest forms of professional courage.
Five Levers for Building Relational Intelligence – With One Action You Can Take Today
Lever 1: Gatekeeper-First Discipline
In network-driven environments such as consulting ecosystems, training partnerships, and multi-vendor IT service arrangements, every intermediary or platform partner carries an implicit ownership of the commercial interface. This is rarely stated and almost never written down. Yet it is strongly felt when violated.
The practical step is straightforward. Before taking independent action on any opportunity that touches a partnership, surface it first to the gatekeeper in writing and with clear transparency. This does not mean giving up your agency. It means showing that you understand and respect how the ecosystem actually works.
Action you can take today: Identify one active professional relationship where you have been operating somewhat independently and send a brief, genuine update to the relevant partner. Not to report, but to connect.
Lever 2: Structured Transparency – The 48-Hour Signal
Silence is the most misunderstood signal in professional relationships. When you go quiet after someone shares an opportunity, even if you are simply busy, the other person fills the gap with their own interpretation. Usually that interpretation leans toward disinterest or selective behaviour.
The simple antidote is a consistent rhythm. Within 48 hours of any shared lead or collaborative action, send a short update. Four lines are enough: what you did, what you heard, what you are thinking next, and one question that brings them back in. Consistency matters more than perfect content. Over time this builds a reputation for reliable care that no single transaction can create.
Action you can take today: Think of one professional interaction from the past week where you have not followed up. Send a four-line message before the day ends.
Lever 3: Read the Room Before You Read the Agenda
Many serious relational missteps in senior IT careers happen not because people are careless, but because high performers are trained to focus first on content. What is the problem? What is the solution? What needs to be said? Relational intelligence asks the prior question: Who is in this room, how are they connected, and what will this conversation trigger in the wider system?
This is not paranoia. It is ecosystem literacy, the same contextual awareness we apply to technical architectures, now applied to human systems.
Action you can take today: Before your next important conversation with a senior stakeholder, spend five minutes mapping one level of their professional relationships. Who do they report to? Who are their peers? How might this discussion look from their position?
Lever 4: Win-Win Framing Is a Language Discipline, Not an Attitude
Most senior IT professionals truly want outcomes that work for everyone. The gap usually lies not in intent but in expression. When a proposal leads with your own requirements or constraints, even legitimate ones, the signal received is self-protective. When it leads with the other party’s challenge and positions your contribution as a response to that challenge, the signal becomes collaborative.
This is a discipline of sequencing, not a personality change. It keeps all your directness and precision. It simply asks you to answer one question first: what do they need to hear before I say what I need to say?
Action you can take today: Take one proposal, email, or conversation you are preparing and rewrite the opening paragraph, so it starts with the other party’s objective rather than your own.
Lever 5: The Post-Action Perception Audit
Every significant interaction leaves a relational residue. High performers often focus so hard on the task outcome that they skip the quick reflection that would catch misalignment early.
The habit is simple. After any important meeting, negotiation, or communication, pause and ask three questions. How did I intend this to land? How might it actually have landed? Is there one small thing I could do in the next 24 hours to adjust or reinforce? This is not overthinking. It is rapid feedback processing, the same discipline we use in incident reviews, now applied to relationships.
Action you can take today: Think of one recent interaction where the feedback, direct or indirect, felt slightly off from your intent. Run the three questions. If a short follow-up message would help, send it.
A Personal Note
I do not write this from a position of having fully solved the challenge. I write as someone who holds strong values: meritocracy, outcomes, directness, and original thinking. I am still learning how to express those values in the relational register that consulting and global IT service ecosystems demand. I have received the kind of feedback described earlier. Strong-headed. Always has an original perspective. Technically correct, yet relationally coded. The gap between who you are and how you land is real. For those of us who built our careers on technical mastery, discovering that gap can feel disorienting.
This transition is not unique to any one person. It is the common experience of every high-performing individual contributor or delivery leader moving into roles where influence, trust, and perceived alignment matter as much as expertise. The encouraging truth is that relational intelligence is learnable. It is not a personality trait you either possess or lack. It is a practice. Savoir-relier. Knowing how to relate. It can be built, one deliberate act at a time.
Start with just one lever. Start today. Your next opportunity, referral, or leadership transition will show the difference.
About the Author:
Rajwardhan Purohit is Capability Architect and Evangelist of the Capabilities-as-a-Service (CaaS) framework—reimagining how organizations build, activate, and scale human potential in the digital age.
He has 25+ years of rich global experience in IT delivery, program management, and served as Head of Innovation at British Council, SSC(GBS) in his last role. Rajwardhan is currently Global Ambassador for ITIL4 and DevOps, and certified ITIL4 Maturity Consultant, Tool Assessor, ITIL4 Managing Professional, and accredited trainer. View expressed in this article are his personal