Create urgency; remind team of upcoming due dates and sales deadlines.
Announce product changes. Welcome new team members. Provide other updates relevant to the day-to-day (i.e. company holidays, policy changes, staff vacations, etc.)
Review one to two potential sales, system or process improvements (i.e. maximizing sales tools, writing great emails, etc.)
Provide an update on who has been hitting their numbers. Recognize top performers.
Share thought-provoking insights, quotes, or other motivational content. Get the team thinking high-level.
What will you take away from this meeting into your day? Open the floor for reps to share their takeaways for the day’s stand up.
Contract Sign Date:
Most engaged user:
Buying Decision Maker:
Team who will be using the product the most:
Customer Success Manager:
Sales Team Member:
Other Key Stakeholders & Their Roles:
What is the main business objective of the customer? How do they generate revenue?
What challenges or pain points does our product solve for the customer? What benefits or features are they most interested in?
Is the customer migrating from a competitor? Why?
How will the customer determine if our product is helping them meet their business goals?
What key metrics will we use to make sure the customer is healthy and we are successful?
Some suggestions (find this information in Vitally):
Number of Users
What is the customer's ideal working relationship? What is the best way to contact them?
How can we tailor the product or experience to better suit the customer? What features do we want to encourage the customer to use based on their business goals?
Were there any hesitations or hiccups encountered during the sales process? How can we ensure these don’t happen during and after the customer handoff?
What do we need to do next to keep the customer healthy? List all actionable steps and the team member responsible for each one.
What are the next steps for the customer? Is any training required? More feature implementation?
Is there any other information worth sharing?
Add Vitally for the suggested metrics
Have each functional team (sales, marketing, product, etc.) prepare and give an overview of how they're running.
Check all that apply.
Write the meeting goal here. (E.g. Discuss agency performance and decide whether to renew for another year.)
What is the main purpose of this sprint? Define key objectives below.
What user stories match the sprint goal? Share this with your team prior to the meeting so they can contribute. Break each user story down into individual tasks. Make sure each task has as much information as possible. Include important metrics.
List out the epics that we're planning to start or deliver during this sprint.
Revisit your definition of "done." Decide on the acceptance criteria that will be used to determine when each individual task is complete. Make sure all of this realistically aligns with your team's capacity.
What potential issues could come up based on the goal and sprint backlog? How can we solve them? Does the scope of work allot enough time for unexpected issues
What were the main insights and discussion points from this sprint planning session?
Get verbal confirmation from your team about the next steps to be taken. Clarify who's completing them and when they should be done by. Note this information here to share and assign.
How will we keep in touch and stay up-to-date about progress? Should we schedule a follow-up meeting?
Tell the story of the company using the fewest number of metrics/charts to properly frame the current status.
Financial performance & forecast (quarterly)
Product engagement metrics
Operations (if appropriate)
Capture learnings from [initiative] and identify what went wrong so we can get better
Put all the details of what happened here. Only the facts. Make sure you answer who what where when why. Customer feedback is good to include if we have it. Include any and all mistakes and what went well. Break up into sections, like “research” “engineering” “customer feedback” “the feature” “marketing efforts” etc.
What happened as a result of the situation? This could include how an initiative performed, what happened as a result of a bug, how a feature fared, etc. Support this section with data
All the details of what went wrong. Opinions are welcome here. Be fair to other people who were involved and let them add to the postmortem or give you context as needed. In the case of bugs, what we could have done better to prevent a problem can be included here as well.
Whatever we learned that will affect how we do things next go around, it goes here. This is the synthesis of everything we’ve figured out from doing the postmortem.
Any action items we have, and who owns each of them, plus dates if possible