This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

Over the last three episodes, we’ve been dealing with relationships and information. The upward signal to your boss, lateral influence with your peers, teammates, coworkers, conflict as information. All of those models assume someone can see the work you’re doing. This episode is about what happens when they can’t. You can have every mechanic in place and still be invisible to the people who matter. Not because you’re bad at politics, because you never designed a signal path between your work and the people who make decisions about you. The core problem isn’t that engineers don’t do visible work. It’s that they don’t design how information about their work reaches the people who make the decisions about their career.

they leave the signal path to chance, and every unmanaged relay point degrades or misattributes the signal.

We’re going to walk through a signal path audit. three inputs. First, map the decision surface. Who makes decisions about your work, your career, your opportunities? Not just your direct boss, anyone who influences project assignments, resource allocation, recognition, advancement.

Most engineers can name their boss.

They can’t name the other three or four people whose perception of them actually matters. Second, trace the signal path. For each person on that decision surface, ask, how does information about my work currently reach them? Directly? Through my manager’s summary? Through someone else’s summary of my manager’s summary?

through nothing at all, every relay point is a compression layer. Your manager summarizes your work for their update. Their boss summarizes that summary. By the time it reaches someone with real leverage, your specific contribution is either invisible or attributed to the relay.

Third, close the gap. Where the signal path is too long or too lossy, you need a shorter path. This is not a political maneuver, It’s a design decision. That might mean a monthly update to a skip level. It might mean presenting your own work in a meeting instead of having your manager present it.

It might mean being the one who writes the project summary instead of letting someone else narrate your contribution.

Here’s the part that engineers miss often. Closing the gap isn’t going around your manager. It’s taking a load off of them. When you present your own work, that’s one less thing they have to summarize. Frame it that way and it stops feeling like an end around. It becomes useful for both of you. The principle is this.

If you don’t author the signal, someone else will and they’ll compress it.

I got caught in exactly this situation. There was a point in my career where I resigned. When I came back, my new manager was someone I had previously mentored. He was now my boss. As we got back into the swing of things, the president of the company started attributing all of the work coming out of our office, either to my manager directly, or if he was feeling generous, splitting credit between the two of us.

My manager, to his credit, pushed back. He did not claim responsibility for anything he did not do. He was a straight shooter in that regard. But the situation didn’t fully correct. The president’s mental model was already set and the signal path was running through the manager, whether anyone designed it that way or not.

The buffer between me and the decision surface wasn’t malicious. It was architectural. My manager wasn’t stealing credit. The president wasn’t being unfair on purpose. The signal path just ran through a relay and the relay compressed my contribution into a shared output.

Even when the relay tried to correct it, the damage was structural, not personal. Now, I felt that buffer and I chose not to push through it. I didn’t want to go around my manager. I didn’t want it to look like an end around or backstabbing, especially given the tension that existed from when I had resigned. So I chose not to self promote and instead, I became frustrated that I wasn’t being recognized. What I didn’t realize at the time is there’s a real difference between self-promotion and signal design. Self-promotion says, hey, look at me. Signal design says, here’s the information you need to make a good decision. Engineers can hear that distinction immediately.

Self-promotion is about you. Signal design is about giving decision makers the information they need to do their job. Engineers resist that first instinct and they should, but they skip the second one too because they consider them the same thing. They’re not. Splitting those two apart is the move.

So what do you do with this now? Pick one person on your decision surface who doesn’t currently receive direct signal from you. Ask what information would they need to make a better decision about my work? Then find one way to get it to them this week. Not a pitch. Not a brag. Just information routed directly.

Now, stepping back for a moment. These last four episodes have been about designing your external operating system. The upward signal, the lateral signal, reading conflict as information, and now visibility. Visibility is the output of that system. If you’ve built the mechanics, but the organization still can’t see what you’re carrying,

The system isn’t complete. This is the last piece. And if you’ve been following from the beginning, you’ve built more than you probably realize. An internal operating system across the earlier episodes, and now an external one across these last four. That’s a real shift. Not a personality change, not a reinvention. A system built by an engineer for how you operate in leadership. Now, go out and use it.