This repository has been archived by the owner on Feb 14, 2023. It is now read-only.

Usability Test 2: Firewood Landing Page (September 2020)

Jump to bottom

aQuib Sylvester edited this page Nov 20, 2020 · 1 revision

Open Forest previously designed, mocked and developed a landing page that allows people to choose from different permit types and forests. This design needs to be evaluated and modified to satisfy the needs identified from the firewood permits research conducted by 18F.

Research Details

Goals

To ensure that the Firewood Permitting functionality and overall concept matches the mental model for most types of users.
To ensure that the Firewood Permitting functionality concept works for users familiar with online permit purchasing with the Forest Service.
To ensure that the Firewood Permitting functionality works for users unfamiliar with online permit purchasing with the Forest Service
To ensure that the users can successfully select a pilot forest and permit content efficiently.
To ensure users can successfully access older content within the new navigational system.
To ensure users can view geographical location of neighboring pilot forest(s)
To ensure users' expectations of using Login.gov credentials for special use application matches user needs.

Test session details

1-hour max staging feedback session
Clickable wireframe (posted on cloud)
Recorded sessions notes (Microsoft Teams)
Forest Service (internal): Teams
Public: Teams, Google Meet
Remote meeting

Participants Criteria

Qualitative study consisting of 3-5 participants who have participated in the firewood permitting process.

General Outcome

Findings and Themes

Many considered it easy to use
Most testers often glance through rules/conditions
Most of the confusion experience was due to limitation of application already known to moderators of stage environment (no buy button, Christmas tree language, etc)
Minor confusion with the side navigation ‘Getting a firewood Permit’ (initiate the process to purchase firewood)
Tester value payment options presented

Results and insights

Overall Positive Experience •UI Changes (Non-MVP) - Ensure the full process is available next round of testing