<?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 Stinelykkeolsen on Medium]]></title>
        <description><![CDATA[Stories by Stinelykkeolsen on Medium]]></description>
        <link>https://medium.com/@stinelykkeolsen?source=rss-78e04ee11141------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xFUyPG-kEq9BnWmyPbQ3-w.png</url>
            <title>Stories by Stinelykkeolsen on Medium</title>
            <link>https://medium.com/@stinelykkeolsen?source=rss-78e04ee11141------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:36:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stinelykkeolsen/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[Technical Writing Certification]]></title>
            <link>https://medium.com/@stinelykkeolsen/technical-writing-certification-10a9a8b8e6f7?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/10a9a8b8e6f7</guid>
            <category><![CDATA[capstone-project]]></category>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[portfolio]]></category>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Thu, 09 Nov 2023 15:36:49 GMT</pubDate>
            <atom:updated>2023-11-09T15:36:49.469Z</atom:updated>
            <content:encoded><![CDATA[<p>In May 2023 I completed the Technical Writing Certification Course at <a href="https://technicalwriterhq.com/">Technical Writer HQ</a> . During the course I learned about important aspects of technical writing, from content management, research, and audience analysis to grammar, style, and user friendliness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEorP95ogaAr3UyHhWThWQ.png" /><figcaption>My certificate</figcaption></figure><h4>Capstone Project</h4><p>To pass the Certification Course, I completed a capstone project consisting of several small projects. Together they form a small portfolio that reflects various genres and types of technical writing.</p><p>This is what I did:</p><p># A Project Summary for a Grant Proposal to the European Union Learning Program (this is a rewritten project summary that I actually did write years ago).</p><p># A user guide: How to fork a repository on GitHub.</p><p># Release notes for EKHO software</p><p># An EKHO user persona and audience learning curve</p><p># A short user manual for a laminator</p><p># A fact sheet on decentralised biogas plants</p><p>As usual I spent a relatively short amount of time on writing the actual text compared to the hours of work that went into the design and layout of the content.</p><p>I will only share a few screen shots of my project, since parts of it are actually quite wordy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2UvpeOlzr6pubTOZkkddZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*G5txj_7ddbDBRx1Y2t_w8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*i3pHxjTtFHPBVXB9zQ4tsg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10a9a8b8e6f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcase: Banking App Boarding Experience]]></title>
            <link>https://medium.com/@stinelykkeolsen/showcase-banking-app-boarding-experience-2d655296506?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d655296506</guid>
            <category><![CDATA[showcase]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[case-study-writing]]></category>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 13:31:11 GMT</pubDate>
            <atom:updated>2023-04-03T13:31:11.985Z</atom:updated>
            <content:encoded><![CDATA[<p>For the final project in the Daily UX Writing Challenge i chose <strong>Challenge 3:</strong></p><p>Write a multi-screen onboarding experience for a banking app that automatically pays a user’s bills every month — as long as they set it up correctly.</p><p>Character constraints per screen (all challenges):</p><p>Headline: 45 characters</p><p>Body: 100 characters</p><p>Button: 25 characters</p><p>Time limit: 1 hour</p><p>I will start with a confession. I spent way more than one hour on this final challenge. I dislike dealing with finances and spend as little time with my banking apps as possible. This meant that I had to do a fair bit of research to find out how to set up an app and write a proper onboarding experience.</p><p>I ended up with 11 screens and I will present them below with a few comments along the way.</p><h4>Screen 1:</h4><p>I decided on a scenario where the user is already a customer at my imaginary bank. Therefore, it was only necessary to set up a user account and not a bank account per se. This means that the bank already has info on the user and doesn’t need to run background checks, etc.</p><p>I decided to include an option for users to scan their passport. The luxury of this challenge is that I don’t have to code the software, so I just assume that this feature is a walk in the park for the development department to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*vkp4N0hRonviCq51W7-WQw.png" /></figure><h4>Screen 2:</h4><p>I just wanted to play a bit with the design program, so this screen is not really relevant. It was fun to design, though.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*r-7fJ7kbDnaftpX0Yfyezw.png" /></figure><h4>Screen 3:</h4><p>Now the user account has been set up behind the scenes in the app. I created a UI to explain that all is almost set, and that the user just needs to create a profile and credentials for login.</p><p>I think that the microcopy is clear enough for most users. Most bank customers that choose to use a banking app instead of visiting their local banking branch are so familiar with technology that no further explanations are needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*I9twkHQAggRflMYd3ODoug.png" /></figure><h4>Screen 4:</h4><p>No Daily UX Writing Challenge without a couple of error messages. I have gathered a few possible messages in one screen shot. There are more potential errors than the two that I display here.</p><p>The user could have a name that the program doesn’t recognize as a name (I wrote an error message addressing this exact problem in an earlier Daily UX Writing Challenge). Passwords may be too weak, contain empty spaces, or be missing numbers and special characters. I know that the creation of passwords and all the coding surrounding password security is a whole field in itself, and I am not going to go further into details here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*gVYzHZuuXM0s-jFVsSCy0g.png" /></figure><h4>Screen 5:</h4><p>Now everything is set, and the user is ready to explore the new app. He just needs to sign into his new user account. This shouldn’t lead to any issues.</p><p>Just to make sure, I have added a “GO BACK” button. Maybe the user wants to check something, or to change his password. I hope that the development department will bear with me, if I they have to jump through hoops to create something smart for the user to do with this option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*Mr-F-Se2Eotm8iWIXD59aw.png" /></figure><h4>Screen 6:</h4><p>Now the user has logged into the screen that greets him right after signing in. I was inspired by a number of existing banking apps when creating this screen. Maybe there should have been other options to chose from, but I think these are among the most common for ordinary banking customers (I know that my persona here is rather well off with that total balance, but I guess his banking needs are still within the “normal” range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*AWfb44OY5CAo-G8FC6RzAQ.png" /></figure><h4>Screen 7:</h4><p>We have finally arrived at the central screen of the challenge. The “Pay Bills” option. In my scenario, the user’s bills are in electronical form and are somehow transferred to the app via the user’s bank. (Don’t ask me how this is done in practice, but my imaginary development department is awesome and they have set this up flawlessly).</p><p>Now, the user has the options to pay the bill and set up automatic payment at the same time. This is convenient for the user since it isn’t necessary to manually enter all information on the payee. I know this option from my own online banking system, and I always use it the first time, I pay a bill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*l9CzfEq-I7Nl6t8hS64f_w.png" /></figure><h4>Screen 8:</h4><p>The user has now entered the “Set up Payment” screen and is presented with a number of options. The screen has been automatically filled in based on the information on the original bill. In the app it’s possible to change these settings by the user to fit his current situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*s0sSK261csfugcYOerN26g.png" /></figure><h4>Screen 9:</h4><p>I have also created a screen for manually setting up automatic payment. On this screen the user must manually enter detailed information on the payee. The idea is that this screen leads to screen 8 when filled out.</p><p>To help the user a bit, I have added some microcopy below the “IBAN” field. The IBAN No. is needed with international money transfers. I also thought about adding options for the user to search addresses and account numbers of payees with the app, but decided to keep it simple. Maybe I could set this function up for MyWallet 2.0.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*5bSHpzWtqFcMkhc3w0pi9g.png" /></figure><h4>Screen 10:</h4><p>All is good, and automatic payment has been set up. This screen displays the details of the new automatic payment for the user to double check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*FznREshyZjU9_XLrp9F2IQ.png" /></figure><h4>Screen 11:</h4><p>I finally decided to include some error messages that might occur during an onboarding process. I am sure that there are many other possible errors that could occur, but I think these are among the most common.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*i0-SVseQMXVnbxnCv_hzHw.png" /></figure><h3>Takeaways from the final challenge.</h3><p>This was by far the hardest challenge for me. Here, I had to produce several screens with microcopy providing the user with coherent and helpful information, not just a few snippets of text. This was a challenge in itself.</p><p>Writing an entire onboarding experience was also challenging because I actually also had to invent parts of an imaginary app for the user to board. I’m not great at coding, but I do know that some things that seem simple to non-programmers are actually quite complex and hard to build. I had a lot of thoughts on functionality and feasibility when “building” the app.</p><p>One important lesson for me during this small project is that development, documentation, and UX writing are best done simultaneously and in teams. I surely could have used some input from someone with more coding knowledge than me and a skilled designer. Still, I flatter myself enough to think that I could have contributed to designing, planning, and building the app as well. After all, microcopy is an essential part of the user experience and the final product. And UX writers tend to know a lot about end user needs. Why not let the UX writer have a say at all stages of app development?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d655296506" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcase: How To Guide]]></title>
            <link>https://medium.com/@stinelykkeolsen/showcase-how-to-guide-a009e7b0cc6d?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/a009e7b0cc6d</guid>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 14:26:26 GMT</pubDate>
            <atom:updated>2023-03-21T14:28:16.829Z</atom:updated>
            <content:encoded><![CDATA[<p>This guide has never been published. I wrote it as part of the <a href="https://www.udemy.com/course/tech-writers-master-class/">Tech Writers Master Class</a> that I completed in January 2022. Being completely obsessed with the Japanese martial art of Aikido, I decided to write a guide to striking the bokken (wooden sword).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yE5mbkkSju7yFYdrrLaMVw.jpeg" /><figcaption>Aikido. Photo courtesy of Nando García @ Unsplash</figcaption></figure><p>I decided on a scenario where the small guide is part of a beginner’s book on aikido. The reader is fairly new to aikido and I really go into details here. I pretended that the text was accompanied by illustrations that showed the different steps clearly. I don’t really have these illustrations, so, please, try to imagine that they are there. And, bear with me and the long text.</p><h3>Aiki-ken: How to strike with the bokken (wooden sword)</h3><h4><strong>Ken kamae: the basic bokken stance</strong></h4><p>All basic sword techniques have the ken kamae as their starting point. At first, this stance might feel a little unfamiliar. It is advisable to practice it often, so the body gets used to the new position and the correct alignment of the joints.</p><p><strong>(Illustration #1)</strong> Stand with your feet shoulder width apart. Straighten your spine by imagining that you press up against the sky with the top of your head. Relax the shoulder, arms, and abdomen. Unlock your knees — bend them slightly, so the joints are not completely locked.</p><p><strong>(Illustration #2)</strong> Place your right foot with the toes pointing straight ahead. Place your left foot shoulder width apart behind your right foot. Your left foot should be at a 45-degree angle on an imaginary line going vertically through the centre of your body, your centre line.</p><p><strong>(Illustration #3)</strong> Twist your hips, so they align with your left foot. That is, the hips are also at a 45-degree angle on the centre line.</p><p><strong>(Illustration #4) </strong>Your shoulders stay aligned with your hips. To illustrate, imagine a straight line going from your right shoulder, down through your right hip, through your right foot, and down into the floor.</p><p><strong>(Illustration #5)</strong> Bend the knees slightly so they align with your toes and do not go past the points of your toes. Ensure that your body weight is distributed evenly on both feet. This way your centre of gravity is aligned in the middle of your body. It might be helpful to visualise that your bodyweight flows down through your spine and your tailbone into the floor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*2ZjE23i5dwis8bv8zMgRIw.jpeg" /><figcaption>Ken Kamae. Photo courtesy of Andypoland @ Pixabay</figcaption></figure><h4><strong>Gripping the sword correctly</strong></h4><p><strong>(Illustration #6) </strong>Place your left hand at the back of the handle, so that the little finger grips the edge of the handle. Place your right hand approximately two fists apart in front of your left hand. Only the little finger and the ring finger hold the bokken in a relaxed, yet firm, grip. The rest of the fingers hold on very softly.</p><p><strong>(Illustration #7) </strong>Hold the bokken in front of your body at one fist’s distance and at the hight of the knot of your belt. Your arms should bend slightly at the elbows.</p><h4><strong>Striking</strong></h4><p><strong>(Illustration #8)</strong> Inhale and raise your bokken straight up over your head in line with your centre line. The movement begins by turning your right hip slightly back. Keeping the shoulders aligned with your hips courses your arms to go backwards, thus creating an imaginary shape of a semi-circle with your hands. “Open” your elbows, so they point at a 30-degree angle away from your centre line. Your right foot slides a few centimetres backwards to follow the movement of your hips.</p><p><strong>(Illustration #9)</strong> Raise the bokken all the way up, until it is placed behind your back, parallel to your spine. Remember to keep your arms relaxed and do not raise your shoulders towards your ears. Hold your breath.</p><p><strong>(Illustration #10)</strong> Initiate the downward strike by moving your right hip back towards the start position and sliding your right food forward. Exhale and bring your elbows forward and down. This way, the bokken falls downwards by itself. Do not try to force the bokken down in a fast or hard movement by using your hands or arms.</p><p><strong>(Illustration #11)</strong> End the strike when the bokken is horizontal. Drop your bodyweight slightly, like sitting down your centre of gravity on a stool straight between your legs. This stabilises your posture and makes the strike more powerful.</p><p><strong>(Illustration #12)</strong> You stop the movement of the bokken by moving your wrists slightly towards your centre line. This causes the grip of your hands to twist, like wringing water out of a cloth. Finish by gripping the bokken with your index fingers. This will help stabilising the ken. Simultaneously you bring your elbows back to their starting position close to your body’s centre line.</p><p>Phew. What do you think? It’s a lot, huh? And, this is merely part of an imaginary beginners’ book, and this technique is actually much more complicated.</p><p>Aikido takes practice and attention to detail. But, it is oh, so rewarding to throw someone or pin their wrists to the floor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a009e7b0cc6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcase: Writing and documenting a silly Python program]]></title>
            <link>https://medium.com/@stinelykkeolsen/showcase-a-silly-python-program-63dffb2e4525?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/63dffb2e4525</guid>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 12:32:02 GMT</pubDate>
            <atom:updated>2023-03-20T13:18:07.146Z</atom:updated>
            <content:encoded><![CDATA[<p>For the last year I have completed a few online coding courses and bootcamps for tech writers focusing on Python and JavaScript. At the moment I am doing the Python Essentials 1 at <a href="https://pythoninstitute.org/python-essentials-1">the Python Institute</a>.</p><p>My goal is not to become a developer. I am better with words and languages than with numbers and algorithms. What I would like, though, is to strengthen my understanding of the inner workings of codes and programming languages.</p><p>This will deepen my technical knowledge and strengthen my technical writing skills. It is always easier to write something, when the subject matter is not completely lost on the writer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5bl70scUMYO8XYFfHF6Xow.jpeg" /></figure><p>Here is a piece of code I wrote as a small exercise during the Python Essentials 1 course:</p><h4>Scenario (copied from Python Essensials)</h4><p>A junior magician has picked a secret number. He has hidden it in a variable named secret_number. He wants everyone who run his program to play the <em>Guess the secret number</em> game, and guess what number he has picked for them. Those who don&#39;t guess the number will be stuck in an endless loop forever! Unfortunately, he does not know how to complete the code.</p><p>Your task is to help the magician complete the code in the editor in such a way so that the code:</p><ul><li>will ask the user to enter an integer number;</li><li>will use a while loop;</li><li>will check whether the number entered by the user is the same as the number picked by the magician. If the number chosen by the user is different than the magician’s secret number, the user should see the message &quot;Ha ha! You&#39;re stuck in my loop!&quot; and be prompted to enter a number again. If the number entered by the user matches the number picked by the magician, the number should be printed to the screen, and the magician should say the following words: &quot;Well done, muggle! You are free now.&quot;</li></ul><p>The magician is counting on you! Don’t disappoint him.</p><h4>Result and thoughts on documentation:</h4><p>Below is a screenshot of my code written in PyCharm, my favorite IDE (integrated development environment) for Python.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSZ7y7UCxxdDAih8bY1m0g.png" /><figcaption>The muggle trap machine</figcaption></figure><p>I am well aware that this tiny program is not very complicated. Since I am firstly a text person, secondly a tech person, I find it quite adorable, though.</p><p>What I focus on here is documenting each line of code and explaining it to non-technical readers how it works.</p><p>Intra-code documentation is not a genre that I am very familiar with. I have the impression that this is generally done by developers who are experts in the subject matter.</p><p>I still find it useful for non-experts to at least edit/proofread this type of documentation. Programmers are often deeply immersed in the code, and run the risk of writing documentation that only they understand. A tech writer who comes from “outside” of the software world is less likely to use too much jargon or become too esoteric in their writing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63dffb2e4525" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcase: EKHO User guide and software]]></title>
            <link>https://medium.com/@stinelykkeolsen/showcase-ekho-user-guide-and-software-93cb012f25d5?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/93cb012f25d5</guid>
            <category><![CDATA[case-study-writing]]></category>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 10:53:19 GMT</pubDate>
            <atom:updated>2023-04-14T10:43:12.502Z</atom:updated>
            <content:encoded><![CDATA[<p>I was hired by the people behind EKHO at <a href="https://bitmatic.com/">Bitmatic</a> to translate the user interface of the program into German, and to make a new edition of the EKHO User Guide.</p><p>To ensure that the target audience is properly addressed and for personal learning purposes I conducted an audience analysis and created a user persona. You find the user persona below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxu4-d03S3Kd4Y91THoTxA.png" /><figcaption>EKHO User guide front</figcaption></figure><h4><strong>What is EKHO?</strong></h4><p>EKHO is a piece of medical equipment that is used to diagnose and help patients with hepatic encephalopathy, a disease in the liver. EKHO is used for diagnosing, treatment, and research purposes, primarily at hospitals in Denmark and Sweden.</p><h4>UI translation EN-DE</h4><p>This was my first medical/technical translation into German. It was great in terms of training. I could focus on getting the terminology right without worrying about grammar and sentence structure (though I love those aspects of the German language, they often turn into rabbit holes for me, and I can spend hours getting one sentence just right).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*szyn94_Kot-pUUUR3DIHlA.png" /><figcaption>A snippet of the translated UI © bitmatic.com</figcaption></figure><h3>The new EKHO User guide</h3><p>Creating a new user guide for EKHO was likewise a great learning experience. I edited and rewrote parts of the content. Afterwards, I redesigned the guide in a new format.</p><h4>Keeping it simple</h4><p>EKHO is mostly operated by nurses and medical secretaries, who are not necessarily super tech savvy or digital natives.</p><p>Therefore, my focus was to keep the text simple, concise, and clear without compromising the comprehensibility of the text. All functions and buttons of the program were accompanied by pictures and icons to prevent any confusion.</p><h4>Tone of voice</h4><p>One of my other focal points as a tech writer is the concept of <em>policy. </em>When I write, I always ask myself, “is the text consistent with the vision and brand of the sender organization?”.</p><p>In Denmark, people are rather informal. This is also the case with corporate communication, and the tone of voice of the User guide reflects this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HWuYoGihhBb3xVF2ZCNkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jurXRLkpHBey1JZ0TaSBVA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksWpVlqsFLvr3Z13ztUzZQ.png" /></figure><h4>Key takeaways:</h4><ul><li>Keep it simple: stay true to audiences and make sure they understand</li><li>Relax: the tone of voice can be professional, yet informal, when representing a company with these values</li><li>UI translation is great when you need to focus on terminology. The focus is on precision, not semantics</li></ul><h4>Ekho User Persona</h4><p>After a brief audience analysis (talking to the owner of EKHO) I created the following user persona and audience learning curve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RVLLszLR8I1CC5SkkE_1DQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EY--boIGoVMzz6eFStzaBQ.png" /></figure><p>To make a more comprehensive audience analysis I would have liked to interview technicians, doctors, and end users. However, this was not within the scope of this project and could be a possible, future project for EKHO’s developers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93cb012f25d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Showcase: The Daily UX Writing Challenge]]></title>
            <link>https://medium.com/@stinelykkeolsen/showcase-the-daily-ux-writing-challenge-2c9d8953cb94?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c9d8953cb94</guid>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[showcase]]></category>
            <category><![CDATA[daily-ux-writing]]></category>
            <category><![CDATA[learning-ux-writing]]></category>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Fri, 17 Mar 2023 11:32:52 GMT</pubDate>
            <atom:updated>2023-03-28T10:19:11.449Z</atom:updated>
            <content:encoded><![CDATA[<p>In March 2023 I picked up the gauntlet and did the Daily UX Writing Challenge from <a href="https://dailyuxwriting.com/">dailyuxwriting.com</a></p><p>My aim was to write better and sharper microcopy. Microcopy is another word for the short snippets of text we meet on our devices all the time, such as notifications, error messages, buttons, tool tips, and log in forms.</p><h3>The challenge</h3><p>For 15 days I received a prompt via e-mail with a scenario and a set of requirements for the content and scope of the texts.</p><p>The most annoying requirements were the limitations on space. All challenges had a character limit, mostly 45 for the headline, 175 for the body and 25 for the call-to-action button(s).</p><p>To imitate real life situations, the challenges were timed. Most exercises had a ten-minute time limit.</p><p>Finally, the people behind the challenge recommended that I share my results in the Daily UX Challenge group on Facebook. It was kind of intimidating at first, but I decided to go ahead and put myself out there.</p><h3>My Tools</h3><p>I used my computer and (sometimes) a timer.</p><p>I also tried (and failed to) create my content with tools like Figma and Miro, but I ended up struggling too much trying to figure out how they worked. Instead, I have used Canva. I decided that I am, after all, a writer, not a designer.</p><p>So, without much further ado, here are a few examples of the microcopy I made:</p><h3>UX Writing Challenge: Day 1</h3><p><strong>Scenario: </strong>A traveler is in an airport waiting for the last leg of a flight home when their flight gets abruptly canceled due to bad weather.</p><p><strong>Challenge: </strong>Write a message from the airline app notifying them of the cancellation and what they need to do next.</p><p>Headline: 45 characters | Body: 175 characters max | Button(s): 25 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhJfemqbI17PYP_RZ7qCGQ.png" /></figure><h4>Key takeaways:</h4><p>Having your flight cancelled is really vexing. Soften the blow of your message with an emphasising tone of voice and by offering easy solutions for the user.</p><h3>UX Writing Challenge: Day 3</h3><p><strong>Scenario:</strong> The user entered the wrong email address to sign in to their account.</p><p><strong>Challenge:</strong> Tell the user to enter the right email.</p><p>40 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*fIAyDXv3___jsZudamadsA.png" /></figure><h3>Key takeaways:</h3><p>Guess it’s safe to say that I am NOT a fan of writing error messages…</p><p>I found it hard to write something nice and emphatic within such a constricted space. One of my fellow UX writers pointed out that emphatic writing doesn’t have to be flowery or apologizing, so I decided to stick to this wording:</p><h3>UX Writing Challenge: Day 4</h3><p><strong>Scenario:</strong> A user is in their favorite supermarket. They open the supermarket’s app on their phone to see what’s on sale and are greeted by a promotion.</p><p><strong>Challenge:</strong> Write a promotional home screen for a subscription service that delivers groceries to the user once-a-month for a flat fee.</p><p>Headline: 45 characters max | Body: 175 characters max | Button(s): 25 characters max</p><p>The great thing about this exercise is that the audience — a potential buyer- are already physically present in the supermarket and probably receptive to the product.</p><p>The USP (I don’t know if this selling point is really that unique, actually) of this product is CONVENIENCE. The user is already a seemingly loyal customer at this supermarket, since they are using the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*II5ebX9YO25nzM2RtYi9Bw.png" /></figure><h4><strong>Key Takeaways:</strong></h4><p>The headline should be informative, short, and sweet — as we are interrupting the user during their shopping.</p><h3>UX Writing Challenge: Day 5</h3><p><strong>Scenario:</strong> The user works in graphic design. While critiquing a design in a mobile app, their phone abruptly turns off. When they restart the phone, they reopen the app.</p><p><strong>Challenge:</strong> Write a message that the user will read immediately upon opening the app. What do they need to know? What steps (if any) do they need to take to recover their content? What if they can’t recover the content?</p><p>Headline: 40 characters max | Body: 140 characters max | Button(s): 20 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*fZ7EJUmkymp0nPI993FtKw.png" /></figure><h4>Key takeaways:</h4><p>At times like these you can rest assured that the user will be fuming. Few things in the world are as frustrating as system failures during the work day.</p><p>You don’t want to frustrate them further by writing overtly technical or esoteric messages right now. Keep the tone of voice informatory, helpful, and solution-oriented.</p><h3>UX Writing Challenge: Day 6</h3><p><strong>Scenario:</strong> It’s Monday. A user has just gotten into their car to drive to work. They plug their phone into the car and start driving.</p><p><strong>Challenge:</strong> How would you let the user know there’s a fire happening in a nearby town that is causing road closures? The effect on their commute is unknown, but there is a definite danger if the fire gets closer. How do you communicate this to them? When? Write it.</p><p>Headline: 30 characters max | Body: 45 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*Z932WRV32SQ-YxoLSEiE3A.jpeg" /></figure><h4>Key takeaways:</h4><p>The user is driving and doesn’t have time to read a long text. Thus I kept the message short and to the point.</p><h3>UX Writing Challenge: Day 7</h3><p><strong>Scenario:</strong> A sports fan is at a wedding while their favorite team is playing against their arch-rivals. Their team scores.</p><p><strong>Challenge:</strong> How would you, quickly, let the sports fan know about the latest play, the current score, and the key players? Write it.</p><p>Headline: 30 characters max | Body: 45 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*2xzSilOTTvDnWv-e8Cb1gQ.png" /></figure><h4>Key takeaways:</h4><p>When writing content, always keep an expert at hand. I don’t know anything about football 😊</p><h3>UX Writing Challenge: Day 8</h3><p><strong>Scenario:</strong> The user is a casual music fan and (on occasion) goes to live concerts. They have a music player app on their phone.</p><p><strong>Challenge:</strong> Tell the user that one of their favorite bands is playing live in their town. How would you compel them to want to go?</p><p>Headline: 30 characters max |Body: 45 characters max | Button: 25 characters</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qhk8jhjiW2XVR9-QuVF44g.png" /></figure><h4>Key takeaways:</h4><p>Again, keeping the character count down was rather annoying. But hey, buttons go a long way, because they imply that more info i readily available.</p><h3>UX Writing Challenge: Day 10</h3><p><strong>Scenario:</strong> The user is trying to view a website to help them buy a car. But the content can’t load without the user’s location. They need to enter their ZIP code and first name.</p><p><strong>Challenge:</strong> Ask them where they live and who they are without sounding like you’re unnecessarily mining their data.</p><p>Headline: 25 characters | Body: 45 characters | Button: 15 characters</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nFEAzaeD7JnAsNDg7gW-ZQ.png" /></figure><h4>Key takeaways:</h4><p>No serious company wants to come off as trying to get your hands on peoples’ data without good reason.</p><p>I decided to use a button to give the user a chance to learn more about the purpose of knowing their name and location: to improve the user experience and functionality of the app.</p><h3>UX Writing Challenge: Day 11</h3><p><strong>Scenario:</strong> An elderly user is doing a Google search to find an easy way to buy contact lenses online.</p><p><strong>Challenge:</strong> Write a title and meta description for a website that sells subscription contact lenses delivered to a user every 30 days — convince them to try it.</p><p>Title: 60 characters max</p><p>Meta Description: 160 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*RALe4ADzIUSzg8J7k2SrdQ.png" /></figure><h4>Key Takeaways:</h4><p>Dear old Google. Key Word Density, rankings, algorithms. As a writer with a deep love for the written word, SEO is a genre that often makes my heart (and eyes) bleed.</p><p>To me SEO should never ruin the integrety of the text, and the copy should never feel forced. I tried my best here. Fortunately, the project manager (me) didn’t complain. Unfortunately, it sometimes happens in my real life job.</p><h3>UX Writing Challenge: Day 13</h3><p><strong>Scenario:</strong> A short-haul truck driver has a phone app that monitors his route, schedule, fuel &amp; deliveries.</p><p>He has 6 more deliveries before stopping for fuel and lunch. Due to unexpected traffic, he’s behind schedule.</p><p>He can choose to stay on his planned route for a few more stops, but risk running low on fuel and missing lunch, or he can get fuel and lunch now and finish the deliveries later.</p><p><strong>Challenge:</strong> Write a push notification alerting him of this dilemma and options.</p><p>Headline: 30 characters max</p><p>Body: 45 characters max</p><p>Button(s): 25 characters max</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5M6VE8exW6PMy_uC_r4Cw.png" /></figure><h4>Key Takeaways:</h4><p>I know a former short-haul truck driver who quit because his job was too unpredictable to combine with the role as a father and husband.</p><p>I therefore knew there was wisdom in the hint that accompanied the challenge:</p><blockquote>Before you write your solution, try and empathize with the litany of crap that a truck driver probably has to put up with on any given workday. Once you feel like you have some perspective, give this challenge a shot.</blockquote><p>My strategy was to guide and ease the decision making process of the driver by providing easy to follow instructions and solutions to the problem.</p><h3>Bonus: Random Microcopy Prompt</h3><p>I did a few extra excersises from <a href="https://dailyuxwriting.com/">dailyuxwriting.com</a>. Here is one of them:</p><p><strong>Scenario: </strong>A user is about to sign-up for a year-long subscription to Amazon Prime. <br>Write a message to go under the button that will make them feel better about the choice <strong>— 30 characters max.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*ZQGgeHsNBBi3HssVR-tNTg.png" /></figure><h4>Key takeaways:</h4><p>It often hurts to get your wallet out of your pocket. Which better way to forget the pain than bingewatching your favorite show?</p><h3>What did I learn?</h3><ol><li>UX really is a genre in itself. It challenges grammatical and semantic rules of our language and shifts the focus from writing <strong>correctly</strong> to writing <strong>user centred</strong></li><li>Time constraints are helpful. Lots of time does not always mean better results — often the opposite. The ten-minute limit stopped med fro overthinking and forced me to cut to the chase.</li><li>Character constraints are painful. But they are necessary and actually sometimes boost creativity.</li></ol><h3>Why am I interested in UX Writing?</h3><p>UX Writing is a fun, challenging, and instructive genre to explore as a writer. Writing clear and concise microcopy with the end user in mind is demanding, but it also teaches writers to get straight to the point. If you only have 45 characters’ space, you need to keep it <strong>simple</strong>, yet <strong>nice</strong>.</p><p>To me, these principles are essential in all areas of technical communication. Therefore, even for non-UX writers, UX writing is a great mindset to “think with” when creating content.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c9d8953cb94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first post here on Medium….]]></title>
            <link>https://medium.com/@stinelykkeolsen/my-first-post-here-on-medium-42d56821c0f3?source=rss-78e04ee11141------2</link>
            <guid isPermaLink="false">https://medium.com/p/42d56821c0f3</guid>
            <dc:creator><![CDATA[Stinelykkeolsen]]></dc:creator>
            <pubDate>Thu, 02 Mar 2023 08:05:40 GMT</pubDate>
            <atom:updated>2023-03-02T09:29:34.978Z</atom:updated>
            <content:encoded><![CDATA[<p>I just applied for a job as a content writer at the most amazing company ever. They sell “protective gear” for board and trading card games like Magic the Gathering.</p><p>Being a huge nerd myself, I really, really would love to work with these people. To unfold my inner Planeswalker (I told you, nerd) on a daily basis (and getting paid for it) would really be a dream come true.</p><p>Instead of writing a cover letter to apply for the job, I turned myself into a Magic card. If any of you who read this play Magic the Gathering, you will know that I went a *bit* over the top. The card might be slightly over powered. Anyway, I had a blast creating the avatar and the card.</p><p>Check it out. And tell me: If you were a mtg creature card, what kind of card would you be?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*UJxOl0SeZUA644-g95HA7w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42d56821c0f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>