Approach
How I take on a problem
When presented with a problem I have found the best way to deal with it is through some variation of the following steps. Many variables are considered throughout the process, depending on the challenge, but a strong emphasis is put on the need for user-centred solutions. Lets be honest, keeping a rigorous method is never possible, especially in a corporate environment. Not all steps in an ideal UX workflow can always be hit, not all designs can be implemented, when there are budget, timeline and outside limitations, One needs to be flexible in approach. Maintaining user focus is the priority.
Product research
Beginning with initial research, I focus over the product request document. Searching and researching anything relatable or similar to the requirements. Where applicable, I check the existing version and wrap my head around the domain. My domain is UX design, that comes with a necessity to master any area I am working in.
To paraphrase a famous quote:
The first step to solve any problem is to clarify it.
Once I am happy with the amount of information I have about the problem, I move on to competitive benchmarking, the competition, similar functions on other apps and anything else that could be beneficial.
Design update Competitor benchmark
Product request document
Following a benchmark, it is best to get the users perspective in the situation, surveying potential, past and current users. If there is no user body to access, I create a Persona to run through simulations on potential use for ideation.
If there is an existing product, I end this leg of the approach with a usability test, normally with a number of people fitting the target audience of the product.
If there is not, I move onto user interviews to flesh out the requirements and needs from the users perspective.
Personas
Survey results
User interviews - Basic setup
With the bulk of the research completed, notes, benchmarks and surveys all gathered, I find myself with a mountain of raw and unsorted data in various forms from notes, to photos, to videos. The natural next step is to sort through the data, organise it as much as possible and present the research in as strong a way as possible.
Affinity Diagram to layout the specifics of the apps before card sorting or (preferably) user lead card sorting to weed out the pain points and build up the framework of the product. When all of the data is accounted for and dissected, what is left is the project’s skeleton. Ready to be built upon with the UI and design system side of the process.
Card sorting
Flow diagram
The last step of consolidating the information is to create a flow map of the product and how it will be experienced by the users. Turning to my sketchbooks, I begin the planning process of how the product will look, if a design system is in place I strive to use it, if not I begin creating it.
Card sorting
Creating customer journey maps, using the information collected to this point to see how they would feel about several simulated layouts. Applying PESTLE & Swot analysis to the data and the company.
Allowing us to track through clicks and thoughts of the user applying it to the rough low fi sketches ideating not just the screen layout but the flow.
Customer journey maps
As far as I am concerned, design systems are the building blocks for creating an aligned and more reliable product for a designer to maintain and grow. With copious amounts of Sketching done, I present my designs for feedback, doing one step forward where necessary and creating a low fidelity prototype to demonstrate the journey so far and offer an opportunity for testing with users or clients given the opportunity to give us feedback on the product.
Wireframe breakdown
With experience in Adobe InDesign, Illustrator, and Photoshop, among others as well as Figma, Sketch and other digital design software, turning the low fidelity sketches into high-quality designs is the easiest step of my approach. With the sketches digitised and the designs ready, I begin the second last step, the Prototyping stage.
Clickable prototype
Once all of this is completed, the prototype is ready to be user tested again. Feedback will be taken away and analysed, returning back to step 1 in order to fully take advantage of user feedback. And so the process begins again. And will continue, until user satisfaction is reached.
Don't get me wrong, this is not the end.
Next steps include, test, feedback, iterate, repeat. Once the majority of issues/requirements have been met enough for an MVP it is time for a handoff.
This will include feasibility checks, implementation break downs and compromise on scope.
That is the hard part but when the above steps are complete, the reasoning behind decisions and solutions becomes difficult to push back on. No matter how stubborn your PM is!