What does "flying on instruments" mean for a manager?

It's a discipline borrowed from aviation. When pilots lose sight of the horizon, their inner ear lies to them, so they're trained to trust a cross-checked panel of instruments over what their body feels. For a remote manager, flying on instruments means basing decisions on real signals — shipped work, explicit status, outcomes, direct conversations — instead of the gut read of "how the team feels," which was calibrated to office cues that no longer exist.

Isn't trusting your gut a sign of good leadership?

In the right environment, yes. Kahneman and Klein showed intuition is reliable when the setting is predictable and you've had fast, clear feedback to learn from — like an in-office manager reading body language for years. Remote work removes both conditions: the visual cues vanish and feedback loops break down. So the same instinct that served you in person becomes overconfidence remotely. The fix isn't to abandon judgment; it's to back it with instruments.

What counts as an "instrument" on a remote team?

Anything that measures real altitude rather than motion: the actual work produced, written status updates, a consistent 1:1 cadence, and progress against a clear goal. What doesn't count: green status dots, response speed, hours logged, and your sense of someone's tone on a call. If a metric tracks busyness instead of outcomes, it's a broken gauge that will fly you into the ground.

How is this different from surveillance or micromanaging?

Surveillance measures the person — keystrokes, active hours, mouse movement — and it's exactly the broken instrument to avoid, because it reads motion as progress and warps behavior. Flying on instruments measures the work and outcomes, not the human. An altimeter doesn't care how hard the pilot is gripping the yoke; it reports altitude. Good instruments make you trust your team more, not watch them more.

Flying on Instruments: Managing a Team You Can't See

Q: Why does remote work break intuition specifically?

Because intuition is pattern-matching against cues, and most of a manager's cues were visual and ambient — who's in early, who looks stressed, hallway chatter. Surveys show 96% of executives notice in-office contributions more than remote ones, which means the cue stream collapses when people work from home. With the cues gone and feedback loops weaker, your gut keeps generating confident readings from data that's no longer there.

In 1954, the University of Illinois ran a quiet experiment that should be required reading for every remote manager. They took 20 pilots who were not trained to fly by instruments, put them in simulated cloud where they lost sight of the horizon, and timed how long they lasted on instinct alone. Nineteen of the 20 spiraled out of control. The average time from "I've got this" to total loss of control was 178 seconds.

Managing a team you can't see is the same flight. You spent years learning to read a room — the slumped shoulders, the side conversation, the energy when someone walks out of a meeting. Then everyone went home, the horizon disappeared, and your instincts kept flying as if it were still there. Flying on instruments is the discipline pilots learn to survive exactly this moment, and it's the single skill that separates calm remote managers from the ones quietly spiraling. Here's how the disorientation works, why your gut is the problem, and how to fly your team on instruments instead.

The 178 seconds when your instincts turn lethal

The terrifying part of spatial disorientation isn't that pilots get confused. It's that they feel completely certain while they're wrong.

Your sense of balance lives in the fluid of your inner ear, and it has a hard limit. The semicircular canals only register angular accelerations above roughly 2°/sec² — "angular accelerations below this value cannot be detected," as the research puts it. Bank the plane gently enough and your body feels nothing. The wing drops, the turn tightens into what pilots call a graveyard spiral, and the whole time your gut is reporting, with total confidence, that you're flying straight and level. You're not nervous. You're sure. That's the killer.

The most famous example is John F. Kennedy Jr., who was not instrument-rated and flew into night haze over water in 1999. The NTSB's probable cause was blunt: "the pilot's failure to maintain control of the airplane during a descent over water at night, which was a result of spatial disorientation." He almost certainly believed he was level until the moment he wasn't.

Now translate that to a manager who "has a great feel for the team." The feeling of certainty about a remote report — they're fine, they're checked out, they're not pulling their weight — arrives with the exact same conviction as the pilot's. And it's calibrated to a horizon that's no longer there. Spatial disorientation doesn't feel like doubt. It feels like instinct. So does proximity bias, and so does the manager who's quietly written off a teammate they haven't actually talked to in three weeks.

Your instincts didn't break — your cockpit did

Here's the steelman, because trusting your gut is genuinely good advice in the right cockpit.

Intuition is real expertise, not a parlor trick. Daniel Kahneman, the skeptic of human judgment, and Gary Klein, the champion of expert intuition, spent years arguing and then co-authored the truce. Their 2009 paper, "Conditions for Intuitive Expertise," landed on two conditions that have to both be true before you can trust a gut feeling: the environment has to be regular enough that valid cues exist, and you have to have learned those cues through prolonged practice with rapid, unambiguous feedback. Chess masters have both. So do firefighters and ER nurses. When both hold, intuition is just fast pattern-matching, and it's superb.

When either condition fails, the same feeling becomes overconfidence wearing a confident face. And remote work breaks both conditions at once.

Condition one — valid cues — collapses the moment your team leaves the office. The Envoy At Work Survey found that 96% of executives admit they notice in-office contributions more than remote ones. That's not a character flaw; it's a confession about cues. Your management instinct was trained on a rich visual stream — who's in early, who looks fried, who's huddled with whom — and almost all of it vanishes on a remote team. You're flying in cloud.

