A kick-off is complete when the delivery team can start safely—not when introductions are finished. Confirm the tenant identity and plan in Organization General, then use the meeting to turn the approved initiative into named work, owners, dependencies, and decisions for the relevant teams, agents, and workflows.
Required Participants
Include the business sponsor, customer project owner, platform admin, infrastructure or IT owner, security representative, data owners for the first use case, delivery lead, and at least one pilot-user representative.
Agenda
- Confirm the business outcome and first-phase boundaries.
- Agree on vocabulary for initiatives, configuration, product issues, infrastructure changes, and custom work.
- Name accountable owners and escalation contacts.
- Review the organization setup, deployment model, identity, network, Data, and tool dependencies.
- Select the first pilot and define its exit criteria.
- Establish the working channel, meeting cadence, decision log, and reporting format.
- Record immediate actions, owners, and due dates.
Decisions to Capture
| Decision | Expected result |
|---|---|
| Scope | In-scope outcome, users, systems, and explicit exclusions |
| Ownership | Business, admin, security, data, and delivery owners |
| Environment | Deployment model and responsibility boundaries |
| Access | Identity setup, required accounts, source approvals, and credential process |
| Pilot | Target users, scenarios, success measures, and stop conditions |
| Cadence | Working channel, weekly review, technical sessions, and escalation path |
Exit Criteria
Do not close the kick-off until unresolved access and security questions have owners and dates. The output should include a confirmed roadmap, responsibility matrix, first pilot brief, dependency list, meeting schedule, and decision log.
Continue with Rollout Roles and Delivery Cadence and the appropriate Deployment Model.