View source for Using personas as representations of users in application design and development

Using personas as representations of users in application design and development / ← Best practices for developing personas

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

== How personas are used in design == Personas are a design tool that help you group users according to the responsibilities that they assume within a process, the cases on which they work, and the channels that they can access. This grouping provides for a more granular level of control over the user experience, from defining which stages of a case belong to which type of user, to customizing the interface to include only the information that a specific role requires. You can create as many personas as you like and use them as reference for building access groups in your application. However, think about your scope as you develop personas for a specific feature. The size of components, UI elements, and action areas should target the proper device size and persona. For example, because Pega allows multiple app views in a single application, one can easily create a simplified mobile and chatbot view for end-users and a back-office view for employees, each using the same data and processes but displaying in different views based on persona's needs.

Return to Best practices for developing personas.