My Process
Designing an intentional solution ⬇️
Discovery exercises - these provoke questions like why, why not, and for whom
Understanding the problem 📝
To get up to speed on the product or problem, it is imperative to get context. Interviewing users and/or internal team members are helpful to understand current workflows, opportunities, pain points, and constraints. These charge up relevant solutions.
Tools Used: UserZoom, Google Meets, FullStory
Competitive analysis 🔎
This is useful to see how the product stacks up with various competitors and the unique value it proposes. Acknowledging that not all problems are unique, looking at competitors in different verticals will shine a light on what worked, what didn’t, and what to implement in the desired solution.
User Research 👤
Every product intends to solve use cases for the end user. Including usability tests or interviews in the design process assures solutions are objective and provide value.
Tools Used: UserZoom, Zoom, FullStory
Ideation exercises : these exercises include a lot of conversations about trade-offs and final decision making
Ideation 💭
Now that a solid grasp on the product and the context it lives in has been made, intentional wireframes and fat marker sketches can be drafted quickly and communicated via a short feedback loop each time.
Tools Used: Miro & Figma/Figjam
Design & prototype 🎨
Wireframes have been refined with consideration to stakeholder feedback. Now, a design system comes into play to assure things are consistent and ease dev-handoff. Prototyping the designs to share with stakeholders is also a helpful artifact.
Tools Used: Figma, Sketch, and Abstract
Await outcomes 📊
The design process starts and ends with a story told with data. After we ship code (the only way we deliver value), the team will refer to the cadence of metrics we set to track. We will benchmark our design solution and learn from the data.
Tools Used: Looker, Pendo, Fullstory
Process in Action
Understanding the Problem
The problem with FPL’s continual improvements to their Energy Dashboard was that their demographic wasn’t easily receptive to change. The changes to the UI disrupted the design patterns users were used to, thus, preventing them from understanding their energy usage
Competitive Analysis
Shown here I am doing my due diligence in understanding the niche of recruiting software to empathize with busy recruiters and see how the best platforms leverage data visualization.
User Research
At LSQ, I was able to lead user interviews and usability tests with the internal accounting team to sub for the end users. It was important I acknowledged they were power users and the Report Center would have to be inclusive to non-tech savvy users.
Ideation
After building a solid understanding of the product, I began designing mid-fi’s and cross collaborating with product managers, developers, and designers to get approval on how the designs set out to help users accomplish task flows with the LSQ Report Center.
Design
I quickly transitioned the mid-fidelity wireframes into hi-fidelity screens with the Zoho Recruit Redesign. To keep things consistent with Zoho branding, I implemented a design system. It was important to have attention to data visualization and dashboard design in this project to help recruiters make actionable insights at a glance.
Prototype & Test
Being able to make the Report Center screens come to life with Invision was great to communicate the value of the solution to stakeholders and demonstrate how it would check off the pain points the product needed to solve in the beginning.