Are you overwhelmed in the Process of User Experience? Don't know how to start a new project? what should be the process? which is the initial point? As I have worked alone in multiple startups in past 3.5+ years, I know this feeling of loss in the process. let's start with the important step to keep in mind when starting a new project/exercise.
I've defined the overall process of digging the problem to deliver the solution. which is as below.
- Define Problem
- Deliver Solution
In Discovery, It's important to understand End users who are going to interact with the final Product with keeping the business idea in mind. A problem can be solved in multiple ways but after understanding the end user's requirement you'll come up with a more insightful solution. In this step, you can talk/Interview end-user, Observe their routine. This is how you'll be able to put yourself in the shoes of the user.
Tip: Divide requirements into two categories, first put all the "Need to have" and another is "Nice to have". This exercise will help you understand what is the major pain points should be solved at a higher priority.
2. Define Problem
As we've done discovery and as result, we know the pain points of user and also you'll have much more information about user's schedules and problems user-facing. Now it's time to define what is the actual problem you are solving for End Users and make their life simpler, add value to their life.
Tip: Try to Define the Problem in a little brief so, your other team members can understand the scenario of the problem you are trying to solve because according to this definition(Problem Statement) you are going to find the best suitable solution.
Here design means start sketching solution with Note & Paper and try to find as many as possible solutions(Weird one as well, but keep user needs and business goals on priority). start wire framing and connects dot of every function you've finalized in the "Need to Have" category, Process all the information you collected during Discovery, which will help you to define the best suitable solution. try to discuss with your other team member so you can though through multiple perspectives if you are missing anything.
Tip: Never fall in love with the first solution, try to look into the competitor's solutions, analytics that will convert your Ideas invalidated proof.
Testing the solution you've finalized will let you discover the broken link of the solution. again is this solution fully solve the user's pain point, is it reliable in every situation give it a wild thought, you can also test the prototype with the end-user and get feedback on what they think of this solution and iterate the solution.
Tip: Observe, don't tell them what you've thought through let them interact with the solution, ask them to share their experience.
5. Deliver Solution
And here you are ready with a detailed and briefly defined solution to handover to the developer(Or to the next level). coordinate with them to understand each and every detail you've defined in the solution. and also check whether they've understood the specification as you thought the final product would be.
Note: To avoid confusion from the developer end, try to provide scenarios(both, Best & Worst case) in the detailed documentation.
It's the process of iteration, whatever process you adopt to solve problems, there'll always going to have a scope of improvement. so keep processing whatever information you've gathered from the user. Try to drive deep in the problem and iterate the process to add value to the end user's life.
Let us know, which process you find helpful!!