Hello Reader,

There's a particular kind of engineer who never misses a deadline. They deliver exactly what was asked, exactly when promised. They are consistent, dependable and reliable to a fault and somehow, zero influence on anything that matters.

This isn't a competence problem. It's a range problem.

When people can predict you perfectly, they stop paying attention to you.

You become essential and invisible at the same time. You're in the room but not in the conversation, executing but not deciding. People appreciate you quietly, without consulting you on anything that isn't already in your lane.

You built your reputation by being predictable. Now your predictability is your ceiling.

Reliability and range are different things

Reliability is about what you deliver. Range is about what people suspect you're capable of.

The most influential engineers I've studied aren't the most consistent people in the room. They're the ones who occasionally show up in ways that make people stop and recalibrate. They ask a question nobody was expecting. They push back on a direction in a meeting where they were only supposed to be a technical resource. They send the email that reframes the problem before the project starts.

Influence lives in the gap between what people expected from you and what you actually gave them. Every time you close that gap, you reset what people believe you're capable of. And what people believe you're capable of determines what they invite you into, and how much weight they give your words.

Reliability builds trust. Range builds anticipation. Most engineers have over-indexed on one.

Three ways predictability is costing you right now

The damage is rarely dramatic but It accumulates quietly.

The scope ceiling. When you're known for doing one thing reliably, that one thing becomes your indefinite assignment. New projects get scoped to your established pattern. New problems get routed to other people. You've given no data point that suggests otherwise.

The timing problem. Decision-makers consult people whose reactions they can't fully predict. When you're fully mapped, you get brought in after decisions are made, not before. You're told what was decided. You don't shape it.

The identity collapse. The longer you perform only your predictable role, the more that role becomes your identity in the organization. You stop being a person with judgment and become a function with a headcount. Functions get allocated. People get consulted.

The strategic surprise

Erratic isn't the goal. Deliberate pattern interrupts are.

Walk into a conversation you weren't expected in, because you have something genuine to add. Take a position in a meeting that surprises people, backed by reasoning they couldn't have anticipated. Ask the question that reframes the problem before the group commits to a flawed solution. Write the document nobody asked for that makes the argument nobody was making.

Each of these is a data point. Data points accumulate into reputation. The goal is to leave people with the sense that there's more here than they've mapped.

Because the moment they've fully mapped you, your ceiling is already set.

The question worth sitting with

Think about the most influential engineer you know. Not the most technically brilliant. The most influential. The one whose opinion actually moves decisions.

They're reliable, yes. People trust them. But they also carry enough surprise that when they speak, people lean in. That uncertainty isn't a weakness. It's what keeps their ceiling open.

Influence is built on what people suspect you're capable of, not on what they already know.

What have you done recently that required people to update what they thought you were capable of?

If the answer is nothing, that's where to start.

That's all for this week