All our processes and tools are built around collaboration and holistic product design.

We design digital products, not interfaces.

Okay, of course we also design interfaces, as well as brands and websites. But we believe designers need to take ownership of the process as a whole and they need to have an understanding that goes beyond our design software.

Development
Business
Product
Management
Design

How we make a digital product in three steps

Now, we don’t want to raise wrong expectations. Many smaller steps in between and lots of iterations are required to go from a problem to public release. But to explain the overall process, we tried to keep it simple.

Understand

Research & Understand

Before we can test possible solutions, we need to develop a well-founded hypothesis. We do this by defining the problem, empathizing with users, ideating solutions and sorting our results.

First user story map
First MVP Definition

Validate

Prototype & Test

In the next step we substantiate the hypothesis by creating a clickable prototype. The goal is to validate or falsify our assumptions and iterate multiple times between prototyping and testing until we’re there.

Clickable prototype
Validated hypothesis

Execute

Design and Development

Now that we know how the product will work, we decide how it will look and feel. Then we hand off our results to development where smart people write the code that turns our design into a functional product.

Visual Design
MVP Development

Public Release of MVP

Well then, our job is done, right? Not yet. We helped you to bring the product live, now we want to enable you to sail the ship on your own. We help you to build an in-house team that replaces our competences. Until then, we build upon the MVP and evolve the product working with data driven agile development.

Research & Understand

Before we can test possible solutions, we need to develop a well-founded hypothesis. We do this by defining the problem, empathizing with users, ideating solutions and sorting our results.

Understand
First user story map
First MVP definition

Prototype & Test

In the next step we substantiate the hypothesis by creating a clickable prototype. The goal is to validate or falsify our assumptions and iterate multiple times between prototyping and testing until we’re there.

Validate
Clickable prototype
Validated hypothesis

Design & Development

Now that we know how the product will work, we decide how it will look and feel. Then we hand off our results to development where smart people write the code that turns our design into a functional product.

Execute
Visual design
Development of MVP

Well then, our job is done, right?

Not yet. We helped you to bring the product live, now we want to enable you to sail the ship on your own. We help you to build an in-house team that replaces our competences. Until then, we build upon the MVP and evolve the product working with data driven agile development.

Public Release of MVP

Collaborative workflows are our key to high quality

412

412

We use real-time collaboration tools for nearly everthing we work on. This way we can always design collaboratively and our clients stay as close to our work as possible.

James Ciclitira
Diego Ballin
Samuel Frey
Niklas Tomkowitz
Max Ropohl
Marvin Horstmann
Colin Böhning
Sören Gröbke
Feray Tatar-Kazanci

We are not creatives,
we are designers

We see design is a craft, a hands-on, artisanal process. It requires a lot of practice and rules to follow. The most fundamental ones shape our design philosophy.

Every pixel counts

We define rules for spacing and sizing of every detail. An interface is like a puzzle and only with accuracy and consistency we're able to match all the pieces.

Design critique is inevitable

We always need more than one perspective. With regular in-depth reviews we ensure the quality of our work before we get feedback from clients or users.

Build maintainable designs

How you structure your pages, components and styles defines how maintainable the project will be. This is why we use carefully designed component setups and always take the time to clean up our work.

Now try something else

It doesn't matter if it's about a user interface, a logo or a name. We try to generate lots and lots of ideas that solve your problem. Only then we're able to evaluate the solution.

No decisions without reasoning

In order to evaluate design decisions we have to reason them. We take a step back and try to understand how the design solves a specific problem.