Beeline Project: Supplier and MSP Product Lines

CLIENT Beeline SAMPLE PROJECT #1 Adding Supplier and MSP product lines (covering the emphasize and define phases of the Design Thinking process)

CLIENT Beeline PROJECT Adding Supplier and MSP product lines (emphasize and define phases) KEY PLAYERS PROJECT DESCRIPTION Beeline helps their clients manage contract labor, from beginning to end. We were changing the legacy app from one do-it-all interface for all users into individualized, persona-based feature lines. Chris d Aquin Judy Bumgarner Daniel Sudhindaran Cody Abraham Sarah Schuler Two consultants (For a fresh perspective and to help conduct user research) Sr. Product Designer VP of Product Strategy Director of Product Design Product Manager Product Manager From Fuego UX BUSINESS PROBLEM Hiring a new contractor is lengthy, complex, and involves multiple touchpoints from four different personas. How can we: make common roadblocks in the process easy to identify and overcome? eliminate confusion by providing clarity to current statuses and conditions? provide each persona with easy access to their most common priorities? HOW WE ATTACKED THE PROBLEM 1. Two months of product and user research 2. Task priority surveys sent to ~500 users 3. Outlined the different journey maps for each persona 4. Design Thinking/Brainstorming sessions to put it all together

CLIENT Beeline PROJECT Adding Supplier and MSP product lines (emphasize and define phases) HOW MANY BRAIN STORMING SESSIONS? After three sessions, we had our master journey map! This identified how all different product lines interacted and what features to add. We were ready for the next design phase wireframing.

CLIENT Beeline SAMPLE PROJECT #2 Prototype testing of new Talent product line (covering the iteration and testing phases of the Design Thinking process)

CLIENT Beeline PROJECT Prototype testing of new Talent product line (iteration and testing phases) KEY PLAYERS PROJECT DESCRIPTION Beeline was redesigning the interface shown to contractors (the talent persona) when they entered hours on their timesheet, as well as adding additional usefulness and functionality. A random mix of employees in the Beeline office who didn t have any knowledge of the project. HOW I ATTACKED THE PROBLEM We didn't need a lot of users to test how smoothly users would progress through the account creation process and if the information architecture made sense. BUSINESS PROBLEM We had gone through several wireframe iterations and had our first prototype. How well did it work, especially for someone using who needed to create an account and was using it for the first time? I spent three hours walking through the office with a laptop, grabbing people who were away from their desks for a quick 10-minute prototype test.

CLIENT Beeline PROJECT Prototype testing of new Talent product line (iteration and testing phases) WHAT DID WE DISCOVER? With just seven prospective users, we found the prototype was easy to navigate and understand. BUT We discovered some specific usability issues with password creation, confusion over section labels, and users kept wondering if their updates were saved or not. AND THE SYSTEM USABILITY SCORE (SUS) SURVEY REFLECTED IT The design scored well for ease-of-use but failed in areas of confidence and consistency. Despite the poor scores, this test was successful because it led to specific changes in the next iteration. SYSTEM USABILITY SCORE (SUS) SURVEY RESULTS 1 2 3 4 5 6 7 8 9 10 I thought the system was easy to use I found the system unnecessarily complex I would like to use this system frequently I would need a user guide or customer support to use this system I found the various functions in this system were well integrated I thought there was too much inconsistency in this system I imagine most people would learn to use this system very quickly I found the system difficult to use I felt confident using the system I needed to learn a lot of things before I could get going with the system Anonymous Anonymous Anonymous Anonymous Anonymous Anonymous Anonymous 4 4 5 4 3 5 5 2 2 1 3 4 4 2 3 3 4 3 2 4 5 1 1 1 2 3 2 1 3 5 5 3 1 3 2 1 2 1 2 4 3 2 4 5 5 4 4 4 5 1 2 1 3 3 2 2 4 4 4 3 2 5 5 1 1 1 2 2 1 1 4.3 2.7 3.5 1.7 3.2 2.3 4.5 2.2 3.8 1.3 *Avg Answer Target 4 and over 3.3 2 and under 2.3 4 and over 2.5 2 and under 3.3 4 and over 2.2 2 and under 2.7 4 and over 3.5 2 and under 2.8 4 and over 2.8 2 and under 3.7 ^Usability Score (0-4) *White and green blocks show scores that hit the desired mark. Pink and red blocks show where the usability score doesn t measure up. Total Avg Usability Score 72.9 Grade C