To get things started, we conducted a series of user interviews, both with internal stakeholders (product owners, security team, sales team) and current users of GoToMeeting or GoToWebinar that have previously supplied feedback related to recording. These interviews allowed us to identify user pain points trends and well as the user's overall process when it came to recording before, during and after a session.
User Interview Summaries. The product owner and I conducted interviews with internal stakeholders and external customers to learn more about their processes and pain points.
With the product owner, we created user stories that represented the user pain points we identified from our user interviews, as well as any high priorities items from our internal interviews. We distilled that very long list of user stories into a small initial batch, organized by the user process that emerged from the interviews.
This user story mapping served as a guide as I created the initial set of designs.
User Facing Stories. From the user interviews, it was apparently that users performed distinct activities before, during and after a session. The initial batch of user stories were organized based on this user flow.