01 / My motto!
With my background as a front-end engineer, I speak the language of the developers I work with. I think it is important to understand and empathize not only with your users but also with your team. Knowing how to code helps me understand not only the problems the developers on my team faces but I can also explain to them precisely what I want in the design. Designers should never work in silos. 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.
02 / I believe in Design process
Every project is different and will have different methodologies. Some will need card sorting and some might have the information architecture already well defined. The nitty-gritty method choice tends to differ but I still follow a general process for every project. In order to formulate solutions, I like to have 6 main phases: Define, Discover, Interpret, Ideate, Prototype, and Test. These phases are rarely ever linear and tend to be repeated multiple times before delivery.
Build empathy for
user as team
it's important to understand your users together as a team. Doing so eventually weaves benefits into the product at every level. By increasing your team’s exposure to users, you will increase the user’s satisfaction with the product.
Define and discuss
Take time to understand and clearly define your user’s problems. Feeding the team solutions will only lead to demoralization; people like being empowered and to have a chance to be creative. Let the team stretch their skills, and give them time to truly understand the problem.
Good ideas can come from anyone. Waiting for one member of the team to create the best idea will take time, and will be biassed towards their experience. It doesn’t have to take long, there are exercises designed to generate lots of ideas quickly.
Test prototype with actual users
Fake it until you can make it. Spend the minimum amount of time to create the closest to the real thing. You’re looking for feedback on the idea, not whether your design looks finished. Test with real representative users.
Iterate based on
It isn’t enough to run through a design process once. Learn from your users, learn from your team, and iterate. Your process will mature and you’ll be able to run through it easier and faster on each pass. Being agile is to be set up to react to new information fast.
03 / I can help you with
I've led design projects from strategic concepts (early discovery) to post-launch takeaways (end product). I've worked in agile product teams with two growing startups. I've collaborated with cross-functional teams to create a delightful experience for the end-users.
Learn what our users want, I conduct qualitative research to deeply understand our customer and blend quantitative data to bring a strong point of view and accurately frame the problem.
Combine human-centered insights with business goals to create value propositions and viable and multi-channel experiences informed by objectives and outcomes.
Guide the team to design and test solutions for key challenges in building digital products and services using frameworks within one week.
When a Design Sprint isn’t suitable, sometimes a workshop will suffice. I’ve run several workshops for my projects to gain insights to user testing for digital products.
UX / Interaction Design
Audit and adapt your digital products and services to maximize ease-of-use, accommodate a variety of user flows and eliminate lingering user frustrations. Deliver digital products and services to your users in a way that makes sense, meet their needs, is consistent, coherent, and usable, and ultimately desirable. To learn more about how I arrive at the final solution and why take a look through the work