Remote-First Reality Check ========================== Slide 1: Remote-First Reality Check Narration 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? On-screen text Remote-First Reality Check Designing onboarding, logistics and rituals for a distributed team Slide 2: What "remote-first" really means Narration 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. On-screen text What "remote-first" really means - Operations, tooling and decisions assume no shared office baseline - Misconception: "remote allowed" policies but HQ-only approvals and walk-up support - Remote-first makes IT the new facilities team: devices, access, and rituals must travel - Why it matters: reliability, compliance and employee confidence begin with us Slide 3: First 30 days onboarding map Narration 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. On-screen text First 30 days onboarding map - Pre-day 0: contract + ID + hardware shipment with welcome doc + checklist template - Week 1: async orientation modules led by People Ops; buddies own the first live touchpoint - Week 2: engineering/ops leads run recorded shadowing playlists by function - Week 3–4: manager + mentor co-review first deliverables; measure time-to-first-commit/story - Success metrics: access ready on day 1, first task shipped within 14 days, CSAT ≥ 4.5/5 Slide 4: Device and access logistics Narration 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? On-screen text Device and access logistics - Maintain persona-based hardware buffers with zero-touch images and tamper seals - Regional depot partners handle RMA swaps; Sarah in Berlin had a twin MacBook by Thursday - $800–$1,200 BYOD stipend plus MDM enrollment prevents gaming rigs from hitting prod - "Most teams are remote-friendly until a laptop dies in Mumbai at 3am." Seen that week-long customs saga? - Humor beats panic: nothing says "welcome" like a device touring three customs warehouses Slide 5: Secure joiner/mover/leaver runbooks Narration 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. On-screen text Secure joiner/mover/leaver runbooks - Automate account creation from HRIS/contract tracker with least-privilege bundles - Include VPN, SSO, MFA, password manager setup in the welcome packet video - Deprovision within 2 hours of notice (immediate for terminations); automation revoked Maria's access minutes after HR closed her contract - Keep third-party SaaS inventories so MSPs can disable access without hunting spreadsheets Slide 6: Contractor-heavy teams Narration 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. On-screen text Contractor-heavy teams - Issue company-managed identities; never hand out a founder's admin login - Require data-handling agreements and country-specific compliance addenda - When Maria's design contract ended, automation revoked Figma, Slack and VPN within minutes - If expense approvals take 6 weeks, expect a private Dropbox empire—fix the process instead - Pair every engagement with return labels and hardware trackers so gear comes home Slide 7: Time zone choreography Narration 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? On-screen text Time zone choreography - Publish coverage map + core collaboration hours (e.g. 2pm–5pm UTC) with escalation paths - Follow-the-sun handover templates saved us when London found a 6pm bug before Sydney woke up - Record key meetings with timestamped notes; ask: how many of you survived the "quick" 2am sync? - We learned the hard way that "quick sync" at 2am Melbourne time isn't quick for anyone—sleep > sprint planning Slide 8: Virtual support operations Narration 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. On-screen text Virtual support operations - Run help desk inside chat with triage bots, KB links and emoji status reactions - Offer video office hours and chase a "first-day fix" goal for remote incidents - Stock spare devices at regional MSP lockers to hit 48-hour replacement targets - Track shipping SLAs, customs delays and ticket MTTR as joint KPIs Slide 9: From operations to culture Narration 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. On-screen text From operations to culture - Logistical excellence signals trust: people share context when devices arrive ready to work - Async rituals thrive when onboarding removes guesswork about tools and access - Bridge statement: strong runbooks free managers to focus on belonging, not badge provisioning Slide 10: Culture and belonging Narration 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. On-screen text Culture and belonging - Pair each starter with a culture buddy outside their reporting line for social proof - Host monthly "operations show-and-tell" to surface small tweaks and celebrate experiments - Fund in-person micro-retreats by region when >8 contributors cluster nearby - Rotate facilitation of async updates so every voice practices storytelling Slide 11: Health metrics to track Narration 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". On-screen text Health metrics to track - Onboarding satisfaction score from first 45-day survey - Hardware delivery lead time by geography vs. target of <5 business days - Percentage of roles with documented SOPs, video walkthroughs and owners - Support MTTR for remote device issues and access resets Slide 12: Common failure patterns Narration 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?. On-screen text Common failure patterns - 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 - 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? Slide 13: Action checklist Narration 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. On-screen text Action checklist - Audit remote onboarding artefacts and fill gaps before the next cohort starts - Sign agreements with regional logistics and e-waste partners now - Automate offboarding triggers for payroll, SaaS and physical assets - Review quiet hours, stipends and retreat budgets every quarter