Wireframe Design System

Case Study

Wireframe Design System

A shared visual and structural language for consistent low-fidelity product design across Ackee projects

Design System Architect2024

Role

Design System Architect

Timeline

3 Months

Platform

Desktop / Mobile

Tools

FigmaFigma
ClaudeClaude
NotionNotion

Overview

The Challenge

Wireframes at Ackee had gradually developed their own visual language from designer to designer. That worked well while one person owned a project, but became problematic whenever work changed hands — continuing someone else's wireframes often meant first adapting to their individual conventions rather than focusing on the product itself. I created a shared wireframe design system to establish a consistent visual and structural language across projects. It built on an existing internal project template containing basic foundations such as typography, colours, inputs, and buttons, which I simplified, visually unified, and expanded into a reusable system of nearly 50 components. An additional goal was consistent component naming and structure, making the library easier to interpret not only for designers, but also for AI-assisted tools such as Figma Make and Claude when generating early wireframe concepts.

Case study detail

Research & Discovery

Key Findings

Finding 01

The main inconsistency wasn't in individual components, but in the lack of a shared wireframing language. Each designer had developed their own conventions, making collaboration and project handovers unnecessarily difficult.

Finding 02

The existing internal template provided useful foundations, but wasn't extensive enough for building complete product flows. More complex patterns were still recreated independently from project to project.

Finding 03

A useful wireframe library needed to stay deliberately simple. Components had to be flexible enough to cover different product types without introducing visual decisions that belonged to the later UI phase.

VIEW ALL

Design Process

How I Got There

01
Audit
02
Simplify
03
Standardize
04
Expand
05
Iterate

I started with the existing project template and reduced unnecessary visual variation, particularly in colour usage, to create a clearer and more neutral foundation for wireframing. From there, I expanded the library with commonly recurring interface patterns. Rather than trying to create a component for every possible situation, the system evolved through actual project use and feedback from other designers. New components were added when recurring needs appeared, while existing ones were refined to become more adaptable. The library now contains just under 50 reusable components, each with a dedicated master page showing its available states and configurations.

A separate overview page acts as the working canvas: designers can quickly browse instances of all available components and copy them directly into their wireframes without searching through individual component pages. The introduction of slots in Figma later allowed several previously separate components to be consolidated. Patterns such as cards and segmented controls became significantly more flexible, reducing the need for multiple narrowly defined variants and making the system easier to maintain. Consistent naming was treated as part of the system itself. Besides making files easier to navigate for designers, predictable component names and structure also make the library more suitable for AI-assisted workflows, where tools need to understand and reference existing patterns when generating initial wireframe concepts.

VIEW ALL

Final Design

The Solution

Final design
#1

One shared wireframing language

for creating consistent low-fidelity product designs across designers and projects.

#2

Nearly 50 reusable components

with dedicated master pages documenting their states and an overview canvas for immediate use.

#3

Built to evolve with both designers and new tools

using adaptable component structures and consistent naming suitable for AI-assisted wireframing workflows.

Takeaways

Reflection

The biggest value of the system wasn't the number of components it contained, but the consistency it created between designers. Before it existed, taking over somebody else's wireframes often meant inheriting their individual visual conventions as well. A shared system removed that unnecessary layer and allowed the work to continue in the same visual language regardless of who created the previous screens. The project also changed how I think about component libraries. More components don't necessarily make a better system. As Figma introduced more flexible features such as slots, several patterns could actually be simplified and consolidated. The goal became creating fewer, more adaptable building blocks rather than documenting every possible variation.

Final design detail
PreviousArma 4 Game UX
NextAmbienten VIP
+
+
+
+
0000 · 0000
Daniel Gratza

Let’s make something great.

Prague-based UX designer

Get in touch