Case Study:
Purchase Approvals App

The Brief

Summary:

Users of the Enterprise Resource Planning (ERP) system were falling behind on their approvals, which was slowing down the business process.

Approach: 

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine

Without a development team, it was clear that the organization didn't have the ability to deliver from within, so the first challenge was to find a partner, build a team  of internal resources and get the budget approved. Assuming the role of lead Product Designer/Manager, I engaged a Project Manager (who I mentored as Scrum Master), and a a development partner, who provided a UX Researcher, UI Designer, Developer and Architect to round out the team.

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine

I'm an advocate of Lean UX, which helps move the design process along without waste.  Using this approach, we identified our hypotheses, and defined the Problem Statement for our system. We validated our hypotheses through user research and interviews and refined the problem.
(Some advocates recommend the integration of Design Thinking, Lean UX and Agile as a mature method of product design and delivery. I'm all for this in an environment where there is buy-in and adequate resources assigned to achieve this.)

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine

The prototype was developed by our development partner (using InVision), and reviewing in regular product demos in the early stages of the project. In the later stages the product in development was demonstrated.

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine

Once the prototype was showing signs of completion, we ran some user testing sessions to ensure that the UI was intuitive. I love this part of the process, because you are able to connect with real users of the system, not just the project sponsors and leaders. It helps empathize with the day to day users, get great feedback ,identify issues with the design early and work on better solutions before committing to development.

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine

Armed with feedback we take back what we learned from the users and use that to fuel new ideas to solving issues in the user interface and to improve the flow of the application. 

1. Build a team    2. Define the problem      3. Prototype       4. User Testing      5. Iterate & Integrate      6. Build & Refine