At a recent event, we were asked about the persona pyramid. In this post Enrique Brands explains how the persona pyramid is a concept that can be used to determine how your requirements, development stories and output of those can impact user personas both above and below you.
By utilising this pyramid, we can determine which personas either need to be involved in the story development, be consulted or those that are consequently impacted.
When it comes to IRM, we typically have the following key personas:
1. SLT (Senior Leadership Team)
2. Head of Development
3. Process Managers (Compliance, Risk, Audit Managers)
4. Process Analysts (Compliance, Risk, Audit Analyst)
5. Employees (Control/Risk Owners, Issue Owners etc)
“I would like to have a MI dashboard that will show how many controls are compliant against non-compliant, how many attestations are outstanding and how many active issues we have against broken controls.”
In this case, we can use the persona pyramid to examine how many personas are impacted by this requirement.