<?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 Belinda Ann Lewis on Medium]]></title>
        <description><![CDATA[Stories by Belinda Ann Lewis on Medium]]></description>
        <link>https://medium.com/@belinda.lewis?source=rss-67fc70f18554------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SxkXJ0OV8ZQLmVo6RXzX8w.jpeg</url>
            <title>Stories by Belinda Ann Lewis on Medium</title>
            <link>https://medium.com/@belinda.lewis?source=rss-67fc70f18554------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:55:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@belinda.lewis/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[Chatbots — mapping the user journey.]]></title>
            <link>https://medium.com/feersum-engine/chatbots-mapping-the-user-journey-5a55a1265b81?source=rss-67fc70f18554------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a55a1265b81</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <dc:creator><![CDATA[Belinda Ann Lewis]]></dc:creator>
            <pubDate>Wed, 29 Nov 2017 08:44:37 GMT</pubDate>
            <atom:updated>2017-11-29T08:44:37.429Z</atom:updated>
            <content:encoded><![CDATA[<p>The understanding of a digital experience as steps in a journey along a desired path is a great metaphor for both designing digital products and services, and communicating this experience to other members of the product team.</p><p>The user journey map developed from this design process is a core UX artifact and is deeply satisfying to build (we know UX designers love a good map).</p><p>User journeys are a less useful tool for designing and communicating natural language based, non-deterministic chat experiences. The concept of an ‘optimal’ path through a chatbot experience is sufficient to design simple deterministic chatbots, but once you give users the ability to enter free-form text, they develop the expectation that the chatbot will ‘understand’ them, which can easily knock them right off the path you’ve put all that elbow grease into paving.</p><p>The beginning of the design process for a very simple chatbot could look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fiQCCWdSfEkWkgf_e7J2lg.jpeg" /></figure><p>The user starts the conversation (the point at where they start depends on what they did last time they were there and/or what we know about them). They can perform one of two different actions, or if the chatbot doesn’t fully understand them, it needs to get further detail from them.</p><p>So, if we ignore the complexity in start location, the user journey map looks something like this — users start and either go straight to a specific intent — e.g. <em>Register me for your service</em> — or we clarify what they mean before sending them to the right intent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5GeKqFoxhffLTAkiqy2fkg.jpeg" /></figure><p>When the intent requires multiple pieces of information, for example, providing a name, email address and password, the journey expands:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xAv5CMRb79LdSHo0oELixA.jpeg" /></figure><p>In this case, each of those individual elements still needs an, ‘<em>I’m sorry, I don’t understand what you mean’</em>, or a ‘<em>this isn’t really an email address’</em> response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2TzcLTrsH7sBWA7h7lAuCQ.jpeg" /></figure><p>The user might in fact just give you their name right at the start, without first clarifying that they are trying to register for the service. With this in mind, we need the ability to move through the registration process no matter the order in which we receive key pieces of information, such as<em> a </em>name, email address and password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*joTbZtsCSY4f6AQWfJjBnA.jpeg" /></figure><p>And what about cases where a particular field, such as an email address is used in both registration for the service and registration for a newsletter? We need to be able to, as soon as we identify the change in intent, move people between the two types of interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_EAvn_YLUG-l_GPecrAfw.jpeg" /></figure><p>Since the majority of chatbots will have more than two intents, you can see how a map that explores all options is not the most effective tool to communicate with copywriters and developers.</p><p>So what do you do when you need to design the most robust and enjoyable chatbot experience possible, and create the necessary creative briefs and specifications for the rest of the chatbot production team?</p><p>A good first step for you, as the designer, is still to create a simple, ideal user journey map. But thereafter, you need to start looking at new tools.</p><p>We need to think in terms of bi-directional micro-experiences, and their necessary guards and conditions. We need to identify entry points and end states and make sure that both onboarding and offboarding are satisfying across multiple interactions.</p><p>Chatbot UX design is a new field and we need new maps to navigate the territory. My next post will explore some of the new tools, methodologies and visualisations that I’ve found useful designing experiences in this new space.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a55a1265b81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/feersum-engine/chatbots-mapping-the-user-journey-5a55a1265b81">Chatbots — mapping the user journey.</a> was originally published in <a href="https://medium.com/feersum-engine">Feersum Engine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI heavyweights heading Cape Town for groundbreaking BotCon Africa 2017 conference]]></title>
            <link>https://medium.com/botcon-africa/ai-heavyweights-heading-cape-town-for-groundbreaking-botcon-africa-2017-conference-1d8ce0d7d7af?source=rss-67fc70f18554------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d8ce0d7d7af</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Belinda Ann Lewis]]></dc:creator>
            <pubDate>Mon, 22 May 2017 14:53:22 GMT</pubDate>
            <atom:updated>2017-05-22T14:56:42.575Z</atom:updated>
            <content:encoded><![CDATA[<p>The future of human-computer interaction will be up for debate in Cape Town this week, when some of the world’s leading thinkers and practitioners in the cutting-edge field of conversational interfaces will gather to examine the subjects of artificial intelligences, chatbots, machine learning and natural language processing at BotCon Africa 2017.</p><p>The opening keynotes for BotCon Africa 2017 have now been confirmed as Martin Raison, a research engineer at Facebook AI Research in Paris, and Justin Watson, co-founder of the open-source Botpress framework.</p><p>Raison, who was previously an engineer for the natural language processing platform Wit.ai before it was acquired by Facebook, will open the conference with a keynote on the best practice for chatbot interfaces, under the subject of “Teaching machines to interact with people”.</p><p>“Building chatbots that feel as natural and smart as humans will require great scientific advances,” Raison says, “This talk will give a glimpse of how Facebook AI Research and the scientific community are bringing us closer to this dream every day.”</p><p>Watson, meanwhile, will address the issue of “What makes a great bot?”. Drawing on his experiences through Botpress, which allows developers to quickly create a bot instance and add features via plugins, Watson will highlight some of the lessons learned from thousands of users about how to create a great chatbot.</p><p>“Conversational interfaces and chatbots promise to revolutionise the way customer-facing services are designed across Africa, thanks to low-cost implementation and the ability to implement multilingual support across multiple platforms” says Belinda Lewis, Product Director at chatbot platform Feersum Engine and curator of the BotCon Africa 2017 conference, “Through events like BotCon Africa 2017 we can accelerate local development and knowledge, helping to make African firms leaders in the field of AI interaction.”</p><p>BotCon Africa 2017 takes place at Workshop 17 on Cape Town’s V&amp;A Waterfront, on 25 May. The focus of the conference will be to investigate ways in which AIs and bots can be applied to public and commercial services across Africa. From leading social media platforms to finance houses, attendees will gain valuable insights into the best practice for bot design and implementation through a mix of keynote presentations, technical talks and workshop sessions, plus the opportunity to network with peers.</p><p>Other highlights of the event include a second speaker from Facebook, Head of Messenger Platform Partnerships for the Facebook Messenger, Angelique Kamara. Kamara will discuss how the social media giant is embracing chatbots in her talk, “Bots that connect: The future of the Messenger Platform”. Local innovators who will be presenting talks and workshops include include Riana Smit, from RetroRabbit, DataProphet’s Frans Cronje, Ryan Falkenberg from Clevva and Toufeeq Ockards from the Square Kilometre Array.</p><p>For more information or to arrange a one-on-one interview contact:</p><p><a href="/service/mailto:sam@abetterworld.co.za">sam@abetterworld.co.za</a></p><p>082 556 5188</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d8ce0d7d7af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/botcon-africa/ai-heavyweights-heading-cape-town-for-groundbreaking-botcon-africa-2017-conference-1d8ce0d7d7af">AI heavyweights heading Cape Town for groundbreaking BotCon Africa 2017 conference</a> was originally published in <a href="https://medium.com/botcon-africa">BotCon Africa</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everyone should learn to code]]></title>
            <link>https://medium.com/@belinda.lewis/everyone-should-learn-to-code-d9f1d38841bb?source=rss-67fc70f18554------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9f1d38841bb</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Belinda Ann Lewis]]></dc:creator>
            <pubDate>Sat, 18 Feb 2017 12:40:46 GMT</pubDate>
            <atom:updated>2017-02-19T16:43:16.953Z</atom:updated>
            <content:encoded><![CDATA[<h3>But you can stop whenever you like. And still work in software development. And still be a feminist.</h3><p>I’ve been asked to speak at the Django girls Johannesburg workshop next month. I’m writing this blog post as a way to prepare myself for the event.</p><p>For myself I’m doing this to explore why doing such a thing makes me uncomfortable (and annoyed, and possibly angry). For the sake of my future audience I’m doing it so that my talk is positive and inspirational (I promise) and focusses on the myriad of ways in which a basic understanding of code has helped me in my career, rather than any underlying bitterness and resentment I may feel towards the industry.</p><p>Because, just to be 100% clear about this upfront, <strong><em>I believe that everyone should learn the basics of coding.</em></strong> I believe it should be a primary school subject. I don’t believe its possible to excel at any job in any technical field without this.</p><p>I don’t believe that the next generation, living in a digital world recorded and governed by code, will be able to excel at being human without this.</p><p>But.</p><p>There are so many inherent industry biases that effect gender diversity in the industry, and they are so deeply ingrained, that even people and organisations dedicated to making things better can be guilty of perpetuating them.</p><h3>Industry myths</h3><h4><strong>Myth #1 Expose them, and they will code.</strong></h4><p>Grade 2 me went to <a href="https://turtleacademy.com/">Logo</a> classes. Grade 4 me built a text based game in C++ (full disclosure: it was a Q&amp;A style game show and not at all good). University me built experimental art in ActionScript2 and real world interactive installations. (Full disclosure: In rather stereotypical girl fashion I roped my then boyfriend into doing a lot of the coding and electronics aspects of my homework. But its okay, because I married him afterwards, and we still make interactive art together. And he has never made me feel like my contribution to our projects is lesser because I wasn’t generating the actual code).</p><p>Obviously I’m speaking here from a place of privilege. I grew up white and middle class and to parents who were themselves exposed to these fields (my father is an electrical engineer) and saw the value of sharing this knowledge with a girl child.</p><p>But lack of exposure, due to gender or poverty, is an issue in all STEM fields and not a defining characteristic of the software industry.</p><p>Both of my brothers are software developers, I had as much exposure as them. <strong><em>I’ve just never particularly wanted to be a developer.</em></strong></p><p>One of the most offensive things any (well-meaning and kind and genuinely trying to make the world better) colleague has ever said to me is to ask me what ‘would have made young me want to code?’</p><p>Because I work in software, and I seem smart, so I <em>must</em> just not have had the opportunity.</p><p>Because:</p><h4><strong>Myth #2 Those that can code, those that can’t do other stuff.</strong></h4><p>There is no correlation between being a developer and being intelligent.</p><p>Being a <em>good</em> developer is correlated with <em>specific types</em> of intelligence.</p><p>There are other types of intelligence. These other types are just as valuable.</p><p>A community built upon some perceived inherent superiority is alienating and intimidating and does not encourage participation or diversity.</p><p>And yes, this is an stereotype perpetuated by every movie since <a href="https://en.wikipedia.org/wiki/Hackers_(film)">Hackers</a> where developers are portrayed as near mystical savants, but its also something the industry has whole-heartedly embraced, because:</p><h4>Myth #3 If you’re not a developer you’re in a supporting role.</h4><p>You can’t build good software with just developers.</p><p>Other software career paths are not there to merely provide groupies for developer rockstars.</p><p>Knowing about code makes you a better designer (just remembering the purpose of my blog post here) but equally knowing about design makes you a better developer. And <em>everyone</em> should know about UX because we are all humans experiencing the world.</p><p>Creating a stratified industry where the contributions of certain individuals are seen as less valuable, <em>when all roles are vital to the success of the product, </em>creates tension and poor team dynamics.</p><p>Poor team dynamics perpetuate cliques and discourage diversity.</p><h4>Myth #4 If you’re a modern woman and a feminist you’re totally at ease just <em>hanging out with the boys.</em></h4><p>Modern developer culture, which is largely geek internet culture, is still inherently masculine.</p><p>It feels to me like the diversity in tech movement focusses on making young girls understand that this type of culture is cool. That even though they are girls they can also play computer games and be comfortable hanging out with the guys and having lots of fun.</p><p>Why do we invest all this energy making girls feel comfortable embracing a culture that has not yet changed to embrace them back?</p><p>The culture is the problem.</p><p>Not that girls need to be taught that they can have the same interests as boys.</p><h3>Getting to the point: what does this all mean, young Django girl?</h3><h4>You should definitely learn to code.</h4><p>Seriously, its an investment in yourself.</p><h4>You might not like it.</h4><p>You might not enjoy doing it. You don’t have to try force yourself to like it because you’re worried that its because you’re a girl or because you’re stupid.</p><h4>You might find it hard. Like too hard.</h4><p>You might find it difficult. Not that fun-let’s-problem-solve-and-get-this-sorted kinda way, but in the this-is-so-hard-its-making-me-miserable kinda way. This does not mean you are stupid. This does not mean you’re a failure.</p><h4>You don’t need to be a developer if you want to work in software.</h4><p>There are many other ways to be involved in the creation of digital products and services. These can all be fulfilling career paths.</p><p>You’re not accepting a supporting role because you couldn’t make the big leagues. You’re not generating less value because you’re not pushing code. You are still making things!</p><p>(And if at some stage you should be asked to speak at a Django girls workshop you should not have to feel ashamed to say that “You work in software development” because somehow that’s not actually true, because, I mean you don’t <em>actually</em> code right).</p><h4>You can stop whenever you want.</h4><p>Like whenever.</p><p>You don’t have to embrace it as a career because you want to make things or because you love XBox games.</p><p>You don’t have to keep at it to prove to those idiots out there that you can code despite having ovaries.</p><p>Do what makes you happy.</p><p>Although, if you do decide to become a software developer, remember that we’re hiring!</p><p><em>My next post will (probably, most likely) be about my actual talk.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9f1d38841bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>