Guidelines overview

Explore our guidelines to learn how to design cohesive and predictable products for Culture Amp using Kaizen.

Also known as:
GuidelinesGuideDesign documentation

AnchorNeed to know

  • Guidelines are used to document our decisions, onboard new designers and engineers, and are the source of truth for our shared practices.
  • These guidelines are flexible, and we continuously revise and expand them to match our evolving product needs.

To keep in mind

These guidelines help foster shared language for designers and front-end engineers.

Unlike components, guidelines don't contain reusable code. They sometimes describe how to find and use shared, reusable code, such as design tokens and templates.

When to use and when not to use

If in doubt, have a conversation with the Design Systems team or the design practice. If you feel strongly, talk about that.

When to use
  • Follow these guidelines when the behavior of an element you're designing is identical to an existing behavior.
  • Follow these guidelines when an inconsistent approach from the design system is conspicuous and could cause users to ask "why" something looks different in one place to another. This might even be the best approach when elements behave similarly but not identically.
When not to use
  • When consistency with the design system's guidelines would make an interface less predictable, break away and let the Design Systems team know.
  • When consistency with the system would be detrimental to the experience, break away and let the Design Systems team know.
  • When behavior is different, elements should look different. When designing a new element, let the Design Systems team know.

See also

If you're new to Culture Amp, start by reading these:

External links

Here are some examples of existing design systems or references: