Persuasion & Influence Without Authority.
The Day I Had No Authority… But Everything Was on the Line
A few years ago, we had a major degradation on a regional fiber backbone. Packet loss was rising. Latency spikes were affecting enterprise customers. Complaints were pouring in.
I was not the decision-maker. Not the regional head. Not the vendor lead. Not even the escalation owner.
But I was the one who saw what others were missing.
The issue wasn’t just congestion—it was a misconfigured protection path that kept flapping. Fixing it meant:
- Getting transmission engineers to admit a config issue
- Convincing IP engineers to reroute traffic temporarily
- Getting leadership to approve a “risky” change during peak hours
- And aligning with vendors who insisted “everything was fine”
I had zero authority over any of these people.
Yet within 3 hours, the change was approved and implemented.
Not because I had power… but because I knew how to influence.
Why Influence Matters More Than Authority in Telecom
Telecom is one of the most complex environments you can work in:
- Multiple vendors (Huawei, Ericsson, Nokia… each with their own biases)
- Cross-functional teams (Core, RAN, Transmission, IP)
- Regulatory oversight (strict compliance requirements)
- High-stakes SLAs (downtime = revenue loss + reputation damage)
In this environment, authority is often fragmented.
Even if you’re a manager:
- You don’t control vendors
- You don’t control regulators
- You don’t control other departments
So how do things actually get done?
👉 Through persuasion and influence.
The Biggest Myth About Influence
Most people think influence is about:
- Talking more
- Being confident
- “Selling” ideas aggressively
That’s wrong.
Influence is not about talking louder. It’s about making others feel the idea is theirs.
Scenario 1: Convincing Senior Leadership Without Sounding “Junior”
Let’s say you’re a back-office engineer and you discover a design flaw that could cause future outages.
You escalate it.
Leadership responds:
“We’ll review it later.”
Translation: It’s not a priority.
What Most People Do (and fail)
- Send long technical emails
- Use complex jargon
- Repeat the same point multiple times
Result? Ignored.
What Works Instead
Reframe the conversation in business language:
Instead of:
“There’s a routing inefficiency in the MPLS core.”
Say:
“If we don’t fix this, we risk a 20–30% increase in enterprise downtime during peak hours. That could impact our top-paying customers.”
Now you’ve shifted from: 🔧 Technical problem → 💰 Business risk
Key Lesson
Senior leaders don’t buy technical accuracy. They buy impact.
Scenario 2: Influencing Cross-Functional Teams Who Don’t Report to You
You need the RAN team to optimize a parameter affecting handover failures.
But they’re busy. And honestly? They don’t care about your KPI.
The Wrong Approach
“Please adjust this parameter urgently.”
Ignored.
The Right Approach
Step into their world:
“We noticed handover failures increasing in your cluster. If we fix this parameter, it could improve user experience and reduce complaints coming to your team.”
Now you’ve:
- Aligned with their goals
- Reduced their perceived workload
- Made them look good
Key Lesson
People don’t resist your idea. They resist what it costs them.
Scenario 3: Dealing with Vendors Who Push Back
Every telecom engineer knows this situation:
Vendor says:
“The issue is not from our side.”
You know it is.
But you can’t force them.
What Most Engineers Do
- Argue
- Escalate emotionally
- Send logs aggressively
This creates resistance.
What High-Influence Engineers Do
They guide the vendor to discover the problem themselves:
“We noticed that when traffic shifts to Node B, the error starts. Could we jointly validate that scenario?”
Now:
- You’re collaborative, not confrontational
- The vendor saves face
- The solution becomes mutual
Key Lesson
Influence works best when ego is protected.
The 5 Core Principles of Influence Without Authority
1. Speak the Language of Your Audience
- Engineers → data, logs, evidence
- Managers → KPIs, risk, revenue
- Regulators → compliance, standards
If you speak the wrong language, you lose before you start.
2. Frame the Problem as a Shared Goal
Instead of:
Recommended by LinkedIn
“My issue”
Say:
“Our network performance” “Our customer experience”
Subtle shift. Massive impact.
3. Reduce Friction
People ask themselves:
“How much effort will this take me?”
Make it easy:
- Provide ready analysis
- Suggest clear actions
- Remove ambiguity
4. Build Credibility Before You Need It
Influence doesn’t start during a crisis.
It starts with:
- Consistent delivery
- Clear communication
- Reliability over time
When people trust you, they listen faster.
5. Use Timing as a Strategy
Even the best idea fails at the wrong time.
- Don’t push major changes during outages
- Don’t challenge leadership in public forums
- Pick moments when attention is high
A Real Telecom Case Study: Saving a Network Upgrade
During a nationwide upgrade, a junior engineer noticed something dangerous:
The new configuration could overload aggregation routers during peak traffic.
He raised it.
Silence.
Why?
Because:
- The project was already approved
- Millions had been invested
- No one wanted delays
What He Did Differently
Instead of pushing harder, he changed strategy:
- Simulated the failure scenario
- Presented a simple visual showing impact
- Linked it to potential SLA penalties
- Suggested a phased rollout instead of a full stop
Result?
Leadership approved a revised rollout.
A potential nationwide outage was avoided.
Key Takeaway
Influence is not about being right. It’s about making it easy for others to agree with you.
How to Build Influence as a Skill (Even If You’re Quiet)
Let’s be clear:
You don’t need to be loud. You don’t need to be extroverted.
You need to be intentional.
1. Learn Business Thinking
Start asking:
- How does this affect revenue?
- What’s the customer impact?
- What’s the regulatory risk?
This changes how you present ideas.
2. Practice Structured Communication
Use this format:
- Problem
- Impact
- Evidence
- Recommendation
Simple. Powerful.
3. Observe Power Dynamics
In every meeting, ask:
- Who influences decisions?
- Who resists change?
- Who aligns with whom?
Influence is not random. It’s strategic.
4. Develop Emotional Intelligence
Read the room:
- Are people defensive?
- Are they rushed?
- Are they open?
Adjust accordingly.
5. Build Relationships Before You Need Them
That RAN engineer you greeted last week?
That small connection might save you during a crisis.
The Hidden Advantage of Engineers Who Master Influence
When you combine:
🔧 Technical depth + 🧠 Influence skills
You become:
- The person leadership trusts
- The one teams listen to
- The bridge between silos
That’s how careers accelerate.
Final Thought
In telecom, networks don’t fail because people lack knowledge.
They fail because:
- Teams don’t align
- Decisions are delayed
- People don’t listen to each other
Influence fixes what authority cannot.
So the next time you think:
“I don’t have the power to change this…”
Remember:
👉 You don’t need power. 👉 You need perspective, timing, and strategy.
If you’ve ever had to convince someone without authority, drop your experience below 👇 Let’s learn from each other.
#TelecomEngineering #Leadership #Influence #Persuasion #CareerGrowth #EngineeringLeadership #SoftSkills #TechCareers #NetworkEngineering #PersonalDevelopment #WorkplaceSkills #DigitalTransformation #TelecomLife #GrowthMindset