Test & Hold Design
Problem: “We need a permissions based web app for maintaining a new automated system. The system helps safeguard members from buying and consuming contaminated food, prevents an expensive recall process, and preserves the company’s brand image.”
- Solution Architect, IT Department, Costco Wholesale
Discovery
Learned early that the Project Team was wanting to create an internal facing portal web application that would serve Corporate Employees, Call Center Employees and Vendors.
After some discussion and convincing the Solution Architect and Developer agreed that our web app should be built using the Material.io components library.
I spent time investigating common design patterns for web apps using this library. I also spent time reviewing the technical design specifications, flow diagrams, and story business requirements.
Design
After a few onboarding meetings, the SA and I began sketching ideas as we gradually worked towards a first draft. We used the first draft to confirm the direction with the BA, Dev and PM.
Next, I spent time putting together a high fidelity mockup that was then used to present our proposed solution to the business.
The business was really excited about the direction, but still wanted several adjustments. We iterated on the design and came back for a second round. In that round we got their approval to move forward with development.
Handoff
After getting approvals from the UX Team (my peers), the project team (technical feasibility), my management, and finally the Merch team, I was cleared to hand the design off to have it developed.
Since then I’ve been providing post handoff support.
When the dev had the first draft ready for review, I conducted an assessment of the developed solution against what I had handed over. In my assessment, I indicated discrepancies and provided a usability severity rating so that they could prioritize based on their tight deadlines.
Relationship with…
Project Manager
The PM gave me core team member names, a project charter and deadline information. After initial onboarding discussions with the BA and SA, I gave the PM and the rest of the project team UX strategy and time estimates.
Developer
The Dev gave me insight into what design language I needed to understand in order to turn out a UI design that is accomplishable. They also gave me UI technical feasibility approval. Using mockups and design specifications, I gave the Dev clear and exact description of the desired final products appearance, interactions, and accessibility traits.
Business Analyst
The BA gave me high level business requirements. They also helped me connect with Business Users. Using research and mockups, I helped the BA identify, clarify and confirm Business User requirements.
Quality Assurance
The QA gave me ideas and insights into how we might adjust the design so that it is affordably testable. Using design specifications, I gave the QA clear and exact description of the desired final products appearance, interactions, and accessibility traits.
Solution Architect
The SA gave me technical system feasibility and a high level solution plan. Using research, sketches, and mockups, I helped the SA hone in on what they wanted to propose to the Business Users.
Business Users
The Business Users gave our project team a problem to solve. They also gave the team specific UI requirements, expectations and features. Additionally, they gave final approval of our proposed solution. Using mockups, I helped the Business Users see what their UI idea could look like so that we could iterate on the design or finalize the plan. Finally our project team gave the Business Users a working solution that met their expectations.