Personas are essentially fictional characters that represent the different user types that use our website. I’m not a huge fan of personas as they are one-dimensional and can be misleading, for example, our first persona represents a Developer but our ‘Creator’ group could also be a designer for example. With that said, they do a good job of humanising our audience and communicating the types of user we need to cater for, which can help keep the user in mind when designing the site.
Vincent Martinez - Creator
Job Title: ASP.NET Developer
Goal: Download or try Orchard and get up and running
Notes: Very technical and seasoned developer. Has used other CMS’s so will be conscious how it compares. Concerned with the technology, extensibility of the platform and how easy it is to develop for.
David Tran - Researcher
Job Title: Chief Technology Officer
Goal: Ensure that the product is trustworthy and well supported
Notes: Time poor, high level technical knowledge, architectural. Concerned with commercial viability, security and support.
Laura Curtis - End User
Job Title: Marketing Manager
Goal: Evaluate out of the box features, along with admin UI and ease of use
Notes: Non-technical but MS Office proficient. Concerned with ease of use, out of the box features and flexibility.
Summary & Next Steps
I’ve seen personas with tons of information such as bios, income, marital status etc. but for most occasions this information is not relevant and only adds noise. We’ll revisit the personas when we come to do the user journeys, but first we need to establish our user’s requirements, which is the focus of the next post.