<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Swati Pal on Medium]]></title>
        <description><![CDATA[Stories by Swati Pal on Medium]]></description>
        <link>https://medium.com/@swati.pal2804?source=rss-d24dd4283d46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AoAcgLymjfY2w0ANtiqw7A.jpeg</url>
            <title>Stories by Swati Pal on Medium</title>
            <link>https://medium.com/@swati.pal2804?source=rss-d24dd4283d46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:38:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@swati.pal2804/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Redesigning the Alert System.]]></title>
            <link>https://medium.com/design-bootcamp/redesigning-the-alert-system-758e4dc9a64e?source=rss-d24dd4283d46------2</link>
            <guid isPermaLink="false">https://medium.com/p/758e4dc9a64e</guid>
            <category><![CDATA[anomaly-detection]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Swati Pal]]></dc:creator>
            <pubDate>Mon, 21 Mar 2022 17:51:06 GMT</pubDate>
            <atom:updated>2022-11-09T07:14:47.152Z</atom:updated>
            <content:encoded><![CDATA[<p>Our experience of re-designing the alert system of a SaaS product.</p><p>Team: <a href="https://medium.com/u/d791f9ed3943">Aayush Jain</a>, <a href="https://medium.com/u/d24dd4283d46">Swati Pal</a>, &amp; <a href="https://medium.com/u/2545fcd41997">Devesh Shirsath</a>.<br>Co-author: <a href="https://medium.com/u/2545fcd41997">Devesh Shirsath</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBzZvLGin5TeKxVmS0tcgA.png" /><figcaption>Our primary screens of Incident Management System</figcaption></figure><h3>Cliff.ai overview</h3><p>Dashboards are a bit messy, and also because of the large number of data, there is a high risk of missing the anomalies. At <a href="http://cliff.ai/">Cliff.ai</a>, we work on ‘actively monitoring’ the key metrics and catch unexpected spikes or dips in the metrics <strong>AUTOMATICALLY</strong> and inform our clients.</p><h3>What happened?</h3><p>At <a href="http://cliff.ai/"><em>Cliff.ai</em></a>, we had been hearing our users’ complaints about not being able to receive the alert notifications even after the detection of anomalies. We dug deep into the problem and discovered that users weren’t receiving the notifications because of <strong>the complex process of setting up the “Alert Rules”</strong>. And the functionality of whom and when to notify was bare-bones.</p><h3>Understanding the actual problem</h3><p>As a growing product, there’s always something to improve upon and add value. We expect our users to have a successful journey with cliff.ai and we wanted them to utilize the platform to its full capacity. But after actually listening to their experience of using our alert system, we realized that we had to put more work into the design of cliff.ai.</p><p>While taking proactive actions to push users to complete the happy path, we always had a strong narrative of getting rid of dashboards. For that, we had an Alert Rule feature. An ideal “Happy Path” which looked something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*vAk-manJkeR6k5DC.png" /><figcaption>Our old User Flow</figcaption></figure><h4>But there were a couple of problems with this flow that we realized after listening to our users.</h4><blockquote><strong><em>Problem 1:</em></strong><em> Some users weren’t able to receive the notifications whenever there was any anomaly in the metric.</em></blockquote><p><strong>Reason:</strong> Those users didn’t set up the “Alert Rules” properly. There can be many reasons for them to not set up those rules.</p><p>— a.) They didn’t know they were supposed to set up Rules to <em>receive notifications on their devices.</em></p><p>— b.) They just <em>forgot</em> to set up alert rules.</p><p><strong>Solution:</strong> Automate the Alert Rule setup process. Provide a Default Monitor (yes we renamed Alert Rules to Monitor). So that even if the user does not set up any Monitor by themselves in the beginning, a base monitor will make sure they keep receiving the notification whenever anomalies occur.</p><blockquote><strong><em>Problem 2: </em></strong><em>Users could not choose whom and when to notify in case of occurence of incidents.</em></blockquote><p><strong>Reason:</strong> Cliff.ai didn’t have the functionality of informing <em>specific people</em> of the team at a <em>specific time. </em>That is, ‘<em>after detection of an anomaly, notify John. If he is unable to acknowledge that within the given time, notify Saahil’ and so on…</em></p><p><strong>Solution:</strong> Establish an escalation policy that determines whom, where and when the notifications will be escalated to specific teams or individuals when anomalies occur.</p><blockquote><strong><em>Problem 3</em></strong><em>: It was hard to draw insights about incident patterns on metrics</em></blockquote><p><strong>Reason:</strong> There was no insight page or incident “repository”, where users could draw quick critical insights from the metric incidents from a “single place”.</p><p><strong>Solution:</strong> Provide an incident page where users can see all the incidents datewise and help them notice key information about the incidents.</p><h3>The impact we aimed for our users</h3><ol><li><strong>Time-saving:</strong> Less interaction with the data saves time. The time saved can be used for something more productive and impactful. Business owners’ time is very valuable and in that same duration, impactful work leads to more <strong>value generation.</strong></li><li><strong>Business Growth:</strong> Less reliable metric observability creates friction in business. Good tools will make irregularities more predictable which leads to <strong>better business planning</strong> and hence better business growth for users and cliff.ai as well.</li></ol><h3>Use Case</h3><blockquote><em>Aayush runs an e-commerce platform. To monitor his business, he uses a reliable platform called cliff.ai to track all the metrics.</em></blockquote><blockquote><em>It’s a festive season and the website sees enormous traffic suddenly. He now wants to be notified when the website records traffic of more than 65K visitors so that he can alert his technology team to prepare for upscaling.</em></blockquote><blockquote><em>In order to do so, he sets up a stream, inputs threshold value, and just waits for the traffic notification to pop.</em></blockquote><blockquote><em>Not only does his website traffic surpass 65K threshold mark, but also, he does not recieve any notification from cliff when the incident happened. He got frustrated.</em></blockquote><blockquote><em>Thankfully, he raised a complaint to our customer satisfaction team regarding the same issue which got us thinking.</em></blockquote><p>We then realized that the user flow needed to be improved. That’s when we started working on our Incident Management System.</p><h3>Brainstorming — Deciding the design lifecycle</h3><p>We started brainstorming about the feasibility of the features. We addressed basic whats, whys, and hows about the overall incident lifecycle.</p><p>While brainstorming, we had to decide the exact design lifecycle aka, the process. We didn’t want to waste our time by randomly incorporating non-impactful design steps just for the sake of following the generic UX design procedure. We decided to <a href="https://uxplanet.org/whats-a-design-sprint-and-why-is-it-important-f7b826651e09">Sprint</a> through each part of the user flow one by one. We started with detailed pages of each feature and then designed the insight pages (or list pages) and followed the same reversed order for all the features. So in each sprint, we began with information architecture followed by low-fidelity wireframes. After creating a satisfactory number of iterations, we jumped to high-fidelity screens and worked on them in a similar iterative fashion.</p><h4>Creating User Flow — Inspiring from companies in the infrastructure monitoring domain</h4><p>Now that we have a detailed PRD, we more or less know what the flow was going to look like but that’s not enough, to stand out from the competitors, we first need to see what they are good at and what we can do better. Our competitors in terms of IMS were mainly Pagerduty, Squadcast, Opsgenie(Atlassian). As far as visual design was concerned, we had our design guidelines and patterns established already, so we needed to focus on the UX analysis of these products. Concerning our product design, we had some things from each product we could take inspiration from. But for us, Opsgenie resonated with our flow to a larger extent. Hence, we started to analyze its user flow and found it quite intuitive. To a small extent, their flow had some similarities to our flow, which motivated us to modify our user flow for better.</p><p>Changes we made in our flow after competitors’ analysis.</p><ol><li><strong>Nomenclature:</strong> The naming convention is very important when it comes to accessibility. Users should know what the feature is for or what the given action does just by reading the name. Although our naming convention was easily understood by our team, we realized it could be improved for better and made them user-friendly.</li><li><strong>Hierarchy:</strong> We improved the overall hierarchy of our system.</li></ol><p>After brainstorming the feasibility of all the features, we started structuring all the information we had. Our new user flow had these key steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*9NhP2blQ_xw6Mj7m.png" /><figcaption>New User Flow Overview</figcaption></figure><h3>How we define our Incident management system</h3><p>An incident is an event or series of events that are generated when there is any disturbance in service due to numerous reasons. At <a href="http://www.cliff.ai/"><em>cliff.ai</em></a>, after the creation of a Stream, when a bunch of related anomalies is found, we group them to create an Incident.</p><p>Considering the outcomes of competitive analysis, we worked on the user flow and transformed the navigation of the alert system and we realized the importance of segregating to multiple sections and thus decided to divide our existing alert system into three parts:</p><ol><li><strong>Monitors:</strong> Here, users will be able to select the rule, add a stream, multiple measures, and dimensions by setting upper and lower thresholds for related metrics.</li><li><strong>Incidents:</strong> If an anomaly occurs due to any monitor, an incident will be created and this process will be done on daily basis.</li><li><strong>Escalation Policies:</strong> Now here comes the most crucial step — Whom, Where and When to notify. users have the freedom to select one or multiple users or even teams to notify at different intervals on different platforms like mail, Slack, Viber, etc.</li></ol><p>Let’s go deeper and see all three parts in detail.</p><h4>Monitors</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DCg8rv365Qt-SenBMlfUEg.png" /><figcaption>Final Design for monitor list page</figcaption></figure><p>This is the primary screen of ‘Monitors’ where the users have the list of all the monitors created by them. From this list, users can get the details of the:</p><ol><li>Type of monitor</li><li>The person who has created it and on what date</li><li>Intertwined stream</li><li>Number of incidents created under that monitor</li><li>Frequency of incidents occurring.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogyqZcB9fLS7JMAa0UzLJg.png" /><figcaption>Monitor List Page Iterations</figcaption></figure><p>We tried a couple of high-fidelity iterations before deciding on the final one. We experimented with the layout based on the information we had and finalized the one that seemed consistent with the rest of the application.</p><p>Now, on opening a particular monitor, we can view all the details related to that monitor, out-and-out. This will help in analyzing the top measures and dimensions on which maximum incidents are occurring along with the respectively assigned responders who are handling these incidents.</p><p>Also, the heatmap will help in viewing all the incidents that occurred on this monitor in the past:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4n9NKEJkmwDsPhFgtklFkQ.png" /><figcaption>Monitor detail page</figcaption></figure><h4>Incidents</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOd3qSw5VreU176mSRcIkQ.png" /><figcaption>Final Incident List page iteration</figcaption></figure><p>The primary screen of ‘Incidents’ consists of the list of incidents that occurred on anomalies based on the thresholds of the monitors created by the users and the list will be created based on a particular date. It will be the central “hub” where the user can view all the incidents/alerts so far in their data. All the alert management-related actions will happen from this view.</p><p>Users will get a holistic analysis of all the incidents with the help of an insight section and a detailed analysis of any particular incident with a page dedicated to that which increases the accessibility of Incident information manifolds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rSaufHT_C30jewhUnQWdwA.png" /><figcaption>Incident list page Iterations</figcaption></figure><p>The Incident Details Page contains:</p><ol><li>Every detail of the incident that occurred is shown on the top.</li><li>Detailed (graphical) insights of what caused that incident so that users can understand and act upon it quickly.</li><li>Responders list and ability to ‘Add New Responder’ to that Incident.</li><li>The timeline of activity that happened on that incident will help in maintaining a log of status changes.</li><li>Comment section where team members can share their thoughts on that incident.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqqO6FhZkg_vnDIo2OI7AA.png" /><figcaption>Incident details</figcaption></figure><p>The Heatmap is to show when and how many similar incidents happened in the past which has been already resolved:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqdl5xytYO4LDWi-wHqFyw.png" /></figure><h4>Escalation Policies</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O5aQ31xyVP3WHvP85jeH5Q.png" /><figcaption>Final Escalation Policy Page Iteration</figcaption></figure><p>Now comes the fun part, as soon as an Incident is generated, the notifications will be pushed to the respected assigned responders based on the Default Escalation Policy, AUTOMATICALLY!</p><p><em>i.e., Users do not need to set up anything for the feature to work properly. Our Base Escalation Policy will take care of it for them. Hence one problem is solved.</em></p><p>However, we had to address the problem of whom and when to escalate the notification. This is where Escalation Policy comes into the picture. By adding any number of users or teams and setting favorable rules so that in case of occurrence of an Incident, the assigned responders would be notified based on those preset rules.</p><p>An escalation policy describes the following three things:</p><ol><li><em>Who</em> to deliver the notifications to</li><li>In what order or <em>interval</em>, notifications should be delivered</li><li>On <em>which</em> platform to deliver the notifications</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FUh-ArlWglTBILuRuKLL6A.png" /><figcaption>Escalation Policy Iterations</figcaption></figure><p>Users can decide who to notify in case an alert goes unresolved. The escalation is also controlled by the number of minutes/hours to wait before notifying the next person in the queue.</p><p>And, if no one in the escalation queue responds, the actions can be repeated <em>n</em> number of times, which is decided by the user.</p><h3>My learnings after leading the project:</h3><ol><li><strong>Planning the roadmap</strong>: Pulling off the design journey efficiently was a big challenge especially because this was a huge project I was given ownership for. I ensured that every individual entity including project managers, stakeholders, interns, and engineers were looped into each design decision that I intended to make.</li><li><strong>Mentoring</strong>: Getting the juniors onboard in every design decision to maximize their participation and learning was one of my priority goals while working on this project. It polished my leadership skills.</li><li><strong>Giving feedback</strong>: Taking feedback is easier than giving feedback on someone else’s designs. It helped me improve in a way that I could give feedback without overwhelming their thought process.</li><li><strong>Audits</strong>: The way we iterate while designing, the same way the developers should iterate after audits as nothing can be built perfectly in one go.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=758e4dc9a64e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/redesigning-the-alert-system-758e4dc9a64e">Redesigning the Alert System.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>