Software Engineering, Project Management, and Effectiveness
At patterns & practices, we introduced personas a few years back to help design user experience for our deliverables. Personas helped with a few things:
I think of a persona as a specific (yet generalized) instance of a role to "personify" and represent what users that play that role, might be like. While we originally argued over the details of the personas, a great by-product was that we focused on the distinctions across our various customer sets. This helped reduce ambiguity during product design. It also helped us make calls on where to put our resources and effort.
One important lesson we learned was that personas weren't as reusable across groups as they originally seemed they might be. In other words, we couldn't just grab a set of personas from another group, and call them our own. Instead, it meant time and effort to build a set that had specific meaning for our group in the context of what we build. While our naming overlapped with other groups, we had our own set of reference examples.
Here's the core personas we originally used:
Here's additional personas we used:
For sharing the persona information, we used a simple template
While that was a practical set of info for quick sharing, the research behind the personas included:
Since our earlier days, I think we've shifted from persona-based design to more customer-connected engineering. We have a lot more direct customer involvement throughout the engineering.
If you're looking for yet another way to help you prioritize your backlog or to help you shape your product's
If you're looking for yet another way to help you prioritize your backlog or to help you shape your
As one component in a customer data gathering project that involves many on our team, Pat Litherland