Strategic & Foundational
Design System Library
A scalable design system supporting Discovery Parks and G'day Parks across web and mobile platforms. Built to improve consistency, accelerate delivery, reduce duplication and establish a shared foundation for future AI-assisted workflows.
Digital Platforms
Discovery Parks & G'day Parks Website, and G'day Parks App
Design & Product Stakeholders
Designers, product owners and developers using design library.
Reusable Components
Shared UI patterns supporting web, app and campaign experiences.
Templates Created
Desktop, tablet and mobile templates accelerating delivery.
Problem
As Discovery Parks and G'day Parks evolved across multiple digital products, design decisions were becoming increasingly fragmented.
Patterns were recreated multiple times, design files became harder to maintain, and handover quality varied between teams.
Without a shared system, maintaining consistency across websites, mobile experiences, campaigns and future product initiatives became increasingly difficult.
My role
I led the evolution of a shared design system in Figma that established a common UX and UI foundation across Discovery Parks and G'day Parks.
This included defining reusable patterns, governance standards, documentation frameworks and component architecture that supported collaboration between design, engineering, marketing and product teams.
The challenge
Create a shared design system capable of supporting multiple brands, platforms and teams while reducing duplication and improving delivery consistency.
What I did
Shared Foundations
Unified Discovery Parks and G'day Parks patterns
Common interaction standards
Reusable UI components
Component Architecture
Atomic component structure
Scalable pattern library
Consistent naming conventions
Governance Framework
Documentation standards
Change management process
Cross-team adoption
Developer Alignment
Shared design language
Improved handover quality
Reduced implementation ambiguity
Design System Expansion
Marketing assets
Campaign components
Product experiences
AI-Ready Structure
Consistent component definitions
Structured documentation
Better support for AI-assisted workflows
Design System Evolution
Before
Separate files
Inconsistent patterns
Duplicate work
Manual handover
After
Shared library
Reusable components
Faster implementation
Consistent experiences
How The System Supported Delivery
Consistency
Shared patterns reduced visual and interaction differences across products.
Scalability
New experiences could be built using established components rather than creating interfaces from scratch.
Collaboration
Designers and developers worked from the same source of truth.
AI Readiness
Structured components and documentation improved the quality of AI-assisted design and development workflows.