<h1 id="alert-fatigue">Alert Fatigue<a aria-hidden="true" class="anchor-heading icon-link" href="#alert-fatigue"></a></h1>
<p>Notes from <a href="https://vimeo.com/274820572">this tech talk</a> by Aditya Mukherjee.</p>
<h1 id="stat-framework-for-thinking-about-each-alert">STAT framework for thinking about each alert<a aria-hidden="true" class="anchor-heading icon-link" href="#stat-framework-for-thinking-about-each-alert"></a></h1>
<ul>
<li>Supported</li>
<li>Trustworthy
<ul>
<li>Do I trust this alert to notify me when a problem happens?</li>
<li>Will it stay silent if things are ok?</li>
<li>Will it give me enough info to diagnose problems?</li>
</ul>
</li>
<li>Actionable
<ul>
<li>At most one decision should be required ideally, the decision to whether take an action or not.</li>
<li>Alerts that are difficult to action become alerts that are ignored. If an alert is painful or annoying to action, you'll feel fatigued next time.</li>
<li>Should try to avoid stuff like "investigate" etc, make things more optional. Decision trees, interactive tooling etc is much better.</li>
<li>If it's unclear who should be taking action, the alert is not actionable.</li>
</ul>
</li>
<li>Triaged</li>
</ul>

STAT framework for thinking about each alert

Alert Fatigue


Hi! I'm Param! This is a place for my personal notes.

My website is https://param.codes, and I write more readable
stuff on my substack: https://newsletter.param.codes.

I've found that taking notes helps me remember things, and it's nice
to look back on information that you processed years ago. I jot down random things, there's no real structure, but some of these
notes could eventually become blog posts.

Some notes you might find interesting:

- [[history.laphams_quarterly.democracy.campaign_finance]]
- [[engineering.being_a_mentor]]
- [[history.china.dynasties]]
- [[history.india.indira_gandhi]]

I also keep notes on books I read [[here|books]].

This is built using [[Dendron|engineering.dendron]] and hosted using
[GitHub Pages](https://github.com/paramsingh/notes).

Get in touch via [Twitter](https://twitter.com/iliekcomputers) or email me at `me [at] param [dot] codes`!
