Azibo Design Systems PropTech

A design system reimagined

Revamping the design system at Azibo

Azibo, a property management platform, had a design system in place for over two years. As the product grew, the system needed to evolve — for consistency across surfaces, faster design–dev handoff, and a library teams could trust at scale.

Three pillars of the Azibo design system revamp: Efficiency and Usability, Enhancing Consistency, and Collaboration and Documentation

Context

Evolving a system for new needs

The existing system was a solid foundation, but increasing product complexity exposed gaps: detached components, inconsistent patterns, and friction when designers and developers searched for the right assets. I partnered with product design, product management, and front-end engineering to align on a vision built around flexible, scalable components.

Drawing on input from the design team and audits of live product screens, we defined a phased rollout — rapid design exploration followed by iterative implementation across the platform.

Team
Product Design, Product Management, Front-end Development
Role
Product Designer — systems, components, documentation
Timeline
Phase 1 — design exploration (3 weeks)
Phase 2 — iterative rollout (~9 months)

System goals

Enhance consistency

Ensure a unified look and feel across landlord, renter, and internal tools — reducing one-off UI and detached components.

Improve flexibility

Allow quicker adaptation to new flows and user needs with variants, tokens, and patterns that scale with the product.

Increase efficiency

Streamline design and development so teams spend less time rebuilding UI and more time on experience quality.

“How did you do that so fast?”
— Lead of Product Management, watching designers adjust flows with system components in Figma

Component structure

UI components

Built a library of reusable elements — buttons, forms, modals, navigation, and status treatments — each flexible enough for multiple product contexts.

Patterns

Documented interaction patterns: drawers, navigation models, lockout flows, and repeatable paths from point A to point B across the platform.

01 — Output

Efficiency & usability

Ensured that designers and developers can quickly find and use the right assets without friction — from tokenized color pills and status labels to annotated component specs in Dev Mode.

02 — Output

Enhancing consistency

Established a well-structured component library with reusable UI elements — buttons, inputs, modals, and account flows — so product screens share the same visual language and behavior.

03 — Output

Collaboration & documentation

Created a design-to-development handoff process with Figma Dev Mode, written specs, and walkthrough videos — so engineers and PMs could ship with confidence.

Approach

  1. 1

    Assessment and audit

    Audited the existing library and live product UI. Mapped inconsistencies, redundant variants, and components that lacked scalability.

  2. 2

    Iterative design and testing

    Prototyped updated components and patterns. Gathered feedback from designers, PMs, and engineers through internal reviews and usability sessions.

  3. 3

    Documentation and implementation

    Shipped detailed usage guidelines, Dev Mode specs, and video walkthroughs. Partnered with engineering on token migration and component adoption.

Impact

Enhanced consistency

Detached component instances dropped to nearly zero. Landlord, renter, and growth surfaces now share a cohesive visual system.

20%

Design lead time reduction

Faster assembly of new flows let the team focus on UX strategy instead of rebuilding UI from scratch.

Improved scalability

Global token and variant updates roll out across hundreds of frames in source-of-truth files — a change that once took days now takes hours.

More work
or a conversation?