What does "dead reckoning" mean for a distributed team?

Dead reckoning is a navigation method: you estimate your current position from your last known fix plus your speed, heading, and elapsed time, with no external reference. For a distributed team, your last sync is the fix and everything since is an estimate—you're inferring where work stands from your teammates' last update plus assumptions. Like real dead reckoning, the estimate drifts and the error compounds the longer you go without checking against reality.

Why do distributed teams drift off course between meetings?

Because co-located teams get constant, free "fixes"—overheard conversations, visible whiteboards, body language—and remote teams don't. Between syncs, everyone extrapolates from stale information, and small misalignments accumulate instead of self-correcting. Atlassian found 50% of knowledge workers only later discovered another team was duplicating their work, a classic case of two estimates drifting apart unseen. Staying aligned between meetings is therefore less about meeting more often and more about keeping a shared, current picture of the work.

How often should a remote team sync to stay aligned?

There's no universal number—it depends on how fast the work is moving and how much ambient visibility you already have. The better framing is to shorten the legs between fixes only as much as you must, and instead widen your instruments: keep real state visible in a shared artifact so people don't need a meeting to take a fix. Sync frequency matters less than fix quality.

Can async status updates replace status meetings?

Often, yes—if the update reflects real, observable state rather than a typed-from-memory guess. The failure mode of both async and live status update meetings is the same: people rebroadcast their own estimates. An async update tied to the actual work (the build, the board, the document) is a genuine fix; a status meeting where everyone recites "still on it" is just dead reckoning out loud.

How do you detect alignment drift early?

Stop relying on the next meeting to surface it. Make position continuously visible through a living source of truth, and end every sync by explicitly comparing where the work is against where you assumed it would be. The bigger the gap between those two, the faster you're drifting—and the shorter your next leg should be before you take another fix.

Dead Reckoning for Distributed Teams

Only 46% of U.S. employees clearly know what's expected of them at work—down from 56% in early 2020, according to Gallup. More than half your colleagues are, on any given Tuesday, partly guessing at the job. Welcome to dead reckoning for distributed teams.

Sailors coined the term for navigating without a reliable position. You start from your last known location—a fix—then estimate where you are now from your heading, your speed, and the time elapsed. It works. It also drifts. Each small error in the estimate carries forward and compounds, so the longer you sail without a fresh fix, the further your guess sits from the truth.

A remote team works the same way. Your last standup was a fix. Everything your teammates have done since is an estimate you're carrying in your head—and, like every navigator eventually learns, that estimate is wrong in a direction you can't see until you run aground.

My argument is simple: most distributed teams are over-meeting and under-fixing, and real remote team alignment comes from better fixes, not more meetings. Below is why the drift stays invisible, why piling on status meetings makes it worse, and what taking a real fix actually looks like.

What Dead Reckoning Is—and Why It Always Drifts

Dead reckoning is "the process of calculating the current position of a moving object by using a previously determined position, or fix, and incorporating estimates of speed, heading…and elapsed time," per Wikipedia. You don't measure where you are. You compute it from where you last knew you were, plus how fast and which way you think you've been moving.

The fatal property is in the math. Because "each estimate of position is relative to the previous one, errors are cumulative," as Geotab puts it. A half-degree off here, a slightly overestimated speed there—none of it self-corrects. It accrues. Wikipedia is blunt about the consequence: errors "compound themselves over greater distances, making dead reckoning a difficult method of navigation for longer journeys."

There is exactly one cure, and navigators have known it for centuries: take a new fix. The accuracy of dead reckoning "can be increased significantly by using…more reliable methods to get a new fix part way through the journey." A fix is ground truth—a position from an external reference, not your own running estimate. It doesn't reduce your drift. It resets it to zero.

Hold onto that distinction. A guess refined is still a guess. A fix is a fact. Distributed teams blur the two constantly, and that blur is where the trouble starts.

Your Last Sync Was a Fix. The Rest Is an Estimate.

When your team is in a room together, you get continuous fixes for free. You see the half-finished whiteboard, overhear the side conversation, catch the wince when someone mentions the deadline. Co-located work is dense with external reference points.

Remote work strips them out. Between syncs, you reconstruct everyone else's position from their last update plus your assumptions about their speed and heading. You're dead reckoning, and so is everyone else—about you.

The scramble shows up in the data. Microsoft's Breaking Down the Infinite Workday found that "57% of meetings are ad hoc calls without a calendar invite," and that workers "are interrupted every 2 minutes by a meeting, email, or notification." That 57% is the sound of a whole company grabbing for a fix it can't get any other way—pinging, hopping on a "quick call," reading tea leaves in a Slack thread. Meanwhile, Atlassian's State of Teams reports that 56% of knowledge workers say teams "plan and track work in different ways, which makes it hard to collaborate." Your instruments don't even agree on the units.

