NOTE: Demo visuals use either blurred real data or synthetic placeholders to protect customer privacy.
Expanding Beyond the Pilot
The early pilot exposed a gap. Some teams depended on CloudWatch for logs, others used Confluence and Go Links for runbooks. Without coverage for all, adoption would stall.
- Logs are missing for teams that relied on CloudWatch.
- Runbooks are organized inconsistently across teams.
- No easy setup path for new engineering groups.
Making Nora Easy to Enable
Rishi rebuilt the configuration flow so teams could enable Nora in Slack with just two steps: add Nora to the channel and run “Edit Persona.” From there, Nora automatically populated its own instructions and began monitoring alerts.
- Added CloudWatch integration for real-time log summaries.
- Linked codebase context to triage reports.
- Surfaced recent PRs and deploys alongside metrics.
- Included team-specific runbooks using GoLinks.
Each new data source deepened context while keeping the setup friction low. Engineers didn’t have to learn another interface or script; Nora lived within the interfaces and scripts they already used.
Broader Impact Across Engineering
As more teams adopted Nora, the gains became structural. Alerts were triaged more quickly and incidents documented more thoroughly. The uniform format of Nora’s posts standardized how teams approached first response.
- More consistent triage quality across teams.
- Reduced mean time to acknowledgment and investigation.
- Improved clarity for follow-the-sun support.
In the next phase, Rishi aims to refine controls so Nora focuses on higher-priority alerts and remains silent during routine noise.
Peer Perpective: Build Momentum
Teams noticed that Nora’s adaptability outpaced the capabilities of commercial tools. The Gen AI team’s quick iteration made every sprint feel immediately valuable. With engineers requesting integrations rather than alternatives, Nora was clearly becoming a default part of incident response culture.
