Forms are used to identify what tools and tactics performed best, such as, a gated whitepaper had a 12% conversion rate. Make sure to capture the KPI associated with the tool or tactic that performed well or poorly. (Sample KPIs include time to resolution in customer support, reduced cart abandonment, form completion) Objectives Identifying the team objectives is critical to planning for the site. This gives you insight into what the website needs to do for the people in the company to succeed in meeting their goals. Where do they want to be in 30 days, six months and one year? What goals would they like to hit (KPIs)? What tasks would they like to automate? What things would they like to be able to do? (gate video content, A/B test marketing campaigns, eliminate live training sessions) Where do they need to be in 30 days, six months and one year?
These will align with your “want to be” questions with one additional component. Any licenses, agreements, or technical requirements Italy Phone Number List that impact timing. There are often previous agreements or support changes for a platform that are expiring. Keeping an eye on how these impact development decisions is critical to avoid 11th hour “oh no” moments. Data Organization I use Google Sheets for data review that require other eyes. It’s a great collaboration tool to avoid version control issues.
Set Up Break down the tasks and goals the site needs to deliver by department and function analyzing goals against tasks. % of the total customer support that the site should handle (goals vs. % handled today) % reduction in shopping cart abandonment handled by exit offers (goals vs. % handled today) % of lead conversion from gated content the site should achieve (goals vs. % handled today) With this process, you now have a team set up for ongoing knowledge transfer, a list of the tools they use and tasks they perform related to quantifiable goals (KPIs), and other looming deadlines that will impact the security.