Prepare the next conversation, session or decision.
Work through these 10 steps and choose the actions relevant to your situation. The pitfalls are illustrative examples, not customer quotations. Use the checklist on screen or print it for your preparation.
Review the sales handoff
Illustrative pitfall
“The implementation team started with a contract and no buyer context.”
- Read approved scope and account notes.
- Identify the outcomes and promises discussed during sales.
- Flag mismatches for resolution before kickoff.
Confirm customer priorities
Illustrative pitfall
“The kickoff followed our template without checking their current goals.”
- Ask which outcomes matter most now.
- Check for changes since the purchase decision.
- Agree the first practical milestone.
Map the people
Illustrative pitfall
“The project depended on someone who had never been invited.”
- Identify the sponsor, project lead and user representatives.
- Clarify supplier and customer responsibilities.
- Include required technical and process owners.
Make scope understandable
Illustrative pitfall
“Each team used the same project name for different expectations.”
- Explain what the agreed scope includes.
- State exclusions and decisions still needed.
- Check understanding using concrete tasks or examples.
Surface dependencies
Illustrative pitfall
“The plan assumed data and permissions would appear on time.”
- Identify access, data and resource requirements.
- Assign an owner and date to each dependency.
- Confirm which conditions block the next milestone.
Agree communication
Illustrative pitfall
“Important questions scattered across unmonitored channels.”
- Choose the channels for updates, decisions and issues.
- Set an appropriate meeting and reporting rhythm.
- Name the contacts for urgent blockers.
Plan learning and support
Illustrative pitfall
“Users received training before they could access the system.”
- Identify role-specific learning needs.
- Sequence learning with access and usable workflows.
- Explain where users can get help afterwards.
Handle uncertainty honestly
Illustrative pitfall
“The customer heard a delivery date before feasibility was checked.”
- State what is known and what needs validation.
- Involve the responsible technical or delivery owner.
- Agree when the customer will receive an update.
Define success evidence
Illustrative pitfall
“We celebrated kickoff without agreeing what successful use meant.”
- Agree observable milestones and acceptance evidence.
- Separate training attendance from workplace use.
- Confirm who reviews progress and signs off decisions.
Close the kickoff clearly
Illustrative pitfall
“Everyone left positive and nobody knew their first action.”
- Read back actions, owners and dates.
- Record unresolved questions and their decision route.
- Confirm the next review and required inputs.
Put it to work
Turn the checklist into focused practice.
NewSkilz shapes practical training around your people, goals, real working situations and approved content.