Design that starts with the user and ends in development
We design interfaces for mobile apps, websites and business systems the design-thinking way. First we find out what people need to get done, then we test ideas with a clickable prototype, and only then do we build.
What we design
-
Mobile apps
App screens for iOS and Android phones and the route a user takes through them. iPhone and Android users are used to different things, such as where the back button is and how gestures work, so we adapt the design to each platform and the app feels familiar the first time.
-
Websites and portals
News portals, webshops and company sites, designed for a phone first and for larger screens after that.
-
Business systems
Admin tools and internal portals where clarity matters more than decoration, because people use them all day.
-
Prototypes
A clickable model of the product to try, show to others and improve before development starts.
Work
-
Rozie
A marketplace app with separate flows for customers and for cleaning professionals.
Read the case study: Rozie -
Lasi.lv
For this portal we designed everything, from the logo and the digital identity to the portal's UX.
Read the case study: Lasi.lv -
Livonia Print
One request list shown as a table on a large screen and as cards on a phone.
Read the case study: Livonia Print
Design thinking: three questions
Design thinking is a human-centred approach to solving complex problems. It looks for a solution that answers three questions at once, and we start design with the first.
- Do people need it
- Does it pay off for the business
- Can it be built
- Solution
-
Do people need it
The solution has to fit what users are really trying to get done. We find that out before we draw screens.
-
Does it pay off for the business
The solution has to suit the company's goals and budget, or it stays a handsome drawing.
-
Can it be built
The solution has to be technically feasible. That is why the developers who will build it review the design from the start.
Five stages
We work by the five-stage model of the Stanford d.school. Each stage has a result of its own that you see and can discuss.
- Research
- Defining the problem
- Developing ideas
- Prototyping
- Testing
-
Research
We talk to the people who will use the product and watch how they work today. We treat our first assumptions as hypotheses until they are checked.
-
Defining the problem
We gather what the research showed, order it by importance and state the problem from the user's point of view. The task becomes a question that starts "How might we…?".
-
Developing ideas
First we produce as many options as we can and do not criticise them. Then we weigh them and choose the ones to take further. We draw flows in plain boxes, so the talk stays on how the product works.
-
Prototyping
The main flows become a clickable prototype to try on a phone or a computer. It is quick and cheap to make, so an idea can be improved or dropped before development starts.
-
Testing
We give the prototype to users and watch where they stop. Then we improve it or go back to one of the earlier stages.
The process is not a straight line
The stages help everyone agree on the work, but in practice they rarely follow one another in strict order. If testing shows the problem was defined loosely, we go back to research or definition, and that happens while a correction is still cheap.
Two ways of thinking take turns. In research and in developing ideas we go wide and look for many possibilities. In defining the problem, choosing ideas and testing we narrow the choice down to one solution.
From prototype to development
Once the prototype has been tested it becomes a design that can be built without guessing.
-
Visual design
We set the typefaces, colours and components and collect them in a small design system, so new screens stay consistent.
-
Handover to development
Developers get the design with sizes, states and texts. On our projects those developers are on the same team.
-
Developers review the design
A design made without developers often asks for things that are expensive to build or slow to load. Ours is reviewed by the people who will build it while it can still change.
-
The designer checks the result
Before a release the designer compares the built screens with the design.
Usable by everyone
We design for a phone held in one hand, for the keyboard, and for people who read with a screen reader or need larger text. We check text contrast against the WCAG thresholds when we choose the colours.
Where the approach comes from
Design thinking is not a new fashion. In the 1960s Horst Rittel described complex, many-sided problems that have no single right answer. In 1969 Herbert Simon was the first to describe design as a way of thinking, and he was already writing about quick prototypes and testing by observation.
The design firm IDEO and the Stanford d.school brought it into everyday practice, and the d.school's five-stage model is the one we use.
Related services
Design is the first step of a product. The next ones are described on these pages.
Have a product that needs a clearer interface?
Show us what you have, or describe what you want to build.