Many organizations use Persona in order to describe a target audience in concrete terms. So what is actually a Persona as a meta object? There are three alternatives to choose from:
- Position
- Person
- Person Role
Position is reserved for the organization hierarchy so it is easy to exclude it.
The short answer is that Persona is modelled with O52 Person Role.
The choice is made based on two observations:
- A Persona is by definition an archetype for a customer segment.
- Personas is usable in User Story (IM42) since it can represent a more detailed and nuanced image that ''customer'' and get completed with specific goal and requirements.
Read more about Personas at the end of this page.
In the following meta models, it is clearly showed that it is the Person Role (O52) which is the meta object used in enterprise architecture. Person (O53) is used only for staffing roles ad
Briefly about Persona:
”A more distinct and personal image of the customers of a business.”
All meta objects and relations that are used in a user story could be used for Organisational Role (O52).
More on Personas
The idea behind Personas is to create a more distinct and personal image of customers of a business.
Personas are built up as follows:
- A Persona is an archetype for a customer segment.
- Create multiple Personas, but not for many.
- Give them personal names and photos and describe in a sentence what is important in terms of value proposition of the business.
- Personas should be based on facts. Do proper research.
- Cover the 7 C:s according to the 7C method (There are multiple different methods)
- Create the Persona in a format which makes it easy to communicate it in the business.
Thanks to Ralph Poldervaart at Persona Company.
Source: https://www.slideshare.net/ralph_poldervaart/how-to-build-a-persona
The 7C Method
Example of Different Personas
Example for how a Persona could be described more in details (The example is in Dutch but It makes the point anyway).