More performance by creating truly independent teams
Micro Frontends – small teams, quick results
In customer projects, we have found that work can be done more efficiently when teams are as small as possible. If one team of 20 people becomes four smaller teams, they can achieve more because decoupling frees up resources. Micro frontends enable the implementation of a vertical organizational structure; they remove the barrier between frontend and backend because they introduce cross-functional teams.
Wer uses Micro Frontends?
Adidas, American Express, AutoScout24, BMW, Breuninger, DAZN, Deutsche Telekom, Douglas, Fricke, Ikea, Kaufland, Klarna, Mercedes Benz, Netflix, Obi, Otto, Paypal, Rewe, SAP, Spotify, Thalia, Zalando, ZeissTime to Market – die Magie der Geschwindigkeit
In a micro frontends setup, faster development and implementation speeds are achieved – time to market for maintenance and improvements is reduced. Productivity of teams increases and they can implement more changes.
“Do you know the law of computer scientist Melvin Conway? It states that the way an organization is structured and how its teams communicate has an impact on the technologies and systems it develops.”
End-to-End method – more responsibility, more autonomy
Teams work truly independently from one another, within manageable systems. Smaller projects are easier to reason about. There is no shared code with other teams. Changes do not affect neighboring systems. Each team owns its part of the system or its features and has the autonomy to evolve them – which in turn increases identification with the product and motivation.
Technology agnostic – choosing the right tools
Which tools are right for which job? Being open in terms of technology is a key piece of the micro frontends approach. Each team is free to choose the technologies it uses and make decisions autonomously. Often, neighboring teams use similar stacks, which makes knowledge sharing and pairing easier. In neuland projects, we typically rely on web and browser standards to integrate the systems, ensuring the architecture remains viable in the long term.
Full customer focus for every team
In a micro frontends architecture, every team has a direct line of sight to the customer. All teams align their work around the needs of the actual users of the application. The focus is clear and each team has a defined mission, which creates a direct sense of responsibility towards users. There are no API teams – only teams working directly on real use cases.
Our introductory offer for you
A consistent UI despite decoupling
A shared design system helps all micro frontends teams create a consistent look & feel – so users experience it as a single product. To define good vertical slices, it’s important to thoroughly analyze the organization and its requirements. As an example and a basis for professional discussion, our colleague Michael Geers has built the Tractor Store.Here, the decomposition of an application becomes tangible – into Team Decide, Team Inspire, and Team Checkout.
Interested in micro frontends?
This autonomous way of working and the high development speed help you move the needle and keep employees motivated. We’re happy to share our project experience and show you what benefits and side effects you can expect.
