1. Aug 2025

Tips for better collaboration between Design & Development

Sometimes there are delays or problems in the collaboration between development and design. This is often the case when teams develop and design new online stores.

But the obstacles can be overcome. The best thing is for designers and developers to pay attention and communicate with each other right from the start.

PAGE asked André Roitzsch, CEO at SHOPMACHER, four questions about this.

1. In your opinion, what are the biggest problems in the collaboration between development and design for online shops?

André Roitzsch: One of the main problems in the collaboration between design and development is the sequential approach: If the design is first fully developed, approved and then transferred to the technical implementation, difficulties often arise at this point. This is because designers are not always aware of the technical limitations of the chosen store system. This results in design specifications that are sensible and attractive from a design perspective, but whose implementation is unnecessarily complex or costly from a technical perspective.

On the other hand, developers sometimes lack an understanding of which “minor” deviations from the design would be acceptable without undermining the overall design concept. In such cases, additional coordination is required – up to and including re-approval by the design team, which results in delays and frictional losses.

But it is also often a one-way street from the other end: if technical concepts are developed in advance and then “adapted” to the corporate design, design corrections can cause considerable additional work during development – especially if they are introduced retrospectively and were not originally planned.

2. How can improvements be achieved with regard to the points mentioned?

The most effective solution lies in the genuine, collaborative development of design and implementation – ideally in close cooperation right from the start. Design and development should not be seen as downstream process steps, but as parallel, interlinked disciplines.

In addition, a realistic database is essential. In the conception phase, idealized sample data is usually used – which leads to aesthetically pleasing, but not always realistic results. As soon as real product data from third-party systems comes into play, inconsistencies quickly become apparent that affect both the design and the technical structure. A common understanding of data origin, structure and logic helps to counteract this at an early stage.

3. Do you have any everyday tips on UX and UI design for designers in companies that operate online shops?

A tried and tested means is the regular exchange in practical workshops in order to develop and implement the UX together with the design partners. In these operational formats, potential points of conflict can be identified at an early stage and viable solutions can be developed together.

Another success factor is a clean, comprehensibly documented data model.

In the commerce environment in particular, it is crucial to understand that design work largely consists of visualizing data. If you know the structure, origin and processing of this data, you can design more effectively and efficiently.

In addition, a basic technical understanding is a great advantage for designers – especially knowledge of HTML, CSS and ideally a basic understanding of JavaScript. In our onboarding process, we therefore emphasize that designers work independently with store or editorial systems, create templates and build pages. The practical experience of technical possibilities and limitations not only promotes understanding, but also increases the quality of the subsequent design specifications.

4. Do you have any tips for developers?

The following also applies to developers: understanding the other discipline is essential. It is not enough to write clean code – what matters is how it works in the frontend. Developers should regularly check their results in the browser and compare them with the originally planned design.

A good eye for design – at least the basics – is part of a front-end developer’s expertise. Those who recognize deviations, take visual details seriously and suggest constructive alternatives contribute significantly to a high user experience – without losing sight of technical efficiency.

André Roitzsch, CEO

ALSO INTERESTING

How sport2000.de fills the MACH idea with life

How sport2000.de fills the MACH idea with life

There is a lot of talk right now about MACH, a software architecture that is microservice-based, API-first, cloud-native and headless – but for historical reasons there are hardly any consistent implementations. The e-commerce agency Shopmacher presents sport2000.de, one of the first major cases in the field.

read more
commerce village

commerce village

WELCOME TO THE COMMERCE VILLAGEEveryone is talking about IT and commerce landscapes - yes, of course! But when we ask in conversations how our counterparts visualize such a landscape, they are always at a loss. To change this, we have developed an interactive map that...

read more
Cookie Consent Banner by Real Cookie Banner