Make the first 90 days fit the role’s real starting point

Audit the starting conditions

List the information, systems, approvals, equipment, and introductions required to begin. Note any dependencies that may not be ready on day one. A role cannot own a result before receiving access or context. This audit often reveals onboarding work the manager must complete before arrival, including clearing calendars for decisions the new joiner cannot make alone.

Sequence learning around real work

Choose a small set of customers, workflows, documents, or meetings that expose the role’s environment. Avoid a month of disconnected presentations. Give each learning activity a question to answer and a person who can provide context. The new hire should be able to connect information to an early task while still having room to ask basic questions.

Build a relationship map

Identify the manager, close collaborators, decision makers, and people affected by the role. Explain why each relationship matters and what the new joiner should learn. Do not make them schedule introductions without context or interpret the org chart alone. For distributed teams, plan overlap thoughtfully and provide written background so access is not determined by time zone.

Choose graduated milestones

Move from understanding to contribution to ownership. A first milestone may be mapping the current process; a later one may be recommending a change and running a cycle. Distinguish outcomes under the person’s control from business results involving many teams. Define what evidence the manager will review at each stage.

• Access ready before needed
• Learning tied to live work
• Relationships have a purpose
• Ownership grows with context

Adjust for a delayed dependency

Illustrative example: a new partnerships manager is expected to propose a channel plan by day 30, but customer data access will take several weeks. The manager changes the first milestone to interview internal owners and audit existing partner agreements. The channel recommendation moves later. The hire still produces useful learning without being judged against an outcome the organisation prevented.

Agree on the manager’s work

The plan should include decisions, feedback, context, and introductions the manager owes. Schedule recurring check-ins with a purpose: unblock access, test understanding, and review evidence. At 30, 60, and 90 days, discuss which assumptions were wrong and revise future outcomes. Do not use the original plan as a trap when the role or business changed after hiring. Add a weekly question for the new joiner: which missing context or delayed decision is preventing useful work? The answer exposes organisational blockers before they become a misleading performance concern.