Anna: This section sets up Remote-First Reality Check. Treat it as the frame for the decisions, handoffs, and evidence that appear in the next slides.
Greg: The practical question is simple: by the end, what should a junior IT professional be able to explain, check, or document in a real workplace?
Anna: "Remote-first" gets tossed around, but most teams still think HQ-first.
Greg: Exactly—policies say "work from anywhere" while approvals still assume you can walk to finance.
Anna: Remote-first means devices, decisions and rituals travel as easily as the people do.
Greg: Which is why IT, ops and culture leads need the same playbook before the next cohort lands.
Anna: How many of you have felt that lurch when the "remote-friendly" promise meets missing equipment on day one?
Greg: Tonight we fix that gap—logistics, security and belonging in one loop.
Anna: Let's map the first month so nothing falls between time zones.
Greg: Pre-day zero we confirm paperwork, ship gear, load accounts and drop the welcome checklist in their inbox.
Anna: Week one stays async on purpose—People Ops hosts videos, buddies handle the human check-ins.
Greg: Week two we queue recorded shadowing; leads annotate playlists so new folks binge the right calls.
Anna: By week three the manager and mentor co-review their first real deliverable using a shared rubric.
Greg: Success looks like access ready on day one, first ship within 14 days and a CSAT above 4.5—hold us to it.
Anna: Most teams say they're remote-friendly until their star developer's laptop dies in Mumbai at 3am.
Greg: And suddenly "just bring it to IT" becomes a week-long international shipping nightmare.
Anna: We keep persona-based spares with zero-touch images, so Sarah in Berlin had a twin MacBook within 48 hours.
Greg: Depot partners plus customs-ready paperwork beat panic and prevent the scenic tour of three warehouses.
Anna: When BYOD is inevitable, we pair the stipend with MDM so that gaming rig never touches prod without controls.
Greg: Seriously, how many projects have you seen derailed by a customs delay or a missing VPN token?
Anna: Joiner-mover-leaver runbooks are where trust either lives or dies.
Greg: Automation fires from HRIS updates so access bundles land without tickets.
Anna: Maria's contract ended Friday; within minutes the bot revoked Figma, Slack and VPN—no heroics required.
Greg: The same playbook pushes MFA kits, password managers and VPN keys on day one.
Anna: We review those flows quarterly so they stay faster than "let me find the spreadsheet" improvisation.
Greg: Because if access takes hours, shadow IT takes minutes.
Anna: Contractor programs crumble when identities stay tied to founder logins.
Greg: Issue company-managed accounts, even if they're short-term, so auditing isn't a scavenger hunt.
Anna: When Maria finished her three-month design sprint, HR closed the ticket and automation clipped every tool within minutes.
Greg: And yes, if expense approvals take six weeks, expect a private Dropbox empire to bloom overnight.
Anna: Quarterly access reviews keep scope creep honest and surface contractors who quietly became team members.
Greg: We pair every exit with a gear return label so hardware doesn't retire in someone's guest room.
Anna: Time zones don't have to be chaos if choreography is deliberate.
Greg: Coverage maps plus core hours make escalations clear before anything breaks.
Anna: The handover template saved us when London spotted a blocker at 6pm and Sydney wouldn't wake for eight hours.
Greg: We left annotated Looms, so Melbourne picked up without pinging anyone at 2am.
Anna: We also killed the myth of the "quick sync"—turns out people prefer sleep to sprint planning.
Greg: So ask every team: which decisions truly require synchronous time, and who pays the sleep tax when they do?
Anna: Remote help desks work when support feels like a chat ping, not a ticket abyss.
Greg: Triage bots route laptop issues, while office hours catch the humans who'd rather talk.
Anna: We stock spare devices in regional lockers so replacements land within 48 hours.
Greg: And every shipment includes customs paperwork pre-filled—future us loves that version of us.
Anna: Shipping SLAs and MTTR live on the same dashboard as CSAT so ops and support stay aligned.
Greg: Fix problems fast and people stop improvising with personal Dropbox links.
Anna: From operations to culture focuses attention on a concrete part of the work. Logistical excellence signals trust: people share context when devices arrive ready to work, Async rituals thrive when onboarding removes guesswork about tools and access, and Bridge statement: strong runbooks free managers to focus on belonging, not badge provisioning.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Async rituals thrive when onboarding removes guesswork about tools and access; Bridge statement: strong runbooks free managers to focus on belonging, not badge provisioning.
Anna: Logistics done right is the runway for culture.
Greg: When equipment arrives ready and access just works, people feel trusted from the start.
Anna: That trust buys time for buddies, rituals and storytelling to stick.
Greg: We pair every new hire with a culture buddy outside their line so they hear the unwritten norms.
Anna: Regional micro-retreats turn Slack handles into people without demanding relocations.
Greg: Async updates rotate hosts so everyone practices belonging, not just the loudest timezone.
Anna: If we can't measure the experience, we can't improve it.
Greg: Hardware lead time, access MTTR, onboarding CSAT—they're our new uptime metrics.
Anna: Track customs delays next to support queues so we know when logistics, not tech, is the blocker.
Greg: And audit SOP coverage; gaps there explain why shadow IT blooms in the first place.
Anna: Leaders love dashboards—give them the remote equivalent of footfall and badge swipes.
Greg: Otherwise they default to "are people online" instead of "are systems keeping promises".
Anna: Common failure patterns focuses attention on a concrete part of the work. Laptop arrives late; new hire spends week one chasing access while shadow IT blooms, Contractors keep local copies because shared storage lags and expense approvals take 6 weeks, and Leaders schedule 10pm status calls "just this once" until burnout arrives—people prefer sleep.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Contractors keep local copies because shared storage lags and expense approvals take 6 weeks; Leaders schedule 10pm status calls "just this once" until burnout arrives—people prefer sleep; How many projects have you seen derailed by a customs delay or a missing VPN token?.
Anna: Let's land this with actions you can execute Monday morning.
Greg: Start by auditing onboarding artefacts—videos, SOPs, access flows—against the last hire's pain points.
Anna: Lock in logistics partners now so the next failed device gets replaced in hours, not weeks.
Greg: Wire offboarding triggers to payroll and SaaS so there are no lingering zombie accounts.
Anna: Revisit quiet hours, stipends and retreat budgets quarterly; remote teams evolve fast.
Greg: And after each cohort, ask "what made remote feel easy"—then scale that habit intentionally.