How I built a structured PM onboarding plan in under a week

A transition that was known for months. Planned for in days.

The outgoing Project Manager's departure had been anticipated well in advance. The business had time to prepare — and chose not to. Every suggestion of a transition plan was declined. It wasn't until the final week arrived that urgency replaced avoidance, and a structured plan was suddenly needed immediately.

Without intervention, the default was clear: the incoming PM would figure it out alone. No structured handover. No documented knowledge. No context on the team, the systems, the clients, or the expectations of the role.

The last week arrived. Nothing was ready.

The season was starting. The incoming PM — Marcus — was arriving into a role that carried significant operational responsibility. The outgoing PM — Jordan — had built relationships, processes, and institutional knowledge over multiple seasons. Without a structured transfer, all of that walked out the door.

In businesses without onboarding infrastructure, this scenario plays out the same way every time. The incoming person inherits confusion. The outgoing person gets blamed for gaps they had no way to fill. The owner steps in to manage the fallout of a handover that never really happened.

• The departure was known for months — no planning had been done and all suggestions for a transition plan had been declined.
• No documented knowledge existed for the PM role — systems, processes, team context, and client relationships all lived in one person's head.
• The incoming PM had no structured path to becoming effective — no Day 1 plan, no Week 1 structure, no defined milestones.
• Three stakeholders needed to be coordinated — incoming PM, outgoing PM, and owner — with no existing framework to do so.
• The season was starting. There was no time for a slow, informal handover.

Key-person dependency without a succession plan is a structural risk

This wasn't a Marcus problem or a Jordan problem. It was an organisational design problem. When institutional knowledge lives entirely in one person — their relationships, their processes, their memory of how things work — the business is one departure away from operational disruption. Every time.

The fix wasn't just an onboarding plan. It was the beginning of a knowledge transfer infrastructure — a system for capturing what key people know and transitioning it deliberately, rather than hoping it sticks.

Three stakeholders. Two phases. One week. Zero gaps.

I designed and delivered the plan in two phases — a Day 1 plan first to provide immediate structure, followed by a complete Week 1 plan covering the full knowledge transfer, system introductions, and stakeholder sessions required to give Marcus a real start.

Every session was purposeful — structured around a specific area of knowledge, with defined participants, clear objectives, and realistic time allocation. I confirmed calendar blocks upfront so nothing relied on informal scheduling.

Every session planned. Every stakeholder coordinated.

A real start — not a survival exercise

The plan gave Marcus something most incoming PMs in owner-operated businesses never get — a structured, intentional first week with clear sessions, defined expectations, and the context needed to become effective quickly. It also gave Jordan a clean, dignified exit with a proper handover rather than an informal goodbye.

The speed of delivery mattered as much as the quality. The Day 1 plan was in the owner's hands before the week began. The Week 1 plan followed immediately after. In an environment where planning had been consistently deferred, having something structured and ready changed the dynamic entirely.

• A complete Day 1 and Week 1 onboarding plan designed and delivered in under a week — from a standing start with no existing documentation.
• A failure scenario prevented — the default outcome of an unstructured handover (knowledge loss, blame, disruption) avoided entirely.
• Three stakeholders coordinated with confirmed calendar blocks — no informal scheduling, no missed sessions, no last-minute scramble.
• The incoming PM arrived on Day 1 knowing what to expect — role context, team introductions, systems access, and a clear structure for the week ahead.
• The outgoing PM completed a structured knowledge transfer — covering team, calendar, systems, and day-to-day operations — rather than leaving gaps that would surface weeks later.
• The owner had visibility and involvement at defined checkpoints without needing to manage the process himself.