Clean logic and stable features should speak for themselves. The engineer writes good code, ships on time, and expects the organization to notice. Status updates and optics feel like political theater beneath their dignity.
This is a failure of translation. The system cannot read your code. It can only read your signals.
⸻
The Bandwidth Constraint
The hierarchy does not have the bandwidth to evaluate raw output. Leaders are saturated with data. They do not have the time to inspect every commit or review every root cause analysis. They rely on proxies to determine who is effective and who is struggling.
Optics are not a substitute for work. They are the interface for it. When you refuse to build that interface, you force the system to guess your value. The system is deeply pessimistic. It will guess low.
⸻
The Incident Hero
We see this clearly during an outage. The engineer who quietly prevented the outage on Friday gets no recognition. The event never happened. The system has no signal to process.
The engineer who ships a critical bug but stays up until dawn fixing it becomes a hero. They generated massive semantic noise. They provided a visible narrative of struggle and triumph that leadership could easily parse.
The organization does not reward the absence of failure. It rewards the performance of rescue.
⸻
The Default Scapegoat
If you do not actively manage your perception, the system will assign one to you. When a project fails, the hierarchy needs a structural explanation that does not indict the hierarchy itself. It looks for the void.
The engineer who does not control their narrative is the easiest void to fill. They become the bottleneck. They become the legacy dependency. Because they provided no competing signal, the system's narrative becomes ground truth.
⸻
Controlling the Signal
Managing perception is not sycophancy. It is protocol design. You must construct the API that the rest of the organization uses to understand your work.
Refusing to manage perception does not make you principled. It makes you legible only to yourself.
Translate your output into the metrics the hierarchy consumes. If they measure velocity, format your stability work in terms of velocity preserved. If they measure cost, format your refactoring in terms of cost avoided.
The signal is the story. Everything else is noise.
End.