Users gave their feedback on Policies
Findings "Free Explore"
- Users largely ignored the "top of the screen" and were immediately drawn to the center of the page
- Users assumed that this was for EE self service based on the screen
- The purpose of Policies was not immediately clear to users "just from the screen"
- Once context was explained in, they viewed the concept favorably and understood its value and purpose
Users were then asked to "create" their own 401K Policy
Overall feedback was very good for policies both conceptually and for the "data" chunking strategy within policy creation.
Findings "Template"
Users clearly understood the use of "template" and workflow for them and how they could potentially have more than one 401K policy that they would need to create.
Findings "Naming"
Users understood the naming entry convention and could easily identify how this would help them downstream (pay statement, GL)
Findings "Eligibility"
Users quickly identified the use and purpose of eligibility grouping, most unprompted offered:
"I assume I would have already created the eligibility groupings before creating my policy here."
The control for "How soon after hire" was adjusted after Atlanta to allow for punching in of numbers, users chuckled at having to press plus 180 times for 6 months of days.
Findings "Source"
All users understood source convention, however:
- Most simply wanted a "Gross" pay option vs. 3 check boxes
Findings "Dates"
- Default setting for "How often" should be "each pay period" within the dropdown
- Users preferred the language of "when will this policy begin and end"? vs. effective which caused some confusion