I talk about personas a lot, and with good reason – it’s how we in all facets of SDLC get our heads around our customer, our audience.
If you want to build anything you’re gonna need a persona.
Most of the personas we create represent groups of people who actually use our product – they help us identify and communicate critical features of our product and its design. They also serve to fortify our user stores and maintain focus on the users’ priorities when talking to anyone in the organization.
Analytics personas tend to be different, in that they often represent users who may not directly use your product, for example, your persona may be managing the process your software is augmenting, or the people facilitating that process. These users rely on the data the system collects to measure, analyze, and then act.
Analytics personas begin like any other (we still want to know about what this specific grouping of users is trying to accomplish) but we also need added specifics related to process and data.
- Who is my boss? ( and who is my bosses’ boss?)
- How do I tend to consume/present information?
- What processes/incentives am I responsible for?
- What am I responsible to report & when (daily, weekly, quarterly…) and to whom?
- What are the pitfalls I scan for that ID logjammed process?
- What incentives am I looking to enforce/improve?
Update your persona library to include analytics personas – it will help your product to correctly address the unique problems your users are trying to solve.