Managing Categories

What are Categories?

Categories organize your evaluation questions into logical groups. During evaluations, results are broken down by category so you can see which areas are performing well and which need improvement.

Understanding Category Structure

Guideline Set: E-commerce Platform
├── Category 1: Navigation & Information Architecture
│   ├── How many clicks to find product categories?
│   ├── Is the breadcrumb trail visible?
│   └── Can users filter by multiple criteria?
├── Category 2: Visual Hierarchy
│   ├── Are call-to-action buttons prominent?
│   ├── Is the visual weight balanced?
│   └── Can users distinguish interactive elements?
└── Category 3: Accessibility
    ├── Do all images have alt text?
    ├── Is color contrast WCAG AA compliant?
    └── Can the flow be navigated by keyboard only?

Creating Categories

When you create a guideline set, you can add categories right away or add them later. Each category:

• Has a descriptive name (e.g., "Navigation", "Visual Design", "Accessibility")
• Gets a color for visual organization (helps during evaluations)
• Can contain multiple related questions

Best Practices

Group logically - Categories should represent distinct areas of evaluation. Don't mix "Navigation" with "Typography" in the same category.

Keep 3-7 categories - Too few and you lose granularity in results; too many and evaluations become unwieldy.

Reuse across flows - The same categories work for different flows and evaluations, which is why consistent naming and structure matter for trend tracking over time.

Managing Categories

You can:

• Add new categories at any time
• Edit names and colors to keep them relevant
• Delete categories (questions within will need to be reassigned or deleted)
• Reorder categories to match your evaluation workflow