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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.