Real-Time Incident Commander Console Brief

Role: Lead SRE Product Designer and Human-Factors Engineer with expertise in critical infrastructure mission-control interfaces.

Context

• Severity taxonomy: {{incident_severity_tiers}}
• Alert data feeds: {{alert_aggregation_sources}}
• Remediation automation level: {{runbook_automation_depth}}
• Live communication hooks: {{team_collaboration_tools}}
• Human-factors safety constraints: {{cognitive_load_guardrails}}
• Incident timeline sinks: {{postmortem_export_targets}}

Task

Produce a rigorous UI/UX design brief for an SRE Incident Command Console that unifies real-time telemetry alerts, collaborative triage, and safe interactive runbook execution during critical system outages.

Method

1. Establish the primary layout grid, prioritizing live health indicators, active responders, and root-cause timelines.
2. Design the alert deduplication and correlation card components, mapping {{alert_aggregation_sources}} to severity markers.
3. Formulate the incident timeline interaction model, supporting automatic event logging and manual operator annotations.
4. Build the runbook execution interface, specifying two-stage confirmation safeguards for {{runbook_automation_depth}} actions.
5. Incorporate visual stress-reduction patterns complying strictly with {{cognitive_load_guardrails}} to prevent alert fatigue.
6. Specify the real-time communication dock linking active calls, chat channels, and external status updates via {{team_collaboration_tools}}.
7. Detail the post-incident transition workflow that aggregates logs, actions, and milestones for {{postmortem_export_targets}}.

Constraints

• MUST require a two-step visual verification before triggering any destructive remediation script.
• MUST NOT overwhelm the viewport with raw unclustered logs; all incoming alerts must group under incident clusters.
• Latency for real-time status updates across collaborative operator sessions must not exceed 200ms.
• Auditable timeline events must have immutable visual state indicators.

Output format

Deliver the design brief formatted under these exact headings:

1. Mission Control Layout Grid (Zone partitioning, information density, and screen hierarchy)
2. Correlated Alert & Severity Component Spec (Visual badges, grouping cards, and triage actions)
3. Safe Runbook Executor UX Model (Action triggers, execution states, progress visualizers, and kill switches)
4. Collaboration & Status Synchronization Dock (Presence indicators, comms bridge, and external broadcast cards)
5. Post-Incident Timeline & Export Interface (Event chronological tree, tagging UI, and export presets)

Self-review

• Verify that the two-stage confirmation model for {{runbook_automation_depth}} effectively mitigates accidental destructive execution.
• Confirm layout accommodates {{incident_severity_tiers}} with unmistakable visual hierarchy.
• Ensure integration components for {{team_collaboration_tools}} maintain clear read/write status feedback.