A shared kit so every government service feels like one country
Dozens of teams, hundreds of services, one citizen who should never have to relearn the interface.
The State of Israel ships digital services across dozens of agencies, each with its own team, timeline, and interpretation of what a form, a button, or a status page should look like. Nothing was technically wrong - it just didn't add up to one government.
My part sat inside a 13-person design team at Deloitte Digital's Awesome studio: building and refining components, aligning styles across the library, and preparing the system for public release.
From scattered products to a single library
The engagement moved from mapping what already existed into a released, adoptable system - each stage narrowing toward one question: will a team actually use this without asking us first?
Audit: Mapping the full range of products and services already shipped by government teams, and the patterns each had invented independently.
Atomic foundations: Structuring the library on atomic design principles, so every element could be composed, customized, and scaled without forking the system.
Responsive components: Building components with Figma auto layout and variants, so a single element behaves correctly from mobile to desktop with no manual rework.
Guidelines: Writing usage rules alongside every component, so adoption didn't depend on a conversation with the original designer.
Public release: Publishing the finished kit as a free Figma Community file, available to any team or agency, inside government or out.
The hard part was never the buttons
Consistency, adoption, and speed each pulled in a different direction - and the system had to satisfy all three at once.
Ensuring consistency: The government offers an unusually wide range of products and services. Unifying them under one visual and interaction language, without flattening what each service genuinely needs, was the core tension.
Cross-functional adoption: The system had to be adopted by designers, developers, and vendors who share no manager, process, or toolchain. Anything requiring onboarding would quietly be ignored.
Speed under constraint: Every team was already shipping. The system had to make things faster from day one, not slower.
Ensuring consistency: The government offers an unusually wide range of products and services. Unifying them under one visual and interaction language, without flattening what each service genuinely needs, was the core tension.
Cross-functional adoption: The system had to be adopted by designers, developers, and vendors who share no manager, process, or toolchain. Anything requiring onboarding would quietly be ignored.
Speed under constraint: Every team was already shipping. The system had to make things faster from day one, not slower.
Atomic, responsive, and free to take
If adoption is the goal, distribution is a design decision - not a launch task.
We used atomic design principles to build a modular library teams could customize and scale instead of rebuilding from scratch. Small, well-defined elements compose into patterns, and patterns into templates.
Components were built responsive from the start with Figma auto layout, so consistent designs could be produced quickly rather than reassembled by hand for every breakpoint.
Master components centralized every style in one place, so a single update could reach every product using the system - keeping it cohesive as it grew.
Distribution decided the rest: publishing to the Figma Community made the kit one click away for any designer or developer, inside or outside government.
A kit, a rulebook, and a single source of truth
Downloadable library
immediately usable components and templates: The full system is available as a Figma file in the Figma Community, so components and templates are ready to use the moment a project starts.
Clear guidelines
consistency without a gatekeeper: Documented usage rules ship alongside every component, keeping products consistent without requiring a conversation with the original designer.
Dynamic components
auto layout and responsive variants: Teams assemble consistent screens quickly across breakpoints instead of redrawing them by hand for mobile, tablet, and desktop.
One place to manage many
master components, one update: Master components keep the visual language unified, so a change made once lands everywhere the system is used.
Downloadable library
immediately usable components and templates: The full system is available as a Figma file in the Figma Community, so components and templates are ready to use the moment a project starts.
Clear guidelines
consistency without a gatekeeper: Documented usage rules ship alongside every component, keeping products consistent without requiring a conversation with the original designer.
Dynamic components
auto layout and responsive variants: Teams assemble consistent screens quickly across breakpoints instead of redrawing them by hand for mobile, tablet, and desktop.
One place to manage many
master components, one update: Master components keep the visual language unified, so a change made once lands everywhere the system is used.
What the system actually changed
Improved design consistency. Standardized elements and styles produced a cohesive interface across projects, lifting both the visual quality and the experience for citizens who move between services.
Increased design velocity. With a consistent set of elements ready to use, designers work faster across projects and spend less time re-deciding what a field or a button should be.
Increased efficiency. Teams focus on innovation and problem solving instead of repetitive setup - the structured, accessible foundation does the boring work for them.
The system is free and public. Anyone can download the Israeli Government Design Kit from the Figma Community and start building with it.