They found the website confusing and couldn’t find details on how the ESP worked. We discovered this through demo request tracking and surveying 10 visitors that requested ESP demos. Want to learn/test and how. For example, how a video demo and new landing page with a feature comparison can reduce support requests and increase premium conversions. Our goal is to reduce the number of customer support requests by 10% and increase the premium conversions by 5%. We believe these are reasonable benchmarks due to the percentage of visitors that submit support or more information requests related to the ESP.
Filling in the Planning Chart While departments are presenting the SCRUM leader fills in the chart on the whiteboard: Learned Section: What was impacted Why By what percent Suggestion Section: Type of suggestion (Content, tool, feature, other) Percent of audience it would impact Size of audience they would like to test with Expected impact Italy Phone Number List Time/cost/resources to implement Voting At the end of the meeting, the team will vote on each item. If there is a tie and not enough resources to execute on the top results, then there is a short open discussion and final vote by the product owner. Note that this data is also key in helping management identify the ROI of expanding the team. It is difficult to ask for more resources. Managing the Process Start by getting your whiteboard set up.
I recommend doing the following: On the left: the OKRs established for this quarter or month to keep the team focused on priorities when voting. Underneath the OKRs: the available resources critical to implementing optimization strategies including the number of hours of design, engineering, or content creation. The chart to capture highlights and suggestions from each department presentations, listing each of the departments speaking in order, so they know when it’s their turn.