-
Notifications
You must be signed in to change notification settings - Fork 18
Design Principles
We designed the PRA Guide based on conversations with desk officers, PRA officers and federal workers who were new to the PRA. In March 2019 we held a workshop for ~20 stakeholders from across these groups to learn more about:
- What they hoped the PRA guide would help them do
- The words they wanted to use to describe the PRA guide in a year
- The words they did not wanted to use to describe the PRA guide in a year
- What could happen to make these items true
You can see the responses to our workshop questions here.
Even among a diverse set of experiences and expertise with the PRA, we heard similar needs, aspirations and concerns. We used this discussion to create the following design principles to help guide our initial site's design and content.
These principles are not set in stone. They should be revisited periodically as the guide grows and as more user research is conducted.
Users should be confident that the site’s guidance is endorsed by OIRA and rooted in PRA realities.
How we can accomplish this:
- Make it clear where information comes from.
- Give current examples from the real world.
- Let users contribute suggestions and edits to the PRA guide.
PRA officials should feel supported by curated, clear guidance and empowered to share the PRA guide with colleagues.
How we can accomplish this:
- Guide users to their next action.
- Provide checklists and templates to build confidence.
- Assume novice. Prioritize the basics.
It should be easy to find and easy to understand guidance on the PRA.
How we can accomplish this:
- Be direct and clear. Make it easy to make choices.
- Show details on request, rather than by default.
- Actions and search should produce predictable results.
It should illuminate how people and processes work together during the PRA process.
How we can accomplish this:
- Connect users to resources beyond the PRA guide.
- Show who and how much time are involved at each stage.