<?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 Beth Aitman on Medium]]></title>
        <description><![CDATA[Stories by Beth Aitman on Medium]]></description>
        <link>https://medium.com/@beth.aitman?source=rss-62b893e22d34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qnH4BAVn0I2eWJ1KmPc5Tg.jpeg</url>
            <title>Stories by Beth Aitman on Medium</title>
            <link>https://medium.com/@beth.aitman?source=rss-62b893e22d34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:00:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beth.aitman/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[Make Slack a little quieter]]></title>
            <link>https://medium.com/@beth.aitman/make-slack-a-little-quieter-2645f7f71438?source=rss-62b893e22d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/2645f7f71438</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Beth Aitman]]></dc:creator>
            <pubDate>Wed, 22 May 2019 13:26:17 GMT</pubDate>
            <atom:updated>2019-05-22T13:26:17.183Z</atom:updated>
            <content:encoded><![CDATA[<p>Even if you like using Slack, it can get a bit noisy and distracting. Fortunately, there are a bunch of settings that can help make things a little quieter!</p><h3>Make notifications and unreads less distracting</h3><ul><li><strong>Slim down your sidebar,</strong> and star the channels and conversations you really care about.<br><em>Preferences &gt; Sidebar &gt; Appearance &gt; Unreads and starred conversations</em></li><li><strong>Don’t play a notification sound.</strong><br><em>Preferences &gt; Notifications &gt; Sound &amp; appearance &gt; Play a sound when receiving a notification</em></li><li><strong>Don’t show an icon when there are new things to see,</strong> so you don’t get so tempted to check it.<br><em>Preferences &gt; Notifications &gt; Sound &amp; appearance &gt; Show a badge on Slack’s icon to indicate new activity</em></li><li><strong>Turn off notifications for @channel and @here.</strong> If people tend to overuse this in a channel, you can turn it off.<br><em>Open the channel &gt; Channel settings (the cog </em>⚙️<em>) &gt; Notification preferences &gt; Ignore notifications for @channel and @here</em></li><li><strong>Leave channels you don’t care about.</strong> You can always join again.</li><li><strong>Use Do not disturb</strong> when you really need to focus.<br><em>The </em>🔔<em> bell icon in the top left</em></li><li><strong>Set your office hours.</strong> Use Do Not Disturb so you don’t get notifications when you’re not working.<br><em>Preferences &gt; Notifications &gt; Do Not Disturb &gt; Automatically disable notifications from</em></li><li><strong>Turn off notifications entirely.</strong> You’ll still see a number next to the channel name if you get mentioned. (If you do this, people won’t be able to get hold of you.) <br><em>Preferences &gt; Notifications &gt; Notify me about &gt; Nothing</em></li></ul><h3>Make it more asynchronous</h3><ul><li><strong>If there are channels you don’t need to keep up with</strong> in real time, mute the channel. This will stop it showing up as unread in the sidebar (it’ll just be grey).<br><em>Open the channel &gt; Channel settings (the cog ️️️</em>⚙️<em>) &gt; Mute #channel-name</em></li><li><strong>Care less about when someone is typing a response.</strong><br><em>Preferences &gt; Messages &amp; Media &gt; Additional options &gt; Display information about who is currently typing a message</em></li></ul><h3>Deal with unread messages better</h3><ul><li><strong>Mark channel as read</strong> using the <em>Esc</em> key.</li><li><strong>Turn on All Unreads</strong>. Look at Slack less often, and use this feature to catch up on everything at once (and quickly mark lots of stuff as read).<br><em>Preferences &gt; Sidebar &gt; Additional options &gt; Show All Unreads</em></li><li>You could also try <a href="https://slackhq.com/focus-on-the-important-things-with-highlights-in-slack-5e30024502cd">Highlights</a>.</li><li>If you leave things unread as a reminder to act on it — instead, <strong>tell Slack to remind you</strong> about it. Ideally, you can block out a bit of time to deal with a few reminders at once.<br><em>On the message: More actions menu &gt; Remind me about this &gt; pick a time.</em></li></ul><h3>Etiquette</h3><ul><li><strong>Avoid using @channel and @here</strong> unless you really need to.</li><li><strong>Rename #general to #announcements</strong>, and only use it for things that everyone needs to know. Chat can go in #random.</li><li>“All channels tend towards #random.” <strong>Try </strong><a href="https://slackhq.com/some-of-the-ways-we-use-emoji-at-slack-a21be5030815"><strong>“raccooning”</strong></a><strong> stuff</strong> that’s off topic, to keep channels focused.</li></ul><h3>Other stuff</h3><ul><li><strong>The compact theme</strong> removes avatars — our brains are drawn to faces, so removing them might make looking at Slack less compelling. Worth a shot.<br><em>Preferences &gt; Messages &amp; Media &gt; Theme</em></li><li><a href="https://slackhq.com/getting-the-most-out-of-threads-ae86797d681d"><strong>Threads</strong></a> can be good for keeping conversations in a channel more contained. Though they get a bit unwieldy if the error gets too long.</li><li><a href="https://slackhq.com/designing-and-formatting-messages-in-slack-dd71e6446124">Format your messages nicely</a> to make them easy to read.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2645f7f71438" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Information design for a Slack bot]]></title>
            <link>https://medium.com/@beth.aitman/information-design-for-a-slack-bot-5dbabda8d0cb?source=rss-62b893e22d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dbabda8d0cb</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Beth Aitman]]></dc:creator>
            <pubDate>Wed, 11 Apr 2018 12:50:14 GMT</pubDate>
            <atom:updated>2018-04-11T12:50:29.720Z</atom:updated>
            <content:encoded><![CDATA[<p>One of our developers was trying to make it easier for our colleagues, after they’ve reviewed a <a href="https://www.atlassian.com/git/tutorials/making-a-pull-request">pull request</a> (PR), to keep updated on that PR’s status. This developer was building a Slack bot to do this. I offered to help — it seemed like an interesting information design problem.</p><h3>Their initial design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*j5Awo7DO3fbhBoT4.png" /></figure><p>This isn’t ideal. It needs a legend to explain what all the symbols mean: the concepts they’re trying to communicate are not simple, and just can’t be summed up neatly by an icon. It’s also hard to get information out of this at a glance.</p><p>It turned out that our developer assumed they needed to use a table — and because they were using a table, they had to use emoji-only headers, otherwise it wouldn’t fit horizontally.</p><p>(For those not familiar with Git and GitHub: the first bit in the pull request column (eg “platform”, “everything”) is the name of the code <a href="https://t.umblr.com/redirect?z=https%3A%2F%2Fhelp.github.com%2Farticles%2Fcreate-a-repo%2F&amp;t=ODMzMTc3NmNiMjBjZjQyOTkyMDEyNTY2ZTE4NzA4NzdlMjhkYmNiYSxnQUdBNUxaSg%3D%3D&amp;b=t%3AgVvjtovQxyopfzuaqpKYLg&amp;p=http%3A%2F%2Fuiwriting.tumblr.com%2Fpost%2F172822022269%2Finformation-design-for-a-slack-bot&amp;m=1">repository</a>; the number is the ID of the pull request; and the rest is the pull request’s title.)</p><h3>A quick fix</h3><p>Firstly, I had a go at a minimal redesign. I felt like the table was causing problems, so I tried to find a different format for the information:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*eZPdSqGs4FaHH3b8.png" /></figure><p>I wanted to do something that would be low effort to implement, making it really easy for our developer to improve the information design. It can be done totally with text and basic markup: doesn’t need any fanciness to implement.</p><p>I also wanted to keep some elements of their design. A total redesign can come across as harsh criticism, and I was basically rewriting all the text they wrote. So I kept some of the clearer emojis, and some of the structure (using “=” signs for the dividers).</p><p>This redesign takes up more space than the original. But that’s fine! Conciseness is important, but clarity has to win out. This design doesn’t require a legend, because it uses clear text labels to replace most of the emojis. It uses phrases (eg “5 new commits”) rather than numbers in a table.</p><p>And the whole thing is much more readable. The users of this bot are trying to find out what’s changed since their last review, so they know what they need to do. This design focuses on efficiently getting them that information.</p><h3>Something a bit fancier</h3><p>Then I discovered <a href="https://api.slack.com/docs/message-guidelines">attachments</a>! This was pretty exciting, because you can use them to format bot messages in a much nicer way.</p><p>I actually really enjoyed using Slack’s documentation around these. The <a href="https://api.slack.com/docs/message-guidelines">Introduction to messages</a> gives an overview of what’s possible with messages and attachments, and also gives a sense of what the features are for. There are some helpful <a href="https://api.slack.com/docs/message-guidelines">Guidelines for building messages</a> that look more at the UX side, and what best practice looks like — particularly if you’re implementing a more complicated workflow. Then the page on <a href="https://api.slack.com/docs/message-attachments">Attachments</a> is what helped me understand the range of possibilities of the format.</p><p>But my favourite bit was the <a href="https://api.slack.com/docs/messages/builder">Message builder</a>. It lets you really quickly prototype a message (including attachments), refreshing whenever you make a change so you can see the effect. I had a lot of fun playing around with it, it’s a great tool.</p><p>I ended up with this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*P97KM32KXJl-uJ8f.png" /></figure><p>Just using the built-in formatting options means we could create something that was <em>much</em> easier on the eye. It has a few other improvements too:</p><ul><li>The heading is now a link to the PR, which is obviously useful.</li><li>I moved the “build” section earlier — because if the build is failing, users probably won’t need to re-review the PR yet. An example of <a href="https://gds.blog.gov.uk/2015/07/21/fail-them-faster/">failing users faster</a>.</li><li>Using the “short” format for fields lets it make better use of the horizontal space.</li></ul><p>In the abstract, I think this is pretty decent now. The next step would be user testing — seeing whether we’re actually including the right information here, and checking which bits matter the most to users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbabda8d0cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on Stack Overflow’s Documentation beta]]></title>
            <link>https://medium.com/@beth.aitman/thoughts-on-stack-overflows-documentation-beta-f5a8b7f10c8?source=rss-62b893e22d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5a8b7f10c8</guid>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[stackoverflow]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Beth Aitman]]></dc:creator>
            <pubDate>Tue, 08 Aug 2017 17:10:11 GMT</pubDate>
            <atom:updated>2017-08-08T17:10:11.639Z</atom:updated>
            <content:encoded><![CDATA[<p>First off: I was really sad to hear that <a href="https://meta.stackoverflow.com/questions/303865/warlords-of-documentation-a-proposed-expansion-of-stack-overflow">Stack Overflow’s documentation beta</a> <a href="https://meta.stackoverflow.com/questions/354217/sunsetting-documentation">was shutting down</a>. I’m a tech writer and sure, you could see that project as a threat to the profession. But it would have been exciting to see innovation in the field, and I was really curious to see whether or not it would succeed.</p><p>Plus, Stack Overflow were in a great position to do something big. SO is a hugely widely-used way to get information, often the first port of call for programming questions. As they say themselves, answers there are basically unofficial documentation already. So I wanted to see if they could use that position to come up with a great solution; I’m sad (but not surprised) that it didn’t work out.</p><p>Their solution was basically this: their Documentation site was a repository of user-written code examples, supported by some — not necessarily much — explanation and extra information. Really, it’s a site of examples, not documentation as it’s traditionally thought of (and that might have been a better name — they did consider it.) It’s not very structured — it just has a bunch of topics under a particular tag for the technology documented.</p><p>They thought this would solve a few problems, which I’ll talk about below:</p><ul><li>Docs are often an afterthought</li><li>Docs are often written from an internal perspective, so they don’t give developers what they need</li><li>Docs aren’t heavy enough on the examples that help developers get started</li></ul><p>SO identified a lot of the problems with the current state of documentation correctly. But the solutions they came up with had some serious flaws.</p><h4>Docs are often an afterthought</h4><p>Absolutely. And I’ve seen that first-hand from the inside of companies. This happens for two reasons: firstly, because sorting the docs out doesn’t seem as important as building the thing itself. Not all companies accept that, for developer products, if you don’t document it, that makes it incredibly hard (sometimes impossible) to use. Secondly, because it takes a significant amount of work to make quality, comprehensive docs that are kept up-to-date.</p><p>“We’ll get the community to do it” seems like an obvious response to the size of that work. But getting that right in itself is a massive effort. It is possible — for example, Mozilla do a great job with this on MDN — but their success has been based on dedicating money and staff to making it happen. SO actually noted in this in their sunsetting post:</p><blockquote>But it was also clear fixing Documentation would require a significantly larger team.</blockquote><p>And seeing as most companies suggest “we’ll get the community to do it” as a way to <em>avoid</em> expense, it’s a bit of a non-starter.</p><h4>Docs are often written from an internal perspective, so they don’t give developers what they need</h4><p>Again, absolutely. Possibly the most important part of the job of a tech writer is finding out what the user perspective is, so that you write the right docs. If you don’t think about users, what you write most likely <em>isn’t actually useful</em>. It’s why <a href="https://www.gov.uk/guidance/content-design/what-is-content-design">designing content</a> has to be so focused on user needs.</p><p>But just because you’re a user, it doesn’t mean that you understand what users in general need. It doesn’t mean you understand users with different use cases to yours, or can reason about the breadth of content that needs covering.</p><p>Building the <em>right</em> set of documentation takes a lot of hard thought; insights from users help you towards that, but they’re not a magic shortcut that gets you all the way.</p><p>By the way, this is why Q&amp;A is so powerful and useful: users actually <em>tell</em> you what they want to know! This kind of feedback is invaluable as a tech writer, but it’s rare to get it in the volumes you do on SO.</p><h4>Users have knowledge that could fill the gaps in existing docs</h4><p>They certainly do: SO answers demonstrate this clearly. But just because they have that knowledge doesn’t make it easy to actually fill the gaps. There are more blockers to that: knowing the right place to put it so that it’s findable, knowing how to explain it well… And the bigger the change, the harder it is to make.</p><p>Again, from the sunsetting post:</p><blockquote>Our interviews showed even very experienced users of T-SQL felt inadequate to contribute documentation. Users with less Stack Overflow experience tended to be intimidated by the prospect of making even trivial edits.</blockquote><p>Docs that are open to contributions are a really nice middle ground on this point. They mean that you can have the advantages of having someone dedicated to working on them, who can make those contributions that people are intimidated by, but also let the community fix the issues that they know how to fix.</p><h4>Examples help developers get started</h4><p>SO felt that a major gap in existing documentation was providing enough examples. Developers love examples — all the evidence suggests that, given a page of documentation, they tend to skip straight down to the first code example, and most will just copy-and-paste that and get going. (That’s why you should be really careful with providing example code that shows bad practices or things you shouldn’t do: most developers will just copy it without looking at the big red warnings above.)</p><p>And yep, examples are really useful. They’re definitely a shortcut to getting going quickly. But examples aren’t a panacea. They aren’t a magic solution to always getting your user to achieve their task, though they might be good at answering specific questions.</p><p>If you have enough examples that they cover all variations, that might go part of the way. But if there are lots of variations, then how do you work out which one you need? If there are loads of examples, how do they fit together? And if they don’t have good supporting documentation, it’s hard to extract the one thing you care about from the stuff you don’t.</p><h3>Things that are hard in the world of tech writing</h3><p>As well as that, there are a few known-to-be-hard problems in the technical writing world, which SO’s solution didn’t address.</p><h4>The other end of the long tail</h4><p>One of the hardest problems tech writers face is working out what to cover, in what detail. There’s a huge long tail of questions that users will have, and we can’t do everything: we have to compromise, and pick the biggest questions for the largest number of users.</p><p>SO is great for this long tail of user questions: it can fill those gaps, and much better than we can — because we have to anticipate those questions, whereas on SO they’ve already been asked.</p><p>But dedicated staff have an advantage when it comes to the other end: the common issues, the core workflows. It’s much harder to deal with these big, broad questions with just drive-by fixes; dealing with those often means you need to think about information architecture and what the content design of your docs should be. It’s not as simple as filling in the blanks.</p><h4>“I can’t find it!”</h4><p>Another big problem tech writers work on is making it so their users can find the information they need. This is why we write task-based documentation: because it’s focused on what users are trying to get done. But the questions users have are often really specific. This is another thing that works in SO’s favour: when a developer searches for a question, it might well match the phrasing of a question that someone has already asked.</p><p>The “I can’t find it” problem requires work on a lot of different solutions. SEO and searchability is one of them: making sure you’re phrasing your docs in the same terms developers use. But it also takes good information architecture, which I can categorically tell you is hard. Finding an intuitive and easy-to-navigate structure for a disparate body of information, that’s logically organised but also based around what users need… I’ve spent the last year working on-and-off on trying to get this right. Generic tags and unstructured topics, like SO Documentation was using, can make it incredibly hard to find what you need.</p><h4>Maintainability</h4><p>Another complaint SO mentioned was that documentation gets out of date. This work — making sure docs are updated — is huge, and massively tedious, and if I’m not careful it means I end up having no time to improve our docs or make them more useful for people.</p><p>It’s one of the reasons for not having examples for everything. Examples that are broken because they haven’t been updated are frustrating at best and useless at worst. My team has limited resources, so I have to say no to things we can’t commit to maintaining.</p><p>There are some ways to improve this — automated testing of code snippets is one we’re working towards right now — but it doesn’t take away the work of fixing what’s broken. So for every new thing you create, you have to make sure it’s worth the effort of maintaining it into the far future.</p><h3>Conclusions</h3><p>To wrap up: it’s easy to identify the widespread problems that documentation suffers from, but it’s hard to solve them. Doing docs well involves a lot of effort: from working out what needs to be produced, to maintaining it and iterating based on feedback, to keeping the whole structure comprehensible, navigable and useful. Writing new content is only a small part of that.</p><p>Some of that work I wouldn’t want to find ways around — for example, I love working out what will help our users, or finding ways to explain complicated things clearly. But it would be brilliant to see people try to solve these problems in innovative ways. If anyone could save me time on the tedious bits of my job, and leave me time to work on bigger and more interesting problems — that would be great. If you work out how to do it — I want to know!</p><h4>Appendix</h4><p>Related posts, if you fancy reading up on the SO Documentation project:</p><ul><li><a href="https://meta.stackoverflow.com/questions/303865/warlords-of-documentation-a-proposed-expansion-of-stack-overflow">Announce idea post</a></li><li><a href="http://jericson.github.io/2016/08/25/long_tail_docs.html">Long tail documentation</a></li><li><a href="http://jericson.github.io/2016/07/13/QA_economics.html">Why do people answer questions on Stack Overflow?</a></li><li><a href="http://jericson.github.io/2016/07/28/what_is_documentation.html">What, exactly, is Documentation?</a></li><li><a href="https://meta.stackoverflow.com/questions/328405/documentation-has-entered-public-beta">Start of public beta</a></li><li><a href="https://stackoverflow.blog/2016/07/21/introducing-stack-overflow-documentation-beta/">Another post about public beta</a></li><li><a href="https://meta.stackoverflow.com/questions/349410/tearing-down-the-structure-of-documentation">Rethinking post</a></li><li><a href="https://meta.stackoverflow.com/questions/354217/sunsetting-documentation">Sunsetting post</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5a8b7f10c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing can’t fix bad design]]></title>
            <link>https://medium.com/@beth.aitman/writing-cant-fix-bad-design-f318aabaaeb0?source=rss-62b893e22d34------2</link>
            <guid isPermaLink="false">https://medium.com/p/f318aabaaeb0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Beth Aitman]]></dc:creator>
            <pubDate>Fri, 26 Aug 2016 09:47:21 GMT</pubDate>
            <atom:updated>2016-08-26T09:47:21.364Z</atom:updated>
            <content:encoded><![CDATA[<p>This door from a train toilet is a great example of adding information in an attempt to fix bad UI design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*f2kh0je5MoiYy94M.jpg" /></figure><h3>What’s wrong with this design?</h3><p>Usually, the way you interact with a door is signalled by cues on the door itself — for example a handle to open it, a bolt to shut. When these <a href="http://www.jnd.org/dn.mss/affordances_and.html">perceived affordances</a> of how to use a door are obvious, you don’t need to add any words to explain how to use it. (Of course, <a href="http://99percentinvisible.org/article/norman-doors-dont-know-whether-push-pull-blame-design/">badly designed doors are everywhere</a>.)</p><p>Here, instead of interacting with the door itself, you interact with these buttons. They’re labelled badly with unclear icons. (I think <a href="https://twitter.com/baitman/status/760975269679226880">icons are almost never clear</a>, but that’s a rant for another day.)</p><p>You can tell they’re bad because the design had to add words *on top of* the icons to explain what they mean. And then also arrows next to the words, because the labels were badly placed, making it unclear which button the labels were for.</p><p>But even that isn’t enough to explain how to use this door.</p><h3>The design itself communicates poorly</h3><p>When you push the “Close” button, it’s not obvious that you need to do <strong>something else</strong> as well in order for the door to lock. (Which is reasonably important in a toilet door.)</p><p>You can tell this has been a problem — there are three separate places where extra text asks you not to forget to push the “Lock” button. There’s piles of information around this design, trying to help people to use it successfully.</p><h3>Telling isn’t the right solution</h3><p>The door design fails to make it obvious what its users need to do, and adding signs off to the side doesn’t help. Many won’t notice the signs because it’s not where their attention is at the time — they literally won’t see the text telling them what to do.</p><p>What’s needed is a design that guides users towards what they need to do, or even better, does it for them. It needs obvious signalling. Clear communication. Understanding of how people behave, and anticipation of what they’ll do.</p><p>When the problem is “people aren’t using this design as intended”, the solution isn’t “tell them to use it properly”. It’s “make a better design”.</p><p><em>(originally posted on </em><a href="http://uiwriting.tumblr.com/post/149502560749/writing-cant-fix-bad-design"><em>uiwriting.tumblr.com</em></a><em>)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f318aabaaeb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>