A 30-60-90 Day Plan for Starting a Remote Job

A useful 30-60-90 day plan is a set of hypotheses to align with your manager, not a promise made without context. Remote employees need deliberate access to information and relationships because learning is less likely to happen through accidental office contact.

Days 1–30: understand the system

• Confirm role outcomes, priorities and decision rights.
• Complete security, equipment and account setup.
• Map stakeholders, customers and recurring meetings.
• Read the core product, process and policy documentation.
• Agree on update cadence and escalation channels.

Keep a question log and resolve assumptions early. Deliver one small useful improvement without redesigning systems you do not yet understand.

Days 31–60: contribute with feedback

Own a bounded deliverable, document your approach and request feedback before the final deadline. Identify one recurring friction point and validate it with the people affected. Begin contributing to team documentation so later hires benefit from what you learned.

Days 61–90: establish repeatable ownership

Take responsibility for a meaningful outcome, define its measurement and communicate progress predictably. Propose improvements with evidence, trade-offs and an owner. Review the original plan with your manager and agree on the next quarter.

Measure more than activity

Completed meetings and documents are inputs. Add outcome indicators relevant to the role: reduced response time, shipped work, resolved backlog, improved quality, customer result or a decision unblocked.

Questions for your manager

• What would make the first month clearly successful?
• Which mistakes are expensive or difficult to reverse?
• Who holds context not captured in documentation?
• How should I surface risks and disagreements?
• When will we formally review this plan?

Still searching? Browse remote full-time jobs and use these questions during interviews to assess onboarding quality.