With a background in linguistics, user research and QA
Rebecca starts out in product support building rapport with customers, enjoying hearing about their needs
Her enjoyment grows as she observes users in action, engaging in user research to develop a more profound understanding of the problem
Rebecca puts this new knowledge to action and a spark is lit as she brings a feature from discovery to launch and optimisation
Business needs required Rebecca’s robust QA mindset to take up role as principal tester, leaving the world of design for QA
However she could not shake the thoughts of design away and felt she could better solve business and user needs by being present for design and strategy
Rebecca takes the UX immersion course with CareerFoundry to formalise her previous experience - eager to learn more and solve user needs
And here she proudly stands, with both practical and theoretical design experience to apply her unique perspective to UX problems with her QA and linguistic background
As a UX/UI Designer
my philosophy focuses on enhancing human experiences through intentionality, reflection and continuous improvement.
UX is not the cherry on top of the cake.
It is a fundamental ingredient for creating human experiences.
I do however enjoy cherries
This is all part of the cycle of continuous improvement, through which we iterate and optimise to enhance experiences.
Immersing myself in the world of
Voice User Interface Design
Concocting Patisserie
I get so much pleasure from experimenting with cakes. I enjoy sketching out my ideas, concocting unusual flavour combinations and learning new methods.
You’ll find me breaking down a complicated cake into manageable steps that I can work on solo as well as with my cake-adoring friends. Some of whom require support as they lack confidence - so it’s my duty to empower them for the good of cake!
In my previous experience, we didn’t use many formal methods for design; We didn’t have formal documentation like empathy maps or journey maps or user flows. But just because we didn’t have this documentation doesn’t mean that I didn’t think deeply about what these deliverables represented. I did - and thanks to my studies and relations with my mentors, I now have a formal language to use and a way to a visualise and communicate thinking to explore and gain consensus.
This doesn’t mean that I’ll be applying every technique encountered to every problem and every project, but it does mean that I have a toolbox of techniques to choose from.
I’ve experienced real-world projects and the dynamics involved with internal stakeholders, technical constraints and legacy applications, days where you fix one bug and several appear in its place holding back release. This is messy. My approach before was ‘I do what I need to do at the time’, and though UX courses may present the materials in a linear fashion, with no curveballs. I’ve been hit by those curveballs and know that my approach still stands: ‘I do what I need to do at the time’ - however this time it is backed by a more thorough understanding of design thinking.