Nobody here is lying or slacking. They're estimating, in good faith, from the last fix they had. That's exactly why the problem is so hard to spot.

Why Alignment Drift Stays Invisible

Dead reckoning feels precise. You have a number, a dot on the chart, a confident answer when the manager asks for status. But precision isn't accuracy. The whole danger of the method is that your estimate looks just as crisp whether it's right or badly wrong—there's no flashing light when you've drifted.

So the alignment drift accumulates silently and surfaces late, as a collision—and because no dashboard flashes red, project drift looks identical to steady progress right up until the deadline slips. Atlassian found that 50% of knowledge workers "have worked on a project and only later found out that another team was working on the same thing"—two boats on the same heading, neither aware of the other, until they meet. Asana's Anatomy of Work Index puts the slippage in stark terms: 88% of knowledge workers "agree that time-sensitive projects and large initiatives have fallen behind or through the cracks." These aren't failures of effort. They're failures of position-keeping.

This is also where distributed teams differ from the systems they're often compared to. A distributed database tolerates stale reads because it reconciles automatically—every node eventually converges on the same state without anyone intervening. A team has no background reconciler. When two people's mental maps diverge, nothing quietly syncs them in the night. The gap just persists and widens until a human notices, usually in a meeting, usually too late. No wonder Asana found people spend 60% of their time on "work about work"—much of it the manual labor of chasing fixes that should have been ambient.

More Status Meetings Are Not More Fixes

Here's the trap, and it's the reason I'm writing an argument rather than a checklist. The instinct, when a team drifts, is to add meetings. A daily standup. A Wednesday sync. A Friday wrap. Surely more frequent contact means more frequent fixes?

Not if the meeting is everyone reading their own logbook aloud. "Still working on the API, should be done Thursday" is not a fix—it's a restatement of your estimate, now laundered through a calendar invite and dignified as a status update. You haven't touched external ground truth. You've just spoken your dead reckoning out loud, and your teammates have written it into their dead reckoning. Errors don't cancel that way; they accumulate.

The bill for this comes due in hours and timezones. Microsoft reports meetings after 8 p.m. are up 16% year over year, and 30% now span multiple time zones—up 8 points since 2021. Stacking more synchronous status update meetings onto a distributed team mostly buys you worse hours and more context-switching cost, not better position. Engineers have complained about exactly this on forums like Hacker News for years: the daily status ritual interrupts the deep work it's meant to protect, and tells most listeners things they don't need to know.

A real fix is cheap and external. It's the working build, not the promise of one. It's the actual document, not a summary of it. The question to ask of any recurring meeting is brutal but clarifying: does this produce ground truth, or just rebroadcast our guesses?

Dead Reckoning for Distributed Teams, in Practice

If you can't be co-located—and most of us can't—you have two honest options: shorten the legs, or widen your instruments so position stays visible between fixes. The best teams do a bit of both. Three principles, in order of leverage:

Make the artifact the fix, not the meeting. Position should live in a shared, living source of truth that reflects real state—the actual board, the actual canvas, the actual build—rather than a status someone types from memory the night before. When the work itself is visible, a fix is something you glance at, not something you schedule. This is the heart of good asynchronous communication for distributed teams: the artifact does the position-keeping.
Reserve sync time for what only sync can do. A live meeting is expensive and precious; spend it on judgment, conflict, and direction—not on reading numbers anyone could have read async. If your status update meetings are pure information transfer, they're a bad use of your most expensive instrument. Decide deliberately what stays sync and what goes async.
End every sync with an actual fix. Before anyone drops, capture where the work truly is versus where you all thought it would be, and write it down where the next leg can start from it. A fix you don't record is a fix you'll have to retake. This is how you keep action items from falling through the cracks—and how you keep the team pointed at a shared destination even when, as commander's intent teaches, you can't check in on every turn.

This is the gap Coommit is built to close. Instead of waiting for the next call to discover you've drifted, a shared interactive canvas plus contextual AI keep the team's real position visible between syncs—and when you do meet, the canvas and AI capture where things actually stand, so the next leg starts from a fix instead of a fresh round of guessing.

Navigate by Fixes, Not Guesses

Every distributed team is doing dead reckoning whether it admits it or not. The only question is how long your legs are between fixes, and how honestly you take them. Drift isn't a character flaw on your team—it's the default physics of navigating without external reference, and it compounds quietly until it doesn't.

The teams that stay on course in the next few years won't be the ones with the most status meetings. They'll be the ones who treat position as something they keep continuously and verify cheaply—who understand that dead reckoning for distributed teams is survivable only when a real fix is always within reach. That's the bet behind Coommit: keep the team's real position on one shared, AI-aware canvas, so a fix is always a glance away rather than a meeting away. Stop reciting your estimates. Start taking fixes. Your future self, staring at a deadline that drifted three weeks ago, will thank you.