<?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 Ally Hangartner on Medium]]></title>
        <description><![CDATA[Stories by Ally Hangartner on Medium]]></description>
        <link>https://medium.com/@allyhangartner?source=rss-5d00b446dec1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gpX-j4ucINFlJVsl78MuBg.jpeg</url>
            <title>Stories by Ally Hangartner on Medium</title>
            <link>https://medium.com/@allyhangartner?source=rss-5d00b446dec1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:43:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@allyhangartner/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[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-b38d2b0e5cf7?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38d2b0e5cf7</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 11:48:19 GMT</pubDate>
            <atom:updated>2023-06-27T11:48:19.466Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Building a New Product Line with Gui Schmitt</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-1Wov_psS5LbQucyw9w0w.jpeg" /></figure><p><strong>AH</strong>: <em>Today I’m talking with one of our longest-tenure designers who’s done quite a few projects in his time here and was actually an early Behind the Pixels guest. Why don’t you start by introducing yourself again? How long have you been in UX? And how long have you been at Klaviyo?</em></p><p><strong>GS</strong>: I am Gui Schmitt. Been a designer here at Klaviyo for almost five years at this point, which is crazy. Throughout my journey here I’ve worked on several projects that include the SMS builder, the email editor redesign project and now more recently I’ve been working on the reviews project which is a major new initiative that is going to be released soon or, maybe by the time you’re reading, this already out, which is exciting. Yay, future me!</p><p><strong>AH</strong>: <em>[Laughs] Yay future Gui! Amazing, and reviews was a different type of team than we previously had at Klaviyo. Can you give us some brief context around the team and how you all work?</em></p><p><strong>GS</strong>: I believe reviews is the first product that we’re releasing that comes out of this initiative called Klaviyo Ventures. In it, teams are free to experiment with new ideas, validate them for product market fit, and then take them to scale and bring it over to our main product or do an independent product. In this case, reviews was released on a limited scale for Shopify last year, similar to a soft launch, where we validated that market fit. This was before I joined the team and once we identified that people were resonating with this idea, we decided “hey, let’s take this and bring it over to the main platform and build all the features in order to enter this new area which has established players”. Obviously for people to switch, they need to have a good set of value unlocks and we want to ensure that we’re meeting their expectations entering this brand-new market.</p><p><strong>AH</strong>: <em>Yes, that’s interesting. You’re definitely hitting a new market and there are some pros and cons there. You know what’s expected, but also you’re trying to make something that’s competitive. Which kind of leads into my next question — you said there was some research early on to validate the opportunity. Did you do more research later? Was there an opportunity to talk to customers about concepts?</em></p><p><strong>GS</strong>: Yeah, this project is fairly different from others in that we already had a product that was very basic. So we did talk a lot with users of that existing product to see what they liked, what they didn’t like, and what they wished to see in a more full solution. And because we were entering this new market, and we had those competitors that were trying to match. We talked to customers of those competitors to see what they like about their current platform, what they don’t like, and what would make them switch. So that gave us an idea of what was the perfect quadrant of things that we should focus our attention on. Ideally, you want the easy-to-build, high-value unlock — not everything is perfect like that, but we were trying to find things in that direction. And I think we’re going to learn a lot as we launch this, and our idea is to have a much quicker cycle of improvement and iteration upon that first release to respond to how people are reacting which is very different and exciting.</p><p><strong>AH</strong>: <em>That’s a really fun way to build and cool that your team was able to pick out what could be a competitive advantage early on. Anything interesting that you did during the creative process to come up with solutions, maybe a particular brainstorm or something?</em></p><p><strong>GS</strong>: Well, I think what was a particular challenge around this project was how it operated within our design system, and the components in it. For those who are not familiar, components are a series of Lego blocks that we can assemble to make any sort of interface that feels, behaves and looks like what people expect from the platform. So I think whenever you’re trying to solve a brand new problem, you are faced with a decision of what can we do with your existing Lego blocks? And should we build any new Lego blocks to better suit this problem space?</p><p>For reviews, there was a lot of back and forth around like, ‘Hey, what should we do here?’ Because you can always do something with the existing Lego blocks, but it’s just a measure of compromise where you have to consider things like — how often are people doing this? Is this a critical path in the overall journey that requires an extra level of investment? I mean, if designers had their way, everything would be custom, right? [Laughs] But obviously, the reality of a business is that you have to make decisions and considerations and choose the best solution for this given moment in time. And a lot of times like you might get a feel of something, but again, going back to that original point, you always want to check and validate that feeling, and putting it out there sometimes is the best way to validate something that you might not be sure about, to see if the investment is worth it. Every project goes through some of that in terms of what is the best solution, but I think when you’re entering a new area like this, it tends to happen a bit more often and so I think that was a considerable, unique characteristic of reviews.</p><p><strong>AH</strong>:<em> Makes sense — it’s all about collaboration and give and take to make the right decision. So, here at Klaviyo one of our design values is trustworthy. I’m curious, how did you all work that into reviews?</em></p><p><strong>GS</strong>: So to me reviews are all about trust. Reviews are taking the customer’s voice and opinion and using that to add trust to your brand and add social proof and validation that this is a product that real people like me and you are using and are saying its great. Throughout my research into this area, I found certain interesting insights about, you know, human psychology when it comes to trust. So, for example, a lot of people might think that having a perfect, 5 stars out of 5 product is the most trustworthy, but research shows that people actually trust products that are around 4.8 or 4.7 because everyone understands that not everything can be perfect. So when something looks too good to be true, people are skeptical, especially when you think about how now with technologies like AI and generative creation of content it’s easy for someone to whip up text. For us, it was key to try to find ways to take the data that we have and that we’re collecting from reviews and make it very clear that this is real and try to use different signifiers to do that, like promoting people to take pictures, so that it’s more realistic. We even consider things like the presentation of a review — if you go to a product’s page, everything is studio-level quality and that’s great, but people also want to see the real lighting, the flashlight on the cell phone look, and things like that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*73EMVGQD7zpwP4vYpFKdHg.png" /></figure><p><strong>AH</strong>:<em> Totally. That’s super interesting, the psychology piece and making it more human, even though it’s technology. We want that to come through in the design. Did you run into any technical limitations as you started to build?</em></p><p><strong>GS</strong>: It’s the piece around the design system, but ultimately, I think we are shipping with the right set of compromises where we feel like we got to do some new stuff as well. It’s not as if we compromise on everything. But in terms of reaching an MVP, you gotta sometimes cut some features — it’s not that we won’t do those but about what do you do first? Not everything is technically feasible for day one.</p><p>On the design side, I had to make several different states of the product — this is the initial release. This is subsequent — slicing the long-term goal into little pieces. I think that helps to drive the conversation because when a stakeholder is seeing a screen that has a lot of stuff in it, depending on the stakeholder, that might be either exciting or anxiety-inducing. [Laughs] Like if you’re talking to an engineer and they see all those features they might start asking ‘Oh, what is this? And this?’ and you’d have to stop and explain ‘No, no, no, don’t worry about that for now.’ So making sure that we’re always focusing on what’s the right thing to show to the right set of stakeholders. That wasn’t quite the question, but that was just something that came to my mind.</p><p><strong>AH</strong>: <em>And incrementality leaves room for more exciting things to come which is always good. All right, what’s the biggest challenge you had to overcome while designing and building reviews?</em></p><p><strong>GS</strong>: So one interesting technical challenge that we had is we looked into how people are using review content in their emails before we released this product and the reality is that people just copy and paste quotes. The thing about that is you can copy and paste anything and it’s also laborious to do that because you have to do all the work by yourself. So we’re trying to find ways to take all the data from things that people have said and use some sort of AI technology to help us parse through all that data and find the strongest sentiment from each review and help bring that over to their emails so that they can easily take the strongest phrases that people are saying and put that into their messages. So we built this AI tech that analyzes each review and finds the short quote or phrase that you can use in your message. That’s an interesting problem because we wanted to do something that was better than the existing copy and paste and we also wanted to do something that would save time. In the future, we want to allow people to also choose other parts that are not just the AI selection because it doesn’t get right every time. But as it gets better, it should become more correct each iteration cycle.</p><p><strong>AH</strong>:<em> That’s really cool. Always fun when we can toss in a little AI magic in there and then connecting back to the Klaviyo app makes the whole thing feel like a really good package. On the flip side, what are you the most proud of thinking back over the process of building reviews?</em></p><p><strong>GS</strong>: I think we’re fairly confident at this time, but again we’ll see [laughs], that what we are putting out there in terms of helping people get the most out of a reviews program meets their needs and can help them save time. The AI quote is an example of a saving time feature, but another thing that we did was with moderation.</p><p>Moderation plays a huge part in the time that you spend with reviews. There’s a bit of setup, but once you’re set up, most of your time with reviews is spent moderating — making sure that the things that you’re putting on your site are okay. And we built reviews so that the task of moderation has a lot of different ways that you can save time. For example, all the things that you have pending are presented on the first page, so you don’t have to go into multiple pages to see any questions or reviews that are pending. And this is something that came directly from feedback that we received from people using the original app.</p><p>So I think I want to be proud, but it’s hard because it’s not out yet. But I think there’s a lot of potential for some of these ideas. We have more features that we want to do in the future that are going to be aligned with that same ethos of saving time — like doing sentiment analysis, for example, or using AI technology to get the sentiment of [reviews] and then also potentially flag ones if someone puts a curse word in your review, for example. People get mad sometimes on the internet, as we know, so having a filter for that could be helpful. We’re building an inbox of tasks that people have to get through, so being able to sift through those tasks pretty quickly and efficiently is our goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPmGmjbXog3bN9NXrLzZ3g.png" /></figure><p><strong>AH</strong>:<em> I like that — something we hear from customers all the time is that they don’t have enough time. So very smart. This next question is kind of similar, but do you have a favorite memory working with a team on reviews?</em></p><p><strong>GS</strong>: We got to meet in person a few times. We’ve got to go to the office, which is great — it’s a different dynamic. I’m glad that we were able to do that early on in the project as we were kicking things off. That’s the moment that you’re trying to get a sense of who you’re working with, how they’re like, and what their way of working is and I think you get a sense of that quickly when you’re in person. And of course, I’m looking forward to the release of it so we can also celebrate. So I guess a favorite future memory!</p><p><strong>AH</strong>: <em>Favorite future memory, lock it in! Cool, and you’ve been alluding to this throughout but what happens next for you and reviews?</em></p><p><strong>GS</strong>: I’m looking forward to continuing working on those features and iterating and learning from the initial release so we can continue to deliver value to this new initiative.</p><p><strong>AH</strong>: <em>So you’re looking forward to getting reviews on your new product, reviews. Sounds good.</em></p><p><strong>GS</strong>: Yeah! [Laughs] We’re always open to feedback!</p><p><strong>AH</strong>: <em>And last question, do you have any general advice for designers who are working on a net new product line like this?</em></p><p><strong>GS</strong>: When you’re entering a new area or vertical, it’s a little overwhelming at times because you’re going against people that have been doing this for years. And I think you just gotta do your best to absorb that and then understand that, ‘All right [our first version] is not going to have all these things that these competitors have’, so how can you find ways to set yourself apart? In our case, a lot of the strength comes from consolidation — being all in one platform and trying to find ways to connect with other areas and unlock value that way. If you’re starting something new at a new company, you might not have that, but it’s finding the little things. Little inefficiencies in these other competitors that you can potentially innovate on and do differently. There might be some gravitation to do things in a certain way, but maybe that’s also an opportunity to do it in a different way and try to stand out through that. I think reviews is an interesting area because there are so many surfaces. For example, you have people filling in the review as a customer that bought something — we didn’t even talk about that on this interview! — but you also have the people they are moderating and using that review to promote their brand. So there are all these different areas where you can find ways to stand out and do things in a different way.</p><p>⭐️✍️— <em>This is the first big release from our ventures team — props to Gui &amp; team on a job well done. Can’t wait to see whats next with reviews and the ventures team as a whole!</em></p><p>Does taking on the big challenges sound up your alley? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38d2b0e5cf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-b38d2b0e5cf7">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-dc222326fcdf?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc222326fcdf</guid>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Thu, 27 Apr 2023 13:22:27 GMT</pubDate>
            <atom:updated>2023-04-27T13:28:39.335Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Renovating Home with Griffin Drigotas</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHieOXmQTyVaxc8wYItzOw.jpeg" /></figure><p><strong>AH:</strong> <em>Let’s start off by having you introduce yourself — how long have you been a product designer and how long have you been at Klaviyo, which is a decently long time at this point!</em></p><p><strong>GD: </strong>It’s crazy. My name is Griffin. I’ve been a product designer for four or five years now. I didn’t study product design at all — totally self taught — I started off doing graphic design, and then joined a startup in Boston where I was their first design hire. There, I did all of the marketing design stuff and all of the product stuff. After about a year, I wanted to stop doing marketing so made the switch fully into product design. So I would say probably a full four years now. I joined Klaviyo April 1, 2020 right when the pandemic was kicking off and have been here ever since doing product design, loving it.</p><p><strong>AH: </strong><em>That was a great day for me since you were coming to help on my team! Okay, you’ve done lots of projects since then, but recently you were on a very tricky, very well known page of the product. Can you give a little introduction into what we’re talking about today?</em></p><p><strong>GD:</strong> Yes, so most recently, and I guess not too recently, it’s been about a year, have been working on Klaviyo’s homepage. This was a page that, as far as I know, hasn’t been touched since Klaviyo was first released back in 2013. So it’s a page that customers are very used to and comfortable with. And we really just wanted to, one, update the UI of it to start matching the rest of our app as we’ve been improving it, and two, present information for our users that’s a little bit more relevant than just listing out all of your flows and all of your campaigns that are happening in a certain time period. A primary goal was to make things a little bit more specific with some more actionable data that allows us to drive users directly into that content to make changes and view results far quicker.</p><p><strong>AH: </strong><em>Connecting it to the rest of the app and also correcting some information too which is good. The team had some changes and switches during the time you worked on it. Maybe a little bit of context around the team?</em></p><p><strong>GD:</strong> Most recently, we’re made up of three engineers, a PM and myself on the design side. We also have a design researcher and a product analyst who’ve both been supporting the team as well. But over the past year, we’ve had a little bit of turnover and some PMs that have been shifting. Four different PMs have come in and out of the project over the last year which has been super interesting, you know, dealing with different processes and mindsets, thoughts, goals, and having to level-set over the year and make sure everyone’s on the same page as it’s changed so much.</p><p><strong>AH: </strong><em>Yeah, of course which answers my question about the difficulties of a shifting team. So then maybe talk to us about the research phase. What were you all researching and what were some of the findings?</em></p><p><strong>GD:</strong> So research… We started off, like I said a year ago, and really our main focus was just on ‘Hey, what’s working on this page, what’s not working for you?’ and how can we be improving that? So that was one of our biggest focuses. I guess it’s kind of weird because we didn’t end up shipping a lot of the stuff that we had originally researched and focused on, and it ended up being a reskin of the old UX, but a lot of [the original research] was focused on how we could be improving. Understanding where people go from home, and how we can make that faster and easier for our users. In the original home, you could click into certain campaigns and flows, but there’s really only revenue data tied to that. On top of that, we learned that people really just jump into reports right away. People want to be able to understand some more data right away. So understanding what level of information people want to see when they first jump into Klaviyo and then where they go after that.</p><p><strong>AH: </strong><em>So you all found that home actually might serve a different purpose than it was originally used for, but then you ended up realizing that your scope couldn’t solve some of the bigger issues. Do you want to talk about how you found other areas needed to be improved in order to eventually get to the place that you wanted to go with home?</em></p><p><strong>GD:</strong> For sure. Flows is a good example of that. Our campaigns list page, for example, has all of your campaigns listed out and you can search, filter, and see all of the data attached to each campaign. But within the last year, you weren’t able to do that on the flows list page. That space was really just a list of all of your flows with some of the logic listed out in the details, but there was no data tied to that. So users were having to rely on the homepage because that was the only place where you could see a list of all your flows that were live during a certain time period with the revenue tied to it. We heard from users that it didn’t really make sense for you to be relying on the homepage to be looking at all of that data. So we thought, let’s also take a step back, use some of our engineering resources, design resources, product resources, and look at a flows list page, revamp that as well so then we can use home in a more effective way. We don’t need to overload home with data. We can use the flows list page, give people information that they want to be seeing there and then utilize the homepage as more of an entry point that’s giving you that high level information without having to overload you with all that other data.</p><p><strong>AH: </strong><em>Yes, you all may not have been able to do it all in the first pass, but I like that we’re starting to unload a few things and make home not take on so much of the burden of reporting. Feels like a good long term goal.</em></p><p><em>So then thinking about the creative process and some of the tools that we use, was there a particular brainstorm or activity that you did while coming up with concepts that was particularly helpful?</em></p><p><strong>GD:</strong> So less about specific tools or activities, I’ve found that oftentimes it’s designers who are popping into brainstorms and thinking through stuff. However, I’ve been super fortunate to work with engineers who are very good product-thinkers as well. I make an effort to bring my team members who are engineers or PMs, product analysts, researchers all into that room so everyone can have a say. I personally like to give everyone that voice because I don’t particularly like a relationship with engineers where I make choices and then just pass things over to engineers, saying, ‘Here, do this, do that’ — I want them to feel empowered. So it’s definitely a learning curve, because engineers aren’t <em>always</em> product-focused. But over the last year, I’ve seen tremendous growth from them being able to think through things and then it helps down the line when you’re a QA-ing, trying to release things, or make some decisions where your engineers end up providing that [product] feedback. It’s just getting more people to have that keen eye when it comes to making product decisions. It’s been really cool and fun to see the growth across our entire team and having people have that confidence to make decisions and raise questions when things might not look right. I can only do so much and catch so much stuff. I tried to catch everything, but even just in the last couple of days of QA-ing home both of our engineers have brought things to my attention that I hadn’t noticed before, which is pretty cool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*bxqGBZ0AAlVDT2G_Z0T7Sg.gif" /></figure><p><strong>AH: </strong><em>I can attest, they’re great. And just the idea of co-creation with the team is a pretty cool way to work. Then on the engineering side, did you all run into any technical limitations? And how did you adjust?</em></p><p><strong>GD:</strong> Yes, for sure. During all of this, we’ve been revamping our design system. So that definitely has played a role because we have been using a lot of new components that were just being built. We were the guinea pigs there and, happy to do it — happy to use some of our new cards, use some of our new tables, some of our new drop downs. But there’s also some things that might have been overlooked when those new components were originally being built. So we had the opportunity to basically do an extended deep-dive QA on those components, to make sure that they were actually fitting the needs for everything like in-app that’s going to be using it. Home was one of the first teams to use quite a few components.</p><p>Load times are another technical limitation we dealt with. We’ve had a huge request since we released the product to add more timeframes and custom timeframes. So it’s this really interesting balance between how much we can give to our users because we know that they want these certain things versus giving them an optimal experience. Like technically we can give users the ability to go back in time as far as possible, but we run into some loading issues there. Pages may timeout or pages may take a very long time to load and that’s really not a good user experience for our users. So we’ve decided to cap it at 180 days in the past, which should give users ample timeframes to do the reporting comparisons that they want to be doing, especially on home, and then they can then dive deeper into say the Overview dashboard or different reporting surfaces and do more in depth reporting there, where there’s not as much data that might need to be loaded or those might just be built in a different way that they are able to load all that information quicker.</p><p><strong>AH: </strong><em>It goes back to what you said, if the true purpose of home is not to be a deep dive reporting area. Do you need to have deep-dive analytic features on there? But then we need to have those available somewhere else.</em></p><p><strong>GD:</strong> For sure. It’s been a reporting surface historically, and I almost don’t view it as a reporting surface. Home is a surface where you get a gauge of what’s happening in the now and then you can dive in deeper and look at specific flows or campaigns, individual ones or marketing initiatives in those product areas as a whole and go to those areas to look at the overall performance. You probably don’t need to do that on home.</p><p><strong>AH: </strong><em>This is a really good segue into my next question about change aversion. So you’re saying home has historically been used as a reporting space where people relied on it for certain analytics they couldn’t find elsewhere and it’s also the most trafficked page in Klaviyo. How did you all balance knowing that there would definitely be change aversion versus making changes for the eventual good in the long term, even if we’re not there quite yet?</em></p><p><strong>GD:</strong> Absolutely. So I think overall at Klaviyo and especially with this project, we’re really focused on looking at the data and trying to understand what success means for our users. So I mean, one of the things we look at internally is like an “FII score”, which stands for fast, intuitive, and inspirational. It’s these three pillars of our design team that we try to focus on when we ship features and make product decisions. So yes, change happens. Change might not be loved by everyone initially, but we know, based off of looking at that data, that these changes that we’ve implemented are actually helping users immediately. We’re increasing the speed in which users can do things. The FII score increased by over 14 percent, with an average 35% increase in a task success rate, and a 15% increase in speed compared to the old home. So it’s those kinds of things that we’re more focused and putting more emphasis on than we are on changing things and having users be frustrated by those changes that we’re making. We know that things might have moved or look different, but they’re completing their tasks faster and more effectively in Klaviyo which really is our main goal.</p><p><strong>AH: </strong><em>Totally. What was the biggest challenge to overcome in the process of building home?</em></p><p><strong>GD: </strong>I think the personnel changes were definitely difficult, and with that there were some changing and competing priorities during the process which made it difficult to navigate. But I think that the biggest thing is that home captures so many different product areas, and there’s so many different opinions and people who care deeply about their individual product areas. It’s kind of a unique place to be working on a feature that touches literally everything. In a lot of the work I’ve done so far, I was really focused on just flows, just campaigns or just a certain report, but this was a feature that we needed to go out and get buy-in from stakeholders across the entire company (plus our customers, plus CSMs, plus leaders). It was an all hands on deck effort across Klaviyo and that was a little bit challenging to navigate at times because there are so many differing opinions and priorities when it comes to these different product areas and finding that balance between them all.</p><p><strong>AH: </strong><em>100% — on the flip side, what are you most proud of thinking back across the process?</em></p><p><strong>GD:</strong> That we shipped it [Laughs]. But no, I go back to that data and I’ve been very happy to see we’re hitting the numbers that we want to be hitting and, at the end of the day, we know that we are providing more value to our users than they were getting before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KP1-wO5b9qT6sShobiUT-w.jpeg" /></figure><p><strong>AH: </strong><em>And it’s not the end, which leads to my next question — like you said, it ended up being more of a reskin with some quality of life improvements, but sounds like there’s more coming. Can you tease any of the things that you’re thinking about as we go forward?</em></p><p><strong>GD:</strong> Yeah, it’s gonna get faster, it’s gonna get more accessible. But there’s also a lot of work that’s happening that’s going to make the entire reporting journey a lot better. From the homepage all the way through to individual objects. This is just the beginning of a much larger reporting initiative that we are undertaking on the design and product side at Klaviyo.</p><p><strong>AH: </strong><em>Very exciting. Okay, final question, any advice for other designers who might be working on a very visible piece of their product, like home?</em></p><p><strong>GD:</strong> Talk to as many people as you possibly can! Make sure everyone is aware early and often about ideas, thoughts, concepts that you have. Don’t be afraid to take and make bold decisions, because that’s really the only way to spark change and make progress. When you have ideas, speak up and challenge other people’s opinions as well. People aren’t always gonna love what you’re doing, but at the end of the day, you have the most knowledge around that particular product area. I’ve been working on it for a year, there’s been a lot of people who came in and out of it — have the confidence to speak up and make firm decisions, but also be able to back them up data at the same time.</p><p>🏡 🚧 — <em>Redoing the most visited page in a product is no small feat. My compliments to Griffin &amp; team. Excited for the future of home and the overall Klaviyo analytics experience!</em></p><p>Does taking on the big challenges sound up your alley? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc222326fcdf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-dc222326fcdf">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-f49b9630d0cf?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f49b9630d0cf</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Wed, 08 Mar 2023 14:51:47 GMT</pubDate>
            <atom:updated>2023-03-08T14:51:47.242Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Content Design with Erin Kelly</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BuIm0mEMEwMi4MaOEmmjg.jpeg" /></figure><p><strong>AH:</strong> <em>So it’s our first Behind the Pixels of the new year and we’ve got an awesome person on today. Can you introduce yourself and then tell us how long you’ve been a Content Designer and how long you’ve been at Klaviyo?</em></p><p><strong>EK:</strong> Hello, Ally! I feel like I’m on a talk show. [Laughs] I’m Erin Kelly and I’ve been a Content Designer for almost 3 years now. I started at Klaviyo in December of 2021 which is so crazy. Jack, a Senior Content Designer here, and I started on the same day and it’s been a party ever since. I remember our first few weeks, everyone was coming to us with so much energy and so many challenges.</p><p><strong>AH: </strong><em>It’s true — all of us were very excited for you to join. But if I’m being honest looking back, I don’t think we quite understood exactly what content design would encompass. So can you give us the lowdown on what is content design at a high level?</em></p><p><strong>EK:</strong> At a high level, it’s guiding users through Klaviyo in the way that makes sense to them. Content design starts at the very beginning of a project. We have to be on the same exact page as our designers– finding out the words that our users use, the way they think about things, understanding their mental model– and using that to inform the entire experience. There’s the concept of full stack content design — which is the idea that content designers can successfully contribute to a project at every stage, start to finish. Beth Dunn describes it in her book <a href="https://www.goodreads.com/en/book/show/57529253"><em>Cultivating Content Design</em></a> as “research and brainstorming, determining strategy and scope, sketching out flows, testing for usability and accessibility, proofreading and polishing the final result, measuring success and iterating based on the results.” While that doesn’t encompass it all, I think it does a good job at illustrating it’s more than just the words– a common misconception.</p><p><strong>AH: </strong><em>Totally, so it’s more than just the copy. It’s definitely an interesting way to think about the problems. I’m curious, what drew you to a career in content design?</em></p><p><strong>EK: </strong>There’s an opportunity to be creative, but there’s also an opportunity to use psychology and guide people through these experiences. I’m very, very collaborative. I need to be working with other people to solve a problem. Also, I always need to understand the ‘why’ behind anything I do. I can’t just do something without understanding why we’re doing it, because there’s no desire for me to get it done. Not only my role, but also Klaviyo uses the ‘why’ to drive our decisions, so I’m really grateful to have something that keeps me motivated every day.</p><p><strong>AH: </strong><em>Cool, and I know you’ve worked with a bunch of different people in your year and change here. Can you go through an example or maybe a particular project that is a good example for people to understand content design in action?</em></p><p><strong>EK: </strong>Yes! Last year, we didn’t have a clear workflow or experience for users who want to set up SMS. We had previously called it “Get your phone number.” And while that’s true, it’s more than that. Users are setting up SMS as a marketing strategy for their business. And we [Klaviyo] needed to design an experience that made users feel ready, and successfully set up with their new channel. I worked with Sara Reich, Senior Product Designer, and we successfully created a workflow for users to get started using SMS if they were brand new.</p><p><strong>AH: </strong><em>So I’m curious because ‘Get a phone number’ seems like pretty simple content. [Laughs] But obviously, there was more to it. How did you kick off that project or begin to understand what the problem was and how you wanted to solve it together?</em></p><p><strong>EK: </strong>When we started, we looked at what was working, what wasn’t working, and what was going to be the most scalable solution. We had to take those 3 things and make them work together. We looked at the current flow and worked with our design research partner to understand issues through user research and then took it from there.</p><p>What we found was that we weren’t using content that works for user needs and they didn’t know what was going on. I don’t know if you remember, but it was just a modal and a ton of legal language. Users would click a button and would get this ginormous modal of things you can’t send, then click OK. All we did was say, “You’re set up now!” but content wasn’t clear. We didn’t ask what countries they wanted to send to, or describe new terms to them. Users would just show up to their settings and they’d have SMS working but [we] weren’t guiding them how they should.</p><p><strong>AH: </strong><em>So the brevity was there, but the logic and the idea of the problem we were trying to solve was totally missing. So moving on to the creative process, obviously on the design side we have all these different brainstorms and activities we do to come up with ideas &amp; designs, so I’m curious is there a particular brainstorm activity that is your go-to for content design?</em></p><p><strong>EK:</strong> There’s an activity I’ll do with designers and I’ll copy it below. Truly, I love the Zoom calls where we’re just going through competitors and inspiration sites together. It might be for 30 minutes or maybe for an hour where we’re just getting in the creative mindset and our brains go into ideation mode thinking: “We could do this. Or we could do this. OR! We could do this…” The creative solutioning together really sparks the excitement for the problem that we’re going to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*2y4QJeVlU8vPRp6x8ALv8A.png" /></figure><p><strong>AH: </strong><em>That’s cool. And you talked about collaboration being one of your favorite parts of the process. Product teams have all these people in different roles and it seems like you work with a bunch of them. What does that collaboration look like for you?</em></p><p><strong>EK: </strong>When I start a project with a designer, first I have a meeting with them to discuss working styles. As a content designer, it’s important to know that every designer works differently. Luckily, I can mold to different working styles pretty well. I don’t know if that’s a personality thing or what, but I’ll ask questions like– “Would you rather use Slack to talk about these things? Would you rather use Figma comments?” Whatever it is, I just need to know what the best communication methods are throughout our project so we can work effectively and efficiently.</p><p>We also have our product partners. I’m always pretty close to the product manager because they have the technical knowledge that I need to write clear content. They have that back-end and front-end mindset that is really great for a partner to have. Right now, Stephen, a Product Designer, and I work together on the developer experience team and we both ask a million questions. Our product manager, Scott, slays. He taught Stephen and I how to make API calls using Klaviyo’s API and that was such a great experience.</p><p><strong>AH: </strong><em>That’s awesome. And now thinking over the last year and all the different projects you’ve been on, is there a favorite memory of working here so far?</em></p><p><strong>EK: </strong>Last May I met my coworkers in person and saw the office for the first time! Flavia introduced me to my new favorite pastry from Tatte and I beat Ke in Mario Kart. So the trip was a huge win. But then we had the Chicago meet up and that was a blast too! Basically any time I can see my coworkers in person, I have the time of my life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6iViwLZiJiFvuk9Aq6q8OA.png" /></figure><p><strong>AH: </strong><em>Getting to know the people you’re working with — it’s part of what makes the work even more fun. I think that’s awesome. Okay, thinking about the future. You’ve completed your first year, but the content team is relatively in its infancy here. What are the biggest opportunities we have for your team in the next couple years at Klaviyo?</em></p><p><strong>EK: </strong>I think making our content design system public is going to be the biggest, most exciting thing not just for our team, but for the content design industry. We want to be a company that has a content design system that works not just for Klaviyo’s product today, but for the future of Klaviyo and for other companies that are looking to build out content design or need guidance. But this month specifically, I’m working with Lauren on our inclusive language guidelines. We’re <em>so</em> excited to make Klaviyo more inclusive and more accessible.</p><p><strong>AH: </strong><em>It’s going to level up Klaviyo and then you all can create the gold standard for others! That’s actually a really good segway into my final question, do you have any advice for smaller teams or people just starting out who are not lucky enough to have an Erin Kelly and her team at their company. Where should they start?</em></p><p><strong>EK: </strong>You don’t need to read all of the books, or the blog posts, or watch the conference talks. You just need to take a couple minutes and read design system guidance. How you frame and structure content within your components shapes the whole experience. When we have a consistent way for users to digest and consume information that they’ve already seen before, they can move through Klaviyo faster and start seeing value faster.</p><p>Those guidelines have been curated for so many use cases that work and they’ve been looked at by so many people. Doing it right is important and doing it consistently is also important. I think reading industry best practices for content, and reading content design system guidance is going to help anyone a ton.</p><p><strong>AH: </strong><em>I like it — you don’t have to be afraid that you’re copying what other people have. Instead incorporate those best practices into what you’re starting with and then you have a good foundation to build on.</em></p><p><strong>EK: </strong>Yep, that’s it!</p><p>🗒👩‍🎨 — <em>It’s been an absolute delight working with Erin &amp; the content team. Can’t wait to continue to watch content level-up our work here at Klaviyo!</em></p><p>Does partnering with a group of talented content designers sound like fun? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f49b9630d0cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-f49b9630d0cf">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-b68591be9a81?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b68591be9a81</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 14:18:05 GMT</pubDate>
            <atom:updated>2022-11-17T14:23:12.006Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Always be Learning with Yujing, Flavia, Mike, Mahima &amp; Vera</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*noIVRhV1GjiRGjhTI7pNlg.jpeg" /></figure><p>In this post we explore how 5 designers utilized their ‘learning stipend’ — an amazing Klaviyo benefit were every year employees have $3k to spend on courses and further education if they choose to.</p><h4><a href="https://www.learnui.design/">Learn UI</a> with Yujing Su</h4><p><strong>AH: </strong><em>Let’s do this. So to start off, can you introduce yourself? Tell us how long you’ve been at Klaviyo and what team you’re on here?</em></p><p><strong>YS:</strong> Yeah, so actually three days ago was my one year anniversary, so here for a little over a year. Time flew — really fast. And currently I’m on the infrastructure team specifically collaborating with the product merchandising and C3 teams.</p><p><strong>AH: </strong><em>Staying very busy rumor has it… so you took the Learn UI course this year with the learning stipend. Tell us a little bit about that course. How long was it? What was the structure?</em></p><p><strong>YS:</strong> It’s a self paced course mostly focusing on improving visual skills and it was virtual of course. To be honest, I haven’t finished it yet. But, it basically covers different topics to improve your visual skills such as alignment, spacing, visual consistency, color choices, typography and creating UI components. Then the last part is about creating your own design portfolio.</p><p><strong>AH: </strong><em>Not bad, pretty extensive it sounds like!</em></p><p><strong>YS:</strong> Yeah. I heard about Eric, the author of this course, from a blog post where he shares free visual design tips. And that’s very helpful itself and it’s free, so that’s why I signed up for this course. And [the course] is mostly focusing on very practical UI tips, so it’s not just color theory you find in textbooks and in college courses. His course is very much structured so that you can use the tips and implement them in your day to day work. There’s seven chapters and I’m only halfway through, but so far it’s really helpful.</p><p><strong>AH: </strong><em>You kind of answered my second question, talking about how you knew his blog, but why did you choose the course? Were you trying to improve a skill?</em></p><p><strong>YS:</strong> Mostly to improve my visual design skills. And I feel I’m pretty comfortable working with a design system — my past experience was always working in an established UX team or product design work. But I feel my growth area is to create visual screens from scratch. Especially while I was interviewing for this job, it took me a while to create a visually appealing portfolio without much guidance from a design system.</p><p><strong>AH: </strong><em>Totally makes sense. And then what have you learned from this course so far? Has it changed any of the ways that you approach your day to day at Klaviyo?</em></p><p><strong>YS:</strong> I think what I learned is being able to create my own visual design or doing a final pixel perfect screen from scratch. Like I said, I’m still working through this course, so I don’t think I’ve used it in my day to day,, but I think definitely it’s going to happen after I finish it. I just have to find the time to do that!</p><p><strong>AH: </strong><em>In all the free time that you don’t have, yep, got it! [laughs] So then, so far, what’s the one line takeaway or review you’d give to someone who hasn’t taken the course?</em></p><p><strong>YS:</strong> I think this is a great resource for anyone who wants to grow their visual design skills. Because I know many of us are focused on the UX part of product design. So I recommend this course for those who are looking to improve on visual design or if they want to become a visual designer, or join the design systems team. This will be the course for those purposes.</p><p><strong>AH: </strong><em>Final question, if you had to give the course a rating, 1–5 stars, what would you give it?</em></p><p><strong>YS:</strong> I think it’s like a 4.5. I took a half point off because it is hard to comment without having finished it. But yeah, this course is structured in a way that you listen to the tutorial and then jump into Figma to do your homework exercises. It’s definitely a more hands on course, I just have to do more of the hands on parts. That’s the best way to take full advantage of this course and learn the most from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*usRMEo6lfK5Ins_dcK-HYQ.png" /></figure><h4><a href="https://www.reforge.com/experimentation-testing">Reforge: Experimentation + Testing</a> with Flavia D’Urso</h4><p><strong>AH:</strong> <em>In Behind the Pixels fashion, why don’t you introduce yourself? What do you do at Klaviyo and what team are you on?</em></p><p><strong>FD:</strong> I’m Flavia and I’m on the strategies team. I’m a senior product designer and have been at Klaviyo for a year.</p><p><strong>AH:</strong> <em>Happy anniversary! Okay, so you took the Reforge Experimentation course with your learning stipend. Tell us a little bit about the course. How long is it? In-person or virtual? How does it work?</em></p><p><strong>FD: </strong>The Reforge course is a hybrid between self paced modules completed individually and virtual discussions with the group based on those modules. You are going to get much more out of those conversations and lectures if you have done the modules in advance. Each virtual session had a guest speaker that could speak to real life examples of the material from their own career.</p><p>For context,I had just joined Klaviyo — I was originally on the experiments team and I wanted to learn more. The course looked really interesting and came highly recommended. It was more about product experimentation — so how we, internally, might experiment with a feature. Just like the experiments being run on the strategies team currently. It strangely overlapped with customer empathy for me, to think about how our customers might think through the process of experimentation, especially upmarket customers. So while it wasn’t exactly what I expected, it was cool.</p><p><strong>AH: </strong><em>Very interesting. You started to answer this one, but why did you choose to take it? Was it a new skill? Sounds like maybe it was influenced by your team?</em></p><p><strong>FD: </strong>Yes, definitely. I felt like I had not been on a team that dealt with experimentation explicitly. The team includes very data science-focused work and folks who are steeped in that language and I just wanted to update my understanding of the problem space. That was the main motivation for picking that course.</p><p><strong>AH:</strong> <em>Cool. And you started to speak to this too, but tell us a little bit more about what you learned and then how it changed or didn’t change your approach to your day to day work at Klaviyo?</em></p><p><strong>FD: </strong>It was definitely interesting, because I think there were a couple moments that, again, provided unexpected crossover. The takeaway for me was also a lot of ‘understanding the problem’ — how would you, mainly product folks, set up an experiment and understand the need for experimentation. A lot of that included questioning around ‘what’s going on?’ And <em>I was</em> in that headspace of like, ‘what’s going on? I’m new to Klaviyo’. So it helped me, coming in cold, to frame my questions around auditing a new product and joining a particular team. I was asking myself throughout — What are my questions? What are my assumptions? How do I want to answer those questions? This experimentation setup was actually a helpful mental framework for joining a new team which is great. While I haven’t run a direct experiment since taking the course I have all my notes for when I do!</p><p><strong>AH:</strong> <em>Awesome. Then for someone who hasn’t taken this course, what’s the one-line takeaway or your quick review on it?</em></p><p><strong>FD:</strong> Put your product and strategy hat on and think about how to iterate quickly and experiment. But as a designer, I think it’d be cool.</p><p><strong>AH:</strong> <em>And then the final question, if you had to give the course a rating, 1–5 stars, what would you give it?</em></p><p><strong>FD: </strong>I want to be truthful… I’d give it a three and a half. While that may sound low, I think it is mainly due to the emphasis on the community aspect between sessions and the energy and engagement wasn’t quite there compared to other cohorts and programs I have been a part of. So I think that this course was interesting in terms of its subject matter, but I think its broader goals of having a strong community feel, where everyone’s asking each other questions, isn’t quite there yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PV6L-fLGNGXL0DXE8l3XzA.png" /></figure><h4><a href="https://online.em.jbs.cam.ac.uk/strategic-thinking">Strategic Thinking for the CXO</a> with Mike Oren</h4><p><strong>AH:</strong> <em>You’ve actually already been on Behind the Pixels, so our readership might know about your background but for someone new to the blog, do you want to give a quick intro into who you are and what you do at Klaviyo?</em></p><p><strong>MO:</strong> I’m Mike Oren and I’m Head of Design Research at Klaviyo.</p><p><strong>AH:</strong> <em>And you took a super interesting sounding course called Strategic Thinking for the CXO. Tell us a little bit about that course. How long was it? What was the structure?</em></p><p><strong>MO:</strong> So I originally thought it was six weeks but it’s apparently eight weeks. [laughs] But that included an introduction and some fluffy content — pretty typical for normal college courses as well, so it’s not a big deal. What was cool about it versus other online courses I’ve taken is that it did mix self guided learning with a couple of optional live courses where the professor would come in and go a little bit deeper on some of the topics.</p><p>The other thing I’ll point out is that despite it having the acronym of CXO, and a lot of people in design thinking that the X stands for experience, it’s actually more of a generic placeholder ‘x’ for any type of C-suite executive. So it’s not specific to design, it’s more of a business strategies course.</p><p><strong>AH:</strong> <em>Ah, the trick ‘x’, not actually representing ‘experience’. All right. So then why did you choose this course? Was this a new skill you’re trying to build or new way of thinking? What was the thought process?</em></p><p><strong>MO:</strong> I’ve taken a couple of different strategy courses that were usually more specialized. I really like the one that HBS online has with <a href="https://online.hbs.edu/courses/disruptive-strategy/">Clayton Christensen’s Disruptive Strategies</a>. [Strategic Thinking for the CXO] was more of an overview of different strategic frameworks. And as someone who’s led design-strategy practices at past companies, in general, good research is strategic and good strategy leverages research. So being able to understand some frameworks that are being used by some of my partners is key. Maybe less so here than at some bigger corporations, but just generally speaking the language of partners is always important to me. So that’s one of the reasons why I’ve been taking lots of different business-related classes.</p><p><strong>AH:</strong> <em>Maybe I should start taking courses like this giving all the communication we’re doing with our partners these days.</em></p><p><strong>MO:</strong> One of my favorites I took was actually this Innovating with Finance course out of Stanford, but they don’t tend to teach it anymore. That was cool too, because it also talked about how startup financing works and helps explain why right now capital is very hard to get — basically how investors decide whether or not to put their money into the market versus a startup versus just putting it in something very safe, like treasury bonds.</p><p><strong>AH:</strong> <em>So interesting. I might look that up myself. Going back to the Strategic Thinking course, what did you learn from taking it? And then has it changed the way you approach your day to day at Klaviyo?</em></p><p><strong>MO:</strong> I’d say the number one thing I learned was about some different frameworks for thinking about strategy. And it did cover a range of different types of strategy, whether it was strategy to continue business as usual or enter a new market or figure out how to balance a portfolio of products or services within an organization. It hasn’t changed much of my day to day yet at Klaviyo and I don’t know if it’ll change my day to day in the near future either, but as the organization matures, there is going to be more of a need for it. Because at some point, everything becomes too large to be driven by one or two people.</p><p><strong>AH:</strong> <em>For sure. Prepping for the future, look at you so prepared! All right, what is the one line takeaway or review that you’d give to someone who hasn’t taken the course?</em></p><p><strong>MO:</strong> So before the course, most of what I knew about Michael Porter, while I did know five forces existed, I didn’t know what the five forces were exactly and how they interacted. But the biggest one was a quote that I love to quote, which is:</p><p>“Strategy is deciding what not to do.”</p><p>And all of the frameworks in some way, shape or form really came down to that. They weren’t about identifying what the organization isn’t doing that it should be doing, it’s about how every organization only has so many people and so much money to go around — how can it make sure that it’s doing the things that are going to move the needle the most, and help them with their end goals?</p><p><strong>AH:</strong> <em>That’s a cool way to think about it. Awesome. And then finally,</em> <em>if you had to give the course a rating, 1–5 stars, what would you give it?</em></p><p><strong>MO:</strong> I’d probably give this one a 5 and again, mostly because you do actually get some live interaction with faculty. Like HBS (Harvard Business School) online does have a couple like that, but honestly the ones that are live tend to have about 60 to 100 students. So you don’t really get your questions answered half the time. This one was like 30 or 40 students or something a little bit more reasonable. So if I had a question, and it was in a live session, it got answered and I appreciate that. It also had a live TA which is also kind of an exception for a lot of these online classes. So that was cool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JCqrVnKnqAM9V_Nt-xJdYQ.png" /></figure><h4><a href="https://www.memorisely.com/live-bootcamp/design-system-bootcamp">Memorizely Design Systems</a> with Mahima Rao</h4><p><strong>AH: </strong><em>Why don’t you go ahead and introduce yourself. What team are you on and what do you do at Klaviyo?</em></p><p><strong>MR:</strong> I’m Mahima and I’m a product designer on the data science team. We are currently working on analytical insights experiments that will lay the foundation for some super exciting things to come next year!</p><p><strong>AH:</strong> <em>Cool and you are taking the Memorizely Design Systems course. Tell us a little bit about it. How long is it? In-person or virtual? How does it work?</em></p><p><strong>MR:</strong> So I’m currently taking a five week course with Memorizely. It is virtual, and we have two classes a week. The first is a two hour long session where we actually learn things about topics for that week. And then an hour-long co-working session, which is super helpful. It is structured in a way where we meet on Zoom and I think the good thing is everyone keeps their camera on. It’s super discussion-oriented and everyone asks questions. I think over the five weeks we will build our own design system and learn as we go through that. I’ve finished two weeks and I’ve already started learning so many things.</p><p>I think what’s really amazing is I can always come back to our design system and see what we’re doing and compare what I’m learning to the actual design system that we have now. Which is really nice and a lot of fun!</p><p><strong>AH:</strong> <em>The design system team is going to want to adopt you here. Okay, so why did you choose to take this course? Were you trying to build a new skill? Did you already have an interest in this?</em></p><p><strong>MR:</strong> For sure, I definitely have an interest in the design systems team. I’m super into developing patterns and understanding how you build scalable and dynamic products. So I wanted to improve on this and also expand my knowledge within the UX space. In addition, as I design things on a day to day basis, understanding and knowing the design system is super important and also helps contribute towards and collaborate with the team.</p><p><strong>AH:</strong> <em>Totally. You kind of started talking about this a little bit, but what have you learned from this course and has it affected or changed any of your day to day work at Klaviyo?</em></p><p><strong>MR:</strong> Let me see. What have I learned? I think what we’re doing right now is like the foundations and the styles, and especially with the colors I’ve never worked through to see how accessible it is, what colors to use. And I think at the foundational level, understanding that and applying that even to the designs and experiments that I do has been super interesting. I’ve also been working on and looking into illustrations for the team. I think illustrations go into the foundations of a design system and as I’m working through that, it’s been super helpful understanding what role illustrations play, how the colors/styles play into it. And yeah, I think it’s been super helpful looking at examples — looking at all the public design systems websites to understand how certain things are organized and thought through. I think I’m just being more intentional when I’m choosing styles, choosing spacing, choosing grids. It’s been really nice.</p><p><strong>AH:</strong> <em>You now have a system to place things in your head. That’s awesome. All right, so what is your review so far for someone who hasn’t taken this course.</em></p><p><strong>MR:</strong> I think as a designer, you are working with so many different experts — with a content strategist or researcher, motion designer, behavioral designer — and I think all of that plays into the system. And I think as a whole, the design system is not really about restricting creativity but empowering creativity and the experience. So taking this course would help you collaborate better with the whole team as well as contribute towards this experience design. And so I think you should take the course! [Laughs]</p><p><strong>AH: </strong><em>Finally, if you had to give the course a rating, 1–5 stars, what would you give it?</em></p><p><strong>MR:</strong> I would definitely give it a 5 because of how comfortable I feel in the class, even in the two weeks. It has been really nice. I think it’s a fun bunch and I’m learning a lot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xv23jLRpHHcRyzIj_PIPCw.png" /></figure><h4><a href="https://www.media.mit.edu/posts/course-ai-generated-media/">AI Generated Media</a> with Vera Guttenberger</h4><p><strong>AH:</strong> <em>So to start off in classic style, let’s have you introduce yourself and what you do at Klaviyo?</em></p><p><strong>VG:</strong> I’m Vera. I’m a product designer here and I work on the SMS conversations product.</p><p><strong>AH: </strong><em>And you used our learning stipend this year. So why don’t you tell us a little bit about the course you took — how long was it? Was it virtual or in-person? Self-paced?</em></p><p><strong>VG:</strong> It was called AI Generated Media (Deepfakes for Good) offered by the MIT Media Lab, and it was pretty short, but I learned a lot! It was a five week seminar and all virtual — so there were five live sessions, once a week, and office hours with researchers were offered throughout as well.</p><p>Every week there was a theme of the lecture and then there was a hands-on assignment based on the theme. You would do it on your own, but you could go to office hours and we did also have small groups we could work with and present artwork to as well.</p><p><strong>AH: </strong><em>Even the course name is super buzz-wordy. I’m curious what made you choose the course — were you trying to improve an existing skill? Learn something new? Was it for the team you’re working on?</em></p><p><strong>VG:</strong> I wasn’t necessarily trying to learn a particular skill, but the course sounded cool and was about a topic I didn’t know a ton about. And honestly, anything offered by the Media Lab I knew would be interesting so I wanted to look into it. The course was really flexible and was a nice intersection of skills, and you could choose what you wanted to lean into. They had you learn about the technology and do hands-on coding projects, but some of the classes were also more focused on the ethical and political implications of AI media, so that was a cool mix.</p><p><strong>AH: </strong><em>Very interesting and what else did you learn from taking this course? And did it change how you approach any of your design work at Klaviyo?</em></p><p><strong>VG</strong>: I learned about how synthetic media technology can be applied in a variety of industries, both for positive and negative impact. And to be totally honest, it made me want to stay very far away from AI generated media. [Laughs] It really freaks me out, especially after this course. It was interesting to be exposed to the behind the scenes of how it works — the coding we did was pretty basic, but we did learn to make AI generated video and audio and it’s almost scary how easy it is. [That] was my biggest takeaway. So while I think the technology is incredible, I didn’t continue to play around with it much after the fact. The more interesting part for me was the ethical implications and governance of it and what it’s used for. They [talked about] how to use it for good. A lot of the positive use cases are in entertainment, like using it for art and music, as well as in education. They even talked about how it can be used in the medical field — having virtual therapists or doctors, which was framed in a positive light, but it is all a bit weird to me as well. But then there are, of course, all of the negative applications of it, particularly the spread of fake news and misinformation, causing a lot of distrust, and new ways of taking advantage of people.</p><p><strong>AH: </strong><em>You can probably recognize it even more now.</em></p><p><strong>VG:</strong> Yeah, that’s a good thing. I’ve had my Grandma send me something and I’m like, ‘This is fake…’ [Laughs] It was interesting to learn how the technology works, at least on a basic level, but also interesting to know more about how to be careful around it.</p><p><strong>AH:</strong> <em>For sure. Which is a good lead into my next question, which is what’s the one takeaway or learning for someone who hasn’t taken the course?</em></p><p><strong>VG:</strong> I mean, this particular one, I feel like anybody could take it. It was nice because each of the assignments, especially the coding assignments, you could do the minimum, which gets you the basics. But then there are bonus things you could do if you were really interested in that particular assignment. For example, if one week you were like, I don’t get this or I don’t care about this, you could just do the basic stuff and not do the bonus coding, but if a particular week you were really interested and wanted to learn more there was lots of additional opportunity to explore. So it was cool because it allowed people to get into it however much they wanted. And some people did, like really extravagantly, and produced some very impressive work! It was very self paced and the office hours are super — you can go talk to the researchers to get help if you want or just discuss what interests you.</p><p><strong>AH: </strong><em>Cool! And final question, if you had to rank the AI-Generated Media course 1–5 stars, how many stars would it get?</em></p><p><strong>VG:</strong> Probably a 4 — I thought it was really good. I liked the way it was structured and how they balance the technical component with the interest in psychology. It didn’t help me necessarily improve a particular work-related skill, but was something that I found interesting and cool to learn about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_7kF5bYERKK6joNYbsKMqg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b68591be9a81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-b68591be9a81">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-6e511589ec16?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e511589ec16</guid>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Thu, 15 Sep 2022 11:00:33 GMT</pubDate>
            <atom:updated>2022-09-15T11:00:33.901Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Journey into Research with Valerie Mensah-King &amp; Katie Barkley</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WcDJ0VqIoZB31UdCR7SD0Q.jpeg" /></figure><p><strong>AH:</strong> <em>Starting off in classic behind the pixels fashion, can you both introduce yourselves, how long you’ve been a UX researcher and then how long you’ve been at Klaviyo?</em></p><p><strong>KB:</strong> I can start! I am a researcher on the App-Intelligence side — joined the team just a couple weeks after Valerie on a new research team that was forming. Currently, I’m conducting research for segmentation, profile properties, lists, and product merchandising teams. In these pods we’re concerned with innovative and easy ways for our customers to access data about their customers in an actionable way. And how long have I been here? It will be a year by the end of September.</p><p><strong>AH: </strong><em>And how long have you been a researcher?</em></p><p><strong>KB:</strong> I’ve been a researcher for two years actually — it’ll be my two year anniversary of being a researcher soon!</p><p><strong>AH: </strong><em>Happy anniversary! And Valerie?</em></p><p><strong>VM:</strong> I’ll start with how long I’ve been a researcher. I’ve been a researcher officially since 2019. I initially thought product design was going to be where I would land, but research called out to me because I had a background in sociology from undergrad and I was like, ‘Hey, look at all those things that you were doing as an undergrad and how applicable they are to what it they’re calling UX research or design research.’ I’ve been here at Klaviyo for about a year and my work has been sort of floating in the ether between App-Communications and App-Intelligence understanding what some of the common points are.</p><p><strong>AH: </strong><em>So both of you had previous lives before you were researchers. And I’m curious if you can tell us a little bit about your journey into research and what led you here. What kinds of roles did you have before you were a formal researcher?</em></p><p><strong>KB:</strong> I feel like we’re kind of gonna be the same in the way that Valerie said, where you get into industry after doing a couple of things prior and being exposed to research. For me, I was in a graduate program, getting a statistics masters in early 2020, at the beginning of the pandemic. During my graduate program, our research group launched and analyzed survey research that started at University of Delaware about different age group’s reaction to COVID-19 protective behaviors. As a research team, we were trying to understand the different factors that influence people’s propensity to wear a mask and receive the COVID-19 vaccine. I think that work was integral to my understanding of underlying motivators for behavior and how statistics can be used to uncover those. In that role, I was really intrigued by the why behind the numbers. Like I can understand it analytically, but I wanted more of an understanding of things like, ‘why is this age group saying that they don’t want to wear a mask and they don’t want to get the vaccine’. So, that role is one of the reasons why I leaned into mixed methods research that starts with looking through a quantitative lens and then focuses outwards towards qualitative work.</p><p>Then after that, I was an analyst at a startup that focused on the same topic, health research. We were trying to help this telehealth startup understand how users’ engagement fluctuates in regards to their level of concerns with data privacy, forming new doctor-patient relationships, etc. A lot of our tools were quant base with work through surveys and analytics, but one-day I was just sitting there thinking, ‘I have all this data, I see all these numbers and graphs, but what is the underlying factor as to why this thing is increasing or why this thing is decreasing’. So I think getting at the why is the reason why I got into research.</p><p><strong>AH: </strong><em>So ‘why?’, is the why. I love it.</em></p><p><strong>VM:</strong> I would definitely echo the why sentiments, that was what pushed me to study sociology as an undergraduate student. It was something that had always fascinated me, why do people organize themselves in these ways? Why do people take these types of actions? I graduated from college in 2011. Didn’t really know how to plug a sociology degree into the world, didn’t know about UX research, didn’t know about design research, didn’t know about any of that. I did a couple years of AmeriCorps and worked in the nonprofit sector before transitioning to healthcare.</p><p>Outside of work, I was pursuing graphic design. I pivoted because the field was moving towards digital, so I wanted to know how I could activate what I’d learned on that side. And that’s when I started to pursue Human Computer Interaction (HCI) thinking I want to be a product designer. However, I definitely dug into the courses that were a lot more research intensive.</p><p>Studying HCI helped orient my awareness of human centered design and how research informs that kind of work. Also shout out to my former manager at Oak Street, he was super, super encouraging of me taking things that I was learning outside of work and bringing them in where applicable.</p><p><strong>AH: </strong><em>It sounds like both of you had a gradual interest in research that led you down a path that eventually became a career. But did either of you have a defining moment where you realized ‘I’m supposed to be a researcher!’?</em></p><p><strong>VM:</strong> I’m gonna be honest, I was like, ‘I hope I can be a researcher’ — that was my thought [Laughs] From my observation, the masters program I came out of was very structured in supporting folks to become product designers (things may have shifted since then) . A lot of the coursework I experienced was about prototyping, coding, information architecture etc. There were a few courses that they put in the program that were strictly oriented towards research and it was so interesting, because a lot of my cohort was like, ‘Ugh, why do we have to do this? Why do we have to write these papers?’ And I was just like, ‘This is great! I really hope I can do this professionally because I feel like being a designer is hard too.’ It’s hard in a different way. And in some ways, I thought being a researcher would let me play the strengths that I had (and continue) to cultivate.</p><p>I definitely have a great appreciation for graphic design and product design, but it seemed like being a researcher would allow me to use my strengths from the humanities while being in the tech field. So there was this hope, like I hope there is room for me to do this. It wasn’t a light bulb moment. It was a steady realization that I really could merge past and present interests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9K_coCPdad0yVxtgt-EDow.jpeg" /></figure><p><strong>AH:</strong><em> And look at you now! Well, it’s interesting, Valerie with your sociology background and then Katie with your quantitative background, that you’re both using that knowledge in your research. I’m curious how your prior experiences in those spaces have influenced how you approach design research?</em></p><p><strong>KB:</strong> Yeah, I would say my background has influenced the way that I approach research. Actually in a role prior to this when I was a researcher, most of the researchers would immediately utilize interviews to understand more about our users in the qualitative realm. And if they needed to size some things, they’d drill in a little bit further with analytics. But it’s weird, for me especially, a lot of colleagues on that team were like, ‘Oh, well, that’s interesting that you’re starting backwards right? You’re not committing to the qualitative research and then quantitative research execution of the workflow; you’re going to quant and then qual.’ So I would say working in a more quantitative realm as an analyst and then as a survey researcher has influenced me to work with analytics and surveys to answer some initial questions that way. This workflow comes from that epiphany I had one day where I would see concrete numbers on the graph with some anomalies here and there; let me get at the fuzzy underlying things that can’t be explained on a graph. So I would say those quantitative roles influenced my workflow and then, like Valerie was saying, education plays a part into how our brain thinks. When you specialize in one discipline like stats, it definitely has a lasting impression on your thought processes and thus influences your initial path forward in solving problems. But now instead of adhering to one discipline, I get to do both. Now I get the best of both worlds!</p><p><strong>VM:</strong> Both worlds 100%. And I would say coming from a primarily qualitative background I definitely appreciate working in an environment with folks that are really well versed and comfortable with quant because it is this back and forth. I gravitate towards qualitative because I think that as humans, it is compelling to talk about our behavior in terms of what’s desirable. That’s just an innate human thing, to say things that are desirable and encouraged. And that can filter down even into how we answer questions and how we engage with folks in basic interviews.</p><p>One of the things that I love is pulling apart what someone says and having them dig deeper into a response they’ve given because it allows me an opportunity to bypass some of those “defenses” in an unassuming and empathetic way. Actually one of the more advanced research techniques I’ve observed and learned is that occasionally when you’re in a session with a participant, sometimes the interview guide goes out the window because they say something that inadvertently can portal you towards what you were actually interested in the first place. This is why<strong> active</strong>, <strong>empathetic</strong>, <strong>non-solution based</strong> listening is a discipline of research that is easier to describe than to do. You didn’t let your imposed order of what you thought was important take control of the conversation, you’re letting participants open up to you in their own way to speak more plainly, and hopefully, honestly about their process challenges, and unidentified needs. At the end of the day, that’s what’s most important for our work as researchers.</p><p>If we can understand why people are doing things the way that they’re doing them — back to the big why’s — it allows us to actually design accurately. In our work it’s not about judging how people use technology, however as representatives of an organization such as ours we still have to be mindful to structure our practice such that we can build rapport and gain trust in a short period of time. I think that’s why interviews in particular are so energy-consuming because I feel like if someone can sense that you’re judging, or worse, trying to problem solve in the moment, they will know that you’re not really listening and that can quietly limit what you learn from them. When you’re actively listening and not trying to troubleshoot or judge you can hear a lot more interesting things to follow up on which can actually open up a whole world of new information.</p><p><strong>AH: </strong><em>Yeah, that’s fascinating. Okay, changing gears a little bit to the Klaviyo side of the house. Does one of you want to share the biggest challenge you’re facing doing research at Klaviyo right now?</em></p><p><strong>KB:</strong> Biggest challenge — I’ll say speaking on [their] behalf I don’t want to put words in the research mouth — I think that there’s so much interest in research that it can be difficult to say no to some requests. Luckily Klaviyo is very much a research oriented culture that the product team’s interest in research is still alive and well even if the research team isn’t directly involved in it for that moment in time.</p><p><strong>AH: </strong><em>So much to do, so many people to teach how to do it — you got your work cut out for you, but we’re all very happy you all are here. All right, Valerie, for you. What are you the most excited about in the future of research here?</em></p><p><strong>VM:</strong> I’m actually excited for the next two quarters, because I know there have been a couple of realignments around what we’re focusing on as an organization. Also our team has expanded at the same time and so I feel like [we’re] now in this research mega-zoid mode, having multiple researchers across these pods and across our pillars to really showcase what our team is capable of now that we’re more fleshed out.</p><p>I think what may have been a little bit challenging was when we were at limited capacity, back to what Katie was saying, prioritizing where we were going to plug ourselves in, what kinds of research aims were we going to tackle and what was going to be the best use of our time. Now that we have a bigger team, there’s going to be more of that tactical to exploratory range, and not necessarily needing to sacrifice what kinds of questions are important to our partners and what are important for getting the company oriented in the right direction. I think we’re going to be much better suited to support so that’s the most exciting part for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLSVpyjK2VHFmLELZdzx6A.jpeg" /></figure><p><strong>AH: </strong><em>Cool. Yeah, that sounds exciting.</em></p><p><strong>KB:</strong> Are we allowed to talk about CDP land?</p><p><strong>AH:</strong> <em>I believe so!</em></p><p><strong>KB:</strong> Yeah, I was going to say the research in that realm specifically is really exciting. Especially coming from the App-Intelligence side. Just thinking about people’s reactions to CDPs in general, I know that there’s an interest in it. And there’s so many strides that can be made at Klaviyo when we’re focusing on that and how to make data as accessible and usable as possible for our users in the ways that they’ve already expressed interest in. Building upon that is something that I’m excited for in the App-Intelligence realm!</p><p><strong>AH: </strong><em>All right, I know we’re out of time, so you’ll have to give me the two sentence version, but for those people out there who are taking their own meandering path to research or like asking questions and looking for the ‘why’, what is the best piece of advice that you can give to them?</em></p><p><strong>KB:</strong> You know, I would say two things. The first thing I would say is stay hungry and thirsty for knowledge. There are so many methods out there that you can use, and it can be a little bit overwhelming when you first start. Like okay, what do I do? Do I do qual or do I do quant? Is this at the beginning of the product lifecycle? Is it towards the end? Are we iterating? Are we exploring? There’s so many different methods. I would say to stay interested in the fundamental ways to extract insights from each of these scenarios and continue to learn about the research function overall. Like understanding how it’s evolving because the field is always evolving. I feel like research in UX was not as big as a thing five years ago, so it’s really blown up. And it can kind of be overwhelming at first to get into the field, but remain open to what you can learn and then once you’re in the field remain open to feedback. Always know that there are some things that you can modify, so please remain open to feedback from colleagues who are experts in an area of research that you haven’t explored yet. Moral of the story is to never say no to learning more in various contexts; whether it be from a textbook when you first start in UXR or from someone on your team when you break into industry. I think those are the most important things, but what about you Valerie? Is there something else I’m missing?</p><p><strong>VM:</strong> I mean, you hit on at least what I was going to say towards the end. I think especially if you’re interested in research at Klaviyo it’s a highly collaborative experience. I don’t know if I’ve worked at a place where it hasn’t been, but I do know that there are some places that have the research function in its [own] box, everything in its box. I think research at Klaviyo is definitely one of those things where you’re bringing your strength but you’re adding to other people’s strengths.</p><p>We have excellent partners from product analytics, product, Voice of Customer, market research, customer advocacy. We are working across so many different groups that are also doing research. And so it’s really not about being a lone rock star. It’s about being like, ‘Hey, here’s what I’ve learned, or here’s what my colleague has learned.’ I think we spend a lot of time routing inquiries to other teams or colleagues familiar with a line of inquiry. ‘Oh, you’re asking this question. My colleague over here has done this. Maybe that’ll help you’. That’s again, going back to the point of making sure that we’re tamping down on duplicative efforts and plugging research that was previously completed into our process so that we’re constantly building on what we’ve learned prior.</p><p>When you’re thinking with a collaborative spirit, it’s easier to open doors so that information can move across the organization and nothing is being held so tightly or so siloed that it doesn’t get socialized, doesn’t get shared because I think that’s the death of research — when you find knowledge but you can’t socialize it and nobody can act on it. And that right there is every researcher’s nightmare that they seek to avoid. So, yeah, staying collaborative, staying connected.</p><p><strong>AH:</strong> <em>Love it — learn, collaborate, share!</em></p><p>🛣🕵️‍♀️— <em>I can personally vouch for the expertise of Valerie and Katie. It’s really cool to have a research team and more generally a design team full of people that come from a diversity of backgrounds!</em></p><p>Think your interesting background could help make our design team better? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e511589ec16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-6e511589ec16">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-a3459ae9bc57?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3459ae9bc57</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Thu, 18 Aug 2022 10:34:50 GMT</pubDate>
            <atom:updated>2022-08-19T11:11:21.432Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: UX Internships with Winnie Tam &amp; Gayathri Ramesh</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1iIFC3Bhu6b2WZLtGnvpyg.jpeg" /></figure><p><strong>AH:</strong><em> Let’s start off by having you both introduce yourselves and tell us what team you worked with this summer?</em></p><p><strong>WT:</strong> I can start off first! Hello, I’m Winnie. I am on the flows team this summer as a design intern.</p><p><strong>GR:</strong> Hi, I’m Gayathri or you can call me G and I’m on the integration team this summer working with the design research team.</p><p><strong>AH: </strong><em>Awesome. All right. Well, you guys are our very first design interns — so exciting! Can you tell us a little bit about what brought you to Klaviyo and why you chose us since I’m sure you had many wonderful opportunities for the summer.</em></p><p><strong>GR: </strong>When I saw the [internship] post, it talked about having both design and research skills which was something I had some experience with. I have a background in computer science and while I was there, I was doing both research and design. Right now I’m doing a master’s degree in UX research and design so that job description was speaking to me. When I was researching the company, I found that it was really collaborative, highly energetic and always up for challenges. But [solving for] those challenges came with a lot of iterations and work to improve the interface and that stood out to me because research and design has to go hand in hand. As you find things, you have to convert that into design and do it all over again. So I applied last December, and it was great.</p><p><strong>AH: </strong><em>Cool. What about you Winnie?</em></p><p><strong>WT:</strong> For me, it came full circle. I actually knew Stephen before he started working for Klaviyo — we had talked and connected through an online webinar. And then we hadn’t talked for a little bit when I saw on his LinkedIn that he posted, ‘Hey, I have this new position at Klaviyo’ and I was like, ‘Oh, what’s Klaviyo?’ And also I thought it was pronounced ‘cla-vi-o’ at the time so I was like, ‘Oh, what’s <em>cla-vi-o</em>? That’s so cool!’ [Laughs] And then I did a little bit more digging into the company and found that everyone had an amazing time there and couldn’t stop raving about the work that they were doing and how intentional it was and the culture. So everything just seemed really amazing. And then, serendipitously there was Diana — I was involved at the time with a mentoring platform called ADPlist. I was running their ambassador program and Diana was also a mentor with ADPlist so that’s how we got connected. She also couldn’t stop raving about Klaviyo and she told me about her story and her transition. Then when I was interviewing with Klaviyo, I really really loved, like what drove it home for me, was they were not afraid to ask the hard questions. Honestly, I think that was one of the most difficult interviews I’ve ever had but in a really good way because it was like, ‘Did you think about this little thing? Did you think about this other little thing?’ I was like, ‘No, I didn’t think about that.’ And I was like — okay, I want to work with a company that <em>does</em> think about those things and that does push me forward. So that’s the long story-short of how I found out about Klaviyo!</p><p><strong>AH:<em> </em></strong><em>I love it. You guys are name-dropping Klaviyo values and saying things that will make everyone blush! So we’ve got flows and then integrations on the research side — give us a little more detail into the projects you guys worked on with these teams.</em></p><p><strong>GR:</strong> I’m working on the integration team, specifically, I’m working on the Facebook advertising integration. So trying to figure out any usability issues that it has and trying to explore whether any fixes could be made. Then checking in on the users’ current experience and trying to improve from there. Also we’re looking to see whether there’s any potential integrations that we should look out for in the future. I’m working with designers, PMs, and product analytics. I’ve also been working closely with the Support team to discuss issues that the users reach out about. And so I’ve been working with the teams to figure out what we could do.</p><p>Another integration that will hopefully be coming out is the Google Ads integration. And that’s something everybody’s excited to see. So they’re hoping that any [challenges] that the Facebook advertising integration is facing, anything that we can straighten out over here, we could hopefully apply to Google Ads. Overall, I think a major goal for the [Facebook] integration is to hopefully find some findings that could translate into standardizing all the integrations, like the design and any sort of other recommendations [for the UX]. That has been the project I’ve been working on for now.</p><p><strong>AH: </strong><em>Super impactful, and you Winnie?</em></p><p><strong>WT:</strong> So I’m working on a feature called back-population in flows. Back-population is really important for users if they want to add previous profiles [to a flow]. So let’s say, for example, a new user comes into Klaviyo — they import all of their previous profiles, they just created a new flow within Klaviyo and they just turned it live — everyone going forward from the moment that they turned it live will be sent in automatically through that flow. However, the previous profiles, prior to the flow turning on live, will not receive those emails. So in order for a user to enroll those previous profiles, they would do something called ‘back-population’. Essentially what I’m trying to do right now is redesign or create a better experience for users.</p><p>There’s currently three main pain points with back-population:</p><p>Number one is discoverability. It’s not very discoverable at the moment because it’s called ‘back-populate’ and users don’t really understand what that means. So either 1) they’ll contact support which leads to really high support ticket volumes, or 2) they go to help docs and community forums and it’s not really clear. So working on discoverability, and really being able to help users access the information when they need it, and when they want it.</p><p>The second main pain point with back-population right now is the lack of clarity behind the language. Right now we’re using a lot of ambiguous and abstract words like ‘relative’. So trying to make sure that we reduce the abstractness and really increase the transparency behind the language and simplify it to something even your grandma can understand. And I know it’s easier said than done, but trying to do that.</p><p>And then the third main pain point is with visual reassurance. So right now once users click back-populate, there’s not really anything giving them a visual indication as to the progression of their back population. And that’s really important because we want to make sure that users can trust [us] and we can instill confidence in our product. So that’s currently what I’m working on — improving that experience and making sure we can also bring as much impact [with it] as possible.</p><p><strong>AH: </strong><em>That’s awesome context. Glad to hear you guys are deep in the problems! Did either of you get the opportunity to talk to customers and if so, did you have any big takeaways or something surprising you learned?</em></p><p><strong>WT:</strong> That’s a good question. So I did not get the opportunity to talk to customers. I did watch a lot of Gong videos and Fullstory sessions and something surprising that I learned, at least in relation to my project of back-population and going back to the key pain points, is we had users who had been using Klaviyo for more than four years, and they still didn’t understand what exactly [back-population] meant. And that was really surprising to me, because I was like, ‘Oh, we really do have such a huge opportunity to make sure that this is as usable and as desirable for users as possible.’ And it was really cool to hear how much our users rely on Klaviyo for their business. I didn’t realize how big the impact was on our users. But after hearing them in the user interviews saying ‘[Klaviyo] is a huge part of our business’, it really hit home.</p><p><strong>AH: </strong><em>You were nodding G — did you get to talk to some customers?</em></p><p><strong>GR:</strong> Yeah, absolutely. Because of my project which was a lot of usability testing, I had to talk to some customers and also non-customers as well. And when I was interviewing with customers, it was interesting to see the wide spectrum of how they use Klaviyo. Some were always hands-on with what they were doing [in Klaviyo] even if it was something small or specific in flows and campaigns. Some even referred to it as a one-stop shop and so they really like using it. What was interesting to me was they all had a lot of growth in their business and they wanted to make sure that they communicated with customers and established that bond. And they found their transition to using Klaviyo was the answer because they saw that growth in their business and also saw a growth in how they were bonding with their customers as well. And what stood out to me was they all found Klaviyo to be very useful and very user-friendly compared to the previous platforms that they were using.</p><p>I also had a chance to “meet” some non-customers through unmoderated usability sessions with them. So I saw their recordings and while they were walking through it, towards the end, they were like, ‘Well, this is actually easy to use. It’s so user friendly’, and although I can’t estimate whether they will convert later on or see Klaviyo as a future opportunity, It was definitely still interesting to see. But yeah, the wide range of how Klaviyo addresses the user needs and the customer needs has definitely been interesting to see.</p><p><strong>AH: </strong><em>Cool. And Winnie question for you — did you find that there was a part of the design process that you really preferred more than other areas when working through back-population problem?</em></p><p><strong>WT: </strong>At heart, I am a researcher — I really love to deep dive. And that’s one of my areas of opportunity, too. It’s like, ‘Hey, remember, don’t go too deep in that rabbit hole!’ So my heart will forever be in research because, for me, that’s my way of really making sure that we are solving the right problem — making sure that we are doing our due diligence and that we’re spending the right time, the right focus and the right intentions towards solving the right problem. That to me is a big thing.</p><p>So that’s why research has always had my heart, but a new piece of it that I’m really grateful to have had the opportunity to learn more about and be a part of is the collaboration aspect, especially with engineers and PMs and other stakeholders. My previous experiences have been with early stage startups. So it’s been me being everything, wearing a lot of different hats. I’ve never worked with a PM before. I’ve never worked properly with an engineer before. So that was a really enjoyable part of the process. Also getting a lot of different people’s feedback and sorting through why they think a certain way. I could branch out and gather different perspectives because sometimes, when you look at something for too long, you’re like, ‘Okay, I need to fresh, new eyes!’ So that was really enjoyable.</p><p><strong>AH:<em> </em></strong><em>Yeah, it’s so fun. We’ve got quite the diversity of expertise here. It’s awesome. You kind of answered my second question too, so we’ll kick this one over to G which should be interesting since you’re completing your HCI masters. Has this opportunity shaped your thinking at all or given you more clarity on where you’d like to focus as you go forward?</em></p><p><strong>GR: </strong>Absolutely. This was my first internship and although I had some experience with academic research before through my master’s program, I was still new to the working world and product design research being applied in real life. So it was a great experience and now I feel more grounded in design research. I think it’s important to have both [design &amp; research]. You need research to get to the design, but it’s a work in progress — it has to go hand in hand like yin and yang. So I think it’s important that I understand how to present research findings and how we apply them to design. Pre-internship, I knew that I was interested in both, but through the internship I was able to grasp more of the importance of it and the subtle things that could change when we understand more about [the problem]. And so I could see myself definitely being in design research more now, while also steadily learning more about design to bridge the two.</p><p><strong>AH:</strong><em> Is there a favorite memory or experience you had over the summer so far? And Winnie if you don’t say hanging out in Boston with me and some of the other designers, I won’t have it. [laughs]</em></p><p><strong>WT:</strong> Yup, that is literally what I was gonna say. Definitely Boston — that was so much fun. I think it’s just a different vibe and it’s a different energy when you’re in person. You’re like, ‘Oh, hey, you’re not just a face on Zoom! You’re a person. You’re real. Let’s connect!’ Also, the airplane session was super fun. I really liked that. Boston was definitely one of my favorite memories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*NmY2aRCCiXHNVWdYWCfkuA.gif" /><figcaption>Spontaneous competition amongst the designers to create the most aerodynamic paper airplane</figcaption></figure><p><strong>GR:</strong> Well, unfortunately, I was not able to have in-person meetings because my team members are all over the United States. So a lot of it focused on super fun online workshops and events. Some of my favorite memories would be some of the design research workshops. For instance, my team members, Natalie and Valerie, conducted and presented a huge research study, and it was very insightful to the rigor that went into it and it was definitely enlightening as well. Other than that there were a lot of social events as well with the design research team. We meet twice every week and so monthly we do something fun and one of them was doing a <a href="https://rocketcrab.com/tvay">Drawphone activity</a> or recently we went on a <a href="https://virtualvacation.us/guess">virtual vacation </a>— I can send the link later on. It was definitely really fun!</p><p><strong>AH:</strong> <em>Virtual vacations?! What have the rest of us been doing?</em></p><p><strong>GR:</strong> Yeah it was fun! This was something I didn’t expect; with remote I expected it to be a bit disconnected and not have that in-person energy. But honestly, I feel really connected with my team and that was something I did not expect at all. It was really fun and I feel like I really know the team members as well.</p><p><strong>AH: </strong><em>That’s amazing. I’m curious since you both mentioned the remote aspect. Were there any challenges or any surprises that came out of having this internship totally remote?</em></p><p><strong>GR:</strong> I didn’t really have any challenges per se in terms of remote work. I expected maybe I would have some issues but honestly all my team members were very open — they had an open line of communication like ‘Hey, if you have any questions, just ping me and I’ll be there.’ And so I was always able to set up some time in case I needed some help. I know in person, maybe that would have been more like looking over the shoulder and asking ‘Hey, what can I do with this?’, but I was still able to do something similar online as well.</p><p>And then there’s like the work/life balance with remote work and watching the computer for too long. And so, [the team] was also very understanding of that, and Klaviyo itself was very understanding of that, for instance with the wellness benefits. I think they were very mindful of making sure that I keep that balance as well. My team members always tell me ‘Don’t work overtime, why are you online so late?’ And I’m like, ‘No, that’s just Slack online!’ They’re always very considerate of making sure that I’m in my best state.</p><p><strong>AH:</strong><em> You want to add anything Winnie?</em></p><p><strong>WT:</strong> I’m good. I think G said it all!</p><p><strong>AH: </strong><em>Next question, what was the biggest learning from your time this summer?</em></p><p><strong>GR:</strong> Initially, I was very conscious of the fact that I was new and I was an intern. I was concerned about stepping on toes and making sure that I didn’t cross the line. So I was sort of hesitant on speaking up during team feedback [sessions] or research conversations. But my team was very encouraging in terms of saying things like, ‘You’re not just an intern, you’re a valuable team member. Don’t feel like you can’t speak up. You provide a really fresh and new perspective. Some of us, since we’ve been on this platform for a while now, might not be able to see [things] and so it would be great if you could share your insights and your ideas would actually be super helpful as well.’ That helped me speak up more and feel more comfortable, so that was one of my biggest learnings I suppose. Other than that, when we did those research findings for different projects that we were on, I could see that there were a lot of things that came up that were similar things to those that came up in different projects. So what we’re thinking is ‘This could probably bubble up into something that goes beyond just our specific projects’ and that was very interesting to me and the team and we’re excited to see how that goes out and know what the team uncovers overall as well.</p><p><strong>AH: </strong><em>Larger, thematic thinking rather than being specific to the project. Nice!</em></p><p><strong>WT:</strong> For me, I think the biggest learning — and it kind of parallels G what you were saying about speaking up — was not being afraid to ask questions. I still struggle with this one a little bit. But I think it’s definitely gotten better since being at Klaviyo and I’m really appreciative of the learning environment and everyone saying, ‘Hey, there’s no such thing as a dumb question.’ Everyone is always super nice and super willing like ‘Throw some time on my calendar and we can chat about this.’ If anything, I might ask too many questions. So I’m always scared — I’m like, ‘Oh, but what’s this? And what’s this?’ and all the little details. And I worry am I gonna annoy someone if I ask all these dumb questions, but I have never gotten that, if anything I’ve been more encouraged to empower my questioning and curiosity further, which I really appreciate. It was a really good learning lesson for me.</p><p><strong>AH: </strong><em>How have your internship projects here compared to some of the projects that you’ve worked on during university?</em></p><p><strong>GR:</strong> This was something I was asked in interviews when we were searching for internships — they used to ask ‘Have you worked on cross functional teams across different teams like engineering or product or teams like that.’ I think that was a bit hard for me to achieve through uni because of the current situation with COVID 19. It was hard to find real world projects, and so I did not have that experience.</p><p>I think it was definitely interesting with the internship to have that opportunity to talk to design, devs, support team and PMs and work across those teams and try to see how we could learn from them. That opportunity we not may not have in universities in general. So through the summer. I definitely learned a lot that I could not have learned at uni.</p><p><strong>AH: </strong><em>I love that and Winnie you had mentioned something similar with the collaboration aspect being nice to have this summer.</em></p><p><strong>WT: </strong>Yeah, 1,000%. Mine is a little bit different. So I transitioned fields and was previously marketing in University. I graduated and a year later I transitioned into design. I can speak more to my own projects that might parallel the ones you do in University. The main difference, like G mentioned before, was collaboration and then also [dealing with] constraints was a really good thing for me to learn this summer. With personal projects or uni projects, you might have more free rein to go where your imagination goes. But in real life projects, there are a lot more considerations to take in mind. It’s not just you who has ownership of this project. It’s everyone else that has built this company from the ground up. So you have engineering, you have PMs, you have sales, you have marketing — no matter what everything is interconnected. And it’s really, really important to take that into consideration and to try to understand where people are coming from if they’re giving you perspective or they’re giving you feedback. I think the main thing that really helped me, and is still something that I’m trying to improve on, is just having a beginner’s mindset. No matter how much you have been a part of a project, you still don’t know as much as the people in the room. So it’s always good to hear them out and collaborate and just work together. Because working together I feel always creates a better product than just yourself in a silo.</p><p><strong>AH: </strong><em>Totally agree. And we’re at our final question — if you could go back and give advice to yourself at the beginning of the summer, and/or give advice to other people trying to make the most of their internship experience. What would it be?</em></p><p><strong>WT:</strong> So if I could give myself a piece of advice, it would be to be more confident with certain things. Like the impostor syndrome — she still hits me every day! But I think something that I would love to tell myself is to be more confident in your skill set. There’s a reason why they hired you and there’s a reason why you add value to the team and don’t forget that.</p><p>In addition, I think it’s really important to have goals for yourself or set an intention in the way that you approach work. I’ve noticed that it really makes a big difference in the way you think about things and what your mindset is going into certain projects or approaching certain challenges. So something that I think would help everyone whether you’re in university or looking for an internship or looking for a job, is be intentional and sit down and have a conversation with yourself asking ‘What are my goals? Why am I doing this?’ And then work backwards. I think that’ll be super helpful in helping you manifest whether you are wanting to find another position or what you want. I know that sounds a little woo woo but the good energy that you put out, you’ll receive that back.</p><p><strong>AH:</strong> <em>That’s good general life advice! You want to add onto that G?</em></p><p><strong>GR:</strong> Yeah, with that in mind, finding an internship will be hard. My general advice is to keep applying, despite the rejection emails and I know it’s easier said than done but don’t take it too personally. There are other factors that are in play — that doesn’t mean it’s a reflection or report on your skills. But I think like Winnie said, just believe in your own potential and your own skill set and continue doing the work and exploring the topic because if it’s something that interests you and you’re passionate about, I think you can get beyond that. So just keep going, that would be my personal advice. I know that it’s something that [other] people tell you when you reach out for advice, and I know it’s sort of cliche, but it’s the same thing I find even now. But it’s also important to check in with yourself and then take some time off if you need to, when it’s getting too difficult. Focus on your mental health or do something else (that’s not stress-inducing) and then find time to come back when you’re ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*smqO6SaKatqQEX7Qk5z04Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqdXvqitYR43NE59RsSnRw.jpeg" /></figure><p>👩‍🎓🎨 — <em>Thank you Winnie &amp; Gayathri for all your amazing work this summer -our team and Klaviyo as a whole are better for it!</em></p><p>Does hearing about their experience make you want to be a part of our crew? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3459ae9bc57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-a3459ae9bc57">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-491ecc4040d5?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/491ecc4040d5</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Wed, 03 Aug 2022 13:01:06 GMT</pubDate>
            <atom:updated>2022-08-10T10:21:38.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Building a UX Research Team with Mike Oren</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*an8oxZ3AJyc9pK0ML_zh_g.jpeg" /></figure><p><strong>AH:</strong> <em>Alright, welcome Mike! Let’s start with the basics. How long have you been a design researcher? And how long have you been at Klaviyo?</em></p><p><strong>MO: </strong>Well, second question is the easier one. I’ve been here at Klaviyo for about a year. For the first one, it will depend on how you count it — if you count since I formerly had a design researcher title, 2012 was the first time. So a decade. But before that, I spent a year as more of a product designer where I was doing the interaction design, sort of doing the visual design — but it was largely coming from a style guide — the prototyping and then all the different research. Before that, there was grad school and my very first exposure to user experience and doing UX research with undergrads was in 2004. I did a research experience for undergraduates where I ended up designing, developing and doing some iterative research sessions and then a longitudinal study on this gesture-driven icon system for a collaborative group where the same set of gestures would open different tools depending on the icon where the user drew the gesture. So it’s basically PowerPoint, but then students could also send their responses back. That’s why that one’s a more complicated answer for how long!</p><p><strong>AH: </strong><em>So what you’re saying is it was in your bones from the beginning. It just took a little winding path to get to the official title.</em></p><p><strong>MO: </strong>That’s right. You could claim 18 years or you could claim a decade</p><p><strong>AH: </strong><em>Depending on who you’re talking to - I love it. All right, well, first things first, when we’re talking about UX research, what does that encompass?</em></p><p><strong>MO: </strong>It’s really everything starting from helping identify who potential businesses’ customers are going to be. So if you’re trying to create a new type of product or create a new business, really identifying and going out into the world to try to observe - what are the different areas of friction in people’s lives? Or what are the areas that they want to see improvement? And where are they potentially willing to invest in those solutions? Because there’s lots of different problems people have, but a lot of those aren’t necessarily worth investing in — they’re not willing to get themselves out of their current way of doing things.</p><p>So that’s the journey of exploratory stuff, then as we move along the path we move on to concept evaluation where we have this big set [of ideas] and we diverge. We know all these different areas where there are potential problems. We’ll work with designers or if you have a researcher who is a good artist, which most of us are not but there are some who are, then they could design/mock up those concepts, create storyboards, vignettes, and whatever else in order to help articulate potential ways that those different friction areas can be smoothed out and made better for people. We’re then able to start converging into the solutions that will really provide value to people’s lives.</p><p>And after we have a sense of the real solutions that are really going to provide value to people’s lives, we diverge once again. Now that we have some sense of a core solution, how does that solution actually need to work in order to be usable? Especially if it’s early on and you don’t have a design system (and even if you do have a design system, there’s still different tools, different layouts that might solve that problem), understanding what’s the right way to engage people and have that efficiency is important. So mocking up multiple solutions then iterating and getting to that final prototype and doing evaluative research to understand how well it’s performing versus other things on the market versus previous designs is all important. This is the ideal flow of going from a blank slate. Or if you have existing solutions, we’re also pulling in quantitative data. At Klaviyo we use Productboard, so looking through Productboard to understand. Listening to Gong recordings with customer support and sales. Viewing flows on Fullstory, etc.</p><p><strong>AH:</strong> <em>Makes sense. That is a nice lead into my next question — you talked about these diverging paths, all these different opportunities, so the team can obviously be very diverse and contain a lot of different specialties. As a research leader, talk to us about the ideal team makeup and then what our team at Klaviyo looks like currently.</em></p><p><strong>MO: </strong>The ideal team makeup is going to vary a little bit from company to company and depend on the different needs. But at Klaviyo… Well first I will say I am a major advocate of mixed methods research. So making sure that no matter what, no matter where you are, you have people who really understand qualitative research deeply as well as people who have a deep sense of quantitative. So we have hired for people who are across the spectrum. We’ve got some folks who are not allergic to numbers per se because again, we believe in mixed methods, but they are much stronger in qualitative research. On the other side of the spectrum, we’ve got people who are really strong in quantitative methods. They’re comfortable with qualitative methods, but they wouldn’t necessarily know how to do some of the more complex qualitative methods — like they wouldn’t necessarily know how to run a diary study, or the right way to do field research, which we don’t do field research so much during a pandemic [laughs] but someday!</p><p>At Klaviyo, one of the important things — and I shouldn’t say just Klaviyo this is generally an industry trend - is research teams should not own all of the research. That actually does a disservice to the people that we’re designing for because it’s important that the product managers, designers, even the engineers and data scientists, build as strong of an empathy for the people that they’re building for as possible. So part of a modern research team’s value, and something you have to think about when you’re hiring people, is finding people who are comfortable educating and training others to have these conversations with customers and look at these different types of data and not feel like they have to do it all themselves, but really understand and empower the wider team. That’s something that’s been important as we’ve been building out the team here at Klaviyo — getting people who don’t feel like it has to be done perfectly, because that’s another thing that sometimes researchers get hung up on is they want this perfect model of research. And if you have a perfect model of research, it’s sometimes hard to allow pieces of it to be democratized. Especially if it’s not your sole job to do research, then you’re not going to and you shouldn’t have to care about all the little nuances that someone who’s focusing only on research will have to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twhkl4hfu_7lQFcuODR0_g.png" /><figcaption>An output from a diary study conducted by two of our researchers 😲</figcaption></figure><p><strong>AH: </strong><em>That’s a nice dovetail into the next question — you all are your own team and less embedded in a single pod, although we are moving towards a hybrid model. So how do you determine where your researchers are going to spend their time or what projects everyone should pursue?</em></p><p><strong>MO: </strong>It’s a combination. Number one northstar is the company’s overall goals and objectives. Things that AB and his leadership team are saying are the most important things for Klaviyo right now. Anything tied into those are where we lean in. Anything not tied into those, since we know that they’re still important in order to get work done at Klaviyo, what we end up doing in those cases is understanding what’s the complexity and ambiguity of those different things. Also, what are the different breakdowns of the skills between the product managers and designers in each pod and portfolio. Then we make sure we’re syncing up with the design director and product director within those pillars to prioritize which areas we’re going to lean into and which ones we’re going to, not ignore, but let those pods own a little bit more.</p><p>Across the board, there’s recognition that in some pods, the product manager is a little bit better at the interviews and in some, the designer a little bit better and in others, neither have a strength in research. So that’s where we might lean in a little bit more. Sometimes the designer and product manager might have to focus on the near term deliverables, but they also know that they can’t ignore what’s coming up next on the roadmap. We’ll lean into those areas in order to help them get more runway so when they get into that next quarter, it’s not that we’ll have done all the research, but we’ve reduced the ambiguity enough that there aren’t as many risks of putting certain things at the top of the backlog for the developers, designer and product manager.</p><p><strong>AH: </strong><em>Yeah, that’s interesting. It’s that relationship between the pod PM, designer and researcher.</em></p><p><strong>MO: </strong>I should say some of that is shifting now that we’re getting more researchers on the team. There was a survey done amongst product managers last quarter that asked for more technical support from research. This was always part of the plan, as long as people were finding value in the consulting that research was doing, to get to a better ratio. We’re still not quite at the 1:4, researcher to product pod level, but we’re close enough that we can start to operate at that level. It’s still too many pods for the researcher to do all the work and so the pods still own their research, but it’s also few enough pods that if one or two of those groups have really important things or the designer or product manager feels overwhelmed, the researcher is able to lean in and offer more support.</p><p><strong>AH:</strong> <em>So we’re working towards that ideal ratio! In the meantime, you guys have put together a lot of resources and opportunities to get feedback. Can you describe what opportunities you all are providing like office hours so people can get help if they don’t have a dedicated researcher?</em></p><p><strong>MO: </strong>That is something that we have been experimenting with and we’re working on getting more consistency across all the different pillars and pod areas. We have had weekly office hours that I run for anybody to ask me questions. We also have the Slack channel for anybody to ask asynchronous questions. Adrienne, a researcher within the App Communication pillar, was working through a weekly cadence of meeting with the design lead and then also with the director of product on a weekly or every other week basis.</p><p>In other areas, like the area that Katie had been supporting, it was much more of an ad hoc setup. As people had questions, they would reach out to her and then she was largely working with product managers within areas that her research was most directly affecting.</p><p>And then we had some researchers whose work didn’t tie to a single pillar. They were only having conversations when we identified that the work was actually going into a pillars area and then we’d go down to that particular pod that would be impacted and have that conversation with them.</p><p>What we found is Adrienne’s model works most effectively here at Klaviyo. So these models mentioned will work to different levels of effect depending on each different organization. One exception that doesn’t work is if you’re only working at that top level. You also have to have a similar structure at those lower pod levels. Basically having regular meetings with all the designers and product managers in the pods. But again, too many pods and the researcher will get overwhelmed and won’t get any work of their own done. Too few and they’d be leaning too much into the work… We’re hoping that we’ll get to that right structure now.</p><p>From here, we’ll normalize what the expectations are for researchers working within that [system]. This will include not just doing their research, but because research often crosses pillars especially with the nature of Klaivyo, researchers will be leveraging their relationships with other researchers to do cross-product initiatives. We are trying to create more of a spiderweb, hive mind, collective intelligence, whatever you want to call it. This way every researcher should hopefully get to know everything that’s going on.</p><p><strong>AH:</strong> <em>That’s awesome and totally understand it’s a work in progress. That being said you have taken us from having no research team to having a really robust group of people. What has been the most challenging thing in the last year of building the team?</em></p><p><strong>MO: </strong>I’d say making sure that we’re keeping everything equitable amongst the team — you have different size challenges and projects. At the same time, you have different skill sets, you’ve got different philosophies. Anthony (senior researcher) told me when we were hiring people, he was surprised by the diversity of skill sets on the research team because he’s been used to research teams where basically all the researchers were interchangeable cogs, which is very much not my philosophy when building teams. So that’s been somewhat of a challenge — making sure everybody’s aware of [our team’s diversity] and why different people are assigned to projects based on their skill set. I haven’t had anybody complain about it or have any issues with it, but it’s just something that I keep in the back of my mind. On top of that, making sure we keep up that diversity of talent — when I say that I mean the big scope, like different thinking styles and an ability to collaborate and learn from one another because that’s what ultimately makes them the best researchers in tech. You’re going to be exposed to so many different approaches to research, and you learn how they all come at it from different angles and even different levels of rigor. Sometimes you need high levels of rigor. Sometimes you need the quick, dirty answer. And I will admit I am very much a quick, dirty answer type of researcher.</p><p><strong>AH:</strong> <em>But you’ve built a diverse team to support it. I love it. All right, so now thinking towards the future, what is the biggest upcoming challenge you foresee and then the thing you’re most excited for?</em></p><p><strong>MO: </strong>I would say biggest challenge I see is now that we’re starting to align researchers closer to the product team’s org, as well as building a better structure for getting full alignment with research projects, is making sure we don’t lose sight of some of the things that are important to know but people don’t realize they’re important to know until we get the findings. Like, for example, the flows work that was done, it improved flows turning on by 16.5%, and it’s not just that the work wouldn’t have been done but the research to prioritize making that change probably wouldn’t have been prioritized by product at the time. So making sure we don’t lose the ability to do the right thing for customers while at the same time making sure the product org feels like their voices are heard in the prioritization process.</p><p>Part of that, too, is making sure that the team continues to feel connected with each other especially across different pillars. Now that we’re adding some structures, some researchers will have their scope of work slightly decrease and then others will see their scope of work slightly shift.</p><p><strong>AH:</strong> <em>And what are you the most excited about?</em></p><p><strong>MO:</strong> Most excited about… Everything with Klaviyo honestly. I think Klaviyo has a lot of different opportunities to expand and grow. And I think it’s an exciting place with fun people! Especially if we start doing international expansion. We can do international research. That would be awesome.</p><p><strong>AH:</strong> <em>Endless research opportunities! And now finally two questions about advice, what advice would you give to someone who is interested in learning more about or becoming a design researcher?</em></p><p><strong>MO:</strong> There’s a reason why the #1 answer researchers provide is “it depends…” context is empress in anything research related. The background you’re coming from, the skills you’ve practiced, etc. can help define what your “shortest” path into research will be as well as where you most need to grow. There’s not one “right way” to do research so much as there’s the right way for what is needed. Increasing your breadth of methods (I created a now horribly in need of updating “<a href="https://docs.google.com/spreadsheets/d/1WspreZQ1tVCJvXEb-plCG80ZqFdh4ULthR9tcuQBHvM/edit#gid=0">cheat sheet</a>” a decade ago) are helpful but so is getting a good understanding of sociological, psychological, anthropological, etc. theories and understanding how to <em>apply</em> those to help interpret what you’re hearing and observing. Also some books to get you started: <a href="https://www.amazon.com/Observing-User-Experience-Practitioners-Research/dp/0123848695/ref=sr_1_1?keywords=observing+the+user+experience&amp;qid=1654790269&amp;sprefix=observing+the%2Caps%2C78&amp;sr=8-1">Observing the User Experience</a>; <a href="https://www.amazon.com/Understanding-Your-Users-Interactive-Technologies/dp/0128002328/ref=sr_1_1?keywords=kathy+baxter&amp;qid=1654790298&amp;sprefix=kathy+baxter%2Caps%2C76&amp;sr=8-1">Understanding Your User</a>s; and <a href="https://www.amazon.com/Rethinking-Users-Design-Ecosystem-Thinking/dp/9063695810/?_encoding=UTF8&amp;pd_rd_w=hUPkm&amp;content-id=amzn1.sym.5fe95cd4-8512-42fa-bf21-63d83b898785&amp;pf_rd_p=5fe95cd4-8512-42fa-bf21-63d83b898785&amp;pf_rd_r=0KGW630JZVHQ3RKVVXTR&amp;pd_rd_wg=9PQ0h&amp;pd_rd_r=008eb5a1-a5c9-4447-b3db-e6e462e19190&amp;ref_=pd_gw_ci_mcx_mr_hp_atf_m">Rethinking Users</a> (especially if you’re in a B2B design space)</p><p>Research is not just reporting what you hear and observe, but understanding the why people do or say what they say and working closely with Product and Design to turn understanding into action. Like most of design, there is some learning via “apprenticeship” or doing and it’s definitely not something you can master just by reading about.</p><p><strong>AH: </strong><em>Very good. Second, for those not lucky enough to have a Mike Oren and team at their company, what advice would you give them to make sure they’re doing their due diligence for research?</em></p><p><strong>MO:</strong> The most common mistakes I see designers without a research team making are focusing on the discovery work — this is often seen as the “sexy” type of research, but it’s also the most prone to misinterpretation of data and/or failing to bring value to the business (lots of politics in that space); not doing usability testing (less sexy but the best way to find out if your design is working and easiest to start showing the value of research); and only reporting verbatims (user quotes) vs. the WHY that drives the behavior.</p><p>Even when establishing new research teams, the standard operating model is to always make the first initiative a usability test of some type because it’s always actionable and the results are always measurable to show the impact (and value) of research so designers working solo shouldn’t fall so in love with their designs that they skip this vital step to learn how their design could work even better for other humans.</p><p>🗒🕵️‍♀️ — <em>It’s been awesome working with Mike and the research team here at Klaviyo. Good research is an amazing secret sauce to creating world-class prouducts!</em></p><p>Does working with or being a mixed-methods researcher sound fun? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=491ecc4040d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-491ecc4040d5">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-7fb0fc17728f?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fb0fc17728f</guid>
            <category><![CDATA[ux-interview]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Thu, 16 Jun 2022 12:33:10 GMT</pubDate>
            <atom:updated>2022-06-16T12:33:10.111Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Design Recruiting with Caitlin Beausoleil</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iU0OF5JPWpM9G05Su-47xg.jpeg" /></figure><p><strong>AH: </strong><em>Let’s start with having you introduce yourself. How long have you been a design recruiter? And how long have you been at Klaviyo?</em></p><p><strong>CB: </strong>Hello, I’m Caitlin. I have been a Klaviyo since July of 2021 and that’s also as long as I’ve been a design recruiter! Before Klaviyo I was at a different startup recruiting across the gamut of some technical roles and a lot of non-tech roles, but I became solely dedicated to design when I came here.</p><p><strong>AH: </strong><em>So you’ve done everything and now you have a specific role with a specific group. What does the recruiting team look like here at Klaviyo and then particularly for design?</em></p><p><strong>CB: </strong>For the Talent Acquisition team as a whole, I think there’s around 35 of us across both the US as well as in London. Broken down into just the design team, it’s myself and Jolene Adler, who’s the most fabulous human in the world. But it’s just the two of us — you could say we’re a mighty team of two supporting the design team!</p><p><strong>AH: </strong><em>What’s different about having a specified team that you’re recruiting for versus recruiting for everything?</em></p><p><strong>CB: </strong>It’s definitely different. When you’re recruiting for a lot of different teams in different parts of the business, you still have to get to know your managers and stakeholders. But what’s been really nice with Klaviyo and the design org is I feel like I don’t just know the managers well, but I also get to know the people on the teams too. We go to the design all hands meetings and other internal meetings, we’re on the team slack channel. We’re really integrated and get a really good view into what it’s like to be a designer here and can actually have a lot more of that firsthand knowledge and anecdotes of what goes on. We’re in different groups — like there’s the UX ladies group, and we’re a part of that. There’s just a lot more depth.</p><p><strong>AH:</strong> <em>Totally — you have less that you have to know across multiple teams so you have more depth in your area and get to know people a lot better. That’s cool.</em></p><p><strong>CB:</strong> Exactly, like I would have never known there’s so many people who love pottery on this team.</p><p><strong>AH: </strong><em>The important things you learn when you have the ability to go deep!</em></p><p><strong>CB: </strong>There are also like seven people who saw Dr. Strange on opening weekend.</p><p><strong>AH: </strong><em>These are the things you need to know! [Laughs]</em> <em>All right. What does a typical day or week look like in the life of Caitlin the designer recruiter?</em></p><p>[Caitlin’s dog Brooks decides he wants to be part of the interview &amp; paws her]</p><p><strong>CB: </strong>Hanging out with my dog? Here it is. If you just want to screenshot this and put this as the answer. Just kidding. <em>[Except Ally did screenshot it — see below!]</em> A typical day or a week… They’re all very different. We have our set meetings and check-ins with stakeholders throughout the week, but just depending on when interviews are happening, or when they’re booked it ebbs and flows and goes up and down. Fridays are usually always busy because we’re trying to wrap up a lot of things, whether it’s offers or interviews or closing things up with candidates before the weekend. Then throughout the week there’s slacks and email — slacks to hiring managers and teams, emails with candidates. We spent a lot of time sourcing and doing a lot of outreach to candidates, going through resumes, applications, portfolios, getting things scheduled. It’s like being a project manager… of a lot of different people at once!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GtR2ZxkzNXyj0_mW" /></figure><p><strong>AH: </strong><em>You were talking about coordinating with stakeholders. How do you collaborate with the managers, design leadership as well as the designers who are helping do the interviews?</em></p><p><strong>CB:</strong>In a remote world, as we all know, things are definitely a lot tougher. Checking in with them weekly, especially with stakeholders [is important], and even if it’s just ‘the update is no update’ or whatever is in the pipeline. It’s having a lot of open communication and staying aligned with each other as things change. I’m very lucky my stakeholders and the managers I work with are wonderful and we talk often and have built that trust. And Ally you get it, you are a stakeholder of mine and when working with you and others, I think a lot of it is showing you ‘Hey, I am your partner in all of this’. It’s also understanding how we can work together to improve on things. Like our candidate interview guides and our internal interviewing guides — that was a lift from folks in design as well as TA. Even switching up our process with new types of interviews, that had to be a group effort. I’m not the design expert, you are. You know design and I know people, so how can we then bring that together and work together? Everyone’s different and I think that’s part of it, too — just figuring out what works best for different people and adjusting yourself.</p><p><strong>AH: </strong><em>You </em><strong><em>are </em></strong><em>the people person. All of our candidates want to become friends with you. Before, after and during interview processes. So nailing it!</em></p><p><strong>CB: </strong>Honestly, truly all it is, is just being a human and treating people like humans at the end of the day. Doing interviews is tiring and changing jobs is a life-altering decision. Just treat people with kindness and respect!</p><p><strong>AH: </strong><em>That kind of dovetails into our next question — how are we making sure that our interview processes are best-in-class and that we provide candidates with an awesome experience?</em></p><p><strong>CB: </strong>I love that question. Because it is something that not only myself and Jolene and the rest of the TA team takes seriously but the design team does as well. Yes, we have a high caliber here. We’ve built a really fantastic design team, but we’re always keeping in mind that every person is different and what we needed a year ago is not the same as what we need now. Just like in design, you might create something or do something and then you iterate. You grow and you adjust. As the design team, you all are really big on a culture of feedback, which has been great because that bleeds into our interview processes as well. We have anonymous surveys that go out to candidates. We’ve even just asked candidates for feedback on their side, especially in the final interview stage. Like ‘How did you feel about this type of interview?’, ‘What did you feel went well?’, ‘What didn’t?’, ‘What feedback do you have?’ ‘How could we improve your experience?’. And we get [feedback] from our managers and interviewers too. We’re not perfect, but we’re always trying to improve. Things are different from a team of 15 to a team of 60. It’s continually iterating on these things to have a really good process. It’s listening to feedback and actually taking it to heart, and we do that here which is nice. You’ve been a part of some of those discussions — we’ve changed our interview process so much since I’ve started and it’s gone leaps and bounds and we’ll just continue to make it great! We don’t want to make it impossible for folks to come in, but we want it to be as real life as possible — like this [interview] conversation should be similar to what it’s like working at Klaviyo and vice versa. We want candidates to meet a bunch of folks they’d potentially work with and get a really good sense of what it’s like to work here, but also have a really good time in the process.</p><p><strong>AH: </strong><em>Totally. You certainly have been sitting in on design meetings — saying you’re ‘iterating’ &amp; ‘designing’ your own process.</em></p><p><strong>CB: </strong>I don’t think I ever used the word iterative until I started hanging out with you people! [laughs]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2GpIuqHRyP2laOJ_pQ4vw.jpeg" /><figcaption>Example of an old interview improvement brainstorm</figcaption></figure><p><strong>AH: </strong><em>Speaking of, what are some of the things that you enjoy the most about working with designers all the time?</em></p><p><strong>CB: </strong>Oh, the people. I truly adore this team. I say this to all of my candidates — that I hands-down adore this team. I’ve never worked with a group who’s so authentic, genuinely kind and wants to be better for themselves and for each other and for the company. It’s a really fantastic group — I love it. Anytime I’ve been like, ‘Hey, I think we could work on this or improve something’, everyone’s like ‘Okay, great. Then let’s be better.’ It all goes back to that mentality of feedback and improving.</p><p><strong>AH: </strong><em>Aw, all the designers will appreciate reading that! Alright, switching over to the candidates. What are you looking for in design candidates at Klaviyo?</em></p><p><strong>CB: </strong>What do we look for in candidates? People who line up with our company values that’s always the big one.</p><ul><li><strong>Always put the customer first</strong></li><li><strong>Strive to make the world more equitable</strong></li><li><strong>Are ambitious</strong></li><li><strong>Are always learning</strong></li><li><strong>Collaborate radically</strong></li><li><strong>Are remarkable</strong></li></ul><p>In my conversations, that’s what’s important — that candidates align with those values to make sure that they will be a good addition to the team. Having the same mentality of people who like to learn and grow and collaborate. That’s a huge part of being on this design team — collaborating with each other and with other teams. People who are just passionate about design and people who really love Klaviyo is always big bonus too.</p><p><strong>AH: </strong><em>We’ve also grown the team 3x in the last year alone. Talk to me about the challenges on the recruiting side when it comes to scaling an organization like that.</em></p><p><strong>CB: </strong>Previously, we would look for more generalists, and now we are looking for more specific needs because we’ve taken a step back and looked at the team and said ‘okay, we have fantastic people with these different skills. But now in this group, we could use someone who’s really good at this or that’, for example, data visualization. Now we know we can hone in on candidates with that [skillset] because it will complement everyone else. So as we scaled, it was a matter of taking that step back and really looking hard at the team and asking ‘What do we need now? Where do we see ourselves six months or a year from now?’ Making sure that we’re opening the right roles and finding the right profiles of who we’re going to need, and then making sure that it’s communicated to the managers, teams and between recruiters.</p><p><strong>AH:</strong><em> For sure, it levels up the entire team to bring in people who have specific skills.</em></p><p><strong>CB:</strong> Yes and then when people come in, we see how things play out because they may have a skill you didn’t even realize! They could be kick-ass at something else too, which just changes the [future] needs of the team, which is great. That’s the part of growing — always reevaluating and seeing where we’re at and what we need next.</p><p><strong>AH: </strong><em>Yeah, constantly changing and reevaluating. All right, my last question, is any piece of advice for designers out there who are starting the interview process, whether that’s at Klaviyo or somewhere else and they’re starting to talk to recruiters like yourself?</em></p><p><strong>CB:</strong> Always do some research on the company. You don’t have to do hours of research ahead of a recruiter phone call, but at least get a good idea of [the company] and why you want to work there. That’s what we really want to look for, do our values line up with what you’re looking for? Does the role? Does the product? Is this something you’re going to be passionate about? Regardless whether it’s Klaviyo or elsewhere, you should always do that ahead of those calls. And just be yourself. Genuinely don’t answer questions based on what you think a recruiter wants to hear. Answer based on yourself because that will help you find the right fit — the company, the team — because they might have something opening up a month or two from now that’s actually a much better fit, that you would enjoy a lot more, but if you answer how you think they want you to, you might miss out on something that could actually be even better for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fb0fc17728f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-7fb0fc17728f">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-e4cc7c14488f?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4cc7c14488f</guid>
            <category><![CDATA[behind-the-pixels]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Mon, 23 May 2022 12:46:58 GMT</pubDate>
            <atom:updated>2022-05-23T12:46:58.129Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: The Benefits of Mentorship with Diana Reed</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQ7pqLBFlsTlhLqmQMabyg.jpeg" /></figure><p><strong>AH: </strong><em>All right, Diana, why don’t we start by having you introduce yourself. How long have you been a designer and then how long have you been at Klaviyo?</em></p><p><strong>DR: </strong>I had to do the math. I went to school for design but I majored in graphic design — it was print at the time. I worked during college and so I’m gonna say almost 20 years if I’m honest, but since I graduated college, probably more like 15.</p><p><strong>AH:</strong> <em>Been designing almost since you were born! And how long at Klaviyo?</em></p><p><strong>DR:</strong> I’ve been a Klaviyo for three months. I just passed my 90 day mark.</p><p><strong>AH: </strong><em>It definitely feels like you’ve been here longer than three months. That’s really crazy. And you’ve been mentoring others for a long time now. Can you give us a little bit of detail as to how you first got involved in design mentorship?</em></p><p><strong>DR: </strong>It started with people mentoring me. I’ve been able to find somebody at every role that I’ve held that was willing to be a mentor, whether it was formally or informally. As I grew in my career, I started to pay it forward and mentor those who were less senior than me and proceeded to be a part of a couple of pilot programs. Recently, I signed up in September 2021 with ADPList, and I’ve been mentoring on that platform since.</p><p><strong>AH: </strong><em>That’s awesome. And maybe for those of us who aren’t super familiar, what’s the difference between leadership and mentorship?</em></p><p><strong>DR: </strong>The way I think about it is like steering a ship. You’ve got folks who are collectively bringing the group together and influencing, which I consider leaders. Then you have individuals who are experts in a particular skill set and teaching others how to improve. For example, tying knots for sails or navigating the ship or being the lookout on a ship - to me that’s mentorship. I know some people think about leadership as management. I don’t think that way because I consider myself to have been a design leader for a pretty long time and this is the first role where I’ve held a manager position. I think what it comes down to is to be a leader, you just need to influence the group and bring the group together. Whereas when you’re a mentor, it’s more focused — it can be focused on a perspective or skill sets or anything that helps someone improve and grow.</p><p><strong>AH: </strong><em>I like that analogy. Mentorship can be much more specific and less about driving a big group. Do you think that mentorship is key for career development, why or why not?</em></p><p><strong>DR: </strong>It certainly helped me. I want to say I’ve been trying to be a manager off and on for about eight years, and got really serious about it four years ago. Last year, I came out of a performance review and it was a great performance review, but unfortunately, there were no comments about me moving in the direction of management even though I had communicated to my manager that I wanted to. So part of my journey into management was looking for opportunities for me to grow my skill set and I knew one of those ways was through mentorship. That’s why I signed up for ADPList and started mentoring others on the platform. Between ADPList, and a couple other opportunities, doors started to open for me and showed others what I could do. The best part was showing that I could take the initiative to do it myself rather than wait and hope someone would hand me the opportunity.</p><p><strong>AH: </strong><em>That’s really interesting and I feel like that happens a lot.</em></p><p><strong>DR: </strong>It does and not a lot of people talk about it, which bothers me because all the stories we hear are like, “You’re a great individual contributor, you should be a manager.” But the reality is more stories like mine are happening and nobody’s been sharing them, so I’ve been on a mission.</p><p><strong>AH: </strong><em>I love it. Maybe I should do something similar! What are some of the most common questions that you get as a mentor and, if you’re willing to share, some common answers that you give?</em></p><p><strong>DR: </strong>I get a lot of individuals signing up asking me to look at their portfolio because they’re breaking into the industry. They’re either coming out of school, bootcamps or a grad program, and they just need some perspective. I give a ton of specific feedback around their work, but I also try to help them see a bigger picture and how to approach the portfolio. It’s not necessarily about throwing everything in the kitchen sink into your portfolio, but the goal of the portfolio is to get the interview, the goal of the interview is to get the job, and how can you create this ecosystem throughout the entire interviewing experience to communicate that. Especially for younger designers, it’s useful because they’re showing the same project over and over and allows them to show that 10,000 foot view in the portfolio case study and then when they’re in the interview panel, they can act like they’re taking the individual along with them at the hip. I call it the ‘boots on the ground’ view. It allows them to be selective about what they want. It’s all about marketing — you’ve got to figure out how to market yourself and cater to your audience.</p><p>Outside of portfolios, I think the other question I get is around my experience. I’ve been able to bounce from midsize companies, to startups, to consulting, to larger companies. And now I’m at Klaviyo which feels kind of like a midsize startup. Folks are curious as to how I’ve been able to do that and not just stay in one industry. What I tell them is that it’s really about the problems I’m interested in solving and not necessarily the work that I’m doing. If I’m interested in a problem and I gravitate to that role.</p><p>Then lastly, at least as of late because it’s been coming out a little bit about me being a parent and that in order to have my son, I went through IVF. Some people are personally interested in how I’m able to do the things that I’m doing, going through IVF, being a parent, and navigating my career. I will say it’s hard but I’m lucky that I have a great partner. We divide and conquer. There are times when I have to focus on work and he kind of takes the brunt of it and vice versa. It really is a team effort and takes both of us to make this work.</p><p><strong>AH: </strong><em>I can only imagine. And that’s actually a perfect transition into the next question as there’s been a big focus around keeping women in the workforce but there’s often so much to balance and it’s not easy. So women in tech, big opportunity space, and as you just described you’re in a great position to help as a woman who’s been through all this and now is in design leadership — how are you helping address this need and helping other women?</em></p><p><strong>DR: </strong>I show up. I’m not shy about my opinion, which I feel is an amiable quality. I’m also an introvert and it can be hard for me to speak up, but I’ve learned that constructive criticism actually goes further than anything. The other half is, and there are times where I struggle with this, but I really try not to make it about gender. Part of it is because I don’t want I don’t want to constantly sit in a position and think ‘are they talking to me about this because I’m a female, or are they talking to me about this because I’m a leader and have an equal seat at the table?’ If I start to think about it, in the former, it tends to be a slippery slope — it becomes really toxic. It’s not to say that there haven’t been instances where I’ve been discriminated against because I’m a woman. It has happened for me in the past and it’s unfortunate. I’ve used these moments as an opportunity to have a healthy discussion and give constructive feedback. I try not to make it about me or my situation, but rather focusing on whatever problems need to be solved. The other half of this, which I learned early in my career, is bringing my whole self to work. I think about all the hats I wear — being a designer, being a product manager sometimes, being someone’s coach, being a mom, being a spouse, being a friend — it’s a lot of hats to wear, and hats that interchange throughout the day. In order for me to be myself and wear these hats successfully, I have made it a point to seek out companies that align with me and allow me to bring my authentic self. That was part of the reason why I was interested in Klaviyo. Everybody I met was kind and smart, but they were also authentic, and I felt that there was a space for me here to be my authentic self, which I very much appreciate.</p><p><strong>AH: </strong><em>Yeah, for sure. Something I certainly appreciate and why I’ve stayed as long as I have as well.</em></p><p><strong>DR: </strong>Remind me, how long have you been here?</p><p><strong>AH: </strong><em>It was four years in January. So I guess we’re approaching four and a half. Really wild. Some days it feels that long and other days it feels shorter but depends on the day. [Laughs]</em></p><p><strong>DR: </strong>I always try to estimate at companies if I can see myself there for a long time. I usually take the job if I can see myself here for a long time, but the last time I was at a job this long was at a startup eight years ago.</p><p><strong>AH: </strong><em>And with a startup half of that time is just getting things off the ground! Now switching back to Klaviyo, we’re starting to work on a more formal mentorship program here. Can you tell us why that’s important and how we’re helping our designers within the company in this way?</em></p><p><strong>DR: </strong>As a designer, you’re constantly wanting to learn things and if you stop learning, you’re doing yourself a huge disservice. Mentorship is a great opportunity for folks to learn from others, whether it be a skill set, or just gaining perspectives on how to advance yourself in your career, which you need to get to the next level. You can do it on your own — and I actually am a firm believer in having and finding mentors outside of your company or workforce because I think it’ll give you a different perspective — but I also think it’s great to have a mentorship program like what we have a Klaviyo because it allows everybody to level up collectively. You’ve got folks that are coming in and wanting to learn something new like prototyping and you’ve got individuals who are experts in this and they can come in and help those individuals. You’ve also got folks asking what it’s like to be a manager versus a lead IC. Those individuals can gain perspective and figure out what their career path should be. When you’re working together and learning about others, you build stronger relationships, which can create empathy for others and their situation within the workplace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPAa8j2l6IsTQHReqaAePA.jpeg" /></figure><p><strong>AH: </strong><em>That’s so true… What’s the first thing you tell a mentee or maybe one thing you’d want a mentee to take away from your session with them?</em></p><p><strong>DR: </strong>When I’m working with a mentee, my number one goal is to ensure that they feel heard in whatever situation that they are bringing to me. In doing what I do, I want to create a safe space for that individual to come and talk about anything on their mind. I give them perspective, but I also know that sometimes they’re not going to take my perspective and that’s totally okay. Whatever ends up happening, I’m just providing them information to make a decision one way or another, or improve a skill set one way or another and give them tools to do that. And whatever decision they make after that I support 100%.</p><p><strong>AH: </strong><em>Listening, it’s one of those underrated things these days because a lot of people like to talk.</em></p><p><strong>DR: </strong>Yeah, one of the books that I read early in my career was <a href="https://rosenfeldmedia.com/books/storytelling-for-user-experience/">Storytelling for the User Experience</a>. They have this key line in there about listening to others, and they were talking about it more in terms of the discovery process and aligning with stakeholders. Once I read it, my reaction was, ‘No, this is what you need to do with <em>people</em>.’ I’ve ingrained that quote into my life and my philosophy!</p><p><strong>AH: </strong><em>It’s so true. And I mean, in our industry, it’s huge — it’s the whole point.</em></p><p><strong>DR: </strong>Yeah, it’s part of our job to listen.</p><p><strong>AH: </strong><em>All right now on to our advice questions. If there was one thing you could tell every mentee that you have, what would that advice be?</em></p><p><strong>DR: </strong>Similar to the last one, give yourself some grace and some empathy. We’re hard on ourselves as designers, myself included — I’m highly critical — and creating space for yourself in the situation will pay dividends for you. I learned that the hard way with management. I’ve been trying to jump into that for such a long time and I wanted it to come instantaneously, but to be honest, it came at the right time because of the fact that I gave myself the grace to do it and live my life how I need to. Could I have done it earlier? Probably, but I wouldn’t enjoy it as much as I enjoy it right now.</p><p><strong>AH: </strong><em>Very valid. All right, now for designers out there looking to get involved in mentorship, either as a mentor or as a mentee, what advice would you give them on getting started?</em></p><p><strong>DR: </strong>I’d say just rip the band aid off and do it. The sooner you get involved in it, the sooner you’ll learn from it. For people who want to become mentors, usually there’s trepidation around the fact that they may not have enough experience, but you have perspective, you have experience, and that experience will be valued by somebody else. You just need to find that person who resonates with you and create that relationship. For mentees, it’s the spirit of you never stop learning and so this is just a tool to learn from others. Instead of learning by reading, you’re learning by talking to others. I’ve learned so much both as a mentee and a mentor — I’ve actually learned more from the people I mentor lately than I have in other situations because they’re bringing these different, unique perspectives and I have to think about it but I also have to hold empathy for the fact that they’re there in that situation. I feel like it’s made me a better manager because of it.</p><p><strong>AH: </strong><em>Love it. And you’re on ADPList. Would you recommend ADPList? Any other places people can go to?</em></p><p><strong>DR:</strong> I’m not aware of any other platforms outside of ADPList. I do love ADPList because I think it really provides a platform for connecting. I’m connecting with individuals worldwide, whereas beforehand I was only connecting with individuals that I worked with. Both are great, but I think I’m getting a better perspective and starting to question some parts of the design process because I’ve encountered different people with different perspectives. I don’t think I would have had that in any other situation.</p><p>🗣👂 — <em>It’s awesome to see mentorship taking shape here at Klaviyo and in the general design landscape. Didn’t get enough? </em><a href="https://adplist.org/mentors/diana-reed"><em>Continue the conversation with Diana on ADPList</em></a></p><p>Does bringing your authentic self to work resonate with you? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4cc7c14488f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-e4cc7c14488f">Behind the Pixels</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>
        <item>
            <title><![CDATA[Behind the Pixels]]></title>
            <link>https://medium.com/klaviyo-design/behind-the-pixels-edec6256bb51?source=rss-5d00b446dec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/edec6256bb51</guid>
            <category><![CDATA[ux-careers]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[behind-the-pixels]]></category>
            <dc:creator><![CDATA[Ally Hangartner]]></dc:creator>
            <pubDate>Wed, 11 May 2022 12:51:53 GMT</pubDate>
            <atom:updated>2022-05-12T09:16:05.693Z</atom:updated>
            <content:encoded><![CDATA[<h3>BTP: Designing as a Lead Individual Contributer with Zach Robinson</h3><h4>Behind the Pixels is a conversational blog series that aims to give a glimpse into the work &amp; life of being a designer at Klaviyo</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7f6x8kPfrbTvgPqizWSSHA.jpeg" /></figure><p><strong>AH:</strong> <em>So to start off, why don’t you introduce yourself and then tell us how long you’ve been a designer and how long you’ve been at Klaviyo?</em></p><p><strong>ZR:</strong> I’m Zack Robinson and I’m a lead product designer at Klavivo. I’ve been designing ever since I graduated college, and I was in the startup space for a long time before I transitioned to working at Klaviyo. So I was [in that space] since 2010 working with early stage startups, mostly out west in the San Francisco Bay Area. And then I also worked with a couple companies in Boston — worked at the Twitter office in Cambridge, which was an acquisition of a company called Crashlytics — and then after that I worked as a founding team member of a startup in Boston called Drafted for about four to five years. Then transitioned to working at Klayivo after that. So I’ve been at Klaviyo for about a year now.</p><p><strong>AH: </strong><em>Okay, cool. And you are one of our first lead ICs (individual contributors) we’ve had on the team here and now you and our other lead, Alex, are helping craft what this role is going to look like going forward. Can you tell us a little bit about what a lead IC role entails?</em></p><p><strong>ZR: </strong>Well, the main thing for the lead ICs is being able to work with other designers on the team on some of the harder, more strategic projects that we have here at Klaviyo. Another part is allowing designers as they level up and grow to be able to have that pathway so that they can continue to be an individual contributor for their team without going into management. Still working across pillars, across product management and engineering, but without having the responsibilities of management and still being able to execute on design and be a leader for either their pod or their pillar by executing at a high level while mentoring and leveling up their team as well.</p><p><strong>AH: </strong><em>And when you first started at Klaviyo and some of your other historic roles, you were managing a team. What made you make the decision to go back to an individual contributor role?</em></p><p><strong>ZR:</strong> I really enjoyed the team I was managing, but I think part of it is knowing where you can help out the company and the team the most and looking at what you might be exceptional at. I think for me I am probably a better designer than I am a manager and I think being able to be a lead designer will help me work with many other designers on our team and also work on some of the projects that might cross our different pillars of the organization that are very important to Klaviyo this year and next year. I think the choice was pretty simple because I have been a designer my entire career essentially, even when I was at my startup, so that is kind of like my bread and butter. And so the transition was pretty easy and the decision was pretty easy because it’s really about looking at and knowing where you can provide that significant value to the company and the team.</p><p><strong>AH: </strong><em>Sounds like a natural fit. You started to talk a little bit about some of high-level strategy projects. Can you elaborate on that and talk us through the types of projects a lead designer might take on?</em></p><p><strong>ZR: </strong>Yeah, for some parts of the projects, it’s about where you can provide significant help to a team, like when I was helping out the design systems team. But then part of it too is being able to look at the complete customer journey, the end to end workflow, in some of these important areas of our app right now. As a lead designer, you should be able to have a full understanding of every part along the way whereas certain pods might be handling certain sections of [that] user flow. And they might be working on that in coordination with other pods, but hopefully, a lead is able to look at the whole thing holistically and make sure that it’s going in the right direction. I think that’s part of what I’ll be working on for Klaviyo in this coming year — taking a look at some of the most important workflows that we have for our customer and their journey and making sure that it’s a more unified experience along that workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kcpIWeNQSt83UXgq_6V0ig.gif" /></figure><p><strong>AH: </strong><em>Connecting some of the bigger dots across the platform. Would you say this role has to take into account business strategy more so than other design roles?</em></p><p><strong>ZR: </strong>Yeah, I think you know, my background is actually in entrepreneurship. And when you work for very early stage startups, you do many things beyond designing. I do think part of it which is very important for the lead designer is knowing not only some of the business decisions, where the company wants to go and the technical limitations of what we can build, but really kind of planning out a pathway for where the company <em>can</em> go. In the next year, for instance, where we could be in just a couple of months, but then also what can we do starting tomorrow? And I think in thinking about the entire product lifecycle, in terms of how it could be developed from where we want to go to where we are now, is very important and you do need to consider some of the business implications — what’s important to work on now to meet some of the business goals, what are some of the engineering limitations in terms of like resourcing and then obviously, what can provide the biggest impact for the customer. So, yeah, you do need to think about several different things simultaneously and that’s typically how I handle it.</p><p><strong>AH: </strong><em>Nice. So what would a typical day or week look like? I know you said there’s no management, but you’re still coordinating with folks.</em></p><p><strong>ZR: </strong>For me, the coordination meetings are typically in the moment. I do sometimes have a typical stand up with the individuals who I might be working with. It could be someone in product management or an engineer or another designer. But typically, the communication and collaboration is always there. And so it’s more like you’re, and I know we’re all remote right now, but more like you’re in the office and working side by side with someone on something. Being able to ask them a quick question or get some feedback on something in more of an ad-hoc way. That’s typically the type of collaboration that I have with the individuals I work with and so it’s not as formalized in terms of having coordinated meetings all the time, but more just continual design collaboration throughout the week beyond just the typical meetings that you might have as a lead designer with other leads across the design org and other other pillars. So for the most part, I’m working with someone or a couple of people together, especially when they’re in different roles. It’s definitely an all-the-time collaboration effort, I would say.</p><p><strong>AH: </strong><em>And how much time would you say you are spending doing deep design work?</em></p><p><strong>ZR: </strong>I would say I do deep design work, honestly, probably like 70 to 80% of my time. I’m not someone that multitasks a bunch of projects, honestly. So I need to go deep and just work for several hours on end. It’s not something where I can work for 15 minutes and then join a meeting and then work for 15 more minutes and then join another meeting — I really need that extended focus time for me to go through [the work]. During that time, like I said, I will be chatting with other people getting feedback and asking questions along the way, but I consider that to be part of the deep focus of actually designing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YOuqkImAaHvrZJ-0u63vXw.gif" /></figure><p><strong>AH: </strong><em>Gives you a depth of focus that you don’t get when you have to break up your day. So then what about coordination with other leads, either ICs or the people managers — how does this role interact with those other team members?</em></p><p><strong>ZR: </strong>Ideally you have a design lead associated with each pillar. And I think having that type of open communication probably like a weekly meeting would be the most appropriate — meeting with the engineering lead, the people manager lead for design, the product manager, lead for the pillar as well — to have that type of coordination. So, I think that’s an ideal ratio where it’d be about one lead per pillar. And right now, since we are still growing out our design lead roles here at Klaviyo, we’re working with multiple pillars, which is totally appropriate for right now. And since we’re growing so quickly, I think as we start to expand out the senior design leadership a little bit more, I think associating one person per pillar would make the most sense because then you always have that continual context, not just with the people managers but also with the design team there. Then you can be held responsible for leveling up the quality and the craft and the mentorship and being in touch with the senior designers in that pillar. So I think that’s important to creating the relationships.</p><p><strong>AH: </strong><em>In general, I think it’s pretty awesome that we’re building out both these tracks for managers and ICs. You’ve done both in your career and seen different levels of companies. Why do you think it’s important for companies to have both tracks for designers to grow into?</em></p><p><strong>ZR: </strong>I think especially if you have designers that are exceptional at doing the design work, it would make sense that they would continue to do that. You see this track for engineering. And not always having management be the path that every person needs to step into, especially when it’s not for everyone. But if you also think about it from a company standpoint, you probably want the people who are like best at what they do to continue to do that work. So if you really do have exceptional talent at design, on the individual level, it would make sense that they will still be able to continue executing on that for the company. So yeah, I think the two tracks are very important and I think you see that for engineering, and now we’re starting to see that for design too.</p><p><strong>AH: </strong><em>It’s true, if the people want to keep working as an individual contributor, it makes sense that they have the opportunity to do that at a high level. So thinking into the future, what are you the most excited about for developing and working in this new role?</em></p><p><strong>ZR: </strong>This will be a big year for Klaviyo. One of our more recent product offerings is definitely in the SMS space and one of the things that definitely excites me is growing out that product offering to our customers and really making [it] an exceptional experience. Because Klaviyo is very much known for email and isn’t really as known for our SMS [offering] and I think by the end of the year having an SMS experience that is just as exceptional as our email experience for our customers will be a huge addition to our experience. And that’s what I’m really excited to build out, because I think it could be a huge, huge market for us, but also it’ll be a huge win for our customers to be able to execute in the SMS marketing space as well.</p><p><strong>AH: </strong><em>We’ll hold you to it and check in at the end of the year. All right, final question — what is your advice for designers out there who are trying to determine whether they want to pursue a lead IC role or go into management?</em></p><p><strong>ZR:</strong> Well, I think the important thing is, ideally, a manager isn’t really doing design work. And are you going to be okay, not really doing design work as you step up and choose a different career path. So I think that’s one thing to think about, but also, you can try out management and since they are parallel tracks, it is okay. Assuming you’re ready to go from design to management, if it’s not a fit, it’s okay to then switch back to being on the IC track as well. It’s not something where you have to make a single choice in the moment in time and then you can never go back. In the meantime you can see lead designers going into management as well later on in their career too. And so, I think it’s okay to try it out if it makes sense for you and for your manager. But then also try to take a look at what you think would make you the most happy and where you think your skills align the best. If you are an exceptional designer, and you love designing, it’s okay to continue with the IC track because they are parallel paths.</p><p>👨‍🎨📑 — <em>Zach and Alex are helping establish what will hopefully be an awesome career option for our designers. Can’t wait to see folks on our talented team grow into this role!</em></p><p>Does being a lead IC at Klaviyo sound like your next role? We’re always looking for great people to <a href="https://www.klaviyo.com/about#careers">join our team</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edec6256bb51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/klaviyo-design/behind-the-pixels-edec6256bb51">Behind the Pixels</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>