More on Personas

If you saw
this blog post on personas and user stories, you’ll know that personas
are created characters based on actual end-users (in our case, UVA employees)
who will be using the newly implemented system (Workday). A different user
persona is created for each type of employee that will be interacting with
Workday, and the FST team will keep these personas in mind while building the
Workday tenant to ensure the different needs of UVA employees are met.

During this
month’s Steering Committee Meeting, FST shared a bit more information regarding
how the team is using personas.

For example,
it’s important to keep in mind that one employee can have multiple personas
depending on what information you need to access. These multiple possible
personas will help the functional team think of transformation opportunities as
they build the system.

Also of
note, the personas the FST team are using will not determine security access.
Personas are only used for the moment as a guide toward improving the system. Who
has access to what features will be discussed in greater detail at a later
stage in implementation.