open source website maker

Hi, my name is Sylke

Pronounced "sil-key"

My background in multimedia, web development and instructional design has lead me to an exciting career as a multi-disciplinary UX and UI designer. I currently assist various teams at Dycom Industries with user research, product strategies and rapid prototyping to empower users throughout the telecommunications industry. My passion for education and human-centered design involves leading workshops in various topics such as design thinking, CSS/SASS, and UX best practices with a focus on accessibility. I truly believe it is our responsiblity to promote inclusion and advocate for all users.

I like
- Sunday morning bike rides on Palm Beach island
- Hiking with Maggie, my rescue dog, and my partner Dado
- Volunteering at Girl Develop It West Palm Beach
- Volunteering at Code Palm Beach
- Designing fun infographics

Sylke sitting on a bench

Design Process

It starts and ends with human behavior

Research the problem

Start with discovery to determine what is the issue the users are facing and make a list of needs and goals. Research the competition and market, what's currently out there and what are users saying about them? What is the user's current behavior? Will the changes to the current product be dramatic and unecessary? It's important to empathize with the users to make sure the product will not further disrupt their lives.

Measurable Goals

Now that we have empathized with the users and identified the issues we need to take into consideration resource limitations, business goals, and listen to stakeholders to establish a baseline. A product roadmap will visually explain the goals to get buy-in from the key stakeholders. This will show the bigger picture of the product and help determine the features that will be released in the MVP and the features will be released in the future stages. It's important to keep in mind that improving a complex system doesn't necessarily mean designing it to be simpler, but to remove the pain points and create a more elegant system.

Collect Data

Now that we have clearly defined goals and timelines we can choose the user research process that makes most sense. Every project is different and surveys, interviews, onsite observations, and usability testing can be conducted in various combinations if time and budget allows. Most importantly, get insight into the real users. Once the raw data is gathered, it needs to be compiled into usable data.  

Iterative Design

With usable data we can hypothesize possible solutions and take the user stories and turn them into user flows. Quick design cycles can help the team determine the most effective solution. There are already effective design patterns that can be implemented to keep the product familiar and accessible and avoid delivering a completely foreign product that will intimidate. New design patterns should be approached with caution and with options for the users to go back to the familiar or allow them to ease into it.

Rapid prototypes will turn into pixel perfect mockups, style guides, documentation and hand-off assets to developers.

Testing

The design should be validated quickly by having users interact with the prototyes early on. Involve different departments within the company to interact with it as well, such as customer support, human resources, sales, etc. 

Launch and Review

Once the product is ready for beta release, it is important to collect user feedback in the wild as opposed to in a controlled user testing session. Some metrics to consider for feedback are: user's satisfaction, engagement, adoption, retention and task success.

Feel free to hit me up with any inquiries 🧐

© Copyright 2018 Sylke Lopez - All Rights Reserved