Start with the design system Start with the design system to build on the research and experience of other service teams. This helps you avoid repeating work that has already been done. The design system gives you a strong foundation for common service needs. It allows your team to focus on the specific challenges of your product. Build on it. Do not start from scratch. Design system by role Why start with the design system? Streamline collaboration

Designers and developers work from shared components and guidance. This reduces rework and misalignment.

Improve accessibility

Accessibility is built into both the design and coded components.

Reduce testing effort

Components are tested across devices, browsers, and service contexts.

Maintain consistency

Components align with the broader system to create a cohesive user experience across government services.

Spend more time on high-value work

Using existing components saves time. You can focus on work that improves service quality, including:

  • Usability testing
  • User research
  • Content design
  • Accessibility reviews
  • Design quality checks
  • Low-fidelity prototyping and testing

This leads to better outcomes for users.

How to use the design system in your service

Follow these steps when designing and building your service.

Use system components first

Start with existing components and patterns. These meet most user needs.

Identify gaps through user testing

Test your service with users. Identify needs that are not covered by current components.

Before you design something new

Check what's already available and what's in progress. The team can point you to existing components, solutions other teams have built, and planned work that may meet your need.

Design and test new solutions when you need them

If you still have a gap, design a new solution and test it with users. Move forward only when testing shows clear user value.

Share what you learn

Share your findings with the design system team. Your solution may become part of the design system.

Do not create custom components without a clear user need. Unnecessary customization:
  • Increases maintenance effort
  • Slows delivery
  • Reduces consistency
Always confirm the need through research and testing. View the design system governance process Join design system drop-in hours to:
  • Get feedback on your service
  • Propose new components or patterns
  • Suggest updates to existing resources
  • Ask questions
  • Share feedback
Drop-in sessions are available to Government of Alberta product teams. Book time in drop-in hours