I never design a building before I've seen the site and met the people who will be using it.

- Frank Lloyd Wright

Client: Hi, I'm Tod. We got MVP of this project and we're looking for UX guy...

Me: Okay, show me what you got. What's the problem you're about to solve? What results you got from the MVP?

Client: This and that...


Every field has its experts. Every problem has its experts too. Most usually it's the customer.

What is the current solution?

Sorting the data

This is the difficult part. Possible process is followed: get all the data from research, split them to the smallest parts, choose the right framework and place the separated data back in order they belong to.


The output of synthesizing are the core revelations that we’ll build on during all following processes.

First rule of design process -
there is no static design process.

— Me

Information architecture and messaging

This is the initial part of the actual designing process, when we understand the user’s and the business needs.

It is ones best interest to order and organize information to best satisfy these needs. So – before the wireframing and prototyping, it’s necessary to have knowledge and about major part of the content and it’s structure. That’s why Lorem ipsum is such a disaster.

Wireframing & Prototyping

I believe in tools that allows me to work and iterate quickly. But basically anything may be used for wireframing. Even a paper and a pencil. 😉

“Don’t even try to build startups. That’s premature optimization. Just build things that seem interesting.”

— Paul Graham

Testing, Building, Iterating

Without proper processes there used to be a chicken and egg problem: How to validate something when it’s not done yet?

Keeping what matters

Chaos is redundant.

Where do we go from here?