Communicating Technical Influence

Before writing a single slide or sentence, answer four questions:

1. Who is the audience, and what do THEY care about? (money, risk, time, reputation — rarely "technical elegance")
2. What decision do I need them to make? (one sentence, no ambiguity)
3. What's the cost of inaction, in THEIR currency? (money, risk, competitive position — not engineering terms)
4. What objection will they raise first, and how do I pre-empt it?

If you can't answer #2 in one sentence, you're not ready to communicate — you're still thinking.

Progress:

• Step 1: Define the audience's decision criteria (not your technical criteria)
• Step 2: Translate technical facts into business/risk language
• Step 3: Build the narrative arc (Problem → Cost of Inaction → Solution → Ask)
• Step 4: Design visuals that remove cognitive load, not add decoration
• Step 5: Pre-empt objections and build coalitions before the meeting
• Step 6: Deliver, actively listen, adjust in real time
• Step 7: Follow up in writing — unambiguous, with explicit next steps

Step 1 — Decision criteria, not technical criteria

Every stakeholder has a native language:

• Executives: money, risk, strategic positioning, competitive threat
• Investors: ROI, timeline to value, downside protection
• Customers: reliability, cost of ownership, their own deadlines
• Engineers: correctness, maintainability, technical debt

Translate your argument into theirs. If you're talking "latency" to a CFO, you've already lost. Talk "lost contracts" or "penalty clauses."

Step 2 — Translation technique

Use the "So what?" chain: keep asking "so what does that mean for [stakeholder]?" until you hit something they actually care about.

Example chain:

• Technical: "The battery management system lacks thermal redundancy."
• So what? → "Under sustained load, cells can overheat."
• So what? → "Overheating risks mid-flight failure."
• So what? → "A failed drone over a client site is a liability claim and a canceled contract."
• Stop here. This is the sentence a non-technical exec understands.

Step 3 — Narrative arc

Structure every pitch as:

1. Problem (grounded in audience's world, with cost already quantified)
2. Cost of inaction (what happens if we do nothing — be specific, use numbers/timeline)
3. Solution (what you propose, at the right altitude — no implementation detail unless asked)
4. Ask (one explicit, unambiguous action: budget, approval, decision, date)

Never end a technical presentation without a specific ask. "Something to think about" is not an ask.

Step 4 — Visuals that add, not duplicate

• One idea per slide. If a slide needs narration to be understood, it's doing its job; if it needs narration to be read, it's failing.
• Use comparisons, not raw numbers: "30% more than a cancelled contract" beats "+$240K."
• Diagrams show relationships (before/after, cause/effect, timeline), not inventories of facts.

Step 5 — Pre-empt objections, build coalitions

Before the meeting:

• List the 3 most likely objections and prepare a one-line answer to each (data, precedent, or trade-off)
• Identify who in the room has aligned interests — talk to them before the meeting, not during
• Find one ally with credibility to the audience (finance person who agrees with your numbers, ops lead who's felt the pain)

Step 6 — Deliver and listen

• Open with the ask's context in their language, not your agenda
• After presenting, stop talking. Let silence do work.
• Practice active listening: when they respond, do not formulate your rebuttal while they're speaking. Paraphrase their concern back before responding ("So the worry is cash flow in Q3, not the technical approach itself — is that right?")
• Watch for non-verbal signals (crossed arms, quick glances between stakeholders, note-passing) — these tell you who to address next

Step 7 — Written follow-up

Send a short written summary within 24 hours:

• What was agreed
• What decision/ask is still pending, and by when
• Who owns the next action

No ambiguity, no hedging language. Written communication is where "I think we agreed" becomes "we agreed."

Example 1: Budget increase despite cuts

Input: Need 30% more budget for a drone project during company-wide cuts. Standard approach (showing technical necessity) is not enough.

Output:

• Don't lead with: "We need better sensors for obstacle avoidance in GPS-denied environments."
• Lead with: "Three competitors have already won municipal contracts requiring certified obstacle-avoidance. Without this upgrade, we're excluded from $2M in bids opening this quarter — more than 6x the requested increase."
• Cost of inaction: Quantify lost pipeline, not technical risk. "We lose eligibility for Tier-1 RFPs for at least 12 months (next budget cycle)."
• Solution: "$180K gets us certification-ready hardware by Q3, in time for the city contract cycle."
• Ask: "I'm asking for budget approval today so procurement can start this week — the RFP window closes in 60 days."
• Pre-empted objection: "I know budgets are tight. This isn't new spending — it's reallocation: we recover it within one contract win, and I've identified $40K we can cut from the test-rig budget to offset it immediately."
• Coalition: Get sales/BD to confirm the pipeline number before the meeting, and have them in the room or quoted directly.

Example 2: Difficult feedback conversation

Input: An engineer repeatedly missed deadlines, affecting a client delivery.

Output:

• Private setting, not public.
• Open with observation, not judgment: "The last two milestones slipped by a week each. Walk me through what happened."
• Listen fully before responding — don't pre-load the conversation with a fix.
• Separate the person from the pattern: "This isn't about your ability — I need to understand if it's workload, unclear requirements, or something else."
• Agree on a concrete, trackable change: "Let's check in every Wednesday on the next milestone, so we catch slippage three days earlier, not three days late."
• Close by restating trust: "I'm telling you this because I want you succeeding on the next project, not just flagging a problem."