Self-Employed
2009 – Present
UX/UI Design Consultant
In conjunction with analytics to identify problem areas or dropouts of journeys.
Zooming into problem areas and identifying areas/ideas for improvements. This could be for certain components or whole journeys.
Depending on the context, the output could be lo or hi-fidelity prototypes for usability testing.
The testing sessions would be setup and arranged by me. Participants procured through a third party using screeners I had put together. Writing the testing scripts with a hypothesis driven approach. Looking to either prove or disprove the product/journey theory.
Running the observation room on the day with the team and key stakeholders present. The output would be a report to shared with the team and wider business with key findings and takeaways.
Other testing methods utilised are gorilla testing, appetite testing, A/B testing and multi variant testing (MVT).
I feel it can be hugely beneficial to a Product Team to work in a continuous cycle of:
RESEARCH & DISCOVERY > TEST > LEARN > ITERATE > RELEASE …AND REPEAT >
In all but a couple of assignments I have also written the UX copy for the product journeys, where I always looked to 'Keep it Simple' and inline with 'Tone of Voice'.
At EE & Compare the Market I collaborated with copywriters on the copy.
A product vision is important and should be:
Purposeful, aspirational, concise, achievable and well documented, meeting the needs of both the business and its customers.
I like to think of myself as more than just a Product Designer, also a cultivator of teams. Mentoring and encouraging those with less of a voice into conversation and collaboration.
Running workshops on certain skill-sets or taking the time to give 1 on 1 help to those that need it. I believe that giving back is important for us all.
Steve Ponsford