As we're moving through the designing phase of the Org model epic, we're feeling the need for more formal user personas to aid us in designing for the types of users who will be using the Portfolio version of the registrar. We currently have two documents that help us understand the types of users we design for:
While these are useful documents, we need a deeper level of understanding now that we're moving towards the organizational model where multiple user types/roles are interacting in the same UI as opposed to our current system where we have just domain managers and domain requestors (who go on to become domain managers).
Acceptance criteria
[x] identify the primary user groups that will be users in the Org model / Portfolio experience
While this might focus on federal agencies to start, we should consider how this could expand to the other organization types that we'll open to next (i.e., states, tribal governments). Some example federal agency roles that would use the org model might be: Chief Information Officer (CIO), IT Manager/Director, Systems Administrator, etc. Additionally, as we're diving into member roles and permissions, getting a deeper understanding for these users wants and needs would be helpful.
Issue description
As we're moving through the designing phase of the Org model epic, we're feeling the need for more formal user personas to aid us in designing for the types of users who will be using the Portfolio version of the registrar. We currently have two documents that help us understand the types of users we design for:
While these are useful documents, we need a deeper level of understanding now that we're moving towards the organizational model where multiple user types/roles are interacting in the same UI as opposed to our current system where we have just domain managers and domain requestors (who go on to become domain managers).
Acceptance criteria
Additional context
While this might focus on federal agencies to start, we should consider how this could expand to the other organization types that we'll open to next (i.e., states, tribal governments). Some example federal agency roles that would use the org model might be: Chief Information Officer (CIO), IT Manager/Director, Systems Administrator, etc. Additionally, as we're diving into member roles and permissions, getting a deeper understanding for these users wants and needs would be helpful.
Links to other issues
No response