<?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[GA UXDI-7 - Medium]]></title>
        <description><![CDATA[User Experience Design Immersive blog for homework, UX opinions, and portfolio notes. - Medium]]></description>
        <link>https://medium.com/uxdi-7?source=rss----a75f3d0103bd---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>GA UXDI-7 - Medium</title>
            <link>https://medium.com/uxdi-7?source=rss----a75f3d0103bd---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:22:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/uxdi-7" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Semantic Design]]></title>
            <link>https://medium.com/uxdi-7/semantic-design-8f71c25c8d66?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/8f71c25c8d66</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[John Thaler]]></dc:creator>
            <pubDate>Wed, 03 May 2017 15:13:12 GMT</pubDate>
            <atom:updated>2017-05-03T15:13:11.863Z</atom:updated>
            <content:encoded><![CDATA[<p>Good wires can help developers create semantic, SEO friendly, and accessible website because if layed out correctly, the wires already lend themselves to being turned into things like “Articles,” “Nav,” and “Asides.” Accessibility inherently helps with SEO because if you are writing alternative text for images on the page, that will all be found by search engines as well. I do not have any great examples of how accessibility contributes to SEO because I just learned about it last week, but below is a wire that might show how something could be broken up semantically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WHO--kMZc8DEKtF6WyeMVw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f71c25c8d66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/semantic-design-8f71c25c8d66">Semantic Design</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wait, data is…fun?]]></title>
            <link>https://medium.com/uxdi-7/wait-data-is-fun-e3e0eb1ba9c1?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/e3e0eb1ba9c1</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Sun, 30 Apr 2017 23:06:21 GMT</pubDate>
            <atom:updated>2017-04-30T23:06:05.435Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://invis.io/P3BIGV4U8">A Titanic deep dive.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBhbrvRMUO5wHWaDOPju1w.png" /><figcaption>White Star Lines Dashboard, <a href="https://invis.io/P3BIGV4U8">see full prototype in InVision</a>.</figcaption></figure><p>Armed with an excel spreadsheet and a bad attitude, I took (poorly) to visualizing data I felt James Cameron, Celine Dion, hideous purple jewelry, and the 90s in general had already tortured me with.</p><p>“You’re so stupid Rose!”</p><p>Barf. I hate Titanic.</p><p>Not one to pour over fictionalized tragedy, an exercise in actual tragedy was also a dark starting point. We were using a partial data set from the real passenger manifest of the Titanic, provided by our fellow data science students. The surface details of 890 souls aboard, their fates either a one or a zero in a long column. Tough stuff to get excited about. Not to mention my near paralyzing hatred of spread sheets. I fully grasp their function, but I‘m a spoiled designer and like fun, bouncy, pretty things.</p><p>Regardless, I got to it. First venting to anyone near me, “I am finishing this project tonight! And not spending another GD minute on this yadda yadda yadda…”. You get the point.</p><p>Yearning to take a creative route, and knowing this could be my last moment as a true student, <strong>I decided upon three historical proto-personas and stories. </strong>Why not?</p><h4><a href="https://invis.io/P3BIGV4U8">For a larger exploration, please see my prototype at InVision. &gt;</a></h4><h3>Story One</h3><p><strong>Man wanting to marry off his son.</strong> He’s looking for a young, available lady of equal, or higher, class status. They are traveling second class.</p><p>From the portion of the manifest we were given, Mr. West’s goal is pretty doomed on many levels. Even using the legal age to wed in 1912, <strong>(12 for girls (!) and 14 for boys), </strong>there would only be 18 young ladies available. Not to mention the remarkable competitive disadvantage of many, many more young men aboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*h-FB6VN7LSU-ncl36XL5nw.png" /></figure><h3><strong>Story Two</strong></h3><p><strong>Mom researching tickets for her family to voyage to America.</strong> She’s looking to go budget in either second or third class. Let’s hope she postponed the trip.</p><p>In actuality, this story revealed something pretty dark. When I dove into the largest families aboard their chances were some of the very worst.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*iayhzHF_hHGBbltSPRAiig.png" /></figure><p>The Sage family was a family of TEN people. Goodwin seven. Andersson, Asplund and Skoog, 6 people. All five members of the Rice family perished. In this entire group only 4 (women, all) survived in 40 total.</p><h3>Final Dive</h3><p>Finally, to acknowledge the dark root of the data set: <strong>A reporter trying to accurately report on the tragedy.</strong> Not interested in politicizing it, he wants to really articulate, visually, the true loss to England. The embarkment most affected (as my exploration in the numbers eventually reveals) by a horrifying level.</p><p>My final dashboard design was grounded most in this story, as it was a lot to unpack. The numbers continued to reveal deeper and deeper tragedy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDpGkxUftjr4_ylQgsX7TA.png" /></figure><p>Well, by the end of this exercise, I realized I had actually spent days down the data hole. Not only did I NOT HATE translating the numberic to the visual, I had truly enjoyed creating a dashboard.</p><p><strong>Daaang data, you got me.</strong></p><p><a href="https://invis.io/P3BIGV4U8">If you made it this far, you should really check out the InVision prototype.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kM8bN99bsv5DBVvAjpUjDg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3e0eb1ba9c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/wait-data-is-fun-e3e0eb1ba9c1">Wait, data is…fun?</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 8 Homework (Sysco Chatbot)]]></title>
            <link>https://medium.com/uxdi-7/week-8-homework-sysco-chatbot-703f9f4c940f?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/703f9f4c940f</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[John Thaler]]></dc:creator>
            <pubDate>Sun, 30 Apr 2017 19:26:28 GMT</pubDate>
            <atom:updated>2017-04-30T19:26:28.056Z</atom:updated>
            <content:encoded><![CDATA[<p>The first thing we did after collecting what the deliverables were and the requirements from our client on the MVP was to conduct comparative research on the various types and functions of chatbots already in existence. When we came back together after that we conducted affinity diagramming to try and determine ways to profile how possible users might use possible features of a chatbot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfFOpbZ6h6wTePzMo4aM0w.jpeg" /><figcaption>Affinity Diagramming</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5JS5CZlf9NoMlsaRNN6tPw.png" /><figcaption>Resulting Profile Chart</figcaption></figure><p>Using the profiles we decided to create two personas. We created a “Restaurant Owner” persona in order to make sure that all of the use cases provided by our client were met. We also created a persona for the chat bot so they we knew how the bot would interact with its customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3SLAmf3g6X_HLWxojugYg.png" /><figcaption>Restaurant Owner</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJct-htXVK7bwx0cX2eDcw.png" /><figcaption>Chatbot Persona</figcaption></figure><p>The next thing we did was lay out as many of the possible paths customers might take inside the chat bot UI as possible. We used XMind for the original process. We then printed out the “Site map” and taped it onto the wall to continue expanding each use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8ViUBAaSOeY5en6O2G2oA.png" /><figcaption>Original User Flows</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9RIGYsRTMCmLARX1gI2ocA.jpeg" /><figcaption>White-boarding additions to the chatbot flow</figcaption></figure><p>The next thing we did was create detailed user flows for each use case and begin creating prototypes for each one so that we could begin conducting user testing on Monday.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DU5KW7WdtKqftUPpgrwrdg.png" /><figcaption>Promotional Items User Flow</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwvEhQCTos04%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwvEhQCTos04&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwvEhQCTos04%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/98a86c9e1f061c0366494de975f1b6a9/href">https://medium.com/media/98a86c9e1f061c0366494de975f1b6a9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=703f9f4c940f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/week-8-homework-sysco-chatbot-703f9f4c940f">Week 8 Homework (Sysco Chatbot)</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JOG.AI]]></title>
            <link>https://medium.com/uxdi-7/jog-ai-9fc1df6d826e?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/9fc1df6d826e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Sun, 30 Apr 2017 06:52:48 GMT</pubDate>
            <atom:updated>2017-04-30T06:52:59.161Z</atom:updated>
            <content:encoded><![CDATA[<p>“Everything should be made as simple as possible, but no simpler.” -Einstein</p><h3>JOG.AI tells you, <strong>This Robot Takes Notes for You.</strong></h3><p>And it does! It’s great. JOG.AI captures transcripts of meetings, so you don’t have to take notes. This simple SaaS enables one to initiate a conference call, transcribes the meeting, separates individual speakers, and even allows you to mark important moments you can revisit and share later. Super, right?</p><p>Well, as tremendous as the service is, the interface suffers an odd challenge. <strong>JOG is so simple, it’s practically skeletal. </strong>No featuritis here. So, after a initial chat with founder and product owner, Sam Gaddis, our team members were all on the same page. The challenge clear: IxD this mother and onboard his lovely site. Retain that repeat audience by giving users a confidence in the product. JOG as a business tool should be friction free, second-nature, and above all, really useful.</p><p>JOG can afford some affordances. For starters: the central dashboard is austere. Features <em>are</em> there, they just needed a little nod.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TUn3LCQHgH_w0XOacc_VSw.png" /></figure><p>Helpfully, you can tag conversations, but this isn’t apparent until you hover. “Manage Conference Call” and “Create Conversation” are long-winded indicators, and what they really lead to isn’t clear. After clicking “Create Conversation”, you seem encouraged to upload audio as it’s the brightest button around. Great feature to offer, but does it qualify as starting a conversation, like the button suggests? I’m not so sure.</p><p>When you click “Manage Conversation” a bright arrangement of Quick Markers greet you. And a less obvious prompt to maybe(?) click a phone number? The page offers very little instruction on how to actually manage your conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AhYnHrYVucJsVgQ_jvWDyQ.png" /></figure><p>Finally, the last big engagement for users is the Conversation page. A colorful array of segmented transcripts and speaker information. All of this is helpful, but scattered wide compared to previous pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQbpg79ZxZ3GygmrQYQQEA.png" /></figure><p>The Conversation page also features some hidden gems. Renaming your call is a hidden clickable option, and the “Merge Adjacent Speakers” button is below the fold on a laptop. And what does “Merge Adjacent Speakers” mean, really? I think I may know, but I’m definitely not 100%.</p><p>All said, JOG.AI keeps to a slim structure. With some time spent, a user can definitely uncover its many useful functions. But who’s needs that? A little attention spent on hueristics would elevate the entire JOG experience.</p><h3>Iterate good calls, come on!</h3><p>With a little over 2 weeks to present JOG’s improved UX, we need to LEAN real far in. Flow and iterate, rinse repeat. In order to test our story (based on proto-personas, and flows) we got to sketching immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_b3lHdGDgGDTenuMP4T7kQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SxrTACPYtXh46aBtGnvlaw.jpeg" /></figure><p>One thing becomes obvious through our many sketches. Build up an enhanced, clear dashboard to center the sites actions from. Designate taxonomy and commit to some obvious navigation. From our sketches, medium fidelity options are being tested, see sample screens below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*Qx3Wpk9HU2GzsdktvR-zAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*D8Bx8YpvNAhe1n-LaBVQAA.png" /></figure><p>So here we are, at the end of week one of our onboarding. Evaluative research coming soon! And responsive versions! ’Cause we all use our mobiles to make business calls these days, amiright?</p><p>Hold please.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fc1df6d826e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/jog-ai-9fc1df6d826e">JOG.AI</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum: the sequel]]></title>
            <link>https://medium.com/uxdi-7/scrum-the-sequel-a58aac19bbb?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/a58aac19bbb</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Sun, 09 Apr 2017 18:46:14 GMT</pubDate>
            <atom:updated>2017-04-09T23:43:46.320Z</atom:updated>
            <content:encoded><![CDATA[<p>Subtitle: Strenths and less-strengths.</p><p>The scene: So you are well down the path, your MVP comes into focus here and there, like an oasis over the next dune. Your sprints are moving from “in-progress” to “completed”, user stories guiding your flow, and your sketches, wires are filling out, making the whole process whir like the nice buzz of a happy machine.</p><p>But suddenly there is a metaphorical screeching of brakes. A big, confirmed idea suddenly lost its foundation. While pouring over our “Wall of Wires” our team realized that each of us had an entirely different idea about a particular function of our site. Without upending a happy team, we realized it needed to pause work, and get addressed immediately.</p><p>For our goal, and most specifically for our deadline, we needed to reprioritize our sprints. In the luxury of letting every team member dip their toes in many pools (we are students after all, everyone had taken a bit of research, a bit of design, a bit of competitor analysis) we’d lost some precious time and a realized we’d need to commit to some distinct tasks.</p><p>In the moment, this restructuring didn’t look so orderly, but looking back I realized our team, in declaring our strengths and weaknesses, commited to roles. Division of labor, if you will. As a seasoned visual designer, I took on the getting some of our composition elements in order: finish the wires, make sure the design would be bootstrap ready, and get the logo cleaned up. (Just get that sprint over and done with, it was so close). Phil, our analytic thinker, took the overwhelming task of cementing the site map, and became our editor extraordinaire. While Natalie tied up our profile research, creating our various personas and each individual flow.</p><p>In the moment it was more knee-jerk than this orderly description. But in the end, this decisive path-taking took us the the scrum finish. <br>End scene. Sunset, roll the credits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a58aac19bbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/scrum-the-sequel-a58aac19bbb">Scrum: the sequel</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrummin’ it]]></title>
            <link>https://medium.com/uxdi-7/scrummin-it-2e98f370bd63?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e98f370bd63</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Sun, 09 Apr 2017 17:42:30 GMT</pubDate>
            <atom:updated>2017-04-09T17:42:03.903Z</atom:updated>
            <content:encoded><![CDATA[<p>For our collaboration with the Development Team (WDI) we took our first crack at an Agile work environment, embracing the Scrum process. Our team’s challenge: <strong>create a website for school nurses and doctors to communicate in an urgent care-type capacity, with a portal for parents to sign up their children</strong>. Without the guide of a seasoned Scrum Master, or actual Product Owner, first time self-guided methodology is not so different from stabbing in the dark. But being capable, motivated and well adjusted, we did out best to embrace the process, even as novices.</p><p>Knowing we had weeks of design work to complete before we could actually pass our deliverables to the Dev team, we agreed on check-ins and progress reports for them. Show them user stories, flows and lo-fi mockups in a few days, wires by the end of week one, with a fully developed design, packaged for hand-off, by the deadline.</p><p>Determining the overall scope, we found it helpful to work backwards. We need a dev-friendly, high fidelity mockup packaged in 2 weeks? Well we took to our boards, and task boxed “completed hi-fi Sketch mockup”, due the day before. After that we reversed tasked the project, lo-fi, wires, paper sketches, personas, profiles, and on. Eventually we landed on research as our first step. Brainstorming and listing our various resources, we assigned sprints for each design team member daily. The sprint might be just to show progress on a particular task. We worked our way toward our goal, a little at a time, over the broad surface of our project.</p><p>Our team really embraced the Stand Up. At the beginning of the work day and at close, we would share what we did, what we were going to do, and blocks if we had them. This was by far and away the most helpful portion of the Scrum process for me personally. The sense of attainable sprints, team accountability, and check-in/pleas for help were a great way to not let any one team member drift too far for too long. This twice-daily refocus was the gift Scrum gave me for the project, and something I intend to embrace for future collaborations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e98f370bd63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/scrummin-it-2e98f370bd63">Scrummin’ it</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum and my UX Process]]></title>
            <link>https://medium.com/uxdi-7/scrum-and-my-ux-process-ff8f6ad12ada?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/ff8f6ad12ada</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[John Thaler]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 12:05:28 GMT</pubDate>
            <atom:updated>2017-03-29T12:05:27.923Z</atom:updated>
            <content:encoded><![CDATA[<p>I do not believe that scrum affects my UX process too much. From day 1 I have naturally leaned into what could be called an agile process and the only thing scrum really requires me to do differently is to track my progress on a Trello board and collaborate more. Since I started UX I have tried to complete small tasks and user test them without realizing that was already a system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff8f6ad12ada" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/scrum-and-my-ux-process-ff8f6ad12ada">Scrum and my UX Process</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WebMD needs help. STAT.]]></title>
            <link>https://medium.com/uxdi-7/webmd-needs-help-stat-289e80ad6efa?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/289e80ad6efa</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[iteration]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 06:14:26 GMT</pubDate>
            <atom:updated>2017-03-20T06:14:04.836Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRR5BTwzk8963Ec1GLfUEA.jpeg" /></figure><p>WebMD has plenty of traffic, sure. But how many people feel either fed-up or panic-stricken when they eventually disengage from the digital sinkhole that is WebMD? The answer was MOST people, when we asked.</p><p>Self-diagnosing hobbyists usually start at Google, but the majority end up at WebMD. From there they are treated to an onslaught of format changes, advertising minefields and thousands of possible search results and unrelated articles for something as common as a sore throat.</p><p>To tackle the anxiety-inducing site, my project partner Jonathan and I began by interviewing users. With these results we generated affinity and mind-map nominal groupings. Finally, we created empathy diagrams for specific users: a man seeking reassurance on a recent diabetes diagnosis, a mother looking up a prescription for her child, and a college-age man with common symptoms: a cough and sore throat. Each path we took for our users through the website brought us to the same conclusion. <strong>WebMD is frustrating.</strong></p><p>We identified our goal: make the site more comforting and trustworthy with improved structure. Reduce advertising real estate on the site. <em>Instead</em> promote an on-demand consultation service, <strong>the Video Doc, </strong>as an revenue alternative users will actually appreciate.</p><h3>Early Sketches</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fr8jew3B4s403bp50v5fjQ.jpeg" /></figure><p>Early iterations included emphasis on searching. The big reason to visit the site. As seen left, a large search bar was made prominent, menus became large content areas, and advertising reduced from immediate prominence.</p><p>While simple, it was too partitioned and far from intuitive. The structure didn’t work well when applied site-wide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*psyzJnBYFLk6MQSDwetHgA.jpeg" /></figure><p>Our next iterations were called the “polite site”. Simple, conversational language was used to reassure and encourage visitors on their path. Be nice, even suggest they don’t self-diagnose, let our Video Docs help. They are always available.</p><p>Advertising was moved lower on the page, especially for search result pages. In research, our users especially didn’t appreciate having to search for their search results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*laxU5UuiE-7aLCBp1qTMjg.jpeg" /></figure><p>Before beginning our wireframes, we employed a three column look to the site, even for mega-menus. Home and secondary pages all kept to a 2/1 look, emphasizing important, featured content and the Video Doc.</p><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVTc5pEIARhRHDZb2QUuVg.png" /><figcaption>Home Page / first iteration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FavA-XdFfEcVkfc5jwcpiQ.png" /><figcaption>WebMD / the “polite site”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*2LBgRHeyap8rVBWxeGVxLA.png" /><figcaption>Video Doc / chat window and scrolling transcript</figcaption></figure><p>Our wireframes went through multiple iterations. One particular modal was… well, reviled by users, and tossed immediately. Our “polite site” wasn’t always seen as professional enough, users didn’t trust a medical site that was overly casual.</p><p>Finally, we felt our WebMD redesign hit on a nice balance of reassuring and innovative. Users appreciated the Video Doc, the ease of interaction, especially with an insurance option, and many found the consistent layout easier to navigate and more trustworthy. Users made clear they would visit, and revisit, the site we proposed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*1WppIrR5ovPfv6edXcO-ZQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=289e80ad6efa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/webmd-needs-help-stat-289e80ad6efa">WebMD needs help. STAT.</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Portfolio time, run and hide.]]></title>
            <link>https://medium.com/uxdi-7/portfolio-time-run-and-hide-c3b287972969?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/c3b287972969</guid>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 03:15:26 GMT</pubDate>
            <atom:updated>2017-03-20T03:15:11.491Z</atom:updated>
            <content:encoded><![CDATA[<p>Killing yourself for a client, deep diving and iterating for the umpteenth time is what we do. Indeed <em>who</em> we are, right? And even on hard days it feels great to move a project forward, getting an idea closer and closer to <em>right.</em></p><p>But when it is time to do that for yourself? It is so. damn. hard.</p><p>I’ve put together numerous portfolios through the years. Heavy, physical ones in expensive leather covers were once the fashion. Now one is expected to have a clean, polished digital presence. Before re-inventing my portfolio <em>yet again, </em>I decided to really peer into many I found truly successful. One I particularly enjoy is <a href="http://joshuataylordesign.com/">the portfolio of Joshua Taylor</a>, product designer and startup advisor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSbxp4CPkKPq9gFIPrtBZQ.png" /><figcaption>Snowball / smart notifications app for Android</figcaption></figure><p>Joshua’s site is simple and lovely, yet full of remarkable content, due of course to the incredible projects he’s worked on.</p><p>Employing full-width color fields and images, in a consistent formula, the site’s structure works to amplify the work. One can easily navigate directly from the homepage to individual case studies, leading to bright, attractive explanations of his role in each project, the challenge faced and the process employed to solve them. Each project is easily segmented to flow naturally and highlight content, making text easy to read and follow. Projects are described with historical context, goals, strategy, process and glowing testimonials.</p><p>Literally my only complaint after scouring Joshua’s site is of a headline font size. Rather than offering a raving review, the font size seems to shout it.</p><p>Regardless, I recommend anyone to check out <a href="http://joshuataylordesign.com/">Joshua’s terrific work</a>. I think I’m sufficiently inspired to start framing out my own portfolio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3WNEWiwTnFNKrmwFPo9zIA.png" /><figcaption>Evernote Penultimate / iPad writing experience app</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3b287972969" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/portfolio-time-run-and-hide-c3b287972969">Portfolio time, run and hide.</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pronto Coffee]]></title>
            <link>https://medium.com/uxdi-7/pronto-coffee-d27f2e56631?source=rss----a75f3d0103bd---4</link>
            <guid isPermaLink="false">https://medium.com/p/d27f2e56631</guid>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Amanda Smith]]></dc:creator>
            <pubDate>Mon, 06 Mar 2017 14:59:09 GMT</pubDate>
            <atom:updated>2017-03-08T21:08:17.450Z</atom:updated>
            <content:encoded><![CDATA[<p>Local, Independent, Fast.</p><p>As my first foray into UX app design, exploring coffee, and coffee-ordering, was a great spring board. The downtown Austin area is littered with a wide variety of coffee-slinging spots, providing a perfect research base. In just a few blocks one can find high-end cafes, bare-bones joints, etablished franchises, and personable, independent shops in abundance.</p><p>Beginning in the field, I observed 3 locations over the course of a couple hours. 1886, the lovely historic cafe in the Driskill Hotel. Followed by The Hideout, an independent theater and cafe, unassuming and casual. My third location was your classic, bustling Starbucks. At each location I spoke to either the staff or the patrons, allowing me a deeper dive into a world of coffee most of us know, but may experience differently.</p><p>While I interviewed people devoted to Starbucks, including their pre-order app, I found a group of coffee drinkers in need. Specifically, those people for various reasons prefer independent, locally owned coffee shops. Through observation, interviews, affinity diagrams and empathy mapping I developed an app prototype. <strong>My app’s goal: an easy, intuitive path for users to pre-order quality coffee from a network of independently-owned cafes</strong>. Busy folks could still feel good about supporting their local “little guy” coffee shop, even if they were just flying through. A reason some gave for reluctantly using a larger franchise like Starbucks, the easy, fast capability they can provide.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fmarvelapp.com%2F543751h%3Femb%3D1&amp;url=https%3A%2F%2Fmarvelapp.com%2F543751h%2Fscreen%2F25506702&amp;image=https%3A%2F%2Fmarvelapp-live.storage.googleapis.com%2Fserve%2F2017%2F3%2F7641a860414f789d96f3693678d9c9.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=marvelapp" width="452" height="925" frameborder="0" scrolling="no"><a href="https://medium.com/media/781d235590dee088c9bb3b57ac89f95d/href">https://medium.com/media/781d235590dee088c9bb3b57ac89f95d/href</a></iframe><p><a href="https://marvelapp.com/543751h/screen/25506702">See the entire flow of Pronto prototype here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d27f2e56631" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxdi-7/pronto-coffee-d27f2e56631">Pronto Coffee</a> was originally published in <a href="https://medium.com/uxdi-7">GA UXDI-7</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>