Last year we discussed our motivations for using personas at GitLab, including why they're important and how to create them through UX research. Since then, our teams have had many conversations about improving the design of our product and continuing to empathize with our users. As a result, we created an initiative to fully incorporate personas into our design process. This will help everyone learn more about the different people who use GitLab!
We’ve made several changes in format since the first iteration of personas:
- Gender-neutral name: humanizing the persona while still ensuring that it is inclusive
- Job description: helping your audience learn about what the user does and who they work with
- “Jobs-to-be-done” (JTBD) framework: making the information more concise and easier to digest
- Alternative job titles: understanding how the research findings apply to other user groups with similar needs and challenges
Typically, the most insightful personas are a realistic representation of user needs. They help you understand who you’re designing for and allow other people in all departments of your company to hear directly from users. In this series, we’ll share findings from our recent round of research and highlight what we’ve learned about each role.
Want to learn more?
You can now view the personas in our handbook. Here's a quick summary of what's inside:
- Parker, Product Manager
- Delaney, Development Team Lead
- Devon, DevOps Engineer
- Sasha, Software Developer
- Sydney, Systems Administrator
- Sam, Security Analyst
How does your team use personas in the design process? Connect with us @gitlab, and stay tuned for the next posts, where we’ll dive deep into the findings, limitations, and opportunities of each.