Internal Accounts

A major undertaking for Recreation.gov was to create a common set of user roles that could manage federal lands and employees. These roles had to be common across twelve unique agencies yet fit into a small number of categories to make administration of the site manageable.

For this Internal Accounts micro-service, I acted as both UX designer and product manager. To create a useful and accurate framework with full client buy-in, I held a weekly Subject Matter Expert (SME) meeting and invited representatives from all the major agencies. Throughout the week, I would collect questions my team encountered and enter them into a Jira Confluence page. At the weekly SME meeting, I showed an agenda of the meeting topics, went through the proposed design/framework, asked questions, wrote down new questions, created action items, and assigned action items to people present. People in the meeting had access to the Confluence page and could reference any past meeting to see questions, answers, and links to designs.

With this system in place to create content, I set about designing a way to:

  • create and manage an account for yourself (including emails, passwords, contact info, etc.)

  • create and manage an account for someone working at a site you own

  • set limits of access for seasonal workers

  • place a site within a hierarchy of regions/districts, parks/forests, and down to individual campgrounds

  • allow managerial access to a distinct combination of sites/employees that may or may not fit into clear hierarchies

There was a user interface that we designed, developed, and iterated upon for months, but the brunt of the work for me was mostly in coordinating with SMEs to create rulesets for the developers to implement.