Picture this. You're the founder of a 30-person startup. You believe in "radical transparency." Every Wednesday at 4 p.m., you host an all-hands. This Wednesday, you calmly share that the board has flagged concerns about the runway model and is reviewing whether the next milestone is achievable.
You phrase it carefully. You take questions. The engineers nod. The marketers ask intelligent questions about strategy. Everyone says they appreciate the transparency. You go home feeling like you've done the job.
For the next nine days, your engineering team ships absolutely nothing substantive.
They check TechCrunch more than they check the codebase. Two senior engineers quietly update their LinkedIn profiles. The lead designer asks her partner if maybe they should hold off on the kitchen renovation. Nobody mentions the all-hands. Nobody says they're worried.
You thought you did the responsible thing. You did the exact opposite.
The Cognitive Light Cone
There is a term from developmental biology that explains this perfectly. A Tufts biologist named Michael Levin talks about the cognitive light cone — the spatiotemporal size of the biggest goal an entity is capable of pursuing. Not the things it can physically touch, but the goals it can hold in its mind.
A single cell has a tiny cognitive light cone: its goals operate over micrometers and minutes. A dog's is bigger: the perimeter of its yard, the food bowl, yesterday's walk. A human's is enormous. In fact, Levin notes that humans might be the only species capable of holding goals that are structurally impossible for us to attain. World peace. What happens when the sun burns out. The welfare of strangers a continent away.
Levin flags this as more than just a biological curiosity. It produces a unique, crushing psychological pressure: the experience of holding a goal you cannot reach.
This is exactly what happens when you give your IC engineer the runway update.
The board's runway model is well within a founder's cognitive light cone. The founder can pursue it as a goal, act on it, and pull levers to fix it. But when you hand that same trajectory to an engineer, it becomes a goal she is forced to hold in her head without any levers to influence it. She's been handed a goal that is the wrong size for her position. The light cone expands, but her action range does not.
You didn't transfer agency. You transferred unresolvable anxiety.
Why "Awareness" Isn't Free
In 1908, psychologists Yerkes and Dodson mapped out a concept that sits in every undergrad psych textbook: performance on cognitive tasks is an inverted U-curve based on arousal. Too little arousal? You're bored, slow, and sloppy. Too much? You're anxious, frantic, and sloppy. Peak performance lives in the middle.
When you hand someone a goal they can act on, you raise arousal in a productive way. They point at the thing. They do the thing. Arousal drops. Performance holds.
But when you hand them a goal they can hold but cannot reach, you spike their arousal with nowhere to put it. They ruminate. They doomscroll Slack. They write overly long emails. They make trivial decisions worse. And because the goal is fundamentally unresolvable from their position on the org chart, the arousal never decays.
Fifty years ago, cognitive scientist Herb Simon said it cleanly: A wealth of information creates a poverty of attention. Telling your team things they cannot act upon costs them the attention they desperately need to do the things they can.
The EM as a Filter, Not a Conduit
Over twenty years of working at startups, I have come to the view that the single most vital job of an Engineering Manager is to be a filter.
Most companies run on the conduit model. Information enters the top, the EM relays it downward in the name of "alignment" or "transparency," and the team is left to metabolize the stress.
The filter model operates differently. Information hits the EM. The EM holds it. The EM decides what is strictly actionable, translates it, and eats the rest.
The Conduit says: "The board is reviewing our runway."
The Filter says: "Our absolute top priorities this sprint are these two specific epics."
The Conduit says: "The CEO is terrified about Q3 churn."
The Filter says: "We are heavily prioritizing the onboarding flow this month."
This is not lying to your team. It is load-balancing.
Spotting the Difference
You can always spot a conduit manager's team the week after major company news. They are distracted. Velocity plummets. Résumés get polished. A few ambitious ICs try to "help" by getting involved in strategic decisions wildly above their pay grade—which is the most expensive form of distraction, because it forces senior leadership to manage the help.
A filter manager's team is heads-down. When the dust settles, they are surprised to learn what was happening behind the scenes. Some might initially feel betrayed. Most, upon reflection, understand exactly why they were shielded.
Can the filter model be abused? Yes. Bad managers use it to hoard power, hide toxic behavior, or protect a fiefdom. But the right response to those failure modes isn't to abandon filtering for reckless disclosure. The response is to be a leader who filters with such high integrity that your team trusts your shield, even when they don't know what it's blocking.
The Executive Playbook
If you are an EM or an engineering leader, here is what filtering looks like in practice:
Default to absorbing, not forwarding: When you receive executive information, the first question isn't "who needs to hear this?" It's "is there anything in this my team can actually influence?"
Translate, don't quote: Convert anxiety-inducing inputs into action-shaped outputs.
Triage by action range: If they can act on it, share it. If they can't, you reroute it to the limited group who can or you carry it.
Resist the transparency flex: "Radical candor" means giving honest feedback. It does not mean telling everyone everything.
Schedule the bad news: When bad news must be shared, batch it and deliver it with the action items already mapped out. Surprise, drip-fed anxiety is the absolute worst kind.
Be honest about scope: You aren't lying when you say, "This is not something your role can act on, and I am not going to make you carry it."
The Truth
This job is incredibly hard. You will carry weight your team never sees. You will absorb worry that has no outlet. You will occasionally be accused of being closed-off when you are actively bleeding to protect them.
Some of your team will resent the filter. Others will figure it out and thank you years later. Both will happen, because that is the job.