Improve Employee Data Entry
In order to achieve our key result which is to generate 5% increase in revenue by Q4 2022, we need to evaluate our existing customer journey to identify pain points that might have hampered the revenue growth.
By addressing those pain points, we expect an improvement in;
monthly active users growth rate which has been slowing down from 3% on average in last year to 2% on average year to date. monthly churn rate which has been increasing from 0.5% on average in last year to 1% on average year to date.
Improvement in monthly active users growth will impact the new annual subscription while lower churn rate will help us with subscription renewal. Both will help us to increase overall business revenue within this quarter.
The problem that we want to solve in this project is how we might help the admin input the employee data easier and quicker so that they can start using the features sooner.
Based on our research conducted in August 2022, 20% of our customers think they are frustrated with the employee information entry process because it requires too many employee data to be pre collected at once. This frustration has become the reason of 30% of bounce users and 50% of churn users.
The problem also got the highest RICE score compared to other problems we identified because it will help both new and existing users and impact both new annual subscription and renewal revenue.
Simplify the employee data entry process and make the completion progress easier to monitor
We want to ask for less information requirement by prioritizing only mandatory information in the 1st time onboarding process. We also want to help admin monitor the completion progress more easily so they can estimate the timeline.
Goals & Success
What does success look like? What metrics are you intending to move? Explain why these metrics are important if not obvious.
Give an overview of what we’re building. Provide an organized list of features, with priorities if relevant. Discuss what you’re not building (or saving for a future release) if relevant.
Show some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works.
⭐️ Now you can embed private Figma files, too!
Open Issues & Key Decisions
Keep track of open issues / key decisions here. Sometimes, certain decisions are made that might feel controversial; document these here so people know that the discussions have happened and there’s strong awareness of the tradeoffs.
Identify any relevant milestones (e.g., a Dogfood or Beta milestone) that people should know about. Make sure to show when you’re expecting to publicly launch, too.
Make sure you answer all of the questions below and involve necessary stakeholders.
Instructions if "Yes” (or unsure)