notification-hierarchy

Guide four-tier notification hierarchy for SaaS user feedback systems.

28|3|Updated Feb 22, 2026

Search Tags:#notifications #ui design #user feedback #alert fatigue #saas design #ux patterns

Ready to run

npx skills add https://github.com/oborchers/fractional-cto --skill notification-hierarchy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: notification-hierarchy
Source: https://github.com/oborchers/fractional-cto/tree/main/saas-design-principles/skills/notification-hierarchy
Command: npx skills add https://github.com/oborchers/fractional-cto --skill notification-hierarchy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the common issue of alert fatigue and misapplied notification patterns in SaaS applications, ensuring users receive timely and appropriate feedback without being overwhelmed.

Core Features & Use Cases

Notification Hierarchy: Guides the use of inline messages, toasts, banners, and modals based on disruption level.
Feedback Patterns: Defines best practices for success, error, and informational messaging.
Alert Fatigue Prevention: Provides rules and principles to minimize unnecessary distractions.
Use Case: When designing a user interface, use this Skill to determine whether a "Save successful" message should be a temporary toast or a persistent banner, and ensure destructive actions are always confirmed with a modal.

Quick Start

Use the notification-hierarchy skill to review the design of a new toast notification system.

Frequently Asked Questions about notification-hierarchy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to design user notifications in a SaaS application?▼

To prevent alert fatigue, map notification patterns to a four-tier hierarchy so message urgency matches the disruption level. Using inline messages for contextual feedback and reserving modals for destructive actions minimizes unnecessary distractions.

When should I use a toast notification versus a banner in UI design?▼

Use a toast notification for temporary, non-critical feedback like a successful save action, whereas a banner should be used for persistent, system-wide messaging. This distinction aligns UX patterns with appropriate user interruption levels.

How do I design UX feedback patterns for success and error messages?▼

Designing UX feedback patterns for success and error messages requires matching the notification type to the four-tier hierarchy. Success messages often work as temporary toasts, while error messages and destructive actions require persistent banners or modal confirmations.

What are the limitations of using modals for user feedback?▼

The limitation of using modals for user feedback is that they cause high disruption by interrupting the user's workflow. They should be restricted to confirming destructive actions or critical errors to avoid severe alert fatigue within your SaaS design.

Does this notification hierarchy work for all SaaS design systems?▼

The notification hierarchy works for any SaaS design system by adhering to established design system principles. It provides flexible guidelines for feedback patterns and alert fatigue prevention that can be applied across different user interface workflows.