A remote team should communicate as often as the work requires, using an agreed cadence rather than a universal meeting schedule. The manager should ensure enough structure for clarity and accountability, while the team helps shape frequency, channels, response expectations and review points because they experience both the cost of missed information and the cost of interruption.
There is no universal number of remote-team meetings or check-ins that fits every team. The cadence should be agreed with the people doing the work, based on how much coordination the work requires, which issues need live discussion, what can move asynchronously and how quickly problems need to surface.
The manager has a responsibility to create enough structure for clarity and accountability. The team also has information the manager does not: where interruptions are costly, which handoffs are fragile and which channels actually help. A useful cadence combines both perspectives and changes when the work changes.
Start with coordination needs, not a calendar template
Kevin Eikenberry’s Genius Talk conversation puts intentionality at the center of remote leadership. He argues that leaders can slip into unpredictable contact that feels like “checking up” rather than useful communication. His alternative is an agreed cadence: clarify how, when and why people will communicate.
That shifts the design question.
Instead of asking, “How many meetings should a remote team have?”, ask:
- Where does work depend on another person’s input?
- Which decisions become expensive if they wait?
- Which updates can be read rather than discussed?
- Where does ambiguity regularly create rework?
- What information needs to be visible to everyone?
- Which conversations benefit from immediate back-and-forth?
- What requires uninterrupted focus?
The answers tell you more about cadence than a generic meeting schedule.
A product team near a release may need a different rhythm from the same team during a quieter planning period. A small group doing tightly coupled work may need more frequent coordination than specialists whose tasks can move independently for several days.
Cadence should follow the work.
Separate synchronous work from asynchronous work
Remote teams often create too many meetings because live conversation feels like the safest way to make sure communication happened.
That can solve one problem while creating another. Every live meeting consumes the same block of time from several people and interrupts whatever they were doing before it.
A better question is what the communication needs to accomplish.
Use synchronous communication when the value comes from interaction: resolving ambiguity, making a contested decision, working through a complex trade-off, handling a sensitive issue or generating ideas that depend on rapid exchange.
Use asynchronous communication when the value comes from visibility: status updates, routine documentation, decisions that have already been made, background reading, requests that do not require an immediate answer or information people may need to reference later.
This is a design choice, not a rigid rule. A written thread can become confusing enough to justify a call. A meeting can reveal that the remaining work is better handled in a document.
The point is to choose the mode for the job it needs to do.
Give each channel a job
Eikenberry’s cadence logic includes channel choice as well as frequency. If every channel can mean anything, people have to monitor all of them as if everything might be urgent.
Assigning jobs to channels reduces that uncertainty.
A team might decide that:
- project decisions live in the project system;
- routine updates go into an asynchronous team channel;
- urgent issues use a defined real-time channel;
- sensitive one-to-one matters happen privately;
- longer reasoning belongs in a document people can review before a discussion.
The exact tools do not matter as much as shared expectations.
Michael Gerharz’s Genius Talk work on communication adds a useful standard: a message only helps when the audience can understand why it matters and what to do with it. Remote teams need that clarity because the sender is often not present to repair a vague message immediately.
A channel norm should therefore cover more than location. It should also make the expected response visible. Is this for awareness? A decision? Feedback? Action by a deadline? A question that can wait?
Those distinctions reduce unnecessary back-and-forth.
The manager should not decide cadence alone
A manager is accountable for ensuring the team communicates well enough to do the work. That does not make manager preference the best design principle.
Eikenberry explicitly frames cadence as something to agree with the team. That matters because communication has two costs: the cost of missing information and the cost of interrupting work.
The team experiences both.
A practical way to set the cadence is to ask people where they currently lose time. Do they wait too long for decisions? Sit through meetings with little relevance? Get repeated requests for information already documented elsewhere? Miss updates because the channel is noisy? Feel unsure when a problem is important enough to escalate?
Then design around those failure points.
The manager can propose a structure, but the useful test is whether the structure improves coordination without creating unnecessary surveillance or interruption.
Make room for hierarchy and participation differences
A remote meeting can look inclusive while still concentrating the conversation among a few people.
Myriam Hadnes’s facilitation work draws attention to hierarchy, silence, group dynamics and perceived permission to speak. She treats these as context-sensitive factors rather than fixed traits of any culture or group.
That matters when a team decides how communication will work.
Some people will speak quickly in a live call. Others may contribute better after time to think. Junior colleagues may hesitate to challenge a senior person in a group setting. People working across languages or cultural contexts may need more space to formulate a response.
A cadence can account for this without stereotyping anyone.
For example, a team can circulate questions before a meeting, collect written input, allow a short period after the meeting for additional comments, or ask for views before the most senior person gives theirs.
The objective is not maximum participation in every channel. It is making sure the communication design does not systematically hide useful information.
Protect focus as part of the communication system
More communication is not automatically better communication.
A team can be highly connected and still struggle to finish difficult work because attention is fragmented across messages, calls and status requests.
Mike Lane Evans’s Genius Talk discussion of communication emphasizes listening, silence and curiosity. Those ideas apply beyond coaching. A remote team needs periods in which people are not expected to be continuously responsive so they can think and execute.
That means the cadence should define response expectations as carefully as meeting times.
If a message can wait several hours, say so through the channel norm. If a decision needs an answer before work can continue, make that urgency explicit. If a role requires uninterrupted blocks, protect them.
Without those distinctions, every message competes for immediate attention.
Watch for over-communication and under-communication
A cadence needs adjustment when the symptoms change.
Signs of under-communication can include:
- work repeatedly stops while people wait for decisions;
- two people unknowingly solve the same problem;
- priorities are interpreted differently;
- important risks surface late;
- handoffs fail because ownership was assumed;
- team members are surprised by decisions that affect their work.
Signs of over-communication can include:
- the same status is reported in several places;
- meetings repeat information already available in writing;
- people receive frequent check-ins without a clear decision or support need;
- response expectations make focused work difficult;
- the manager becomes the center of every update even when no decision is required.
Neither list produces a universal schedule. It gives the team evidence for changing its own schedule.
Review cadence when the context changes
Eikenberry uses “it depends” as a prompt to ask what a situation depends on. That is a useful rule for remote communication too.
Review the cadence when:
- the team changes size;
- a project moves into a more tightly coordinated phase;
- responsibilities change;
- a new time-zone pattern appears;
- repeated delays or interruptions show that the current system is failing;
- a crisis temporarily requires faster communication;
- the crisis ends and the emergency rhythm is no longer justified.
The stable part is the purpose: enough clarity, relationship and coordination for people to work well together.
The flexible part is how often the team talks, where the communication happens and what deserves synchronous attention.
A good remote cadence should feel explainable. People should know why a meeting exists, why a channel exists, when they are expected to respond and when the arrangement will be reconsidered.
That is more useful than copying someone else’s weekly meeting count.