Project Triage: What to Do When Everything Hits the Fan
summary
A consultancy rewrites a CMS for a multi‑brand medical chain, hits four months of stalled signoffs, and traces it with five whys to a manager avoiding stakeholders; resolution: add interim deliverables, bend the process, and restore momentum. A separate promotion site launch floods logs, prompts a calm triage using an incident response plan, an incident manager, checklists and paired recovery, fixes the exploit, and adds a QA step so the same script omission never recurs.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:12TWO KINDS OF PROBLEMS THE PROJECT KIND THE TECHNOLOGICAL KIND PLANNING UNEXPECTED BUGS
- 9:35OH YEAH, AND WE COULDN'T GET THE CLIENT TO SION OFF ON ANYTHING IT WAS A LITTLE STRESSFUL
- 11:52THEY ARE HUMAN BEINGS WITH COMPLEX BEHAVIORS, THOUGHT PROCESSES, AND MOTIVATIONS.
- 18:43MOST PROJECT (AND PEOPLE) PROBLEMS ARE THE RESULT OF MISMATCHED EXPECTATIONS, A LACK OF COMMUNICATION, OR (MOST LIKELY) BOTH.
- 27:48INCIDENT RESPONSE ARSENAL
- 36:241. CALM DOWN 2. MAKE A PLAN THEN PREVENT IT FROM HAPPENING AGAIN
related talks
35mAvoiding the Petard: Triage at Scale in Firefox Quantum
46mManaging The Process
27mThe art and practice of documentation triage
32mBuild vs. Buy in the Midst of Armageddon
31mPixels, Promises, and Panic - Horror Stories of Production Nightmares
21mRelieving Technical Debt through Short Projects
31mManaging Unmanageable Complexity
45mChaos to contained How a content project can lead to better content BAU