Being Right Is the Cheap Part
Picture the scene. It’s 2 p.m. on a Tuesday. You’re in a conference room — or staring at a grid of faces on Zoom — watching what should be a routine Q3 deliverables check turn into a slow-motion collision. The product lead is pushing hard for a feature release because sales has already promised it to a client. The engineering lead, arms crossed, is explaining for the third time why the current architecture physically cannot support that load without a total refactor. Both of them are correct. Both are speaking English. And neither is hearing a single word the other says.
This isn’t a technical failure. The code can be written. This isn’t a strategy failure. The market need is real. This is a translation failure — and it’s costing your organisation money, momentum, and probably a few good people every quarter.
After two decades spanning systems architecture and executive strategy, here is the most counterintuitive thing I can tell you about leadership: being right is the cheap part. Anyone with enough time and intelligence can arrive at the correct answer. The expensive part — the part that stalls careers, bankrupts cross-functional teams, and turns talented individuals into isolated contributors — is the inability to transmit that rightness to people who operate on a fundamentally different logic setting.
Why “Soft Skills” Is a Dangerous Misnomer
The term “soft skills” has done enormous damage. It implies these capabilities are optional — a nice-to-have layer on top of your “real” technical competence. Something you work on in a weekend workshop and then consider handled. That framing is wrong, and it is disproportionately costly for women in technical and leadership environments, where the implicit message is already that your authority must be earned through demonstrable expertise. Spending political capital on communication is sometimes dismissed as soft when a man in the same role would be praised for his stakeholder management.
Let’s retire the term entirely. The more accurate label is soft power — the capacity to navigate the messy, redundant, frequently illogical operating system known as human beings. Soft power is what allows your correct analysis to actually change something. Without it, your insight sits in a deck that no one reads, or gets nodded at in a meeting and then quietly ignored.
Soft power is not charm. It is not performance. It is a sophisticated technical skill that can be mapped, practised, and deployed strategically. The sooner you treat it that way, the faster your leverage in any organisation increases.
Reframe: Emotions Are Not Noise. They Are API Documentation.
If you think like an engineer — or you work in environments where engineering thinking dominates — there is a strong cultural bias toward treating emotions as interference. Noise that muddies the data. Inefficiencies to be managed out of the system so the rational logic can run cleanly. This framing feels rigorous. It is actually a liability.
Here is the reframe: emotional intelligence is not about being nice. It is about reading the API documentation of the person across from you.
Every person you interact with is running their own internal system — a set of priorities, threat responses, incentive structures, and communication preferences that determine how they process incoming information. When you ignore that layer and simply transmit your technically correct data, you are calling an endpoint without checking the documentation. You might get a response, but it probably won’t be the one you wanted. You might get a timeout. You might get an error code that looks like defensiveness, or passive agreement, or an arms-crossed engineering lead who has stopped engaging entirely.
Reading emotional signals — anxiety, resistance, territorial behaviour, enthusiasm — is not a distraction from the real work. It is the diagnostic layer that tells you how to transmit what you know so that it actually lands.
The Translation Failure Framework
When communication breaks down in cross-functional environments, it is almost never because someone lacks information. It is because the same correct information is being transmitted in a format the receiver is not configured to process. The product lead in that Tuesday meeting hears “total refactor” as “we’re blocking the deal.” The engineering lead hears “sales promised the client” as “we’re being asked to build something structurally unsound.” Both translations are reasonable given each person’s operating context. Neither is a full picture.
Translation failure has three predictable symptoms:
1. Silence Where There Should Be Feedback
When people do not feel heard, they stop contributing signal. A technically brilliant team member who has learned that their concerns are overridden or dismissed will stop raising concerns. This looks like compliance. It is actually information loss — and you will only discover the cost of it when something fails downstream and you realise the warning was there, quietly withheld.
2. Malicious Compliance
This is the subtle one. Malicious compliance is when someone does exactly what was asked, knowing it won’t work, and says nothing — because the environment has taught them that saying something is not worth the friction. If you have ever been on a project where everyone “agreed” in the meeting and then nothing moved, or where the deliverable came back technically complete but functionally useless, you have seen malicious compliance at work. It is the system’s response to a persistent translation failure.
3. Technical Brilliance, Functional Paralysis
The team has the skills. The individual has the expertise. But the inability to align people across different logic settings means that expertise never converts into momentum. The best engineers, strategists, and operators you have ever worked with who somehow never seemed to get traction — translation failure is frequently the culprit. Not capability. Not effort. The breakdown between knowing and transmitting.
The Strategic Cost of Ignoring the Human Layer
This is not abstract. Let’s be precise about what translation failure actually costs.
A 2023 report by Grammarly and The Harris Poll estimated that poor communication costs US businesses approximately $1.2 trillion annually — roughly $12,506 per employee per year. That figure includes time spent on miscommunication, rework, and the meetings required to undo the damage caused by unclear or misaligned exchanges. What it cannot fully quantify is the strategic cost: the missed pivots, the delayed decisions, the talent that walks out the door because they were technically right and organisationally invisible.
For women navigating technical or leadership environments specifically, the stakes are compounded. Research consistently shows that women are more frequently penalised for direct communication while simultaneously being penalised for indirect communication. The double bind is real. But here is what soft power offers as a counterweight: when you understand how to read and match the communication logic of the person you’re speaking to, you sidestep a significant portion of that bias. You are no longer fighting their processing preferences — you are working with them. That is not capitulation. That is leverage.
Practical Architecture: How to Transmit What You Know
If emotional intelligence is the API documentation, then what follows is a framework for actually using it. This is not about reading body language in a pop-psychology sense. It is about diagnosing the operating context before you transmit.
Step 1: Identify the Logic Setting
Before any high-stakes communication, identify the primary logic setting of your audience. Most people in professional environments are operating primarily from one of four positions: risk logic (what could go wrong), opportunity logic (what could go right), process logic (how do we execute this correctly), or relational logic (how does this affect the people involved). Your engineering lead is almost certainly running on risk and process logic. Your product lead is running on opportunity logic. Sending opportunity-framed arguments to a risk-logic listener is not persuasion. It is noise.
The diagnostic question is simple: What does this person stand to lose if this goes wrong? That is their primary logic setting. Lead with that.
Step 2: Translate Before You Transmit
Once you know the logic setting, reformulate your input in that language. This is not dumbing down. It is not changing your position. It is changing the format of the data packet so it can be received and processed by the specific system in front of you.
In that Tuesday meeting, the translation might look like this: to the product lead, “Here is the risk to the client relationship if we ship something that fails under load in 90 days — let’s talk about what a phased commitment looks like.” To the engineering lead, “Here is the bounded scope that protects the architecture while delivering a viable first increment.” Same underlying reality. Different format. Both people can now engage with the actual problem rather than defending their perimeter.
Step 3: Make the Friction Visible Without Making It Personal
In translation failures, the heat in the room is usually generated by people feeling unheard, not by the content of the disagreement. One of the highest-leverage moves you can make in a stalled conversation is to name the structural dynamic rather than the individual behaviour. “It sounds like we have a timing constraint from the sales commitment and an architecture constraint from the current system — those are both real, and they’re in direct tension. Let’s map that tension explicitly before we try to resolve it.” This does three things: it validates both positions, it reframes the problem as shared rather than adversarial, and it gives the room something concrete to work on together. The temperature drops. The data starts flowing again.
Step 4: Audit Your Own Transmission Failures
If your correct analysis is consistently ignored, dismissed, or attributed to someone else after the fact, the problem is almost certainly not that your analysis is wrong. The question to ask is: In whose logic setting did I deliver this, and was it the right one for the person I was trying to reach? High performers who feel invisible in their organisations are often brilliant at generating insight and weak at transmitting it across logic settings. This is a fixable problem. But only if you diagnose it correctly — and that requires treating yourself as a system that can be debugged, not a victim of an unfair environment.
The Real Competitive Advantage
In most high-functioning environments, the raw material of good ideas is not scarce. Everyone in the room has data, frameworks, and opinions. The scarcity is in the ability to move those ideas from one mind into another without signal loss — to translate across logic settings, neutralise defensive postures, and create the conditions in which the right decision can actually be made. That is the skill that determines whether your influence plateaus or compounds.
Being right is the entry requirement. Transmitting that rightness — efficiently, strategically, across the full range of human logic settings you will encounter in a career — that is the actual work. And it is learnable, measurable, and worth every investment you make in it.
The full video goes deeper into the mechanics of this framework — including how to read resistance signals in real time and how to rebuild trust in teams where translation failure has already caused damage. Watch it below, and pay attention to the reframe on emotional intelligence. It will change how you walk into your next high-stakes meeting.
→ Watch the full video on YouTube to get the complete framework for transmitting your insight where it actually matters.