Along with co-founding six mobile apps, I am a product designer with over 15 years of design experience and a broad architectural background.

I combine the processes of those two specialties in a daily routine to create inspired and innovative products. I specialize in planning, conceptualizing, and designing clean, scalable, functional products, and experiences that leave a positive impact on people and solve business problems.
You can follow me on Twitter, Dribbble, LinkedIn

See my Toptal portfolio

Snippets from my UX process

I like to combine being creative and analytical in my work. I strive for a holistic approach, focus on the big picture without losing sight of the little details.

byers 11.png — It all starts with the drawings

The creative process is complex and hard to define, but when ideas are generated, the simplest way of communicating them is by drawing.

It’s good for developing ideas, making quick iterations and team collaboration.

I like to keep the project notebook with my sketches I can always refer to.

Frame 3.jpg — It’s very important to understand users motivations and behaviors. That’s why the research is always very handy. It can be done in many ways ie. heatmaps…

Screenshot 2019-05-22 at 21.52.jpg — …surveys, interviews, qualitative research, cards sorting…

Screenshot 2019-05-22 at 21.43.jpg — …or quantitative data.

I try to understand the goal and a real purpose of the project. Why something needs to be done, and why the solution we’re working on is the best way to achieve that.

Untitled_2 2.jpg — I always start with drawing. As Le Corbusier said “I prefer drawing to talking. Drawing is faster and leaves less room for lies.”

Sometimes the best way to find the proper solution is to work on abstract entities. Creating user flows always put a lot of light to the problem.

byers 10.png — Some wireframes and quick tests among users can put us closer to a satisfactory solution as well.

The first solution is usually, not the best, I make a lot iterations to find something that clicks. I like to keep all of them saved for future reference. Sometimes they are very useful at later stages of design or during kickoff presentations.

Sometimes it’s necessary to make high fidelity prototypes to create convincing and credible testing materials.

You can prototype the behavior of the whole part of the system...

...or a single component (like this complex dropdown)...

… or this micro interaction.

Screenshot 2019-05-22 at 22.36.png — Whatever has been prototyped it's always important to test a prototype and see how people are using it. You can do some automatic tests...

Screenshot 2019-05-22 at 21.53.png — ...ask people about their preference...

...or do the qualitative user testings where you observe how different participants solve previously assigned tasks. I like to use this rainbow matrix to collect feedback among different users.

When I have my feedback, it’s time to prioritize it and decided what to work next. You never work alone and every project has different dependencies.

You can put all benefits and costs together, and generate a chart that helps you with the decision.

Sometimes it's worth to make a heuristic evaluation.

When I work on a final version of the design I believe it’s important to provide a precise and explanatory documentation. There is a developer who needs to execute the project. I want to make it as easy and clear for them as possible

It’s a good practice to describe edge cases and less common scenarios.

You can
define all the elements and rules together and make them the single source of truth for the whole organization.
It will allow the teams to design, realize and develop a product in a much more pragmatic manner.

It’s always a great feeling to see the developed product...

…sometimes, I make an engaging video for the demo purposes…

...but it’s never finished, so I think it’s always crucial to take look on the metrics and talk with clients (or customer happiness team) regularly to figure out the next challenges to work on.

Let’s make something beautiful