Scenarios: connection, camera, and commute

Remote and hybrid work fails in physical ways: a train stops, a mic dies, a hotel router drops packets, a toddler wakes up. This chapter is a dense bank of real exchanges for those moments, shown from both chairs (yours and the other person's), meant for lookup when it is happening to you right now. The move stays the same throughout: name the fact, give the timeline or the workaround, and never make the room wait on a mystery.

You joined the meeting late

  • Slipping in five minutes late. Q: "Glad you could join us." A: "Sorry, back-to-back ran over. Catch me up on the deploy decision and I will follow the rest."
  • You missed the opening context. Q: "We already covered scope, you good?" A: "I will read the notes after, don't rewind for me. What is the open question right now?"
  • Someone pings you mid-call. Q: "You joining standup?" A: "Two min, a call ran long. Start without me, I will grab the board."
  • Owning it in one line. Q: "There you are." A: "My fault, wrong link in the invite. Where are we?"
  • Late and it is your topic. Q: "We were waiting on you for the metrics item." A: "Sorry to hold you. Ready now, sharing p99 in ten seconds."
  • Arriving after a decision. Q: "We just picked option B." A: "Works for me, B was my lean too. Anything you need from me to lock it?"
  • Manager notices in a 1:1. Q: "You were late to the sync again." A: "Fair, two of my recurring meetings collide at the half hour. Can I move standup to 10:15?"
  • You lurked in silently first. Q: "How long have you been on?" A: "Joined at minute three, muted so I would not interrupt. Fully caught up now."
  • Genuinely forgot the invite. Q: "You missed the first half." A: "I dropped it off my calendar, no excuse. Send me the action items and I will own mine."
  • Host offers a recap. Q: "Want me to recap for you?" A: "Just the decision we landed on, then keep going, I can read the rest from the doc."

You are arriving late to the office

  • Texting your team lead. Q: "You in today?" A: "Yes, in around 10:30, dentist ran over. Reachable on Slack the whole time."
  • Missed the in-person standup. Q: "We did standup at the desk, you weren't here." A: "Sorry, on my way now. Posting my update in the thread so nobody is blocked."
  • Badge desk holdup. Q: "Where are you?" A: "In the lobby, my badge deactivated overnight. Security is reissuing, ten minutes."
  • Pairing session waiting on you. Q: "We said 9 for the pairing." A: "I know, running 15 late off the bus. Start on the failing test, I will jump in."
  • Setting expectations the night before. Q: "Are you in tomorrow morning?" A: "In by 11, a delivery window I can't move. Morning reviews I will do from home first."
  • Manager asks in person. Q: "Rough morning?" A: "School drop-off chaos. Here now, and I blocked my afternoon to make up the design review."
  • You will miss the coffee-chat slot. Q: "Still on for our 9:30 walk?" A: "Can we push to 10? Train delay. I will text when I badge in."
  • Someone saved you a seat. Q: "Room 4 is filling up, you close?" A: "Five out. Grab me the seat by the screen, I will slip in quietly."

Your commute is delayed

  • Train held between stations. Q: "Standup in five, you close?" A: "Stuck on the Central line, no signal ETA. Posting my update in text now so you can proceed."
  • Signal failure, no clear timeline. Q: "When will you be in?" A: "Honestly unknown, signal failure at Kings Cross. I will work from a cafe near the station instead of guessing."
  • Bus replacement chaos. Q: "You making the 10am with the vendor?" A: "Rail replacement bus, I will be late. Can you take the intro and I join by phone for the technical part?"
  • Driving into a jam. Q: "You on for the design review?" A: "On the M4, stopped dead. I will pull off and join from my phone audio-only in ten."
  • Flight delay before a work trip. Q: "Landing on time for the onsite?" A: "Delayed 90 min out of Schiphol. I will miss the morning session, catching up on notes tonight."
  • Weather closed the line. Q: "Coming in through the snow?" A: "Line is suspended, roads are worse. Full remote today, calendar unchanged, all calls I will take from home."
  • Proactive heads-up, no one asked. Q: "(you open the thread)" A: "Heads up, major delay on my line, I will be 30 late. Standup update is in the thread, nothing blocked."
  • You will make it, barely. Q: "Cutting it close?" A: "Delayed but moving, I will badge in right at 10. If I am not on the call at 10:01, start without me."
  • Delay eats a hard deadline. Q: "The release window is 11 sharp." A: "My delay puts me in at 11:15. Can Priya hold the deploy button, or should we slip the window 20 minutes?"
  • Teammate covering for you. Q: "Want me to run your part of the demo?" A: "Please, my train is dead. Slides are in the shared drive, I will feed you the numbers over chat."

You are commuting and can only type

  • On the train, camera off by necessity. Q: "Can you hop on a quick call?" A: "On a train, can only type for the next 40 min. Give me the question here and I will answer fully."
  • Asked to present live. Q: "Can you walk us through the schema now?" A: "Not verbal right now, I am on public transport. I will paste the schema and annotate it in the thread."
  • Redirecting a call to async. Q: "Easier to just talk it through?" A: "Normally yes, but I am mobile-only. Write me the two decisions you need and I will decide in text."
  • Approving a PR from your phone. Q: "Can you review before the cutoff?" A: "On the bus, reading on my phone now. Small change, I will approve or leave line comments in ten."
  • Setting the boundary politely. Q: "Standup is voice today." A: "I am commuting and typing only. Here is my update: shipped the retry fix, testing the timeout next, no blockers."
  • Debugging by text while moving. Q: "Prod is throwing 500s, can you look?" A: "Commuting, can't SSH in. Check the vault service health first, that pattern bit us last Tuesday. I am at my desk in 25."
  • Someone wants a decision fast. Q: "Ship it or hold?" A: "Hold. I am on my phone and can't verify the migration. I will confirm from my laptop in 20, don't ship blind."

You are somewhere noisy and cannot unmute

  • Coffee shop background roar. Q: "Can you take the next section?" A: "I am in a loud cafe, staying muted. I will drive it in chat, or Dana can read my slides out."
  • Open-plan office, others on calls. Q: "You're muted, did you have a comment?" A: "Yes, typing it, too much around me to unmute cleanly. My point: the cache TTL is the real fix, not the retry count."
  • Airport gate announcements. Q: "Want to add anything?" A: "At a gate, boarding calls every minute. Muting to spare you. Written thoughts coming in the thread."
  • Construction outside. Q: "We can't hear you over the drilling." A: "Yeah, roadwork right outside. Let me switch to chat for the rest of this, sorry."
  • Kids in the next room. Q: "Can you unmute for the demo?" A: "Toddler meltdown next door, staying muted. Ravi, can you narrate while I share my screen?"
  • You want to signal agreement without talking. Q: "Everyone good with Friday?" A: "(thumbs up in chat) Muted and loud here, but yes, Friday works for me."
  • Dog going off at the door. Q: "Was that on your end?" A: "Delivery at the door, dog lost it. Muted now, ask me anything in chat for the next few minutes."

Your microphone is not working

  • Mic dead mid-meeting. Q: "You're talking but we hear nothing." A: "Mic just died on me. Typing here while I switch to my phone for audio, 30 seconds."
  • Headset not detected. Q: "Can you hear us? You look frozen on mute." A: "I hear you fine, my mic isn't being picked up. Ask me here and I will answer in chat until I fix it."
  • You caused the awkward silence. Q: "We were waiting on your answer." A: "Sorry, mic was muted at the OS level, not the app. Fixed now, can you repeat the question?"
  • Switching devices live. Q: "Still no audio from you." A: "Dropping and rejoining from my phone for mic, keep going, I will be back in a minute."
  • Bluetooth stole the mic. Q: "You sound like you're underwater." A: "My earbuds grabbed the mic in low-quality mode. Switching to laptop mic, tell me if this is clearer."
  • Reviewer asks you to explain a change. Q: "Walk me through the diff on the auth guard." A: "My mic is out, so I will type it: the guard checked the token before decoding it, I flipped the order. Screen share coming."

Your voice is too low to hear

  • Weak signal muffles you. Q: "You're really quiet, can you speak up?" A: "Bad reception here, I will keep it short and put the details in chat so nothing gets lost."
  • Others ask you to repeat. Q: "Sorry, you cut out, say that again?" A: "The gist: p99 doubled after the eu-west failover. Full numbers I am pasting now."
  • Cheap mic, low gain. Q: "We're straining to hear you." A: "Let me bump my input gain. If it is still faint, I will type the key points and just confirm out loud."
  • You keep clipping in and out. Q: "You keep dropping words." A: "My connection is choppy. I will hand the walkthrough to Sam and back her up in the thread."
  • Manager in a 1:1 can't hear you. Q: "You're faint today, everything okay?" A: "Fine, just a weak hotel line. If it is hard, let's move this to a written back-and-forth, I don't want you missing half of it."

You cannot turn on your camera

  • Camera-off in a camera-on culture. Q: "Can everyone turn cameras on?" A: "Mine is off today, low bandwidth. Audio is solid though, and I am fully here."
  • No judgment, just a reason. Q: "You hiding back there?" A: "Ha, no camera, I am on a train hotspot. Voice only from me, but I will jump in."
  • Camera hardware failed. Q: "We can't see you." A: "Webcam stopped being detected this morning, IT ticket is open. Sound is fine, carry on."
  • Client call, they expect faces. Q: "Will your side be on camera?" A: "I will be audio-only, my connection is shaky and I would rather keep the call stable than freeze mid-sentence."
  • Not presentable and honest-ish. Q: "Camera on for the demo?" A: "I will keep camera off and share my screen instead, the screen is the useful part anyway."
  • Bandwidth triage during a demo. Q: "Your video keeps freezing." A: "Killing my camera to save the demo, you need to see my screen more than my face. Better now?"
  • Manager asks you to turn it on. Q: "Mind turning your camera on for this one?" A: "Would if I could, hotel wifi can't hold video and screen share together. Happy to on the office wifi tomorrow."

Your internet is unstable

  • Warning the room early. Q: "(you open)" A: "Heads up, my wifi is flaky today. If I freeze, keep going and I will catch up in chat."
  • You froze mid-sentence. Q: "You cut out after 'the migration should'." A: "The migration should run in two phases, not one. Dropping to audio-only to steady it."
  • Repeated disconnects. Q: "You've dropped three times." A: "My router is the problem. Let me tether to my phone and rejoin, two minutes."
  • Falling back to async. Q: "This call isn't holding for you." A: "Agreed, my line is too unstable. Let's finish the last two items in the thread, I will respond within the hour."
  • Someone offers to cover. Q: "Want me to present your part while you reconnect?" A: "Yes please, slides are in the shared drive, I will feed you notes in chat as you go."
  • ISP outage mid-incident. Q: "We need you on the bridge for the outage." A: "My home ISP is down, moving to phone hotspot now. Give me the current status while I reconnect so I don't slow the bridge."
  • Packet loss ruins voice. Q: "You sound robotic." A: "Packet loss on my end. Switching fully to chat for reliability, ask me anything there."
  • You will drop on purpose to fix it. Q: "You still with us?" A: "Barely. I am going to leave and rejoin on a clean network, back in three, don't wait on me for the recap."

You are working remotely unexpectedly

  • Sick kid, working from home. Q: "Thought you were in the office today?" A: "Kid is home sick, so I am remote. Same hours, all calls I will take, just no in-person pairing."
  • Locked out of the building. Q: "You coming to the offsite room?" A: "Building access is down for maintenance, working from the cafe across the street. Dialing into everything."
  • Home emergency, still reachable. Q: "You in today?" A: "Plumber emergency, remote until noon. Reachable on Slack, I will move my focus block to this evening."
  • Traveling and forgot to flag it. Q: "Why are you on a different timezone?" A: "I am at a family thing in Lisbon this week, my mistake for not flagging it. I am on GMT, so overlap with you is mornings."
  • Power cut at the office. Q: "Office lost power, what now?" A: "Everyone go remote, I already am. I will move the 2pm to a video call and repost the link in the channel."
  • Manager checks the sudden switch. Q: "You were supposed to be in for the review." A: "I know, car wouldn't start this morning. I can run the review over video at the same time, screen share is ready."
  • Unexpected remote, protecting the team. Q: "Does your being remote block the release?" A: "No. I have full VPN and deploy access from here. The only thing I can't do is the hardware test, so Yuki will cover that one step."

Don't be confused: flagging a problem is not the same as apologizing for it. A weak signal or a sick kid is not a moral failing, so lead with the fact and the plan ("wifi is flaky, I will chat if I freeze"), not a pile of sorries. Save the real apology for when you actually made someone wait on a mystery, and even then, one clean line beats three.

Don't be confused: "I might be late" and "I will be 15 minutes late, start without me" land very differently. The first makes the room hold their breath; the second gives them a decision. When your commute or connection wobbles, always convert the vague worry into a concrete number and a clear instruction for the people waiting.

👉 A stalled train and a stalled task both need the same move: name the delay early and hand the room a number instead of a shrug. On to Chapter 51.