Elifsu Tanyeri

Building a system for a product that could grow into 500+ screens.

What started as a set of inconsistent concept screens became a reusable design system and page-level architecture for a large insurance product. I designed the system so changes could propagate across hundreds of screen variations instead of being maintained one by one.

Client

Anadolu Sigorta

Ownership

Design System / UI Architecture / Product UI

Platforms

Mobile & Responsive Web

Year

2025

I turned concept screens into a system ready for a real product.

Concept screens were never meant to be production-ready: typography, colours and components varied from screen to screen. I extracted the underlying visual language and turned those individual decisions into a reusable design system.

I turned concept screens into a system ready for a real product.

I turned inconsistent decisions into shared rules.

Not just for the screens we had, but for the ones we hadn’t designed yet.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

A five-step purchase flow could branch into dozens of screens per step: filled states, validation errors, conditional fields and client-specific variations. One requirement change could affect hundreds of them.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

So I moved reuse up a level: from components to entire pages.

I turned each step of the purchase journey into a page-level component, so structural changes could propagate across every state and variation at once.

I modelled the fullest case once, then derived every exception from it.

Each page component contained every possible field, state and conditional case. Individual screens were created by controlling what appeared, disappeared or changed, instead of rebuilding the page for every scenario.

The same page logic had to scale across mobile and web.

The architecture was adapted across mobile and responsive web without rebuilding the flow logic for every layout.

A revision that could touch hundreds of screens became a component update.

Update the source once, and the change propagated across every affected variation.

Building a system for a product that could grow into 500+ screens.

I turned concept screens into a system ready for a real product.

I turned concept screens into a system ready for a real product.

I turned inconsistent decisions into shared rules.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

So I moved reuse up a level: from components to entire pages.

I modelled the fullest case once, then derived every exception from it.

The same page logic had to scale across mobile and web.

A revision that could touch hundreds of screens became a component update.

More things I’ve worked on

I organize the messy,
design what ships,
and automate the boring bits.

Building a system for a product that could grow into 500+ screens.

I turned concept screens into a system ready for a real product.

I turned concept screens into a system ready for a real product.

I turned inconsistent decisions into shared rules.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

However, component-level reuse wasn’t enough for a 1,000+ screen flow.

So I moved reuse up a level: from components to entire pages.

I modelled the fullest case once, then derived every exception from it.

The same page logic had to scale across mobile and web.

A revision that could touch hundreds of screens became a component update.

More things I’ve worked on

I organize the messy,design what ships,and automate the boring bits.

I organize the messy,
design what ships,
and automate the boring bits.