5.1Remote & hybrid management
The essentials in 30 seconds
- Steer deliverables, not connections: trust by default + clear goals.
- Rituals: weekly team check-in + regular one-to-one to keep connection and weak signals.
- Hybrid fairness: same information, same voice, same opportunities for remote and on-site staff.
Running mini-case — Karim remote 2 days/week
Salim manages a 12-person SME in Algiers. Karim, a seasoned technician, switches to working from home 2 days a week. In meetings, people forget to call him on video; his tickets move forward but nobody sees it. Salim fears "losing control". We will move from presence control to results steering, with rituals and fairness.
This same case runs through the course, the diagram, the script and the 48h challenge.
1. From presence to results
Remote and hybrid work requires moving from managing presence (controlling time spent) to managing by results and trust. Think football referee: they judge goals and play, not the number of steps run.
It's a posture shift: trust by default, explicit deliverables, focus on what is produced. Salim sets 3 measurable weekly deliverables with Karim instead of watching his login hours.
2. Rituals, tools, fairness
The keys: regular rituals (team check-in, one-to-one) that maintain connection and alignment, framed tools (video, messaging, shared tasks) with common usage rules, and attention to balance (isolation, hyperconnection, right to disconnect).
The major hybrid stake is fairness: share all information with everyone, explicitly invite remote staff in, watch access to visible projects. Without that, proximity bias favors those on site.
🔎 Concrete example — Trust without spying (Karim's case)
Clear goals and deliverables, trust on the "how".
Focus on what is produced, not connections.
→ explicitly invite Karim on video (anti proximity bias).Result: distance stops being a handicap.
Lesson: share all information with everyone.
Section vocabulary reinforced definitions
- Remote / hybrid management
- Managing teams partly or fully remote: through trust and results, not presence.
Simple example: Karim remote 2 days: 3 weekly deliverables + Monday check-in on video.
What it is not: watching green connection dots all day.
Reflex: if you watch login time, rephrase as an expected deliverable.
- Results-based management
- Steering on deliverables and goals reached, rather than on presence time.
Simple example: "20 tickets closed, average lead time under 24h" rather than "8h in front of the screen".
What it is not: counting emails sent.
Reflex: each mission = deliverable + deadline + quality criterion.
- Hybrid fairness
- Same place for remote staff as on-site (information, voice, opportunities).
Simple example: video speaking turn first, written minutes shared with all.
What it is not: deciding in the room then "telling Karim afterwards".
Reflex: in meetings, explicitly invite each remote person by first name.
- Remote rituals
- Regular team check-ins and one-to-ones that maintain connection and alignment.
Simple example: 30-min Monday video check-in + 20-min one-to-one with Karim on Thursday.
What it is not: multiplying impromptu meetings "to check".
Reflex: short ritual, at a fixed time, with an agenda and written notes.
In practice — Managing remotely effectively
- Switch to results: clarify goals and deliverables, trust people on the "how".
- Set regular rituals (team check-in, one-to-one) for connection and weak signals.
- Frame tools and usage rules (video, messaging, shared tasks, response times).
- Watch on-site/remote fairness and balance (isolation, hyperconnection, disconnection).
Ready-to-say script — framing remote with Karim (2 min)
"Karim, your 2 remote days: we judge on 3 weekly deliverables posted each Monday. The how is yours. We meet on video at the weekly check-in and in a 20-min one-to-one Thursday. In meetings, I'll give you the floor first so you have the same place. If there's a dip or an overload, tell me early, we adjust. Does that suit you?"
Say in one-to-one, then write in 5 lines shared with the whole team.
Copy-paste template — team hybrid charter
HYBRID CHARTER — Salim team (Algiers SME)
DELIVERABLES: 3 per person/week, posted Monday 9am, Friday review
RITUALS: 30-min Monday video check-in (camera + remote speaking turn first)
ONE-TO-ONE: 20 min/week or every 2 weeks, at a fixed time
TOOLS: video = decisions / messaging = info / task board = tracking
RULES: reply within 24 working hours, no message after 7pm except defined emergency
FAIRNESS: systematic written minutes, visible projects shared
DISCONNECTION: right recalled, isolation alert = direct callFully remote
Everything goes in writing: decisions, notes, shared board. Short but systematic video, camera recommended.
Intercultural
Spell out time zones, holidays, expected video formality. Rephrase in writing after speaking.
Algerian SME
Plan for unstable connection (audio-only backup), Ramadan/summer peaks, WhatsApp channel + simple video.
Micro-business (2-3 people)
1 weekly 15-min check-in + short daily messages. No heavy machinery: 1 shared board is enough.
✓ Best practices
- Steer on deliverables, trust people on the "how".
- Keep regular rituals despite distance.
- Actively watch on-site/remote fairness.
✗ Common pitfalls
- Digital presenteeism (monitoring connections).
- Proximity bias (forgetting remote staff).
- Neglecting isolation and hyperconnection.
Key takeaways
- Remote: from presence to trust and results.
- Regular rituals maintain connection and alignment.
- Major stake: on-site/remote fairness.
- Watch: isolation, hyperconnection, disconnection.
48h challenge — apply tomorrow
Write 3 weekly deliverables for 1 remote team member (including Karim if that's your case), schedule 1 20-min one-to-one, and in meetings give remote staff the floor first. Note what changes.
- I steer 1 team member on deliverables, not on connections.
- I have a check-in + one-to-one ritual at a fixed time.
- I've done the 48h challenge or scheduled its date.
Frequently asked questions
How to trust without "spying"?
Set clear deliverables then judge on output, not connections. Regular check-ins + measurable results replace surveillance, more respectful and more effective.
How to avoid disadvantaging remote workers?
Share all info in writing, invite remote staff first, watch access to visible projects and promotions. Without deliberate attention, proximity bias sets in.
And the right to disconnect (may vary by country)?
Working-time and disconnection rules depend on the contract and the country. Set response times and a "no message after 7pm except defined emergency" rule, after internal validation. Teaching example for illustration only.
Karim is remote Tuesday-Wednesday. In a Thursday on-site meeting, the team decides without calling him then "tells him afterwards". Salim's best reflex?