Meet with stakeholders, developers, product team to members to determine business goals pertaining to the project at hand and the long-term vision. Outline an extremely rough vision of features to solve assumed problems.
Competitor Comparison Matrix
An audit/review preformed of competing products, websites, or apps; creating a report that summarizes the competitive landscape.
A fictional ideal user based on non-hypothetical geographic and demographic data. As the project progresses and more research is done, the persona evolves to incorporate more accurate needs, goals, and observed behavior patterns of the user
Often multiple pages crammed into one, this document serves as an outline of desired learnings from very specific targets. Specific project objectives, features, and team roles are defined to keep all participants of the research informed.
Interviews help you gain a deeper and accurate understanding of people’s behavior, thoughts, and motivations to address and solve a problem. A skilled researcher will delve past superficial words and derive truth from user actions. Afterwards, the team gathers to compare notes, glean insights, identify similar patterns across all users, and group them under logical pillars. Finally, a team member is tasked with compiling everything into a succinct key takeaways document.
Watching a user interact with an existing product similar to the one your team is creating yields a gold mine of both usability and feature frequency vs hierarchy information. As a UX designer, this is the most valuable form of usability research. I’ve saved departments hundreds of hours and tens of thousands of dollars a week by simply observing and designing around usability black holes.
An integral compilation aligning user behaviors and features to support those behaviors, grouped into logical pillars. Eliminate feature bloat and identify opportunities for unsupported behaviors.
Red Route Analysis
A visual application of hierarchy to product features. Assign the tasks with the highest frequency and most adoption the highest priority. When designing these features get visual dominance with accessibility priority.
The five-phase framework incorporates all of the foundational work done up to this point to expedite the final design through rapid prototyping and user testing. Sprints empower your team to reach clearly defined goals in a specified time frame. This Regimented approach encourages user-centered thinking, innovation, transparency, and vision alignment.
- Map how a customer will use your product to solve a learned problem
- Sketch multiple ways that incorporate foundational work to solve this problem
- Decide on 2 or 3 prototypes to build and test
- Design a low fidelity mock to test
- Test your prototype with users. Take the learnings from this test and iterate as needed. Once the prototype is in a good place it’s time to design the front-end UI components developed
There are many approaches to this. Currently, my team and I create Angular components in a UI library that developers can easily reference. We then leverage those components in layouts and work closely with developers to wire up the components to API services.
A small but important note; one size does not fit all.
Above is the current UX process that my team and I have crafted to fit the needs of the projects we’ve been taking on in Fintech. While the staples of research, design, and development persist in every UX process, these specific steps in this specific order will most likely not work when applied to a different industry, or even a different team in the same industry.
For a UX process to work, it has to be tailored to the specific user and industry that it’s intended for. Additionally, it must cater to all of the different departments that end up interfacing with it.