There is a difference between the engineer whose analysis is correct and the engineer whose recommendation is adopted. The gap between them is not technical, which is precisely why it is so frustrating.
Right, and Ignored
In a design review, authority does not come from speaking the longest. It comes from identifying the issue, listening to competing constraints, presenting evidence and remaining steady when challenged.
Both engineers did the work. One of them is in the room where the decision gets revisited.
Advisory weight is not a reward for being right often enough. It is a separate thing, built separately.
Where the Gap Appears
The move from expert to adviser is rarely taught and almost never announced. Most engineers discover it by noticing that their analysis keeps being overruled.
The engineer’s second visibility challenge is moving from technically correct contributor to trusted adviser and potential leader.
Four Principles for Advisory Weight
Four adjustments move a technical contribution from information to recommendation.
-
01
Open with the recommendation
Give the room a clear point of orientation before the technical explanation.
-
02
Show respect for other disciplines
Visible curiosity and precise questions strengthen cross-functional credibility.
-
03
Use calm disagreement
Challenge assumptions through evidence and consequence rather than irritation or superiority.
-
04
Signal ownership
State what you will verify, deliver or escalate and by when.
Certainty Is a Signal, and It Can Be Miscalibrated
Engineers are trained to express uncertainty accurately. It is a professional virtue and a safety requirement, and in a technical review it is exactly right.
In a decision meeting it reads differently. A hedged recommendation is often heard not as intellectual honesty but as an absence of conviction, and the decision moves to whoever sounded more certain — frequently someone who understands the problem considerably less well.
The answer is not false confidence. It is separating the two statements: here is what I recommend, and here is the confidence interval around it. Delivered in that order, the hedge strengthens the recommendation instead of dissolving it.
Stating the uncertainty before the recommendation hands the decision to whoever hedged less. Lead with the recommendation.
Putting It Into Practice
These are the habits that distinguish a report from an opinion worth acting on.
The Adviser Check
Before your next recommendation, ask:
- Am I leading with the recommendation, or with the caveats?
- Have I said what I would do, not only what the data shows?
- Does my manner suggest I expect this to be acted on?
- Am I overemphasising technical depth where commercial judgement is what is wanted?
“Which professional signal do you currently overemphasise, and which one needs more visible support?”
The Signal Audit
Use the five Professional Visibility Signals™ as a diagnostic rather than a set of boxes to tick.
- Rewrite one technical update for an executive audience.
- Notice whether your first answer begins with context or conclusion.
- Practise one respectful challenge statement.
- Close your next meeting with explicit ownership.
Lesson 3 makes both lessons repeatable with a wardrobe system that survives the move from site to office to client in a single day.
Your Merit Deserves to Be Seen
Closing the Visibility Gap™ does not mean becoming somebody else. It means helping people recognise more accurately who you already are.
Trusted adviser is not a title that gets conferred. It is a position that becomes available once the signals stop contradicting the substance.
Download Your Engineer Visibility Notes
A one-page summary of Lesson 2, the principles, the action checklist and the reflection prompt.
Download Visibility Notes — Lesson 2Lesson 3: The Engineer Visibility Wardrobe
One system that works on site, in the office and in front of a client, without compromising either safety or authority.