What I can do
Identify the problem to be solved
Leverage data analytics and behavioral insights to inform decision-making.
I have experience observing metrics and stats that enable me to 'sense' what’s going on, identify high-impact research opportunities and where we should focus next.
Often, this means, simply put—if there's been a drop in the number of people completing their onboarding questions—it's time to conduct research into that decline. In my view, what's important is trusting the process, with a bias toward action.
Previously, I have leveraged data and behavioural insights to inform decision-making on both niche projects as well as feature rich products, over time.
Learn about user needs in relation to the problem.
Short heading here
I've done a lot of user research; I like to take a speculative design approach, creating designs and prototypes early, and putting them in front of users as soon as practically possible.
I have experience conducting user studies, semi-structured interviews, ethnographic observations, workshops, and diary studies to uncover concrete facts about users' lives and perspectives without bias, focusing on their past actions rather than hypotheticals. i.e., 'What did you do last time?' Not; 'Would/might/could you ever?'
I am good at pinpointing user needs and mapping them to user journeys to uncover opportunities, and if desired, nudge user behaviour.
.jpg)
.jpg)
Identify the right solution.
Short heading here
I've defined and tested ideas through interactive prototypes to narrow down solutions, features, and concepts based on user input—at times as the only designer in the team.
In my view and experience, this approach always helps to de-risk time and resources.
I have considerable experience turning ideas into tangible experiences via initial sketches, wireframing, and hifi' designs—whilst ensuring designs are both engaging, and technically feasible.
Ensure the solution is the best it can be.
Short heading here
One of my strengths as a designer is remaining entirely outcome independent during iterations, approaching changes without bias or being wedded to any one layout or UI pattern.
I believe in testing designs in code as soon as possible with real data. This is often reveals technical issues, bugs or problems with usability the fastest.
Moreover, in my experience, this drives real-world validation regarding usability, copy, navigation, and ensure that it offers real value to users.
.jpg)
Launch.
Short heading here
Finally, from launch, I embrace the 'release early, release often' approach.
From Beta to UAT, I prefer basing product changes on real-world feedback—whether this is using user research, analytic tools, or just a carefully worded Slack message.