Collaborative Incident Timeline
Design an incident workspace that turns live technical events, decisions, and communications into a trustworthy shared timeline.
The brief
Understand the problem
Background
During an outage, alerts, chat messages, deployment events, hypotheses, and customer updates arrive from different systems. A chronological dump is hard to trust when timestamps conflict or important decisions are buried.
User context
Incident commander Jules is coordinating a checkout outage with engineering, support, and communications. They need one timeline that remains useful during response and later review.
Product problem
Responders need a fast shared record that distinguishes observed facts, hypotheses, decisions, and imported events without slowing active mitigation.
Objective
Design live timeline capture, event reconciliation, decision logging, and post-incident export for a severity-one outage.
What to design
Define the experience
Required experience
- Scan the current impact and recent timeline
- Add or import a typed event
- Resolve duplicate or conflicting timestamps
- Mark key decisions and prepare a review-ready record
Screens and states
- Incident command view
- Timeline event composer
- Event reconciliation
- Review and export
Core user flow
Follow the critical path
- 01
Jules opens a new incident and assigns core roles
- 02
Deployment and monitoring events stream into the timeline
- 03
Two reports conflict on when impact began, so Jules records the uncertainty
- 04
After recovery, the team marks decisions and exports a sourced chronology
Product rules
Requirements and constraints
Requirements
- Label fact, hypothesis, action, decision, and communication events
- Preserve original timestamps and sources when events are corrected
- Show current owner and status for active actions
- Support fast keyboard entry without forcing long forms
Constraints
- Imported events cannot be silently edited
- Sensitive customer details need redaction before export
- The live record must remain available during partial service failure
Reality check
States worth considering
Finish line
What to deliver
- Four desktop screens showing live response and review preparation
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Montserrat & Crimson Text
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Montserrat & Crimson Text
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
principleLaw of Uniform ConnectednessElements joined by a visible continuous connection tend to be perceived as one unit or as more strongly related than unconnected elements.
phenomenonCocktail-Party EffectPeople can follow one information stream amid competition, while personally relevant unattended material may sometimes capture awareness.
principleLaw of ContinuityAligned elements and smooth paths tend to be perceived as continuing in the same direction rather than changing abruptly.