<?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 Erin Kelly on Medium]]></title>
        <description><![CDATA[Stories by Erin Kelly on Medium]]></description>
        <link>https://medium.com/@erin.kelly_?source=rss-4cab7fbdca24------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XMAF1BDuLPc926yG</url>
            <title>Stories by Erin Kelly on Medium</title>
            <link>https://medium.com/@erin.kelly_?source=rss-4cab7fbdca24------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:08:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erin.kelly_/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[Defining Klaviyo’s notification usage and framework]]></title>
            <link>https://medium.com/@erin.kelly_/defining-klaviyos-notification-usage-and-framework-9edfeb879bfd?source=rss-4cab7fbdca24------2</link>
            <guid isPermaLink="false">https://medium.com/p/9edfeb879bfd</guid>
            <category><![CDATA[content-design-system]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[notification-system]]></category>
            <dc:creator><![CDATA[Erin Kelly]]></dc:creator>
            <pubDate>Thu, 20 Jun 2024 18:52:02 GMT</pubDate>
            <atom:updated>2024-06-20T18:52:02.948Z</atom:updated>
            <content:encoded><![CDATA[<p>“Erin!! What’s the difference between a notification and an alert?”</p><p>That’s how it started. A team of designers came to me searching for clarity on our notification patterns. We held a brainstorm to understand how different stakeholders thought about our notification landscape. We learned that the problem had deeper roots.</p><p>We confirmed that notification guidelines only provided our designers with a basic structure. They weren’t set to scale with future features and product offerings, which resulted in designers, product managers, and developers using notifications differently.</p><p>This led to a 2 month audit of Klaviyo’s product to understand how notifications were being used.</p><p>The result that followed had a goal of providing a cohesive and intuitive notification system that increased user satisfaction, reduced confusion, and improved overall usability<em>. </em>We aimed to standardize the usage of our notification components, and to better define the patterns and guidelines associated with them.</p><h3>Strategy and process</h3><p>I’ve been lucky enough to work on a variety of projects in my time at Klaviyo. My experience across projects, along with my knowledge of the existing notification framework and guidelines, served as a solid foundation to establish the steps and process.</p><p><strong>Initial steps</strong></p><p>We first put together a project plan. The problem and project goals needed to be laid out so all partners and stakeholders were aware and aligned. This plan included the project details, timeline, and jobs to be done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l6Tgq_PgqkdYtGyc" /></figure><p><strong>Get the data</strong></p><p>Next, it was time to pull the qualitative and quantitative data. I wanted to make sure that user insights informed design decisions, so that the final solution met user needs, designer needs, and provided an optimal experience. I reviewed past user feedback on notifications to gauge overall sentiment, collected data on email engagement and various notification types, and consulted our support team to learn more about any issues users might have with notifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ONtEbMNH6OI5FfsW" /></figure><p><strong>Audit</strong></p><p>Understanding the current state of notifications in the end-to-end experience was essential. My goal was to understand usage patterns and if there was an over-reliance on any specific component or type.</p><p>For example:</p><ul><li>Were we only notifying the user about errors?</li><li>Were we only using banners to communicate a certain notification type?</li><li>How were toasts being used?</li></ul><p>Understanding current patterns was key to identifying inconsistencies and informing new guidelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RMLI0LZTSEp_-MQt" /></figure><p><strong>Compare</strong></p><p>Next up was the competitive audit. Identifying industry content patterns and design patterns was the fun part. I analyzed how best-in-class companies surfaced their notifications, and found patterns across softwares in our industry. From there, I looked for similarities and differences to identify where we were falling short and where we were doing well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0giUffWciGibHEVg" /></figure><p><strong>Identify themes + opportunities</strong></p><p>From this work, themes started to emerge. Themes validated that current guidelines weren’t robust enough to be used accurately and that we needed to address the inconsistent use of notifications. So, we needed a stronger pattern for each notification component and type.</p><p><strong>Implementation</strong></p><p>We were focused on creating the most ideal and cohesive experience. This meant being consistent end-to-end and connecting the dots for users. Our notifications should show up the same every time so that users can understand and navigate Klaviyo easily.</p><p>The next steps were to:</p><ol><li><strong>Create pattern guidelines for all notification types and update the framework.</strong> The notification framework would cover our principles, components, and types. The pattern guidelines would cover how to determine when to use a specific notification type and how to write for it. These guidelines included examples, best practices, formatting (casing, punctuation, text styling), message structure, voice, and tone.</li><li><strong>Create content design guidelines per notification type and component. </strong>I created a list of all notification components that needed content guidelines. Then, I began to write guidelines based on what we wanted “great” to look like. I pulled a variety of use cases and examples I’d written in the past. The final guidelines included best practices, character count, formatting, message structure, and examples.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GN_8fAzRpt3oDKJH" /></figure><h3>Contributions and impact</h3><p>Guidelines were published and available for product designers, product managers, developers, and any one who would write in-app notifications at Klaviyo. The examples included in the guidelines have taken designers without dedicated content design help to the next level, allowing them to implement high-quality content that users will recognize. These examples have improved speed-to-creation and quality of content.</p><p>The work I contributed to this project showed my stakeholders the types of activities involved in content design and helped raise visibility to the work content designers do. I was seen as a subject matter expert and am still collecting feedback on how to improve the guidelines going forward. I’m excited to iterate on these guidelines and see where they go next.</p><h3>Reflection</h3><p>Notifications are content-driven components. The purpose of a notification is to communicate. Visual treatment and placement are part of the solution, but they complement the content. All decisions that led to the solution were rooted in how the content would surface.</p><p>I’m lucky to work at a company that provides me opportunities to take ownership and do strategic work across a team of 60+ designers. And it’s exciting to watch others understand how content design can help influence future projects.</p><p>Thank you to my friends and teammates in product design, behavioral design, design research, product analytics, lifecycle marketing, product management, sales, customer success, and support who helped inform the outcome of this project.</p><p>If you want to see the final product, head to our design system, Ascent. <a href="https://www.ascentdesignsystem.com/38f371b04/p/6575b9-notifications">Review Ascent notification framework</a></p><p>If you want to chat about this work, <a href="https://www.linkedin.com/in/eringkelly/">connect with me on LinkedIn</a> or <a href="https://adplist.org/mentors/erin-kelly">schedule a session with me on ADPList</a>. I’d love to learn from others!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9edfeb879bfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Content Design Team’s Favorite Kickoff Questions]]></title>
            <link>https://medium.com/klaviyo-design/our-content-design-teams-favorite-kickoff-questions-93a8ee54b039?source=rss-4cab7fbdca24------2</link>
            <guid isPermaLink="false">https://medium.com/p/93a8ee54b039</guid>
            <category><![CDATA[kickoff]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[content-design]]></category>
            <dc:creator><![CDATA[Erin Kelly]]></dc:creator>
            <pubDate>Tue, 05 Jul 2022 13:59:51 GMT</pubDate>
            <atom:updated>2022-07-05T21:16:13.876Z</atom:updated>
            <content:encoded><![CDATA[<p>At Klaviyo, our project kickoffs are when we learn the information needed to begin wireframing. Our goal is to gather as much information as possible. This makes our writing process a lot easier.</p><h3>What’s the project?</h3><p>First, we need to know what type of project we’ll be working on and where it will live in the product.</p><h3>What’s the goal?</h3><p>Next, we find out what the project goal is and how it will be measured by the product team. Every project is framed by a problem that needs a solution. Aligning on the problem and solution is critical during the early stages of the project.</p><p>Asking questions outright is perfectly acceptable during kickoffs. The product team is composed of product managers and product analysts who work with data regularly.</p><p><strong>Here’s some questions we like to ask for project goals:</strong></p><ul><li><strong>What do we want to learn?</strong> Asking this question allows us to align with the product team and figure out what we want to learn about the user or business from this initiative. This information is always listed at the top of our primary spec document.</li><li><strong>Is this going live immediately? If not, what will this be tested against?</strong> The product team usually tests designs with a small portion of users, a large portion, or all of our users. We’ll ask to see the current experience that we’ll be testing our design against, because it help to determine the variation of the content or design.</li><li><strong>What are the requirements?</strong> We want to know the minimum objectives that need to be met for the proposed solution to be accepted and tested.</li><li><strong>Has this been tested before? What have we tried in the past that has not worked?</strong> We want to make sure we approach the task differently than before. Find out if there are old explorations that exist in a Figma file somewhere that never went live.</li></ul><p><strong>Questions we ask for measuring the project:</strong></p><ul><li><strong>Are we trying to reduce the bounce rate?</strong> This may mean combining pages of content and reframing the order of messaging.</li><li><strong>Are we trying to increase the completion rate? </strong>Of all the users that are in the middle of an action, we want all of them to complete it from start to finish. Analyzing drop off on certain screens can help you implement more encouraging or success messages.</li><li><strong>Are we trying to increase page views?</strong> Of all the users that visit Klaviyo, we want more to go to a certain page in the product.</li><li><strong>Are we trying to increase conversion? </strong>Of all the users that visit Klaviyo, we want to increase the number of users that upgrade their Klaviyo plan.</li></ul><h3>What’s the context?</h3><p>One of the first things we do is find out as much context as possible about users’ experiences while in the app. Collaborating with the UX Research team to find out who our users are for this project and their journey is essential.</p><p><strong>Questions for us to gain more insight:</strong></p><ul><li><strong>What do we know about our users?</strong> It helps to understand what typical user behaviors are to inform the project. User personas are also referenced during this time.</li><li><strong>What is the user flow?</strong> Ask where the user is coming from and where they are going to (or what will set them up for success). Is the user already in Klaviyo? Or are they coming from the marketing homepage? We want to make sure users’ next experience is consistent with their previous experience.</li><li><strong>Are we targeting any specific geographic region?</strong> Find out if the experience will only be tested in specific states, zip codes, or markets. This is helpful for SMS experiments, as SMS is only available in certain regions as of today (July 2022).</li><li><strong>How do we treat existing customers?</strong> Find out if the experience is targeted to new customers or existing customers. If you are targeting new customers, discuss how to handle existing customer traffic.</li><li><strong>What marketing channel are users coming through to land on this experience?</strong> Especially during an onboarding experience, we want to know if users are coming from paid search, natural search, a Facebook ad, email, etc. Knowing this information allows their experience to be personalized from the start.</li><li><strong>Which device type are we targeting?</strong> We want to know if the design will be implemented on mobile, tablet, or desktop (or all 3) because it informs the content length and placement. At Klaviyo, we primarily target desktop users. As we move into future versions of our product, mobile is currently being heavily considered and optimized for.</li><li><strong>What is the user’s current behavior on-site?</strong> Ask this especially if you’re making an iteration (updating an existing design). This may mean tapping the product team to have them pull metrics on user behavior. Use this information to inform how you will use content to direct the user to take a different action. For example, if the user is glossing over a CTA that says “Learn more” (which is vague and has poor information scent), then you may want to try updating the CTA to be more specific and direct by saying “Learn about Campaigns.”</li></ul><h3>Working with sales</h3><p>When working directly with sales, it’s sometimes hard to advocate for the best user experience.</p><p><strong>Questions to strike the balance of being a user <em>and</em> business advocate:</strong></p><ul><li><strong>How should we position our plans and prices? </strong>Be weary of using marketing, salesy language within our product. Our goal is to guide the user through the purchasing flow, not sell them on it. A good product will sell itself.</li><li><strong>What are our top selling plans? </strong>We want to figure out which plan options to display more prominently for specific users.</li><li><strong>How does the customer pay us?</strong> We want to figure out the pain points behind putting in payment, knowing it’s a vulnerable experience. Be sensitive, respectful, and empathetic when talking about money. The way we speak about a user’s money determines how they want to spend it with us.</li><li><strong>Are there plans or features that are worth more to us than others?</strong> At Klaviyo, we have a feature that allows users to turn on automatic upgrades. This feature helps businesses with continuous, upward performance and does not limit users to a smaller plan. Encouraging users to turn on this feature helps Klaviyo, while providing a high-value feature for our customers.</li><li><strong>Are there any plans we can’t sell in certain areas of the app, or to certain customers? </strong>We want to identify alternative flows the design team may need to address.</li></ul><p>Of course there are a million questions you can ask in a kickoff, but these are just our favorite.</p><p>What questions you always ask in a kickoff? We’d love to know!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93a8ee54b039" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/our-content-design-teams-favorite-kickoff-questions-93a8ee54b039">Our Content Design Team’s Favorite Kickoff Questions</a> was originally published in <a href="https://medium.com/klaviyo-design">Klaviyo Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>