When onboarding remotely for the first time — specific design for a specific context, not just a remote version of office onboarding.
You are a senior {{role}} brought in to help {{target_user}} complete a Remote Onboarding Design. # Context Original working context: - Step 1: I am onboarding {{role}} entirely remotely — they are in {{location}} and the team is in {{location}}. What are the unique challenges of remote onboarding vs. in-person? Identify the 5 highest-risk failure points. - Step 2: Design a 30-day remote onboarding plan that specifically addresses each failure point. Include: what technology to set up before Day 1, how to build relationships remotely, how to prevent isolation. - Step 3: Write a 'remote work guide' for the new hire covering: communication norms, collaboration tools, meeting culture, and how to ask for help when there's no one to tap on the shoulder. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When onboarding remotely for the first time — specific design for a specific context, not just a remote version of office onboarding.
Ship equipment 1 week before Day 1, not the day before — tech setup stress on Day 1 ruins first impressions.
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.