<?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 Nathan Major on Medium]]></title>
        <description><![CDATA[Stories by Nathan Major on Medium]]></description>
        <link>https://medium.com/@nathanmajor?source=rss-2cb7ddb0e748------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8ZunGTzF_o7ZfkeA</url>
            <title>Stories by Nathan Major on Medium</title>
            <link>https://medium.com/@nathanmajor?source=rss-2cb7ddb0e748------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:25:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nathanmajor/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[Testing Voice — How to build and deploy VUI prototype for Alexa]]></title>
            <link>https://medium.com/frontline-design/testing-voice-how-to-build-and-deploy-vui-prototype-for-alexa-f09698e275e6?source=rss-2cb7ddb0e748------2</link>
            <guid isPermaLink="false">https://medium.com/p/f09698e275e6</guid>
            <category><![CDATA[vui]]></category>
            <category><![CDATA[amazon-echo]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nathan Major]]></dc:creator>
            <pubDate>Tue, 26 Mar 2019 18:11:40 GMT</pubDate>
            <atom:updated>2019-03-26T18:11:40.493Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing Voice — How to Build, Test, and Deploy Voice Prototypes for Alexa</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hYIn_nCyrPGLDeFo.jpg" /><figcaption>Image from <a href="https://www.logigear.com/magazine/test-automation/guide-automated-voice-apps-testing/">https://www.logigear.com/magazine/test-automation/guide-automated-voice-apps-testing/</a></figcaption></figure><p>As UX designers, we are continuously pushed into new and exciting spaces of design and interaction. One of the most popular new interactions is that of voice, particularly natural conversation devices such as Alexa, Siri, Cortana, and Google Voice. While entering this space presents a lot of interesting new challenges for a UX Designer, it does present a bit of a problem:</p><p><em>How do you test a voice flow?</em></p><p>Generally speaking, it can be assumed most UX designers follow similar patterns when testing visual elements of design. You build either low or hi-fi mockups. You import them to a prototyping tool such as InVision, Marvel, Axure, or others. And you share those prototypes with users, performing usability testing on the designs.</p><p>But with voice we’re presented with a challenge, specifically that there’s usually no visual component. While we could show users our VUI workflows, that doesn’t evoke the same kind of natural interaction a visual prototype does. So how can a UX Designer build, deploy, and test voice prototypes without requiring dev work?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9j2uhZpiSqguM6V25Xdzw.png" /><figcaption>A screenshot of a voice prototype built in VoiceFlow</figcaption></figure><p><strong>Step 1 — Build and Test the Prototype</strong></p><p>While the concept of building an entire Alexa Skill may sound daunting, there are thankfully many free tools available that make the process simple.</p><p><a href="http://getvoiceflow.com/">VoiceFlow</a> is a free tool that allows you to build and deploy an Alexa skill to Amazon Publisher easily. VoiceFlow also has its own collection of Medium articles, particularly this one on <a href="https://medium.com/getstoryflow-com/build-your-first-alexa-skill-in-5-minutes-54d65a3c9f01">building a skill in five minutes</a>, which shows the simplicity of the platform.</p><p>This isn’t the only tool available, but the concept is generally the same across all of them. With these tools you can easily convert a workflow into a functional VUI fairly quickly. The tool offers a plethora of powerful options that fulfill about 90% of most needs, including API calls. I have yet to design a workflow that was so complex I couldn’t replicate a prototype version in VoiceFlow.</p><p>That being said, it’s important to remember that key word: <em>prototype</em>. Similar to how screens on InVision aren’t actually live code, your Skill probably won’t be hooked up to the actual backend (depending on Skill complexity). It’s important to design a skill where test users will be able to naturally navigate it without needing too much instruction. However, this skill must still align with what you want the finished experience to be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*_rdcCOSNlM88_5HnrW6Msg.png" /><figcaption>An example of a text-only test in VoiceFlow</figcaption></figure><p>Lastly, be sure and test your skill before moving to the next step. Errors are much easier to fix when you can quickly type your way through responses rather than having to wait for Alexa to verbally read them out. While this won’t be the last time we test, it’s a good first pass to make sure your workflow converted correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbKXBHcIqLQXGWIu47WtVg.png" /><figcaption>The Amazon Developer Alexa Skill Dashboard</figcaption></figure><p><strong>Step 2 — Export It to Amazon Developer (and Test It Again!)</strong></p><p>The next step is to actually push it to your <a href="https://developer.amazon.com/">Amazon Developer</a> account. If you don’t have one, your organization or company should provide you with one. In our situation, my account is in the same group as our devs, so we all have full visibility of skills being worked on.</p><p>Pushing it to your developer account is easy. Often times it’s baked into these free tools (it is built into VoiceFlow), though if your workflow has errors they’ll need to be fixed before the upload will work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*mtmhyXF_odZxMXYGnvHzjA.png" /><figcaption>Once your skill is uploaded to dev, it is available for you (and your group) on the Alexa app.</figcaption></figure><p>Once your skill is uploaded, you’ll want to test it again, but this time on an actual device. Make sure your Echo device is connected with your Amazon Developer account, then hop on the <a href="https://alexa.amazon.com/">Alexa web app</a>. Here, you can browse Skills and find your own dev skills and easily install your prototype to your device.</p><p>From here, based on what you set your invocation word to be (usually the name of the Skill) you can hop right in and test it on your actual Echo device! I must admit, it was a bit of a magical experience to go from moving workflows around on VoiceFlow in the morning to actually talking to Alexa and using the prototype in the afternoon.</p><p>The verbal test is essential because it will help you weed out unnatural sounding sentences, phrases, or responses. Oftentimes replies that look great typed aren’t as great when dictated orally. This is a final cleanup step that lets you go back to your flow and adjust responses based on both flow and how the phrases sound.</p><p>Now we have a Skill that works on our device, but can’t be sent to other devices. Publishing it to the Skill Store would require Amazon’s approval, which we don’t have time for, so how can we make our skill available for users to test?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXcHFA6mfDvOy6MzjOKeVQ.png" /><figcaption>The beta testing screen, under “Distribution” in the Alexa Dev Console</figcaption></figure><p><strong>Step 3 — Set Your Skill as a Beta</strong></p><p>Amazon Developer has a neat ability that lets you take any Skill, finished or otherwise, and deploy it as “in beta.” A skill that in beta has some restrictions. For example, you can only have a total of 500 beta testers per skill, and the beta session can’t last longer than three months (though you can renew it with new users after that). However, if you’re just going to use this for usability testing a prototype, moving a Skill into beta is the perfect solution.</p><p>To push your skill to beta you’ll first need to fill out all the distribution details required, as if you were publishing it to the store. So it will need a title, description, icon, etc. since users will see all of this when they sign up for the beta. After that, you simply put your device into beta and it’s ready to be distributed. No developer, coding, or Amazon approval required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*ORx-M62FFCnM8MRjzxQrSA.png" /><figcaption>Image from <a href="https://mashable.com/2018/04/19/amazon-alexa-skill-blueprints-potty-mouth/#b6Bv4m9qYGqQ">https://mashable.com/2018/04/19/amazon-alexa-skill-blueprints-potty-mouth/#b6Bv4m9qYGqQ</a></figcaption></figure><p><strong>Step 4— Recruit Users, Send Beta Invites, and Test</strong></p><p>The final step is the one most similar to a visual usability study. First, you recruit your users in whatever way best suits you. Make sure they have an Echo device! Beta doesn’t work on the mobile app Alexa, so they’ll need a physical Echo to talk to.</p><p>Once you have your study times set up, invite users to the beta via the invite on the Amazon Developer page. This will send the users a link that will allow them to install this particular beta skill on their device. Of note: you’ll need to be sure to invite their <em>Amazon account email</em> to the beta. Once they have the skill installed, it will work just like it worked on your dev Echo unit.</p><p>Lastly, perform the usability test as you normally would. Let the user explore your prototype, take notes, ask questions, however you best feel the testing should be conducted.</p><p>And should your research uncover changes you need to make to the prototype, simply go back into VoiceFlow, adjust your workflows, upload it to Developer, and retest.</p><p><strong>Conclusion</strong></p><p>I hope this has been a helpful guide to how to build, deploy, and test VUI prototypes for Amazon’s Alexa. This is a powerful and growing new space, one that certainly will be getting a lot of UX support over the next few years. As Alexa continues to evolve, so will the need for excellent user testing. And with all user testing guidelines, be sure and get your VUI prototypes out and in front of users as soon and as often as possible. This ensures your final Alexa product delights and excites your users.</p><p>Happy testing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f09698e275e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frontline-design/testing-voice-how-to-build-and-deploy-vui-prototype-for-alexa-f09698e275e6">Testing Voice — How to build and deploy VUI prototype for Alexa</a> was originally published in <a href="https://medium.com/frontline-design">Frontline Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When it doesn’t work out — Failure and UX]]></title>
            <link>https://medium.com/frontline-design/when-it-doesnt-work-out-failure-and-ux-9572b3712148?source=rss-2cb7ddb0e748------2</link>
            <guid isPermaLink="false">https://medium.com/p/9572b3712148</guid>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[failure]]></category>
            <dc:creator><![CDATA[Nathan Major]]></dc:creator>
            <pubDate>Fri, 15 Feb 2019 16:44:25 GMT</pubDate>
            <atom:updated>2019-02-15T19:32:20.720Z</atom:updated>
            <content:encoded><![CDATA[<h3>When it doesn’t work out — Failure and UX</h3><p><em>“Failure is the condiment that gives success its flavor.”</em> ― Truman Capote</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LAIGBXyn2zM4-1ws.jpg" /><figcaption>Photo taken from<a href="https://leadingwithtrust.com/2015/02/02/4-ways-to-transform-failure-into-success/"> Leading With Trust</a>, with permission</figcaption></figure><p>You thought you did everything right. Users were interviewed, stakeholders informed. You collaborated, refined the details of workflows and mind maps. Long afternoons were spent in Balsamiq then Sketch, refining the design that met both user need and the business proposition. You put your prototypes into InVision, then tested with some hastily-recruited users. The devs gave the green light, and it was build time. A sprint or two later, and there it was, on production, the culmination of hours of blood, sweat, tears, and Red Bull.</p><p>And a few months later the feedback came in: users didn’t like it. And as a result, stakeholders didn’t like it. Something was off. The design was a failure.</p><p>So now what?</p><p><strong>Failure as a learning tool</strong></p><p><em>“Success is stumbling from failure to failure with no loss of enthusiasm.” </em>― Winston S. Churchill</p><p>UX is a discipline with a heavy emphasis on <em>learning</em>. While the core principles of what makes a good interaction don’t vary too much, trends and new research play a huge role in determining how the next project is designed. Many designers I know chose this field because it keeps you on your toes; a good designer has a Feedly full of blogs, research, and influencers that continue to move the field forward.</p><p>However, I’ve found that many UX designers (self included) struggle when their work seems to fail. Even when designs aren’t total failures, designers are quick to point out the flaws that were never addressed, aspects mistranslated by stakeholders, or even how emerging design trends made their meticulously crafted solution outdated before it even hit production.</p><p>Instead of fixating on these perceived inadequacies, try a different approach. See how you can best approach a failure in a way that isn’t destructive, but constructive. If we expect our usability test subjects to be introspective and open, shouldn’t we be applying that to ourselves with our own work?</p><p><strong>Failure is a key part of the UX process</strong></p><p>“<em>It is fine to celebrate success, but it is more important to heed the lessons of failure.</em>” — Bill Gates</p><p>When I was preparing to enter UX fresh out of school, I asked my mentor at my then-internship what skills would be best for me to cultivate in the growing field. While I expected him to rattle off a list of UX buzzwords, the answer instead surprised me: “Treat failure as an iteration.”</p><p>UX is a field rooted in creativity. Failure is common in all creative work. Authors submit hundreds of query letters to agents and editors before getting that bite. New film directors hash out low-budget art films that are only screened in their parents’ basements. Creativity, by its very nature, leads to both some exhilarating successes and catastrophic failures. But what is important is to recognize that both sides of this coin are expected. You can learn a lot more from failure than success, and you can get much more motivated by success rather than failure.</p><p>As we put designs through user testing again and again, tweaking and refining until we think we’ve got it, each time we’re scrapping creative bits we thought were good for something better. So when a larger rework has to occur, we either can either crumble under the weight of its mistakes, or realize that it is just another step in the iterative process.</p><p>Besides, if everything went perfectly every single time, we would be out of a job.</p><p><strong>Use your Failure to teach others</strong></p><p><em>“Develop success from failures. Discouragement and failure are two of the surest stepping stones to success.”</em> — Dale Carnegie</p><p>I distinctly recall a time in college where a friend of mine was enamored with designing a car HUD (<a href="https://en.wikipedia.org/wiki/Head-up_display">heads up display</a>). We spent weeks working on a device, testing it, buying supplies, all culminating in a test drive to see if it worked.</p><p>It didn’t. It not only wasn’t successful, it nearly got us into a car accident.</p><p>After the incident I was still reeling from the experience, the adrenaline mixing with frustration that our idea had failed. My friend, on the other hand, was in surprisingly good spirits. When I asked how he could still be happy after a near catastrophic failure, he told me, “Yeah, it didn’t even remotely work. But think of the cool story we can tell people now!”</p><p>This may come as a shock, but you aren’t the only person with problems, especially in the UX space. In fact, a lot of your problems just <em>might </em>be the same as a lot of other people’s problems. And as part of a UX team (either your team of co-workers or the larger UX conglomerate) your missteps can provide enlightenment to others struggling with the same issues. There’s no better way to turn the sting of failure into the sweetness of success than by helping others improve.</p><p>The best mentors I’ve ever had didn’t just share success stories, they shared failures. They reflected on themselves to determine what went wrong and what went right, and could interweave both into a lesson on failure. Those lessons not only taught me how to avoid the pitfalls they’d fallen into, but also the value of non-critical self-reflection.</p><p>Mistakes will be made. Turn failures into success for others. Plus, like my friend said, at least you get to tell a cool story.</p><p><strong>Failure isn’t failure unless you let it be</strong></p><p><em>“Failure is the key to success; each mistake teaches us something.”</em> — Morihei Ueshiba</p><p><a href="https://positivepsychologyprogram.com/what-is-mindfulness-definition/">Mindfulness</a> is a pretty hot buzzword right now, though implementation of it might vary from person to person. In a general sense, mindfulness is an act of singular thinking and focus that attempts to decrease the “radio static” of thinking. But for many, mindfulness is more than just zeroing in on a singular point of thinking. It is, instead, a way of learning to separate the emotion from the reaction. In Buddhism, the combination of emotion or reaction can lead to <em>suffering. </em>But learning to separate the two can allow a more insightful look at both the emotion itself, and the cause of it. Perception is everything.</p><p>So must we be with failure. As designers, we try to view small failures as means to improve. A design didn’t test as well as we’d hope? Easy; use the feedback to improve it. But what about larger mistakes? It’s easy to take it personally, blame yourself (or others), or even fall to pieces as Imposter Syndrome runs wild .</p><p>It’s times like these that we need to take a step back, detach ourselves from the emotional sting, and reflect. Why did it fail? Where might we have had a misstep?</p><p>And most importantly, what am I going to learn from it?</p><p><strong>It’s time to be good UX designers</strong></p><p>Failure only remains failure if we refuse to improve because of it. In many ways, failure is our greatest teacher. And while we may feel defeated like Miles Teller’s character in the movie <a href="https://www.imdb.com/title/tt2582802/?ref_=fn_al_tt_1"><em>Whiplash</em></a>, if we can learn something positive then it wasn’t failure after all.</p><p>And before you know it, you’ve taken failure and turned it into a good User Experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9572b3712148" width="1" height="1" alt=""><hr><p><a href="https://medium.com/frontline-design/when-it-doesnt-work-out-failure-and-ux-9572b3712148">When it doesn’t work out — Failure and UX</a> was originally published in <a href="https://medium.com/frontline-design">Frontline Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>