Sacha Connor, Founder and CEO of Virtual Work Insider, spent 11 years leading hybrid and remote teams at major consumer brands before launching her consultancy. Her work centers on a problem that quietly undermines distributed teams: most expectations are implicit, and implicit expectations break down the moment people stop sharing the same hallway.
The wider issue is that most organizations are still running on assumptions formed during in-office work. Response times, working hours, meeting norms, decision rights, and even tone in writing get inferred rather than stated. Distributed work surfaces every gap, and the cost shows up in burnout, missed deadlines, and unclear accountability.
HR leaders who want hybrid and remote teams to work have to make the implicit explicit. That requires a deliberate conversation, not just a policy document.
Why explicit expectations are the foundation of hybrid work
Hybrid work amplifies whatever clarity, or lack of clarity, already exists. Gallup's strategic guide to hybrid and remote teams makes the case directly; Gallup's research on managing remote workers shows that the highest-performing distributed teams have far more explicit norms than their in-office counterparts.
For HR leaders, the practical move is to build expectation-setting into onboarding, manager training, and team rituals. AllVoices' pulse surveys give people leaders a steady read on whether expectations are landing in practice, not just on paper.
That clarity sits inside a wider remote employees strategy that covers communication, performance, and inclusion across locations. Without it, distributed teams default to whoever shouts loudest in the team channel.
What expectations to set, and how
Which expectations matter most for hybrid teams?
Six categories cover most of the ground: working hours, response times, meeting norms, decision rights, performance criteria, and how to raise concerns. Each one needs a clear default, a clear exception process, and a way to revisit the norm as the team evolves.
SHRM's coverage of setting expectations for hybrid work walks through the categories in detail. The point is not to over-engineer; it is to make the norms visible.
How do you keep expectations from feeling like surveillance?
Frame norms in terms of outcomes, not activity. Tell people what good looks like in the work itself, not how many hours their status indicator should show green. Pair clear expectations with strong autonomy, and the result is alignment rather than micromanagement.
Use informal communication rituals to soften the structure. Quick check-ins, virtual coffees, and team rituals keep relationships warm even when expectations are crisp.
What actually works
Write the norms down, in one place
Hybrid teams need a single source of truth for working norms. A team operating doc, no more than two pages, that covers hours, response time, decision rights, and meeting norms saves hundreds of hours of confusion later. Revisit it every quarter.
Train managers to walk new hires through the doc on day one. The first week sets the pattern that follows.
Calibrate manager and employee expectations together
Most expectation breakdowns come from a mismatch between what the manager assumes and what the employee assumes. Make the calibration explicit. Run a structured first-month conversation that covers communication style, working hours, and feedback preferences for each person on the team.
That conversation is more useful than any policy document. Tools like employee survey tools can surface gaps that managers may not notice.
Connect expectations to performance and accountability
Once expectations are clear, performance conversations become specific. Use them in one-on-ones, mid-year reviews, and any performance improvement conversation. Avoid the trap of penalizing people for missing expectations they were never told.
Explicit expectations also protect employees from arbitrary feedback. The clearer the norms, the harder it is for vague criticism to land.
Where Employee Relations Fits
Distributed teams produce ER cases that look different from in-office work: complaints about manager favoritism toward in-office staff, perceptions of overwork, or concerns about communication patterns. AllVoices' employee relations function support helps HR leaders surface these patterns early. Our HR case management system keeps the documentation consistent across geographies.
How does ER help reinforce expectation-setting on hybrid teams?
ER work catches the expectation gaps before they grow into formal complaints. When the same team produces multiple concerns about workload or unclear roles, the underlying issue is rarely a single difficult employee; it is usually a missed conversation between manager and team about how the work should run.
Sharing those patterns with people leaders, in confidence, gives them a chance to fix the underlying expectations issue before it becomes a retention problem.
Frequently Asked Questions About Setting Expectations
How explicit should expectations be?
Explicit enough that a new hire could read the team norms doc and know how to operate from week one. If norms require tribal knowledge to interpret, they are not yet explicit.
How often should teams revisit expectations?
At least quarterly, plus any time the team adds members, changes leadership, or shifts strategy. Norms decay quickly when context changes.
What is the cost of leaving expectations implicit?
Burnout, attrition, ER cases, and missed deadlines. The cost shows up across categories because implicit norms produce variable performance and resentment.
How do you handle pushback on explicit norms?
Listen. Some pushback signals that the norm is wrong, not that the employee is. Calibrate together rather than defending the doc.
How do anonymous channels fit expectation-setting?
They surface concerns about norms employees are not ready to raise directly, especially around fairness across hybrid and in-office staff. Patterns from those channels often reveal where expectations need clearer definition.
What's the first step for HR leaders who want to put this into practice?
Start with one team and one measurable outcome. Pick a function where the issue shows up sharply and a leader who is willing to model the new practice. Map the current state honestly: what is happening, who feels it, and what would good look like in ninety days. Share that picture with the team, ask them what is missing from your read, and adjust before launching anything formal. The goal of step one is alignment, not activity.
Once the picture is shared, pick two or three changes you can make inside one quarter. Resist the urge to launch a full program. Run the changes, measure the response with simple pulse questions, and report back. The combination of a focused team, a clear measure, and a public commitment to learn is what turns a good idea into a practice that spreads. HR leaders who try to launch everywhere at once usually end up launching nowhere.
Iterate from there. The teams that succeed treat the first cycle as a prototype, not a rollout. They keep what worked, drop what did not, and write down what they learned. By the time the practice expands to the next group, it has been pressure-tested by people who have a stake in seeing it work. That is the unglamorous work of putting any people-strategy idea into practice, and it is also the work that compounds.
The Bottom Line for HR Leaders
Sacha Connor's work on virtual teams comes down to a discipline: make the implicit explicit, write it down, and revisit it often. Hybrid and remote work do not require more rules; they require more clarity about the rules that already exist.
HR leaders who treat expectation-setting as part of onboarding, manager development, and ER infrastructure will produce teams that feel coherent across distance. Skip that work, and even great talent will quietly drift.
See how AllVoices helps HR teams hold hybrid expectations and ER work together in one system.
.avif)
.avif)
.avif)