Skip to content
CV
WorkCamelot Design System11 min read01 · Overview

Product Design Case Study · Design SystemsMerger: car2go → SHARE NOW · car sharing · 2019 –⁠ 2021

A system built to survive a rebrand

car2go built its app, web and B2B tools in separate teams. I built and led Camelot, with the brand as its bottom layer. That carried the rebrand to SHARE NOW. When we rebuilt the web, I reorganised it by purpose, so app and web stayed one.

Read the caseRJump to results
Role in the project
Built and ledProduct designer, leading the founding group from 2019
Platforms
iOS, Android and webplus B2B tools, websites and print
Responsibility
Architecture and rulesLayers, naming scheme, principles and icon library; with brand, marketing and engineering
Status
Shipped+2

As of September 2026

  • Shipped

    Carried on after the rebrand as SHARE NOW Design System 2.0

  • Continued

    After I left in 2021, by a design colleague in Stuttgart

  • Open

    Impact figures are not documented

and 2 more states
As of September 2026
Shipped+2

As of September 2026

  • Shipped

    Carried on after the rebrand as SHARE NOW Design System 2.0

  • Continued

    After I left in 2021, by a design colleague in Stuttgart

  • Open

    Impact figures are not documented

I did not build a system for one brand. I put the brand underneath the system so it could carry a change.

Camelot Design System

At a glance

  • 4 layers

    from the brand up to the interface

    4 layersfrom the brand up to the interfaceScope of the system, not a measured outcome
  • 2,239

    components in 68 sets, one naming scheme

    2,239components in 68 sets, one naming schemeSize of the design library
  • 3 platforms

    iOS, Android and web from one system

    3 platformsiOS, Android and web from one systemPlus B2B tools, websites and print
  1. Problem

    Organised by purpose

    Four layers from brand to interface instead of one library per platform.

  2. Intervention

    The brand at the bottom

    When the brand changes, the change runs up through every layer.

  3. Outcome

    Carried the rebrand

    Camelot became SHARE NOW Design System 2.0.

Role in the project
Built and ledProduct designer, leading the founding group from 2019
Platforms
iOS, Android and webplus B2B tools, websites and print
Responsibility
Architecture and rulesLayers, naming scheme, principles and icon library; with brand, marketing and engineering
02 · Starting point

Every team built its own components

At car2go, teams and products grew fast: the customer app, webviews, B2B, registration, later SHARE NOW Pass. A shared system existed only on the design side; engineering teams had no common source for components, patterns or templates and built much of it themselves.

What followed
  1. 01

    Duplicate code

    The same building blocks in several codebases.

  2. 02

    Slow delivery

    Every feature started from scratch.

  3. 03

    Inconsistent brand

    Users experienced every product a little differently.

  4. 04

    No single source of truth

    Nobody knew which component was the real one.

Before: one library per platform

  1. App styleguide

    Customer app with its own components.

  2. Web styleguide

    Website and webviews, maintained separately.

  3. B2B styleguide

    Tools for business customers.

  4. BA styleguide

    Yet another world of its own.

Splitting by platform made ownership easy and collaboration hard. Every team worked in its own silo, new components were hard to contribute, and we kept rebuilding the same building blocks.

The Camelot scope named three job stories, and the product teams add a fourth. What they all share: nobody should have to build the same building blocks twice:

  • CompanyJob story

    When
    new products and teams come in,
    I want
    one consistent experience across all products,
    so
    users reach their goals the easiest way.
  • DesignJob story

    When
    I design a solution for a new feature,
    I want
    a scalable design system,
    so
    I can build solutions and experiences faster.
  • EngineeringJob story

    When
    I build a feature,
    I want
    a scalable component system,
    so
    I don't have to rewrite every component each time.
  • Product teamsJob story

    When
    I build a feature for the app, a webview or the web,
    I want
    to use the same building blocks,
    so
    the brand looks the same everywhere, even when it changes.
The first three are paraphrased from the Camelot scope, where they were written as user stories; the situation comes from its problem statement. The fourth sums them up for the product teams.
03 · Layers

Organised by purpose, not by platform

The order of the layers is the real decision. The brand sits at the very bottom, then the foundations, then the interactive UI and the public-facing pages.

A big influence was Brad Frost and his Atomic Design: small building blocks that combine into larger ones.

