I have experience and interests in a wide range of disciplines including entrepreneurship, software engineering, analytics, product design and management. This allows me to gain unique insights into the product lifecycle and has allowed me to think through the entire customer journey while challenging assumptions.
I believe that in the design process, every stage should be connected to the previous one and provide a reason why the next one is needed
“DESIGN EMBODIES THE PURPOSE IN ITS CREATION - SO BE INTENTIONAL”
Design Principals
01 User-centered design
This principle requires you to put the needs and desires of your users at the center of your design process. By doing so, you can create products or services that are more intuitive, usable, and valuable to your customers.
02 simplicity & prioritization
In any project, there will be a lot of moving parts and competing priorities. It's important to simplify the project's design and prioritize the most important aspects. This helps you focus on what truly matters, avoid unnecessary complexity, and ensure you deliver the project on time and within budget.
03 Iteration
The design process is rarely perfect from the start, so it's important to iterate and refine your design over time. By testing and iterating, you can gather feedback and make improvements to your project along the way.
04 cohesiveness
A cohesive design is one that is unified and consistent across all aspects of the project. This includes everything from the visual design to the user experience to the messaging and branding. A cohesive design can help build trust and loyalty with your users.
DESIGN PHILOSOPHIES
How I like to
collaborate &
my work style
I enjoy sourcing knowledge from various avenues to elevate my growth and project understanding.
This involves engaging with supporters during their Q&A sessions to pinpoint user issues, and meticulously reviewing feedback on our product as well as those of our competitors to gain valuable insights
01 My Engineering Hat
With my background as a software engineer, I know that it is important to the language of the developers I work with. It’s important to understand and empathize with your users as well as your team. With a strong technical background and knowing how to code helps can help me understand the problems the developers on my team faces and allows me to communicate precisely what I want in the product.
02 involve everyone
When creating, PMs and Designers should always try to keep an open line of communication. I try to bring in people who I think have the best insights. I talk to developers, product support agents, stake holders, users and user researchers and bring them into the project as early and as often as I can. I enjoy being collaborative and collecting insights from places one might not think to look.
Design Process
01 Defining The Problem
The first step in the design process is to define the problem you are trying to solve. This may involve gathering data, conducting research, and talking to stakeholders to understand the user needs and requirements.
It's important to always stay on the same page with the rest of the team. At this step, I like to jot down my own hypothesis for what I expect the problem might be.
02 ideate and Brainstorm
Once you have a clear understanding of the problem, the next step is to generate ideas and potential solutions.
I like to bring in developers, other designers, stake holders and customer supports to an ideation session to explore different options. Let your mind go wild and come up with as many solutions as you can. I strive for quantity over quality at this stage.
03 create prototypes
One of my favourite parts of the process! With your ideas in hand, the next step is to create prototypes that can be tested and iterated on. This may involve creating wireframes, mockups, or other visual representations of the solution. The level of details and fidelity depends on how far along in the process I am and what I want to test.
04 Test, Iterate and Test Again
Once you have a prototype, it's important to test it with users and gather feedback. Sometimes it will be a quick guerilla test, while other times it may be a full fledged usability test session. The test results will help us understand what needs to be changed and fixed.