SB
Sam Project lead
This project is about cutting onboarding to seven days. We’re not migrating the CRM.
Project Kickoff
Talk through the project. Leave ready to start together.
Outcomes, scope, decision rights, milestones, dependencies, risks, and immediate ownership become one shared project charter.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
From Sam Scope boundary
CRM migration excluded Out of scope Protects the seven-day onboarding outcome
AL
Ari Sponsor
“Ready to start. Maya owns data access by Friday; Sam owns the first milestone.”
Kickoff ready Confirmed by Ari ✓
Project charter ✓
Kickoff ready Immediate action Secure onboarding data access Maya · Friday
Scope boundary CRM migration excluded Confirmed by Ari
From Sam→Confirmed by Ari
How the template helps
Enough alignment to begin without pretending uncertainty is gone.
The team makes outcomes, boundaries, governance, and early risks explicit before work accelerates.
What the team leaves with
A project charter people can actually work from.
Outcomes, scope, roles, dependencies, risks, readiness, and immediate actions remain connected.
Run a project kickoffCustomer onboarding project Project charter
Ready to startConfirmed outcome Start with the agreed scope and governance
One outcome · three milestones · two immediate actions
Immediate action Confirmed
Secure onboarding data access Maya · Friday
Linked to the first milestoneScope boundary Reviewed
CRM migration excluded Confirmed by Ari
Sam’s source statement attached