Four layersfrom the base up
  1. Brand

    Colours, illustrations, vehicles and imagery as the foundation.

  2. Foundations

    Palette, typography, grid, breakpoints, buttons, input fields.

  3. Interactive UI

    For devices and desktop: map pins, sheets, navigation, tables, forms.

  4. Public-facing UI

    Website and landing pages, responsive, built from the same foundations.

Foundation: the pill buttonsLive in the lab

max.labCamelotLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
Four styles, three heights from 40 to 64 pixels, eight states, built from the foundation tokens.

The names follow the same order: category, subcategory, type, component. “Interactive UI / Device / Messaging / ToastBar” tells you where a building block lives and what it is for before you open it.

This order came later. When we rebuilt the website and the web products for private and business customers, web app elements also found their way into the native apps. There they could not feel different from everything around them, or they would have confused people. So I developed the system further and proposed this order as the new structure in April 2021: for consistency, for flexibility and as the link between app and web. Deliberately not as a hard switch, but as a transition out of the existing libraries.

04 · Platforms

Native in shape, consistent in behaviour

Because the foundations are shared, platforms only differ where the platform demands it. The toggle follows one form on iOS and the web and another on Android; colours, states and spacing stay the same. Typography comes in dedicated sets for web, iOS and Android.

The same toggle, true to each platformLive in the lab

max.labCamelotLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
Switch the platform and compare: the shape follows the platform, colour and states follow the system.

A whole screen, two platformsLive in the lab

max.labCamelotLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
The booking screen from the same parts. Switch between iOS and Android, selection and confirmation: the shape changes, the behaviour stays.

The library grew to 68 component sets and 2,239 components, all following one naming scheme, with a dedicated area for native iOS patterns.

05 · Rules for change

The library mirrors the code

A system only stays shared if everyone knows how to extend it. New components had to follow six principles, and every change to a typeface, a colour or an existing component had to be agreed with engineering, because it takes effect everywhere at once.

PrinciplesSix principles for new components
  1. Search first

    Check the library first. The solution probably exists already.

  2. Scalability

    Don't build just for the task at hand; build so others can reuse it.

  3. Consistency

    Don't reinvent the wheel. Bring it in and make it better.

  4. Snowflakes

    Avoid one-off components, or have the facts to justify them.

  5. Styleguide

    Use the defined palettes and type; agree anything new with brand, marketing and design.

  6. Collaboration

    The library mirrors the components in code. Changes only happen together with engineering.

A justified one-offLive in the lab

max.labCamelotLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
The map pin is the domain-specific building block: only for the map, but made of the same tokens and with clear states.

The pin where it livesLive in the lab

max.labCamelotLiverebuiltrebuiltRewritten for this site, not the original code. Where a detail is approximated, the docs say so.Docs
Map, pins and reservation sheet together. Collapse and expand the sheet and switch the platform.

Later, Storybook became the documentation in code, synced automatically into the native apps. We also had our own icon library and worked with marketing to carry the system all the way into print. In 2021 the library moved to Figma.

Who decides

At Camelot, the design team made the decisions, and made them together. The final sign-off was mine, as gatekeeper. The developers came to me with systems of their own, since iOS was built in Swift and Android natively. That became one shared route: we kept developing Camelot together, tested it pixel-perfect and connected the platforms through the global foundations.

From proposal into the apps
  1. Together in the design team

    The design team decides; the work is done together

  2. Sign-off

    Me as gatekeeper, at the end of the review

  3. Native build

    The developers build in their own systems, in Swift and for Android

  4. Pixel-perfect test

    Checked together against the design, connected through the global foundations

Accessibility

Accessibility was a focus of the customer-app work at car2go and SHARE NOW. In Camelot's six principles, though, it was not a rule of its own. The rebuild now measures against WCAG: white on the primary action blue reaches only about 2.9:1, less than the 4.5:1 that AA requires for normal text.

Learning

Libraries split by platform make ownership comfortable and the system lonely.

06 · The rebrand

Camelot became SHARE NOW Design System 2.0

The move from car2go to SHARE NOW was the stress test for the bottom layer: a new brand met a system that had deliberately put the brand underneath everything else. Camelot shipped and carried on as SHARE NOW Design System 2.0. After I left, a design colleague in Stuttgart took it forward.

The decision came with the 2019 merger: the app had to be rebuilt so it looked like neither car2go nor DriveNow, and the entire design library was to be rebranded. That is where the decision came from to put the brand in its own layer underneath the system. The order by purpose only followed later, when we rebuilt the web products.

