Signed in as:
filler@godaddy.com
Signed in as:
filler@godaddy.com
A deep dive into WorkForce Software
Foundational research
Iterative design
Collaborative build
As the first impression for the application, the home page was visually uninspiring and provided low task value.
The current home page served as primary navigation, making the user go back and forth between deeper content and home. In addition, it did not support quick access to common employee functions like clocking in and requesting time away.
To understand requirements and workflows for the Hub and new Assistant concept, I performed on-site contextual inquiry and phone interviews.
Since navigation was a core concern, I also performed a closed card sort study to explore a new navigation structure.
After working with stakeholders and end-users to understand their needs, the Hub and Assistant were envisioned as a "one-stop shop" for employees and managers. Sketches and low-fidelity designs were created to illustrate the concepts and start the iterative testing and design cycles.
Through direct customer feedback, we learned that employees and managers wanted to quickly take care of business when working in our app. Providing tools and information on the landing page gave time back in their day to move on to more urgent matters.
However; there were regrets…
Usability testing found that most managers weren’t interested in the content on the Hub, and similarly, most employees weren’t interested in the content in the Assistant. In addition, managers with a lot of employees were quickly overwhelmed with Assistant cards. We had to pivot on the already-implemented designs to include options for filtering and personalization to help address these concerns.
Usability testing found that most managers weren’t interested in the content on the Hub, and similarly, most employees weren’t interested in the content in the Assistant. In addition, managers with a lot of employees were quickly overwhelmed with Assistant cards. We had to pivot on the already-implemented designs to include options for filtering and personalization to help address these concerns.
Timesheets are core to many human resource management systems -- they not only ensure work-related record keeping for the business, but more importantly are how an employee is paid.
The current timesheet relied on access to a desktop computer, since it wasn't mobile responsive. In addition, the outdated interface had led to a loss in sales to more modernized competitors.
Because timesheet is highly configurable and can contain expansive data sets, we worked closely with product owners from Day 1 of the redesign.
Using discovery workshops and participatory design, we identified the core components and features for the first release. Narrowing the initial scope and critical end-to-end workflows early in the process was essential for the design team's success.
Timesheet mockups went through many iterations, starting with whiteboard and paper sketches and then low-fidelity system mockups.
A cross-disciplinary team was formed to review these initial concepts for business and user goal achievement, technical limitations, and brand representation.
At each stage of design, we refined the concepts based on product owner input and usability test sessions, gaining a deeper understanding of the use cases for timesheet across industries, and how users interacted with their timesheets.
"Final" designs for timesheet reworked critical functionality for time entry and management, focused on the desk-less worker.
Accessible design principles were applied to the design set, and we capitalized on standard UI affordances using Material design.
The modern, simplified interface gave WorkForce a strong competitive advantage, and attracted attention from high-level competitors.
There is more work to be done...
Exceptions are errors or notes about entries for a timesheet. Although this list could be long, I prioritized displaying them in simple severity order, with a link to the problematic date. I opted for a pragmatic solution to meet basic user needs for the first release. Options to consider for future are filtering or sorting by other data points.