<?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 Christina Holsberry Janzer on Medium]]></title>
        <description><![CDATA[Stories by Christina Holsberry Janzer on Medium]]></description>
        <link>https://medium.com/@christinaholsberryjanzer?source=rss-8249f01a8300------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*O2QnKcU8pAMB8w74.jpg</url>
            <title>Stories by Christina Holsberry Janzer on Medium</title>
            <link>https://medium.com/@christinaholsberryjanzer?source=rss-8249f01a8300------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:24:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@christinaholsberryjanzer/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[How Slack blends productivity and delight]]></title>
            <link>https://medium.com/slack-design/how-slack-blends-productivity-and-delight-4e7c4a35d4fe?source=rss-8249f01a8300------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e7c4a35d4fe</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Christina Holsberry Janzer]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 17:31:51 GMT</pubDate>
            <atom:updated>2017-11-30T17:31:51.062Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6dPPV8kz8Lt3-TCPhexBXw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/kyCNGGKCvyw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">chuttersnap</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>At Slack, we’re committed to making people’s working lives simpler, more pleasant, and more productive.</p><p>It’s safe to say most enterprise tools aim to improve productivity. That’s often the goal and the promise of shiny new enterprise products. When you think about work software, you often think about what those tools enable you to do, such as manage information, store data, track issues, share updates, and whatever else you need to do to get your job done. These are the things and tasks that ultimately enable you to be more productive and better at your job.</p><p>Social products serve a different purpose but in similar ways — they might help us manage people and events, store memories, track current affairs, update your family and friends, and whatever else you need to do to feel connected to loved ones. With that said, one main difference between enterprise and social products is that the former is usually something you’re required to use, while the latter competes for your time by providing a functional <em>and</em> delightful experience.</p><p>We conducted a survey to explore the words that people currently use to describe work tools. The words that came to mind most frequently for survey responders were “professional,” “clean” and “efficient,” while words like “pleasant” were less common.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*vmFLs09Wyqvs9yy5CyPmHg.png" /><figcaption><strong>Words survey responders used to describe work tools</strong></figcaption></figure><p>When you compare with the same question asked of the same people but of consumer products, you see something different:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIfaPrNS5WuPHHWzn7MF_g.png" /><figcaption><strong>Words survey responders used to describe social products</strong></figcaption></figure><p>Words like “fun,” “engaging,” and “enjoyable” are now more prominent.</p><p>There are inherent differences between enterprise tools and consumer products; while enterprise products promise to foster productivity, consumer products aim to delight. But we think bringing more delight into work tools can go a long way in not only building a product that you choose to use and that delights you, but also one that will increase your productivity.</p><p>I’m going to share some principles we think about at Slack and how we take a lot of cues from consumer products. This, in turn, inspires us to build a product that makes people’s working lives simpler, more pleasant, and more productive.</p><h3><strong>Principle 1: Put people, not features, first.</strong></h3><p>We’ve heard this before. Human-centered design isn’t exactly a new concept. But for enterprise tools where the goal is to foster productivity, it’s easy to get wrapped up in the features the tool provides, without thinking deeply about the experiences it enables.</p><p>Listening to your customers is step one, and building a direct line of communication between you and your customers is a must. But simply responding to feature requests isn’t enough — it can sometimes lead to unsolved problems and unmet needs. To solve the real problems people face, we need to first observe and understand their workflows and daily challenges.</p><p>One of my favorite consumer stories to illustrate this point is from Netflix. They shared some <a href="https://www.wired.com/2013/08/qq_netflix-algorithm/">really fascinating research</a> about the work that’s gone into perfecting their recommendation engine. They discovered that the ratings people give are aspirational rather than reflecting of daily activity: many people tell them they often watch foreign movies or documentaries, but in practice that doesn’t happen very much.</p><p>While this isn’t about work, I think the idea translates well. Asking people <strong>what</strong> they want is important, but it doesn’t necessarily tell the whole story. This is why it’s also important to <strong>observe</strong> what they do.</p><p>At Slack we think about this all the time. We’re lucky to have a really strong line of communication with our customers. They tweet at us and write in to us, and our stellar Customer Experience team takes pride in addressing and acknowledging everyone who reaches out. We take each inquiry and request seriously. What makes user research different is that we look beyond what people ask for and we collect data to understand what’s underlying that request.</p><p>For example, we found that people wanted a way to easily integrate with Google Docs. When you think about building a feature to address that request, it’s quite straightforward, technical challenges aside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*puCiyYatdZdsrM_U." /></figure><p>As you can see in the picture, enabling people to share docs in Slack didn’t completely solve the problem. People were sharing docs and forgetting to open up permissions, which prevented collaboration from the start. We gave people what they asked for, but their underlying need wasn’t met.</p><p>After we took into account their need to share docs <em>in order to provide feedback and share comments, </em>we were able to anticipate potential problems before they occurred. That additional understanding inspired us to train Slackbot to intervene — after noticing the file isn’t viewable to the person it was just shared with, Slackbot prompts you to fix it inline, before it actually becomes a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*21SB9H13erNPxjhYUOR7zw.gif" /></figure><p>Putting people first doesn’t just mean checking off each feature request that comes in. It means taking the time to understand the need behind each request, in order to build more pleasant solutions.</p><h3><strong>Principle 2: Bring humanity into the product.</strong></h3><p>One of the top concerns we hear is the worry that tools are impersonal and that written communication will be misinterpreted. In fact, in a recent study we ran of 3000+ office workers from different industries in the US, one out of every four people were concerned that written communication would lead to miscommunication. In the same study, 60% of the participants expressed their preference for in-person communication above email, phone, and video.</p><p>When you talk to people about this, it makes sense. As companies have become more distributed and people have started using more tools, we’ve lost some of the ability and opportunity to pick up on human cues, such as body language and physical presence. For example, if your entire company worked in the same room together, you’d know if someone was out of town because you wouldn’t see them at the office all week. You might also know if someone was having a bad day, because you’d see it in their face or hear it in their voice. If someone was on the phone or in a meeting room, you likely wouldn’t try to start a conversation with them at that moment.</p><p>These cues might seem obvious, but they are strong signals that are often lost when you move from working in the same physical space to working through a virtual tool. We spend a lot of time thinking about how we can build these human cues and connections into our product, and there’s much we can learn from social products, too. Here are some examples:</p><p><strong><em>Emotional cues</em></strong> help us understand how someone is feeling and if they’re happy or sad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/0*wJtf6B58DwcC3uDx." /></figure><p>Imagine if you told your boss you were going to be late on a deadline, and she responded with “OK.” Would it be clear to you how she felt? If she responded in person, you might rely on her intonation or a facial expression.</p><p>We can borrow from social communications here, and use emoji to help convey emotions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*zyqt9DMKR9MXNp__." /></figure><p>Imagine that her response included this emoji. It’s much clearer how she feels.</p><p>Emoji introduce color, clarity, and fun, but they also reduce ambiguity and miscommunication — which leads to increased productivity.</p><p><strong><em>Physical presence</em></strong> is also hard to detect online. So we’ve introduced the custom status feature to help people understand what you’re doing at the moment. Messaging tools can sometimes set unrealistic expectations that lead people to believe you are always on or always accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*-Wuv37JGNkD8N94J." /></figure><p>Custom status helps you set better expectations for your teammates by clearly signaling when you’re on vacation, in a meeting, or otherwise occupied.</p><p>Finally, building <strong><em>personal relationships</em></strong> is really important in establishing trust and camaraderie, and something that you often associate with happening “at the watercooler.” One way we’ve enabled this at Slack is through community channels, which give you a way to connect with coworkers around shared interests and topics. This helps you connect with people you may have never otherwise met, and gives you the opportunity to build meaningful relationships.</p><p>Understanding the underlying concerns — that written communication will be misinterpreted and tools are impersonal — has clarified for us the importance of building social cues and dynamics into our product, in order to build a more pleasant and productive experience.</p><h3><strong>Principle 3: Delight matters.</strong></h3><p>What does it mean to mix delight with work? When I talk about delight, I’m talking about delight in the actual job, in the day-to-day tasks and work that you’re doing. By making jobs easier and by removing unnecessary hurdles and steps, we are delighting people and increasing productivity at the same time. Let me give you an example to illustrate how we think about this at Slack.</p><p>Picture this: You email a file to your team and ask for feedback. Each email response could vary drastically and include any of the following (and more):</p><ul><li>People who reply-all to <em>provide a status update </em>— they got it, they are reading it, or they will read it later.</li><li>People who reply-all to <em>share their feedback.</em></li><li>People who reply just to you to <em>share their feedback.</em></li><li>People who reply to you and a couple other people to <em>share their feedback.</em></li><li>People who think others should be added to the conversation, so they <em>add more people to the email.</em></li></ul><p>In the end, you have potentially received tens (or hundreds!) of replies. But without going through each one, it’s difficult to figure out who actually provided feedback or what that feedback is. Plus, everyone included on the thread now has many emails they likely don’t need to read at all. Without looking at each one, though, it’s hard to tell if there’s something essential or not. Every person involved ends up having little control over their inbox.</p><p>We’ve seen people use Slack for the same use case — only this time people share the file in a channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F_4_O2bTwS0xNWBv." /></figure><p>People can use the “eyes emoji” to indicate they saw it and are looking at it, and they can use the “check mark emoji” to indicate they’ve looked and provided feedback. It organizes those responses together in the context of the shared file, so you can easily track each action. Other people can add someone to the channel or share the file in an additional channel, and it won’t cause additional disruption to anyone.</p><p>Using emoji in consumer products is common, where delighting users is a valued goal. With Slack, emoji bring delight, too — not just from the fun of perfectly expressing a thought or feeling, like with social tools, but also from the organization, improved process, and increased efficiency that result.</p><p>Taken together, we can see that productivity doesn’t have to come at the cost of delighting users. Rather, it’s productive because it’s delightful, and it’s delightful because it’s productive.</p><p>It’s common to hear people say that communication tools often lead to miscommunication, that chatting with someone over a messaging service is never quite as good as meeting with them face-to-face, and that sharing a document is always easier when you’re in the same room.</p><p>But work is changing. Companies are becoming more distributed and remote work is becoming more common. Not everyone has the luxury of meeting face-to-face, much less the ability to connect with remote coworkers.</p><p>We need to shift the conversation away from thinking of tools as the problem, because tools<em> have to</em> be the solution as well. Not only the solution to the obvious communication challenges we face every day as humans, but also to the not-so-obvious challenges that come with working with distributed coworkers.</p><p>I hope these principles have inspired you to think about bringing humanity and delight into the tools we use. We believe that by putting people first, bringing humanity into the product, and focusing on delight, tools have the ability to actually bring people closer together, and to make work simpler, more pleasant, more productive, and more fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e7c4a35d4fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-design/how-slack-blends-productivity-and-delight-4e7c4a35d4fe">How Slack blends productivity and delight</a> was originally published in <a href="https://medium.com/slack-design">Slack Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My running “comeback”]]></title>
            <link>https://medium.com/@christinaholsberryjanzer/my-running-comeback-2f87d48942be?source=rss-8249f01a8300------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f87d48942be</guid>
            <category><![CDATA[pimping]]></category>
            <category><![CDATA[ultramarathon]]></category>
            <category><![CDATA[motherhood]]></category>
            <category><![CDATA[running]]></category>
            <category><![CDATA[marathon]]></category>
            <dc:creator><![CDATA[Christina Holsberry Janzer]]></dc:creator>
            <pubDate>Wed, 29 Nov 2017 04:30:37 GMT</pubDate>
            <atom:updated>2017-11-29T04:30:37.006Z</atom:updated>
            <content:encoded><![CDATA[<p>A funny thing happens when you’re pregnant…or at least it does with me…</p><p>During both pregnancies, at around 8 months, the novelty of being pregnant started to wear off, and I started dreaming about and making plans for when I was no longer pregnant. A big part of it is that I was dying to meet the little human that had been cooking inside of me for the better part of a year — would they look like me or Paul?— but part of it was also <em>really </em>wanting to have my body back. Wanting to sleep on my back again. Wanting to remember what it was like to not have a big belly. Wanting to remember what my feet look like. Wanting to know what it felt like to pick up the m&amp;m I dropped on the floor without doing a crazy squat maneuver (by the way, of course it’s OK to eat the m&amp;m — it’s a known fact that the 5-second rule is tripled when you’re pregnant because it takes you much longer to do things and you’re hungry).</p><p>Anyways, when I was pregnant with Liam, I dreamt about wearing non-maternity clothes and did my fair share of online shopping; not for clothes that actually fit me, but for the body I would hopefully have back sometime soon. Pretty harmless, I think, except for the credit card bills.</p><p>When I was pregnant with Lola, apparently I dreamt about running long distances, because when I was 8 months pregnant I decided to sign up for a 50k — you know, as one does. While I was fortunate to keep up with running until the end of both pregnancies, my distances were more like 3.1 miles, not 31 miles, so it felt like a faraway dream.</p><p>8 months later, here I am, having just completed my first post-baby marathon. I want to share why this race meant so much to me; I want to remember this moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*Fqprebq3tsTZMCIGJdMLEA.jpeg" /><figcaption>Post race. Pumping.</figcaption></figure><p>Running is my jam. I love it so much. It’s my me time. My time for reflection. My time to be strong. My time to explore nature. Running is my form of self-care. When I run I am happier, more productive, and I think an overall better person. But it’s always hard to prioritize self-care, particularly when life is busy. And boy is life busy with a baby and a toddler. So part of why this race was so important to me was not just about the race itself, but about the hours of miles that went into training for the race, and the fact that I made a point to dedicate time for self-care, amidst the wonderful chaos of life.</p><p>I also wanted to prove to myself I could do it. I’m an achiever. I like taking on challenges. I like winning (no not the actual race, I’m quite slow). While I’ve run 50k and even 50 miles before, at the point I signed up for the race I hadn’t run more than 13 miles since BK (before kids), so it was an overwhelming thought, both from an endurance perspective (can my body do that anymore?) and a logistical perspective (how the hell will I find the time to train?).</p><p>Here are the lessons I learned along the way:</p><p><strong>Ask for help</strong></p><p>I did a couple runs with the double stroller, and it was clear I would quickly reach my limit; there was no way I was going to run more than 6 miles pushing my 2 little chunkers. So I needed to figure out how to ditch the kids for a few hours in order to go for my long runs. I’m bad at asking for help and bad at leaving my kids on the weekends because I feel I already have limited time with them. It’s funny because every time I do ask for help, Paul so quickly says yes, it’s as if he wants to make it even easier for me to ask in the future. And every time I leave the kids, they are fine and they don’t seem to love me any less. So thank you, Paul, for supporting me. And thank you Liam and Lola for the smiles and squeals when I return.</p><p><strong>Multi-task</strong></p><p>When I became a mom I swear my multi-tasking skills went through the roof. You quickly learn how to feed multiple people at once (alternate bite for me, bite for Liam, with Lola on boob), and how to do things that used to take your undivided attention while juggling 3 other tasks. It’s kind of a cool super power, to be honest. I reached peak multitasking abilities when I was nursing Lola and had to pee, and was able to accomplish said task without detaching her, all while managing to also wash my hands after. Not something I have done since, but in the moment it made me feel like I could handle anything.</p><p>Over the last couple months, Paul and I have been especially busy with work, finding new childcare (aka the most stressful thing ever), and designing and building a house. I also had the opportunity to speak at the first Slack conference, which meant needing to prep and memorize a 25-min talk. As I was planning a long run one weekend, I was thinking about all the other things I should be doing instead, including going up to Marin to check on our new house. So I tried to be creative about multitasking. Rather than waste 30 mins in the car driving from SF to Marin, I figured, why not run there instead! And instead of listening to music, why don’t I put my talk track on repeat to help the memorization process! I felt like a true super-hero that day when I ran up the driveway, having just accomplished so much.</p><p><strong>Done is better than perfect</strong></p><p>I think this is a pretty necessary and useful motto for parents, IMO. I said buh-bye to perfection a long time ago and only occasionally look back. In this case, I didn’t train <em>nearly </em>as much as I had for previous races. I wasn’t as prepared as I would typically like to be. But I had to be OK with that. And being slightly unprepared and doing it was way more important to me than delaying in pursuit of the perfect race.</p><p><strong>Give yourself a break</strong></p><p>You might have noticed I signed up for a 50k but only ran a marathon. The marathoners and 50kers started and finished in the same place, but there was a point at mile 15 where the 50kers had to loop back around, and the marathoners just kept going towards the finish. At that point I was hurting. I won’t get into the details about why or what the course was like, but I decided to give myself a break, skip the extra loop, and finish the marathon. I was pretty happy with my decision, and thrilled to be able to finish a marathon. I’ll do the 50k next time :)</p><p>While more challenging than any previous race I’ve done, the experience of running this race was everything I hoped for. It was the culmination of a period of self-care. It was the confidence that I could still do it. But most of all, it was 26.2 miles of uninterrupted me time. And it was bliss. Painful, painful bliss.</p><p>And now? It’s nap time. Haha JK I have kids.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f87d48942be" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>