The First 30 Days With Your Extended Team

Days 1–5: align on the outcome

Confirm scope, success measures, decision owners, meeting cadence, working systems, and escalation paths. Review the business context behind the work, not only the task list. A partner makes better decisions when it understands who depends on the output and why timing matters.

Create a single open-items log. Every missing access, question, risk, and decision should have an owner and date.

Days 6–10: transfer access and evidence

Provision named, least-privilege access and test it. Transfer source files, calendars, prior examples, existing procedures, known exceptions, and important contacts through approved systems.

Do not assume the existing process is correct simply because it is familiar. Label known problems separately so the team does not reproduce them as requirements.

• Access inventory and owner
• Process map and recurring calendar
• Examples of accepted outputs
• Known exceptions and unresolved issues
• Communication and escalation matrix

Days 11–20: shadow and run in parallel

Let the partner observe the current workflow, then prepare the output while the prior owner reviews. Compare results, capture decisions, and update the procedure. For critical work, a parallel run creates confidence before responsibility shifts fully.

Focus feedback on standards and business context. Give the new specialists room to improve the process rather than prescribing every click.

Days 21–30: transfer the cadence

The partner should begin leading status, presenting completed work, and raising decisions before deadlines. Review initial measures such as timeliness, exception volume, rework, and internal time required.

End the month with a retrospective and a 60-day improvement list. A successful first month does not mean everything is optimized. It means the operating relationship is clear enough to improve deliberately.