<?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 Ramy Nassar on Medium]]></title>
        <description><![CDATA[Stories by Ramy Nassar on Medium]]></description>
        <link>https://medium.com/@ramynassar?source=rss-ed8bf69d8cf5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cBo07QYWM84LR4Ty8oMgTw.jpeg</url>
            <title>Stories by Ramy Nassar on Medium</title>
            <link>https://medium.com/@ramynassar?source=rss-ed8bf69d8cf5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:07:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ramynassar/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[An Irregular Approach to Travel Innovation]]></title>
            <link>https://medium.com/@ramynassar/an-irregular-approach-to-travel-innovation-9102dd274993?source=rss-ed8bf69d8cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9102dd274993</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[recovery]]></category>
            <category><![CDATA[márketing]]></category>
            <category><![CDATA[tourism]]></category>
            <dc:creator><![CDATA[Ramy Nassar]]></dc:creator>
            <pubDate>Wed, 01 Sep 2021 14:21:27 GMT</pubDate>
            <atom:updated>2021-09-01T14:21:27.830Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the story of two radically different approaches to pandemic recovery from the travel &amp; tourism sector.</p><p>First, we have Delta Airlines. Last week, <a href="https://www.businessinsider.com/delta-ceo-still-wont-say-delta-variant-2021-8">Business Insider</a> reported that Ed Bastian, Delta’s CEO, refuses to refer to the Delta variant of COVID-19, instead calling it by its more technical name — B.1.617.2. Further, Delta’s chief health officer even went on the record claiming that <a href="https://twitter.com/henrytingmd/status/1410053144210558976">“B.1.617.2” is “easier to say.”</a></p><p>At the same time, while travel industry executives are trying to spin COVID to align with their corporate brand, we have a story of real innovation.</p><p>Last week, while in Fonthill, ON, Canada for a wedding, I stumbled upon a beautiful coffee shop called <a href="https://www.thetravelcafe.ca/">The Travel Cafe</a>. I was warmly greeted by the owner, <a href="https://www.linkedin.com/in/lorrainesimpsontravels/">Lorraine Simpson</a>, when I entered. It only took my a moment to realize that the travel-inspired decor was more than just artwork. <em>In fact, The Travel Cafe is a travel agency that pivoted to become a coffee shop!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jg6K0qxBr8B2TZyGSYhkMg.png" /><figcaption>Even the house blend has a unique travel theme — can’t help but want to fly to Italy!</figcaption></figure><p>In the midst of a global pandemic, this little “mom &amp; pop” travel agency took out loans to buy a high-end cappuccino machine and encourage members of the community to come in and dream up their next vacation. That’s innovation! Innovation is so much more than leveraging emerging technologies — it’s about adapting to what your customers want, and uncovering new business models to deliver on that promise.</p><p>So what can innovators and leaders in the travel &amp; tourism industry take away from this?</p><p><strong>First, remember that it’s about discovering new business models.</strong> The team at the Travel Cafe decided that opening a coffee shop would let them drive some revenue, engage with customers, and position themselves perfectly for when travel could resume.</p><p><strong>Second, think about how to deliver value to your customers.</strong> Trying to “rebrand” a particular variant of this deadly virus does nothing for Delta flyers — past or future. The team at The Travel Cafe instead decided to begin traveling the world and sharing their best practices about how to cross borders, safely, with their online community. Offering aspiring world travelers with practical tips on how to navigate the often confusing &amp; contradictory world of international vaccine &amp; testing protocols helps create value and will ultimately drive their core business in the years to come.</p><p><strong>Finally, take some risks!</strong> I can only imagine what would have been going through the minds of the Travel Cafe team over the past year. Revenue completely dried up. Rather than closing shop, the idea was to start a new venture — in a similarly challenging industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omz_ABWJ6sW9ooyxjaL1PQ.jpeg" /></figure><p>So what’s the takeaway here?</p><p>Try new things. Take some leaps. Validate concepts with users, early &amp; often. Innovation doesn’t happen overnight but also shouldn’t take months or years to bring new concepts to market.</p><p>Has the their bet paid off? It’s probably too early to tell. But as I reflect on these two completely approaches to innovation, I certainly feel inspired by the agile and customer-centric nature of what the Travel Cafe team has done. I can only hope that others in the travel &amp; tourism sector begin to think differently about what this industry means for customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9102dd274993" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everyone’s Guide to Designing Great Conversational Interface Experiences]]></title>
            <link>https://uxdesign.cc/designing-great-conversational-interfaces-89ac70fcb611?source=rss-ed8bf69d8cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/89ac70fcb611</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[conversational-ui]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Ramy Nassar]]></dc:creator>
            <pubDate>Tue, 26 Sep 2017 18:32:03 GMT</pubDate>
            <atom:updated>2017-10-04T06:16:48.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*3d8jNWc87M12wTGbBaC4GQ.png" /><figcaption>Air Travel Chatbot</figcaption></figure><p>Conversational interfaces (CIs) are rapidly shifting how consumers interact with brands, and the vast range of CI platforms is making poses a lot of challenges for organizations trying to embrace the technology. While there are a range options ranging from facebook messenger chatbots to Amazon Alexa voice user interfaces (VUIs), certain design elements remain consistent across platforms.</p><p><strong>1. Why Are You Designing a Conversational Interface?</strong></p><p>The first consideration is an honest understanding of what problem you’re trying to solve and who your intended users are. Why would these users interact with a CI instead of more traditional channels (email, call centre support, etc.)?</p><p>A true understanding of who your users are their unmet needs will ensure that the CI you design resonates with customers and increases the likelihood of strong user adoption.</p><p>The ideal way to gain this understanding is to speak directly with your target users. User interviews, focus groups and surveys all present specific methodologies to help collect qualitative data that should inform the design of your CI.</p><p>Quantitative research is equally important and can take the form of web analytics, call centre data and user/customer call histories. Analyzing historic data of how your customers have interacted in the past (across a range of channels) can inform how they would be most likely to communicate with a CI.</p><p>A combination of quantitive and qualitative research will help ensure that you’re building a contextually relevant CI. Where possible, primary research (interacting directly with your customers and their data) will result in more meaningful results than secondary research (reviewing research studies or evaluating competitive systems).</p><p><strong>2. Consider the Range of CI Platforms</strong></p><p>While there are a range of CI platforms, one of the key ways to segment these platforms is between text-based and voice-based systems.</p><p>Text-based CIs (known as chatbots) are more evolved, and as such, there are a range of common platforms. While not an exhaustive list, some of the platforms include:</p><ul><li>Facebook messenger</li><li>Skype</li><li>Whatsapp</li><li>Slack</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*xW2U8gueMsEuy-Z3OfHQGQ.jpeg" /></figure><p>When it comes to voice-based systems, there are a few main platforms:</p><ul><li>Amazon Alexa</li><li>Apple Siri</li><li>Google Home</li></ul><p>Each of these voice-based systems requires more specific and deeper technical integration. For that reason, some thought should be given to an abstraction platform that allows organizations to create a conversational data layer that defines an interaction architecture that is agnostic to a range of CI platforms. <a href="http://www.api.ai/">API.ai</a> is commonly used to provide some scale and future-proofing when it comes to designing Cis.</p><p><strong>3. Evaluate CI Design Patterns</strong></p><p>Conversational interfaces can take a wide range of forms, and depending on the context for which you’re designing, consideration should be made to the most appropriate approach.</p><p><strong>Question &amp; answer</strong></p><p>In this design pattern, a user is taken through the interaction process in a step-by-step manner. Designing a Q&amp;A CI involves creating a decision tree outlining the different paths that a user can proceed down.</p><p>In general, the questions that the CI asks of the user should be close-ended questions, rather than open-ended. Close-ended questions reduce the risk of your user responding in a manner that the CI does not understand.</p><p><strong>Menu-based CI</strong></p><p>Menu-based interfaces resemble traditional interactive voice response systems (IVRs) that we’ve all experienced while dealing with a central customer support line. Traditionally, these have taken the form of “dial 1 for sales, dial 2 for service…”</p><p>When you don’t necessarily know a great deal about why your users are seeking support, or they may not know the full range of options available to them.</p><p>Depending on the specific CI platform you’re employing, certain considerations should be made. For example, Amazon Alexa does not permit users to interrupt, so if you’re providing a list of 3 or more options, users may get frustrated waiting through the full list of possibilities.</p><p><strong>Intelligent menu CI</strong></p><p>Intelligent or secret menu patterns involve asking your user a question, without explicitly providing a list of the potential answers. Apple’s Siri voice-based CI is a common example, given the wide range of actions that Apple’s assistant can provide.</p><p>The intelligent menu pattern works well when there are a range of choices, but the options are all contextually related and relatively predictable.</p><p>An example where this pattern would work well is contacting your mobile phone carrier. While there are a wide range of options (add-on services, technical support, cancel a subscription, etc.) users generally have an idea of what they are looking to accomplish, and it’s unlikely for any “left-field” requests to come in.</p><h4><strong>Take the Next Step</strong></h4><p>Once you’ve completed some initial research and thought through not only how the CI should work, but also what platform(s) will best resonate with your users, it’s time to take the plunge.</p><p>Where possible, consider prototyping the solution in advance of doing a full build and release. There are a range of rapid prototyping tools for both chatbot-based and voice-based CIs. The tools below all work without the need for coding or technical development. While the list is increasing almost daily, some of the top runners in this group include:</p><ul><li><a href="http://www.chatfuel.com/">Chatfuel</a></li><li><a href="https://www.chattypeople.com/">Chatty People</a></li><li><a href="https://www.motion.ai/">Motion.ai</a></li></ul><p>When it comes to voice-based CI prototyping, there are fewer options, but Amazon has recently created the Lex platform for prototyping both voice and text-based CIs. For additional approaches to prototyping and validating a conversational interface application, you can consider looking at a product development company with deep expertise in CI, such as Toronto’s <a href="http://www.connectedlab.com/">Connected Lab</a>.</p><p>Finally, keep in mind that launching your CI is just the first step. It will be important to get real-world feedback on how users are embracing the tool and continue to evolve the system based on this feedback.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89ac70fcb611" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-great-conversational-interfaces-89ac70fcb611">Everyone’s Guide to Designing Great Conversational Interface Experiences</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Agile scares the shit out of executives]]></title>
            <link>https://medium.com/@ramynassar/why-agile-scares-the-shit-out-of-executives-bd9ef684a753?source=rss-ed8bf69d8cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9ef684a753</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Ramy Nassar]]></dc:creator>
            <pubDate>Thu, 19 Jan 2017 15:17:00 GMT</pubDate>
            <atom:updated>2017-01-19T15:17:00.304Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zby3KynME9QGDJmWHz0lA.jpeg" /><figcaption>It’s funny how calling a meeting a Scrum instantly makes a team “Agile”</figcaption></figure><h3>Why Agile scares the $#@ out of executives</h3><h4>Understanding the differences between real and perceived risk in digital product design</h4><p>Executives, across industries love talking about Agile. But why is it that Agile remains mostly an out-of-grasp illusion in most enterprise organizations? Confined to internal labs or innovation departments, Agile has yet to become mainstream in most companies.</p><p>Let’s start by talking about what Agile is, and what it isn’t. Agile is a mindset, rather than a step-by-step methodology, for solving particular types of problems. Specifically, I want to talk about Agile in context of building digital products. Agile is not the only way to create digital products, nor is it always the right way to do it.</p><p>At its core, Agile acknowledges that we don’t always know exactly what we need to build. While we have an idea of what problem we’re trying to solve, we don’t yet fully understand how that solution should work. <strong>This is ok.</strong> In fact, by embracing this simple truth, we can bring solutions to market faster, that are more in-tune with user needs.</p><p><strong>When we don’t use Agile</strong></p><p>Before we dive into the scary parts of Agile, let’s talk about the alternative. Instead of embracing the uncertainty, the alternative is to plan every feature in advance. In most organizations, this type of work results in deliverables such as BRDs (business requirements documents), SRSs (software requirements specifications), and other awful three letter acronyms.</p><p>By doing a lot of up front planning, we create the illusion of certainty, and thereby, the illusion that our product will be a success. Knowing in advance exactly how the product will function and how every feature will behave makes intuitive sense. But what happens if our vision for the product doesn’t match our users’ needs — or those needs change over time?</p><p>The figure below is my attempt at illustrating how Agile carries a lot of perceived risk up front, but that it drops quickly as the initiative progresses. more traditional approach, on the other hand, feels very safe at the outset, but can take less predictable turns after product launch/release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjSemdKOa2aHGwFrtOMlow.jpeg" /><figcaption>How traditional product development approaches give us the illusion of reduced risk, but ultimately can be hard to predict. What products have you seen that sounded great, but flopped upon release?</figcaption></figure><p>Agile acknowledges that sometimes requirements change. This typically happens for one of two reasons. Either a user’s needs evolve or we never understood those needs in the first place. Either way, Agile gives us a framework for dealing with changing requirements, in pseudo-realtime.</p><p><strong>The role of a business executive</strong></p><p>The core responsibility of an executive in any enterprise organization is to control and mitigate risk. There is, however, a distinct difference between perceived and real risk. A traditional Waterfall approach reduces perceived risk by looking for certainty upfront.</p><p>Agile, on the other hand, was developed to mitigate real risk. By understanding that needs change (or in many cases were never understood), Agile allows the product to pivot throughout the development cycle.</p><blockquote>“We must learn what customers really want, not what they say they want or what we think they should want.”</blockquote><blockquote>Eric Ries, The Lean Startup</blockquote><p>One major risk is that we build a product according to requirements that users don’t actually want. There are countless examples of these products, and I’m going to resist bashing any of them in this article. It’s what happens when we don’t talk to end-users or when we make assumptions about what they want or need.</p><p><strong>Agile as a risk reduction strategy</strong></p><p>Agile acknowledges that the path to get to a final product may be non-linear, or the route may change. By considering this fact, we can adapt the approach mid-stream. This is the scary part. This approach requires a fundamental shift in mindset and an appreciation that there may be bumps along the way.</p><p>However, when done right, this approach helps risk decrease over time, in a predictable manner. The figure below tries to illustrate how the methodologies differ with respect to real risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dmhW2eY5h7q3QALPr7pT4g.jpeg" /><figcaption>At the onset of an Agile product development effort, we acknowledge some level of uncertainty and in doing so, with an iterative focus on learning &amp; pivoting, risk decreases over time — sprint by sprint.</figcaption></figure><p>By continuously correcting the product direction through the development cycle, product owners and decision makers can reduce the real risk associated with product design.</p><p>I’ll say it again: <strong>Agile scares the $#@ out of executives</strong>. One reason for this is that milestones and other traditional artifacts associated with project management may be less clear. Rather than a project manager confidently announcing that milestone X was hit on time and on budget, the Agile project manager may instead run a sprint demo illustrating the current state of the product — mid-development.</p><p>With a focus on building the highest-value features first, early product demos can seem a bit abstract. That said, if the product lead is successful, every sprint will move closer towards the ultimate goal of building the right thing. As the product team continues to learn from early customer feedback &amp; testing, confidence in eventual user adoption should increase; and risk therefore starts to decrease.</p><p>In closing, I’ll admit this is <strong>much easier said than done</strong>. It requires strong buy-in from senior project stakeholders and a willingness to fail throughout the process. So the next time you propose an Agile approach, remember that a part of your role is to help stakeholders differentiate between real and perceived risk.</p><p>Finally, I should make a small note about terminology. While I use the term Agile in this article, it’s important to acknowledge that a modern approach to digital product development needs more than just Agile. It should incorporate best practices from the worlds of Lean Startup, Design thinking and Agile development. Those familiar with these schools of thought probably recognize references to them throughout the article.</p><p>By day, I’m the Managing Director at an integrated Strategy, Design and Technology firm, <a href="http://www.architech.ca/">Architech</a>, based in Toronto. By night, I play around with Machine Learning algortihms and muse about the nature of product development methodologies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9ef684a753" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On leading a new kind of UX workshop]]></title>
            <link>https://uxdesign.cc/a-new-kind-of-ux-workshop-8e74b801d8ff?source=rss-ed8bf69d8cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e74b801d8ff</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Ramy Nassar]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 17:14:22 GMT</pubDate>
            <atom:updated>2016-11-04T18:10:30.413Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RMcpeaJLoi7cwLmf0nuynw.jpeg" /><figcaption>The beautiful city of Graz, Austria where the conference took place</figcaption></figure><p>On an ordinary Monday, in a conference room in Austria, a group of forward-thinking designers and usability specialists gathered for a full day workshop on the art and science of getting buy-in for UX design.</p><p>I was asked by the <a href="http://www.worldusabilitycongress.com/">World Usability Congress</a> team to lead this workshop. We brought together exercises and case studies ranging from persuasion skills to executive presentations; from sales strategies to negotiation tactics. The result was nothing short of inspiring!</p><p>I’d like to share three of the key learnings that I hope the group took away from the workshop.</p><h4><strong>A refresher on empathy</strong></h4><p>Design and UX design in particular, is deeply rooted in user empathy. So why is it that designers so often forget that internal &amp; external stakeholders are people too? Whether it’s a client or an internal project executive, it’s important to apply the same principles of empathy and understanding when seeking buy-in or approval for UX design.</p><p>Using a fantastic set of toys designed by Canadian social entrepreneur Ilana Ben-Ari, we ran through a range of exercises intended to remind participants that every person involved with a project has certain goals that she or he is trying to accomplish. The Empathy Toy was created to leverage <a href="http://twentyonetoys.com/pages/our-philosophy">play</a> as a tool for discovering (or rediscovering) empathy.</p><p>Only by understanding what every stakeholder considers a successful outcome will it be possible to get agreement on design decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_pHfH3ugmoN_iEBv2jS9dw.jpeg" /><figcaption><a href="http://twentyonetoys.com/">The Empathy Toy</a>, seen in use above, was developed by Twenty One Toys in Toronto.</figcaption></figure><h4><strong>Structured model for presenting designs</strong></h4><p>While there are a broad range of techniques for presenting design work and seeking agreement, very few designers use a structured approach.</p><p>Leveraging a methodology proposed by Tom Greever, author of <a href="https://www.amazon.com/gp/product/1491921560/ref=as_li_ss_tl?ie=UTF8&amp;linkCode=sl1&amp;tag=tgcom-20&amp;linkId=84214e9d9eb43548e949ad37c2e43f6c">Articulating Design Decisions</a>, participants worked through a real-world design project, where small groups were challenged to “pitch” project executives for additional investment into the design process.</p><p>A major component of this structured approach can be summarized by the acronym <strong>IDEAL</strong>, which helps practitioners remember how to structure their communications plan.</p><p><strong>I</strong> — identify the problem <em>— ensure agreement from all parties on what the problem really is</em></p><p><strong>D</strong> — define the solution</p><p><strong>E</strong> — empathize — <em>not just with end users, but with all project stakeholders</em></p><p><strong>A</strong> — appeal to the business — <em>connect your design decisions with project success metrics</em></p><p><strong>L</strong> — lock in agreement — <em>save time to present and agree upon next steps and accountability</em></p><p>The final two steps are often overlooked, because as designers, we’re not always taught the importance of business context. In the world of sales, the final step would be called <strong>closing the deal</strong>, and is what separates great salespeople from merely good ones.</p><h4><strong>Executive presentations</strong></h4><p>Presenting your work to a group of executive stakeholders needs to be done differently than a design review or sprint demo.</p><p>We began this part of the workshop with a refresher on <a href="http://www.myersbriggs.org/">Myers Briggs Personality Types</a>. In particular, looking at the Sensing and Intuitive approaches to gathering data. Business executives are disproportionally represented by intuition-based data gatherers.</p><p>As a result, when presenting to intuitors, rather than sensors, it’s important to focus on the big picture and the meaning behind the design. Avoiding details and focusing on the future impact of your work to the organization helps get agreement from executives and decision-makers.</p><p>We wrapped the workshop with a set of executive presentations in which team members used the culmination of the skills developed through the day.</p><h4><strong>Wrapping up</strong></h4><p>As much as was learned from the exercises, participants were rewarded to discover that the challenges that they faced were common amongst practitioners from all walks of life. Stories of success and failure were shared throughout the day, and just about everyone in the room could relate to some of the challenges faced by their peers.</p><p>It was an inspiring day to lead-off this year’s <a href="http://www.worldusabilitycongress.com/">World Usability Congress </a>in Graz. To learn more about the workshop or for information on our integrated approach to strategy, design and engineering, please visit <a href="http://www.architech.ca/">Architech’s site</a>.</p><p><a href="https://ux.email/">Sign up for our weekly UX newsletter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e74b801d8ff" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-new-kind-of-ux-workshop-8e74b801d8ff">On leading a new kind of UX workshop</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Ways Designers Need to Adapt in the Age of AI]]></title>
            <link>https://uxdesign.cc/6-ways-designers-need-to-adapt-in-the-age-of-ai-bdf22a55c295?source=rss-ed8bf69d8cf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdf22a55c295</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Ramy Nassar]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 16:44:38 GMT</pubDate>
            <atom:updated>2016-10-14T11:20:06.611Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*miMyWH0slhhn49li6Y71VA.jpeg" /><figcaption>Source: Facebook Research</figcaption></figure><p>Have you noticed anything interesting the last time you uploaded a picture on Facebook? Perhaps you picked up on the fact that sometimes Facebook tries to tag your friends and family for you. Welcome to <a href="https://research.facebook.com/publications/deepface-closing-the-gap-to-human-level-performance-in-face-verification/">DeepFace</a>, Facebook’s facial recognition system. If you’re wondering why it’s called DeepFace, it’s because at its core, the system is based on a type of Artificial Intelligence (AI) called <a href="https://en.wikipedia.org/wiki/Deep_learning">Deep Learning</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eKl7p3BqV5W-waiEGfwVZw.jpeg" /></figure><p>AI is here, and it’s changing the way that we interact with technology on a daily basis. Most of the time, we don’t even realize when it’s happening. As designers, it’s going to become increasingly important to not only understand the fundamentals of AI, but also to adapt our process and mindsets accordingly. Below are six important changes that designers will need to consider.</p><ol><li>First and foremost, it’s time to learn about what AI is. While designers don’t need to create their own HAL 9000s just yet, a basic understanding of AI (in particular, the areas of <a href="https://www.coursera.org/learn/machine-learning">Machine Learning</a> and Deep Learning) will give you a huge advantage.</li><li>Once you’ve learned some of the fundamentals, it’s time to buddy up with your favourite data scientist. Just like digital designers collaborate almost constantly with front-end developers today, similar collaboration with AI specialists &amp; data scientists will be the relationships of the future.</li><li>Design feedback loops are going to get shorter. As methods such as machine learning start providing designers with deeper, more precise insights, designs will need to respond and adapt more quickly. In the long run, this will also help speed up the time required, for example, to find the right product-market fit.</li><li>Designers will need to focus (even more) on asking “why?” The quantitative analytics &amp; insights that come out of machine learning algorithms will help point designers in the right direction, but will rarely uncover underlying human behaviours or motivations. For example, imagine building a <a href="http://www.nsightfortravel.com/big-data-machine-learning-equals-predicting-future-outcomes-for-hoteliers/">travel platform where predictive analytics</a> can help inform the system of the most likely country that the user is looking to book a trip in. While there is of course value in this type of insight, the really interesting piece happens when we can understand why users (or user segments) make the choices that they do so that we can design dynamic experiences.</li><li>The world of AI just starting to open up new modes of interaction, and as designers, we need to catch up. Siri, Cortana and Alexa are all personified AI-based digital assistants. With Apple’s recent opening up of the <a href="https://developer.apple.com/sirikit/">Siri API</a>, application designers can now use voice-based commands to interact with their apps. So fa2r, for most applications, this just allows us to do the same things that we could with a touch interface, using our vocal chords. However, over the coming months and years, designers will start to find <a href="https://developer.apple.com/ios/human-interface-guidelines/features/siri/">unique modes of interaction based on voice</a> that allow us to interface with digital systems in completely new ways.</li><li>Finally, no article about AI would be complete without a consideration for privacy. <a href="https://en.wikipedia.org/wiki/Privacy_by_design">Privacy by design</a> will continue to be more and more important as we create more immersive, dynamic and personalized digital systems and applications. I’ve long considered how online learning courses could be improved if we enabled the cameras on users’ devices to detect a student’s current state of understanding and level of interest. If a student starts to tune out during a video lecture (there are plenty of well-documented facial cues that can be used to detect this), perhaps the lecture pauses, repeats a section or tries to explain the concept in a different manner. In a world where the microphones &amp; cameras on our devices are on by default (in order to have the best user experience), a user’s privacy, and how we communicate that privacy, will become increasingly important.</li></ol><p>It’s been about 10 years since the last major revolution in digital design took hold — mobile devices. Over the next 10 years, AI, and the insights it can deliver, will again radically change the role of designers in creating meaningful, engaging digital tools and systems.</p><p>If you’d like to learn more about how we’re integrating Machine Learning &amp; Design, feel free to contact me or the <a href="http://www.architech.ca/">Architech Team</a>.</p><p><a href="http://ux.email/">Sign up for our weekly UX newsletter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdf22a55c295" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/6-ways-designers-need-to-adapt-in-the-age-of-ai-bdf22a55c295">6 Ways Designers Need to Adapt in the Age of AI</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>