Understanding UX: Prototyping

In this blog series, we are looking at UX and UI design in the context of modern software development. UX and UI design are often misunderstood activities. For laypeople who have heard of it in the context of an IT project, it most likely means: "Make sure the end product looks good". We shed light on this preconception and show the added value UX, or digital design in general, can generate. The impression that saving on design services saves costs is often wrong. This article first offers an introduction to the topic of UX, the activities of professionals in the field of UX and UI, and finally highlights prototyping as a "tool" in a project.

They understand problems, question critically, investigate, and are also a bit of a diplomat with the necessary pinch of visual flair. Whether for a small landing page or a complex specialist software interface: UX and UI designers have numerous initial questions in a kick-off meeting.

• Which user or target group is this landing page or software for?
• What is the goal of the landing page or the software?
• What is the desired user action on the landing page and regarding the software?
• Who are my contacts for this topic?
• And many more!

Questions that deal with branding conformity and visual appeal do not even come up this early in the process. UX and UI designers are also guided by precisely this process. The four questions that UX and UI designers can help answer are these: What do we want to achieve? How do we want to achieve it? What do we want to build? How do we want to build it?

The end users of the landing page or software are at the heart of this "human-centered design" process. Every stakeholder's need and goal must be aligned and harmonized with the goals of the end users. Of course, accessibility must also be taken into account in this process.

No matter how simple an application is in the end, the way it is used plays an important role. in this design process, it may well be the case that native, non-digital parallel processes must also be taken into account or even co-designed ones.

Of course, it's not just UX designers who develop such a solution. Nor is it solely UI designers who determine the visual aspects of the solution. The function of UX and UI designers is to act as a mediating link between different stakeholders.

In agile projects, it is often the case that features are conceived, designed and implemented one after the other, all within the overall framework of the "vision". Depending on how clear this vision is, you naturally take certain risks. What if the feature we are developing today is no longer compatible with the evolving vision next year?

Many assumptions are made in UX and UI design, especially in the world of websites and software. Here are some examples with critical questions attached:

• "A green button triggers a positive action, a red button a negative one." How do we ensure accessibility (in this case color blindness)?
• "Three horizontal lines arranged one above the other are perceived as a menu." How useful is this standard in our application?
• "An asterisk (*) on a form field marks it as a mandatory field." Is there a more elegant solution?

These assumptions are usually validated as part of a prototype or "click dummy". A prototype is the implementation of the user interface with a variable, needs-based level of detail, with or without code. A missing prototype can lead to unanswered questions remaining unanswered and having a negative impact on the project or the final product.

Prototyping can be used at any stage of a project: On paper in an idea generation or conception workshop, as a black-and-white wireframe for process validation, or high-fidelity in a graphics program, either completely or feature by feature.

How prototyping can help a project, depends entirely on the subject matter and the requirements. In most cases, it is much more cost-effective to adapt the prototype and carry out a user test with the newly gained knowledge instead of realizing at the end of the project that the employees unfortunately do not find the new specialist application as good as the old tool that has been in use for 15 years. Modern technology - or not.

A prototype of the product or feature could have been created in a graphics tool and user surveys could have been conducted to validate which features generate added value and meet with acceptance. The opportunity to test a final product in detail, not only in terms of its operation but also in terms of its benefits, costs money but it’s nevertheless cheaper than several months of wasted development.

First and foremost, serious research processes and prototyping create security and reduce the risk of failure. If every stakeholder and every team member knows from day X exactly how the final product should look and function, it is much easier to talk about it across all levels - and anyone who has ever worked in an agile team or a project team in general knows how helpful a clear shared vision is.

Software development is complex and becomes ever more complex. With new possibilities emerge new challenges. Making an informed assumption is good, verifying it is even better. A serious UX and UI process not only helps to create trust during the project and develops a shared vision, but also ensures better acceptance.

Software development is expensive and often associated with risks - prototyping can reduce risks and costs, inspire project teams to adopt new approaches and increase confidence in the project and therefore also in the final product.

Are you unsure whether UX and UI design can generate added value in your project? We will be happy to listen to the challenge in a consultation and can make recommendations on how a serious UX and UI process can help your project. Discuss the topic with us, we will be happy to help!