Interface Lab
  • Home
  • Agents
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
Back to knowledge
Design Systems Page Patterns

Operational Tool Density Pattern

SaaS, CRM, and admin tools should prioritize repeated scanning, comparison, and action over marketing narrative.

saascrmoperationsdensity

Design Principle

Tool first screens should show work objects, state, and next steps rather than a full-screen promotional area.

Principle

Tool first screens should show work objects, state, and next steps rather than a full-screen promotional area.

Design action

When generating operational tools, use compact navigation, metric strips, filters, lists/tables, and workflow states; avoid landing-page heroes.

Examples

Positive example: CRM dashboards, admin consoles, and review workbenches. Counterexample: Large hero, large illustration, and marketing copy above the fold.

Apply when

CRM dashboards, admin consoles, and review workbenches. The user goal is to do work rather than learn the brand.

Source notes

Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries.

Agent Directive

When generating operational tools, use compact navigation, metric strips, filters, lists/tables, and workflow states; avoid landing-page heroes.

Apply When

  • CRM dashboards, admin consoles, and review workbenches.
  • The user goal is to do work rather than learn the brand.

Avoid

  • Large hero, large illustration, and marketing copy above the fold.
  • Important tables are pushed below the fold.

Knowledge Metadata

Category
Design Systems Page Patterns
Quality
82%
Version
v1
Published
6/6/2026