Condition two — fast, clear feedback — collapses too. A November 2025 survey of 1,000 remote and hybrid workers by Founder Reports found that only 40% say they get clear feedback, and just 51% feel their manager communicates clearly. Without a tight feedback loop, you never find out which of your gut calls were right, so you can't recalibrate. You just accumulate confidence. Kahneman and Klein would call that the recipe for building intuition that's confidently wrong.

So the instincts that made you a great in-office manager aren't malfunctioning. Your cockpit changed, and nobody handed you an instrument rating. That's the whole problem with managing a remote team you can't see: you're trying to fly visually in conditions that demand instruments.

How to fly on instruments when you can't see your team

Pilots don't beat disorientation with more willpower or a better gut. They beat it with a trained procedure: ignore what your body is screaming and believe a cross-checked panel of gauges. Here's how to translate that into remote management.

Take inventory of your instruments

A pilot in cloud knows exactly which six instruments keep them alive. Most remote managers can't name theirs. Before you can fly on instruments, you have to know what they are: the work itself (shipped code, published docs, closed tickets), explicit written status, a real 1:1 cadence, and outcomes against a goal. Those are your altimeter and your attitude indicator.

Note what is not an instrument: green dots, response latency, hours "online," and your sense of someone's vibe on a call. Those are the equivalent of staring out a black windshield and guessing. If a number measures motion instead of altitude, it isn't an instrument — it's the disorientation talking. Activity surveillance is the broken gauge here, the one that feeds productivity paranoia instead of curing it.

Run a scan — never fixate on one gauge

The deadliest instrument mistake isn't ignoring the panel. It's fixating on a single gauge while the others tell the real story. Pilots are drilled to scan — eyes moving across the whole panel — precisely because any one instrument can fail.

This is where data-driven decisions for remote managers go wrong. You pick one metric — story points, lines of code, hours logged — and you fly it into the ground while the rest of the picture screams. Trusting one dashboard blindly isn't the opposite of trusting your gut; it's the same error with a spreadsheet. The discipline is the cross-check: does the shipped work agree with the written status, which agrees with what the person says in the 1:1, which agrees with the outcome? When the gauges disagree, you've found something worth a conversation — not a verdict to issue.

Treat certainty as a warning light

Here's the counterintuitive move, and the most important one. On a remote team, the feeling of certainty about a person you haven't actually talked to should trigger alarm, not action.

When the pilot feels most sure they're level, they're often deepest in the spiral. When you feel most sure a quiet teammate is "checked out" or a chatty one is "crushing it," ask what instrument you're reading. If the honest answer is "a hunch from a Slack tone and a slow reply," that's the leans. Go get a fix: a direct, low-stakes conversation. Half the time you'll find the quiet person shipped the best work of the quarter and the loud one is stuck. Certainty without a gauge behind it is a symptom, not a signal — the same way a setback can hijack judgment right when you feel most decisive.

Rebuild the feedback loop

If only 40% of remote workers get clear feedback, your second flight instrument is dark for most of your team. Fixing that is straight out of Kahneman and Klein: intuition can only stay calibrated with rapid, unambiguous feedback, so you have to manufacture the loop the office used to give you for free.

That means feedback that is fast (days, not the quarterly review), specific (tied to a piece of work, not a personality), and two-way. It's also why crisp confirmation rituals matter remotely — the same logic behind the readback rule, where you close the loop out loud instead of assuming the message landed. Every tightened feedback loop is one more working instrument on your panel. Skip it and you're not just flying blind — you're flying blind and never learning you were.

Instrument the room instead of reading it

The deepest fix is to stop trying to "read the room" remotely and start instrumenting it. The reason ad-hoc remote management feels like guesswork is that the signal is scattered across ten tools: the work is in one place, the conversation in another, the context in a third, and none of them are watching for the teammate who's gone quiet.

Closing that gap is the whole bet behind Coommit — pull the work, the live conversation, and a shared canvas into one room, with contextual AI that flags who's stuck or silent so the signal reaches you before the spiral does. That's an instrument panel for a team you can't see: it surfaces altitude and heading instead of leaving you to feel for them. And it measures the work, not the worker — the difference between an honest altimeter and the observation effect that warps behavior the second people feel surveilled.

The horizon isn't coming back

The hardest thing to accept is that remote work isn't a foggy version of the office that will clear up. It's permanent instrument conditions. The horizon you learned to fly by — the hallway, the body language, the read of the room — is gone for good, and no amount of "getting back to in-person energy" brings it back for a distributed team.

That sounds grim until you remember what instrument-rated pilots actually do: they fly through cloud, at night, over water, perfectly safely, every single day. Not because their instincts are better than yours, but because they trained themselves to trust the panel over the feeling. Flying on instruments isn't colder management or more surveillance. It's the opposite of guessing. Name your instruments, scan them instead of fixating, treat certainty as a warning light, rebuild the feedback loop, and put the work where you can actually see it. Do that, and you stop white-knuckling a team you can't see — and start flying it.