07 · Outcome

What came of it

We never measured the goals from the scope. What is documented: Camelot shipped, carried the rebrand and was continued after I left.

  1. In daily work

    Storybook as documentation in code, synced into the native apps

    Part of how design and engineering work

  2. Rebrand

    Carried on as SHARE NOW Design System 2.0

    Rebrand the entire design library

  3. Library

    68 component sets, 2,239 components, one naming scheme

    One source for every platform

  4. Platforms

    Native shapes and type sets per platform, the same colours and states

    iOS, Android and web from the same foundations

  5. In the guildopen

    not documented

    Part of the frontend guild, with at least one vocal advocate

  6. At scaleopen

    not measured

    Replace duplicated foundation components in 80% of teams

08 · Looking back

What I learned and would do differently today

Caveats

I built and led Camelot; design and engineering implemented it together, and after I left in 2021 a design colleague in Stuttgart took it forward. What is documented is its structure, scope and course; there are no figures on its impact. As of April 2021.

Learnings

  1. The brand belongs at the bottom

    A system survives a rebrand when the brand is a layer of its own, not something baked into every component.

  2. Organising by purpose means spreading ownership

    Libraries split by platform are comfortable but lonely. Organised by purpose, teams work on the same building block instead of copies.

  3. Clarify what exists, then build

    During the merger we rushed into one feature and threw it away months later. Since then I start with the roadmap and what already exists.

  4. A system only stays shared if people can extend it

    Clear principles for new components mattered more than any single component.

What I would do differently today

  1. Make the goals measurable

    We had clear success criteria but no measurement. Today I would count the duplicated foundation components before starting, so a goal like 80% of teams can actually be proven.

  2. Spread ownership earlier

    Ordering by purpose and shared ownership only came with the 2021 proposal. Today I would decide from the start who maintains which layer.

  3. Accessibility as a principle of its own

    Contrast, focus and keyboard to WCAG AA belong next to the six as a seventh rule, with values in the tokens instead of in review.

A design system doesn't prove itself at its first release. It proves itself at the first rebrand.

Maximilian Dahl

fin (for now)

CV · Maximilian Dahl
In plain words

What do you actually do, Max?

My parents and family have nothing to do with tech or my profession. They told me they did not understand my website. This is for them. And for anyone who would like an explanation without the jargon.

I make software easier to work with.

When someone spends ages searching for a button or has to enter the same information three times, I want to know why. I watch how people work, talk to them and design a better way through the task. Then we try it together.

My title is Principal Designer. That means I also make decisions about how whole products fit together and help the team build on them. I still design and write code myself.

Here is a simple example.

At zvoove, I designed an assistant called zAIn. This simplified example shows the idea:

  1. Someone asks

    “How much holiday do I have left?”

  2. The assistant looks it up

    It finds the information and explains the answer.

  3. The person decides

    If they want to book time off, they review the details before anything is sent.

My job is to work out what people need to see, how the answer should be explained and when the program needs their approval.

A design system is a bit like LEGO.

Imagine every team inventing its own bricks. Nothing fits. With a shared kit, the pieces connect, even when people build different things.

Shared pieces. Different things you can build.
Book time offReview an invoice

In software, those pieces are things like buttons, input fields and messages, plus rules for how they work together. I built this kind of kit at Container xChange. It is called Compass.

What has come out of my work?

One starting point
At zvoove, I designed the shared starting point for several programs and tried it out in code. It became Launchpad, which has been live since August 2026.
Built, too
I built the visible part of the notification centre myself. A backend engineer built the part behind it, and we shipped it together.
A team that can build on the work
At Container xChange, I grew the design team from 4 to 14 together with Niclas. Compass gave designers and developers a shared kit to work with.

What am I particularly good at?

I look beyond the screen in front of me. When several teams run into the same problem, I look for a solution they can share. That is how Compass came about.

And I like making an idea tangible early. I can build a working version myself, put it in front of someone and find out where it falls short. I would rather learn that from using it than from a long discussion about a picture.

What would I like to do next?

I want to help decide what a product should become, support a team and keep building myself. I am looking for a role as a Principal Designer, Team Lead or AI Product Builder, in a team that builds with artificial intelligence.

In plain words: I want to take responsibility for the whole thing, without giving up the part I enjoy most — trying things out and making them work.