Workshop Goals
By the end of the hour, you'll have practiced four things that actually matter on release day.
Confidence Building
Walk into your next launch day knowing you have a repeatable playbook for the moment things break.
Teamwork & Communication
Bring different release day perspectives into the discussion, share context, and land at a decision the whole War Room can back.
Triage Mastery
Sort a pile of incoming bug reports into severity levels and effort levels— quickly, and with reasoning you can defend.
Debugging & DevTools
Practice using the browser Console, Elements, and Network tabs (plus AI as a debugging partner) to isolate root causes fast.
Bug-Busting Mindset
Bugs on release day come with the territory. A calm War Room isn't one where nothing broke — it's one that knows how to react. Three pillars carry that.
Psychological Safety
Reward Curiosity
Respond together, not with blame or panic. Surface what's broken and share context.
Strategic Triage & Trade-Offs
Functional over Flawless
Weigh impact against effort. Resolve true release blockers now; defer the rest.
Leveraging Your Voice
Own Your Reasoning
Back your decisions with clear rationale. Make sure your reasoning is visible, not just assumed.
Bug Severity Levels
Severity describes how badly a bug affects the product. Priority describes how urgently your team should address it. Use severity alongside customer impact, available workarounds, and release timing to choose a priority: P1 (High), P2 (Medium), or P3 (Low).
Blocker — Feature Completely Broken
No workaround exists. Prevents a primary user flow. Causes severe loss of revenue, data loss, security vulnerabilities, or widespread app crashes.
Behavioral — Badly Frustrating UX
A workaround exists but causes highly frustrating user experience. Frustrated users can still eventually check out, but something important is clearly wrong.
Cosmetic — Polish & Alignment
Typographical errors or minor alignment issues with negligible impact. The app functions correctly but looks less polished. Users can still shop without friction.
Bug Categories
The Bug Report contains a variety of issue types. Each requires different debugging tools and approaches.
Visual / CSS
Layout breaks, z-index conflicts, pop-ups that won't close, mobile responsiveness issues.
Logic & Calculation
Incorrect totals, wrong price references, off-by-one errors, string math instead of number math.
Form Validation
Overly strict regex, stale state carried between selections, generic error messages that don't help the user.
Database / Data
Incorrect data references, sale prices not honored, data fetching errors.
Interaction & State
Buttons not responding, double-click registering twice, sold-out items silently added to cart.
Device-Specific
Touch targets too small on mobile, scroll bugs on iOS, viewport-specific rendering issues.
Prompting
AI agents can accelerate your debugging — but only if you prompt them well. Know where they shine and where they need a push, then use the three-step framework below on every prompt.
AI's strong suits
- Decoding a cryptic error — paste the surrounding code and one sentence about what you were doing; you'll usually get a real lead.
- Spotting the mechanical stuff: typos, missing semicolons, swapped argument order. Anything a second read would catch.
- Drafting unit tests once you've told it the behavior you want. Coverage without the boilerplate.
Where AI needs a nudge
- It can't see your app. Describe what's on screen and what you expected instead — vague prompts get vague fixes.
- Don't accept the first suggestion. Make it defend its logic, then read the diff before you click accept.
- Feed it the framework, file paths, and data shape — otherwise you'll get textbook Angular answers to your very specific bug.
You can't throw a vague request at an agent and expect production-ready code. To get the most out of AI during a high-pressure release, use a three-step framework: Brief, Audit, and Own.
Brief the Agent
- Define your role and the specific issue.
- Provide full context — logs, code, environment.
- State the current behavior vs. the expected behavior.
Audit the Output
- Don't assume AI is correct — watch for hallucinations.
- Force the agent to defend its logic.
- Stress-test for missing edge cases.
Own the Solution
- Never just click "Accept."
- Ask for step-by-step breakdowns.
- Cross-reference with reputable documentation.
Release Day Stakeholders & Bug Reporters
A release day War Room brings together people with different responsibilities. These stakeholders bring different perspectives to triage, fixes, and launch decisions.
Engineers investigate errors, read stack traces, and write fixes. They assess technical risk and estimate how much work a fix will take.
Product managers connect bugs to customer experience and business impact. They help the team prioritize issues that affect revenue, conversion, and trust.
Designers spot confusing interactions, layout problems, and barriers to using the product. They help the team assess whether a fix works across screen sizes and input methods.
Engineering managers protect the team from unnecessary panic, keep work scoped, and make sure the right people work on the right issues.
QA testers reproduce issues, identify edge cases, and verify fixes. They check for regressions and help the team assess whether the release is ready.
Leaders weigh release timing, business risk, and customer impact. They need clear status updates to support launch decisions and communicate with stakeholders.
Customer support brings reports from affected customers into the release day conversation. They collect details engineering needs, spot patterns across tickets, and keep customers informed while a fix is on its way.