HIGH FOCUS
ON USER EXPERIENCE

We put your users first and design everything else around it.

Our user centred design approach leads to a high engagement with your users and customers right from the beginning.
Thus, the software project will include parts bringing real value only. In result, this delivers the best outcome for you and also saves development time and costs.

USER CENTRED
SOFTWARE PROJECTS

BUILDING THE RIGHT PRODUCT + BUILDING THE PRODUCT RIGHT

STRUCTURED
USAGE REQUIREMENTS

Board with user stories in requirements analysis phase

Usability is the extent to which a product is effective, efficient, and satisfying in a particular context of use.

We usually start a software project with high level workshops, as eg. OKR or the Lean approach to understand the business and the definition of measurable outcomes. This enables all stakeholders to evaluate success in the project.

Then, contextual usage requirements result out of in-depth expert interviews. These findings are documented, grouped and prioritised. All results are made available for review and discussion online to clients. Thus, we achieve best possible transparency.

INVOLVING USERS
WITH AGILE PROTOTYPING

UX optimisation with Zeplin

Historically, user experience (UX) in a project was built upon requirements capture and deliverables which were documented as detailed as possible at the start of the project.

Nowadays, the focus instead should be on obtaining user feedback as early as possible in the design process so that it can be tested by users and used to make quick decisions. This avoids time and costs for the need of much bigger alterations at a later time.

Thus, we use agile methods as Lean UX and Design Thinking. The latter is an iterative process in which we seek to understand the user, challenge assumptions, and redefine problems in an attempt to identify alternative strategies and solutions that might not be instantly apparent with our initial level of understanding.

INVOLVING USERS
WITH AGILE PROTOTYPING

UX optimisation with Zeplin

MINIMUM VIABLE PRODUCT
DONE AGILE

Minimum Viable Product life cycle

In our world, a complex environment, nothing is surely predictable. The risk that comes with a conservative project approach based on the waterfall model is a changed environment before end of the project when the product is delivered to the end user.

Our agile approach aims on the possibility to implement changes during the actual building process. Thus, the product is built in steps, beginning with an MVP version (minimum viable product).

If functionality of a product cannot bed reduced further without jeopardising the main use case, the product then is minimum but still viable.

In the end, this enables fastest user feedback and therefore quick development turnouts and thus is the foundation for achieving the most valuable outcome in the fastest possible way.

QUESTIONS?