Big + Fire
Red signals danger, urgency, and error. Red warnings demand attention. Red alerts indicate critical problems. Red error messages mark failures. The color's psychological urgency makes it appropriate for high-priority signals but creates problems when overused. Everything marked red dilutes red's impact—if everything is urgent, nothing is urgent. Red should be reserved for genuinely critical states. Systems with good color discipline use red sparingly. Non-critical warnings use yellow or orange. Informational messages use blue or green. The red scarcity preserves its signaling power. Red also indicates heat and activity—red-hot CPUs, red zones on heatmaps, red-line performance limits. The intensity association makes red appropriate for showing maximum values and boundary conditions. Use red deliberately, not habitually.
Red is universal alert signal. Stop signs are red. Emergency buttons are red. Critical alerts are red. The color immediately communicates danger or urgency.
Interface design uses red for errors and critical states. Red text indicates failed validation. Red icons mark system failures. Red badges show unread critical notifications. The consistent use reinforces red's alerting function.
But red loses power through overuse. Systems that mark minor issues red train users to ignore red signals. The boy-who-cried-wolf effect makes genuine red alerts less effective. Red should be reserved for situations requiring immediate attention.
Red represents heat and high intensity. Temperature visualizations show hot areas in red. Performance graphs show maxima in red. Resource utilization shows critical levels in red.
Heatmaps use red for maximum values. Traffic concentration, error rates, resource consumption—all show peaks in red. The color immediately identifies hotspots requiring investigation.
The heat association makes red appropriate for showing dangerous proximity to limits. CPU temperature approaching thermal shutdown. Memory usage approaching exhaustion. Request rate approaching capacity. The red coloring signals imminent problems.
Red means stop. Red traffic lights halt traffic. Red prohibitory signs forbid actions. Red buttons trigger emergency stops. The stop signal is culturally universal.
Destructive actions use red buttons. Delete actions, shutdown commands, data-purging operations—all appropriate for red treatment. The red coloring signals irreversibility and danger.
But overusing red for ordinary actions dilutes its stopping power. Cancel buttons shouldn't always be red. Routine operations don't need red warning. Reserve red for genuinely dangerous actions.
Operating "in the red" means exceeding safe limits. Financial losses put accounts in red. Performance beyond sustainable capacity is redlining. The red zone is dangerous territory.
System monitoring shows red zones for critical thresholds. Disk usage above 90% shows red. Error rates above tolerance show red. Response times beyond SLA show red. The red highlighting demands intervention.
Red zone proximity requires different strategies than red zone entry. Approaching red (yellow/orange) suggests preventive action. Entering red demands immediate response. The color gradients communicate urgency escalation.
Red herring is misleading clue—something that appears significant but is irrelevant. False positive alerts are red herrings. They trigger red warnings but don't indicate actual problems.
Excessive red herrings degrade alert credibility. When most red alerts are false positives, operators ignore them. The genuine critical alert gets missed among false alarms.
Reducing red herrings requires tuning alert thresholds. Tighten criteria to reduce false positives. Add context to distinguish true problems from anomalies. The tuning preserves red's signaling value.
Form validation shows errors in red. Invalid inputs get red borders. Error messages appear in red text. The red treatment clearly marks what needs fixing.
Real-time validation uses red feedback immediately. Type invalid email, field borders turn red. Enter out-of-range number, red warning appears. The instant red feedback guides correction.
But premature red frustrates users. Showing red before user finishes input feels hostile. Validation should wait for field exit or form submission. The delayed red provides correction without harassment.
Status lights use red for failed or critical states. Service health shows green (healthy), yellow (degraded), red (failed). The traffic light pattern is intuitive.
Dashboard design uses red sparingly. Too many red indicators create panic. The sea of red obscures which failures are most critical. Priority ranking prevents red overload.
Red status should indicate actionable problems. Red without available action creates helplessness. The red state should accompany clear remediation steps.
Red-green color blindness affects significant population. Red-only signaling fails for color-blind users. Combining red with shapes, icons, or text ensures accessibility.
Critical alerts should never rely solely on red color. Add warning icon, use distinct positioning, include explanatory text. The multi-channel signaling works for all users.
Color contrast matters for visibility. Red on black has good contrast. Red on orange has poor contrast. The color combination should ensure readability.
Business intelligence uses red for negative metrics. Revenue below target shows red. Customer churn above threshold shows red. The red highlighting identifies underperformance.
Executive dashboards use red indicators for metrics requiring executive attention. The red filtering helps executives focus on problems needing their intervention.
But chronic red creates learned helplessness. If metrics are always red, the red stops motivating improvement. Systems should be tunable to show achievable green states.
Red button is emergency control—last resort for critical situations. Emergency stop buttons are red. Panic buttons are red. The red button is both warning and enabler.
User interfaces rarely need true red buttons. Most "delete" operations don't warrant red button treatment. The red button should be reserved for genuinely dangerous operations.
Red button design should prevent accidental activation. Require confirmation, add delay, use two-step process. The protections ensure red buttons activate only when truly intended.
"In the red" performance metrics indicate unsustainable operation. CPU constantly at 100% is red performance. Memory paging heavily is red performance. Network saturated is red performance.
Red performance requires intervention. The system cannot continue in red indefinitely without degradation or failure. Temporary red is acceptable; sustained red demands capacity increase or load reduction.
Performance dashboards show current state color-coded. Green indicates comfortable margins. Yellow suggests approaching limits. Red indicates exceeded thresholds. The colors enable at-glance assessment.