<?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[Nairobi Design Community (NDC) - Medium]]></title>
        <description><![CDATA[Nairobi Design Community brings together product designers, UXers&#39;, startup founders, UI designers, and any other people who have an interest in using different design thinking methods to solve our day to day life challenges. #UXNairobi - Medium]]></description>
        <link>https://medium.com/nairobi-design-community?source=rss----f8ce58153298---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Nairobi Design Community (NDC) - Medium</title>
            <link>https://medium.com/nairobi-design-community?source=rss----f8ce58153298---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:45:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/nairobi-design-community" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Digital Financial Services in Africa Still Fail Users at the Point of Need]]></title>
            <link>https://medium.com/nairobi-design-community/why-digital-financial-services-in-africa-still-fail-users-at-the-point-of-need-f1575bf07ef2?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/f1575bf07ef2</guid>
            <category><![CDATA[financial-inclusion]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[africa-dfs]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[digitalfinancialservices]]></category>
            <dc:creator><![CDATA[Maryann Wangari]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 17:56:53 GMT</pubDate>
            <atom:updated>2026-04-22T19:23:49.344Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Safaricom’s My OneApp reveals about service design, trust, forced transitions, and the cost of ignoring the people you’re designing for</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AsC890rmhNnKCw3NBhXPkw.jpeg" /><figcaption>An old photo of me conducting design research for a mobile wallet for farmers in Tamale, Ghana, in 2016.</figcaption></figure><p>A person wakes up, reaches for a familiar app, and realizes something has changed. The name is different. The flow is different. The old app is gone, and so is their history.</p><p>That moment may seem small from the outside. But in financial services, where people are trying to send money, buy data, pay school fees, or support family, it is not small at all. It is where trust begins to break.</p><p>That is why the backlash around Safaricom’s My OneApp matters. On paper, the launch made strategic sense. A unified app replacing separate M-PESA and MySafaricom experiences promised simplicity, integration, stronger security, and a more modern service. But what many users seem to have experienced was something else: a forced transition, broken continuity, confusing access conditions, and new friction in the very moments the service was supposed to make easier. That is why the backlash around Safaricom’s My OneApp matters.</p><p>Safaricom positioned My OneApp as a unified experience bringing together M-PESA and Safaricom services in one place, and later published FAQs explaining the app as a single hub for connectivity and M-PESA needs. But after launch, the company publicly apologized, saying the experience had “fallen short” and acknowledging that some customers had a poor experience, including those who were auto-migrated through updates and customers affected while roaming.</p><p>The issue here is bigger than a rough launch. My OneApp is a useful case study in a deeper pattern: digital financial services in Africa still fail users at the point of need when they are designed around <strong>internal structure</strong>, <strong>platform ambition</strong>, or <strong>technical logic</strong>, but not enough around real human context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MqhKmp0DCv33sC3NIbU91g.png" /><figcaption>Nano Banana Ai generated Image</figcaption></figure><h3>A familiar financial ritual, suddenly interrupted</h3><p>The strongest reactions to My OneApp were not really about visual design alone. They were about interruption.</p><p>Many users described waking up to find the old M-PESA app gone or silently replaced. Some thought they had deleted it by mistake. Others thought something was wrong with their phones. One comment captured the unease with unusual clarity: <em>“I go to bed, I have one app, I wake up, no explanation, no reason… another app has installed itself on my phone.”</em> — User comment, anonymized</p><p><strong>That feeling matters.</strong></p><p>In financial services, routine is part of the product. Familiarity is part of the interface. Saved paybills, remembered flows, quick paths to send money, buy airtime, or check balances are not cosmetic conveniences. They are part of how <strong>trust</strong> is built over time.</p><p>So when one user says, <em>“I only lost my list of favourites… rent payment… school fees. I now have to manually key in the paybill and account numbers again,”</em> that is not just an inconvenience. It is a break in continuity. — User comment, anonymized</p><p>And continuity matters even more in African DFS contexts, where these services sit at the center of everyday life. They are infrastructure for households, hustles, remittances, emergencies, and repeated daily actions. When that kind of service changes abruptly, the burden should not fall on the user to catch up.</p><h3>A rollout, a backlash, and an apology</h3><p>The timeline matters.</p><p>Safaricom introduced My OneApp in early April as its new unified app experience. Within days, local tech reporting and user commentary were already documenting login failures, migration problems, and difficulty for users trying to revert or simply complete basic tasks. By April 16, Safaricom issued a formal apology, acknowledging that the rollout had caused a poor experience and saying the transition had fallen short of expectations. Tech reporting around the same period described the launch as marked by login failures, outages, diaspora access problems, and frustration among users who were moved over through auto-updates.</p><p>This is what makes the case important. The complaints were not random. They clustered around a few specific fault lines.</p><p>The first was <strong>forced migration</strong>. Many users felt they had not actively chosen the new experience. One person put it bluntly: <em>“We were not given the choice.”</em> — User comment, anonymized</p><p>The second was <strong>authentication</strong> and <strong>connectivity</strong> friction. Based on Safaricom’s own explanation, first-time login required Safaricom mobile data for SIM-based verification, after which users could switch to Wi-Fi. But in practice, that design collided with how people actually use their devices: dual-SIM phones, preferred non-Safaricom data lines, home and office Wi-Fi, roaming, and mixed connectivity habits. It also raises a bigger question. <strong>If M-PESA is often held up as one of the world’s most influential mobile money products, why does access to its app still depend so heavily on a Safaricom line at the point of entry?</strong> In an era where digital services increasingly use flexible forms of authentication, it is fair to ask whether this is a <strong>technical limitation</strong>, a <strong>regulatory constraint</strong>, or <strong>simply a design choice</strong> that has not kept pace with how people live and connect today.</p><p>The third was the <strong>diaspora lockout</strong>. This appears to have been one of the sharpest points of <strong>pain</strong>. Users outside Kenya described being unable to activate or authenticate because the service required a Safaricom network handshake over mobile data, a condition that did not match their reality. Local reporting also singled out roaming and diaspora customers as among the worst affected.</p><p>One user described the trap clearly: <em>“Pushing the updates locked me out… I cannot because it’s only possible with the actual SIM in the phone, with Safaricom data, and with airtime. But I cannot get to that point because I need to access my M-PESA to load airtime.”</em> — User comment, anonymized</p><p>There were other recurring issues too: disappearing saved favorites, repeated logins, random logouts, cluttered flows, slow responsiveness, delayed OTPs, and extra taps for common tasks like Lipa na M-PESA. Reporting from Tech-ish also noted a rapid sequence of Android hotfixes in the weeks after launch, suggesting Safaricom was still stabilizing the experience in public view.</p><p>But the pattern underneath the complaints matters most. Users were not just saying this app has bugs. They were saying: <em>&quot; This service no longer meets me in the moments I need it most.”</em></p><h3>This is not just a UI/UX issue. It is a service design issue</h3><p>It is tempting to read the My OneApp backlash as a branding problem, a rough launch, or a UI cleanup job. But those readings are too narrow.</p><p><strong>Service design asks us to look beyond the screen and examine the whole experience: the sequence of actions, the conditions under which people use the service, the backstage decisions that shape frontstage moments, and the wider ecosystem of trust, access, and support around the product.</strong></p><p>That lens matters here.</p><p>If we borrow from core service design principles, several things stand out immediately.</p><p>First, this does not appear to have been human-centred enough in the deepest sense. A service can look modern and still fail to account for how people actually live with it. In this case, real use conditions seem to have included dual-SIM habits, Wi-Fi dependence, roaming realities, diaspora use, urgent payment contexts, and familiar financial shortcuts built over time.</p><p>Second, the rollout does not seem to have been real and holistic enough. Good service design is tested in the mess of actual life, not only in ideal technical conditions. If major user groups discover severe friction only after launch, especially around setup and access, that is usually a sign that the service was not stress-tested enough in the contexts that matter most.</p><p>Third, the transition itself appears to have been weakly designed. This is critical. Migration is not an operational footnote. It is part of the service. First-time login is part of the service. Renaming a trusted financial app is part of the service. Auto-updating people into a new environment is part of the service. If those moments feel confusing, coercive, or brittle, then the service has already failed before the user even reaches the homepage.</p><p>And finally, the experience suggests a familiar tension in digital products: utility losing to architecture. Internally, a <strong>super app</strong> may solve <strong>consolidation</strong>, <strong>platform</strong>, and <strong>business problems</strong>. But users do not experience architecture. They experience service. They experience moments. They experience whether they can pay, send, withdraw, log in, or recover quickly when something goes wrong.</p><p>As one commenter put it, <em>“This is what happens when teams stop designing and building for people and instead design and build around internal constraints.”</em> — User comment, anonymized</p><p>That is the lesson My OneApp puts on the table.</p><h3>Design can anger, exclude, and quietly harm</h3><p>This is where <a href="https://www.linkedin.com/in/jonathanshariat/">Jonathan Shariat</a> and <a href="https://www.linkedin.com/in/cynthiasavard/?locale=en">Cynthia Savard Saucier’s</a> framing on tragic design becomes useful.</p><p>Design does not only delight or frustrate. It can also <strong>anger</strong>, <strong>exclude</strong>, <strong>sadden</strong>, and <strong>quietly harm</strong>.</p><p>The reaction to My OneApp shows all four.</p><p>There is anger in the public response, yes, but beneath the anger is something more revealing: loss of control. People felt acted on. They felt shut out of routines they depended on. They felt made to adapt on someone else’s timeline.</p><p>There is also exclusion. Diaspora users were among the loudest critics not because they dislike change, but because the security and activation logic treated their context as secondary. Yet for many people abroad, M-PESA is not an occasional convenience. It is how they support family, meet obligations, and stay connected to home.</p><p><strong>Then there is the quieter harm:</strong> confusion, embarrassment, self-doubt, and extra cost.</p><p>One user wrote, <em>“The app is messing with my mental health… after switching off the phone I have to logging again?”</em> — User comment, anonymized</p><p>Another line that should make product teams pause came from a widely shared reflection: <em>“Somewhere in Nairobi right now, a perfectly intelligent adult is standing in a supermarket, WiFi switched off, burning through Safaricom data, trying to log into a Safaricom app, in order to pay for groceries using Safaricom M-PESA, and failing.”</em> — User comment, anonymized</p><p>That is not just friction. That is design creating strain in a moment that should have been simple.</p><p>This is also where the language of dark patterns becomes tempting. I would be careful with it. Harmful intent is hard to prove from the outside. But it is fair to say that some elements of the rollout produced outcomes users commonly associate with <strong>dark patterns</strong>: <em>reduced choice</em>, <em>forced migration</em>, <em>confusing substitution</em>, and <em>friction that shifts cost</em> and <em>effort onto the user</em>.</p><p>Whether intentional or not, those outcomes matter.</p><h3>Why this matters for digital financial services in Africa</h3><p>This story matters beyond Safaricom.</p><p>Digital financial services in Africa operate in contexts where trust is fragile, connectivity is uneven, device behavior is messy, and people often rely on multiple workarounds to make daily life function. Many users are on dual-SIM phones. Many switch between data lines. Many depend on Wi-Fi. Many transact under pressure. Many abroad rely on these services to maintain real responsibilities back home.</p><p><em>So when a DFS product fails, it does not fail in a vacuum.</em></p><p>It fails in checkout lines. It fails during urgent school payments. It fails in moments of remittance. It fails in the gap between a user’s expectation and a system’s new logic.</p><p>That is why “at the point of need” matters so much. It is the point where service design becomes real.</p><h3>Designing for Everyday Realities Calls for Better Service Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gz_aD-VUq9ziuMYUxxXvrg.jpeg" /><figcaption>An image of Maryann and the Mercy Corps AgriFin team in Tanzania during prototyping and learning research.</figcaption></figure><p>There are practical lessons here for anyone building digital financial services in Africa.</p><ul><li><strong>Design transitions with people in mind, not just systems in mind.</strong> Migration is not a technical step at the end. It is part of the lived experience. When people rely on a service for rent, groceries, school fees, or family support, an abrupt change feels less like innovation and more like disruption.</li><li><strong>Preserve user agency. In trust-heavy systems, people need to feel invited into change, not cornered by it. </strong>Good service design respects the user’s pace, gives them clarity, and avoids making them feel acted on.</li><li><strong>Test ideas before they are implemented in the real world.</strong> This is what service design advocates for: not just building the thing, but testing how it works in the messiness of real life. That means testing with diaspora users, roaming users, dual-SIM users, Wi-Fi-first users, and people trying to make urgent payments under pressure.</li><li><strong>Keep fallback paths alive during transition.</strong> Parallel systems are sometimes the price of protecting trust. In essential services, reliability matters more than forcing everyone into the new thing at once.</li><li><strong>Do not let security become rigidity. </strong>Security should protect people without trapping them in one narrow route. If a secure design excludes the very people it is meant to serve, then the system needs to be rethought.</li><li><strong>Preserve continuity. </strong>Saved favorites, remembered recipients, familiar naming, and common flows matter more than teams often admit. These are not small details. They are part of how trust is carried forward.</li><li><strong>Design for the whole service, not just the interface.</strong> Human-centred design and service design both ask a deeper question: <em>what is happening in the person’s life when they reach for this service?</em> The answer should shape the experience far more than internal architecture ever should.</li></ul><p><strong>Good service design does not ask people to carry the weight of change alone. It absorbs that weight through testing, clarity, continuity, and care.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1575bf07ef2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/why-digital-financial-services-in-africa-still-fail-users-at-the-point-of-need-f1575bf07ef2">Why Digital Financial Services in Africa Still Fail Users at the Point of Need</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Event] UxP — The Nairobi UX & Product Design Conference]]></title>
            <link>https://medium.com/nairobi-design-community/event-uxp-the-nairobi-ux-product-design-conference-6751ea575d3b?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/6751ea575d3b</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[emerging-markets]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Maureen Macharia]]></dc:creator>
            <pubDate>Thu, 16 May 2019 19:33:21 GMT</pubDate>
            <atom:updated>2019-05-16T19:33:21.166Z</atom:updated>
            <content:encoded><![CDATA[<h3>[Event] UxP — The Nairobi UX &amp; Product Design Conference</h3><p>UxP is Nairobi’s inaugural annual design conference bringing together the community of creative leaders, designers, developers, and entrepreneurs. The conference will be centered around practical approaches to driving innovation in emerging markets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*FY1g8fzAmsid7fUI0AE94w.jpeg" /></figure><blockquote><strong>To reserve a slot, go to </strong><a href="https://mookh.com/event/cf627cd4-9b52-49c2-a87f-0c249586d61d"><strong>bit.ly/UxP2019</strong></a></blockquote><p>Under the theme of ‘<strong><em>designing for emerging markets</em></strong><em>’</em>, East Africa’s first UX design community driven annual conference will highlight the importance of a design-driven approach to innovation. Nairobi is continually growing as the region’s innovation hub &amp; UxP Nairobi is designed to support the region’s efforts to build products and services that are effective, innovative, user-friendly and follow the best practices to enable scale and growth.</p><p>The learning event is a practical and hands-on user experience and design conference that allows participants to connect and learn from their peers and leaders in the industry. The conference has a strong practical focus and attracts industry practitioners and decision-makers who want to innovate.</p><h4>For full conference details, visit <a href="https://uxpnairobi.com/">www.uxpnairobi.com</a></h4><p>A sample of the speakers lined up are:</p><p>Maureen Macharia — Founder &amp; CEO @ Spindle Design</p><p>Shikoh Gitau — Head of innovation @ Safaricom Alpha</p><p>Ravi Chattpar — Co-founder &amp; Partner @ Dalberg Design</p><p>Ibanga Umanah — Co-founder &amp; head of strategy @ Brave</p><p>Silas Macharia — Innovation center leader @ IBM</p><p>Fady Rostom — Director @ Ark Africa ….and many more</p><p>There are limited tickets remaining, so RSVP on <a href="https://mookh.com/event/cf627cd4-9b52-49c2-a87f-0c249586d61d"><strong>bit.ly/UxP2019</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6751ea575d3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/event-uxp-the-nairobi-ux-product-design-conference-6751ea575d3b">[Event] UxP — The Nairobi UX &amp; Product Design Conference</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Event] The Impact of Design Leadership, in Building Successful Products]]></title>
            <link>https://medium.com/nairobi-design-community/event-the-impact-of-design-leadership-in-building-successful-products-ee56ad2a649b?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee56ad2a649b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[event-design]]></category>
            <category><![CDATA[silicon-savannah]]></category>
            <dc:creator><![CDATA[Kipkorir Arap Kirui]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 08:18:10 GMT</pubDate>
            <atom:updated>2018-12-13T08:18:10.589Z</atom:updated>
            <content:encoded><![CDATA[<p>With the increasing growth of the design community in Kenya, we intend to bring together all design disciplines at the intersection of business, design, and technology for a discussion about how to lead a creative team and inspire cooperation.<br>Trust is in the heart of successful creative work. What creates trust in creative teams and collaboration? How do you keep your team motivated?</p><blockquote>To RSVP &gt;&gt; <a href="https://www.meetup.com/Nairobi-Design-Community/events/257031256/">https://www.meetup.com/Nairobi-Design-Community/events/257031256/</a></blockquote><p>Our topic for discussion will focus on learning the challenges of managing creative environments, building a winning culture and running a sustainable creative business.</p><p><strong>Event Details:</strong></p><p>Date and time: Monday, December 17, 2018, 6:00 PM to 8:00 PM</p><p>Location: Metta, Riverside Drive</p><p>RSVP: <a href="https://www.meetup.com/Nairobi-Design-Community/events/257031256/">https://www.meetup.com/Nairobi-Design-Community/events/257031256/</a></p><p><strong>Panelist:</strong><br>- Maureen Macharia — UX and Product Design Consultant<br>- Max Ngari — Executive Creative Director<br>- Chandni Motwani — Head of Product Metta<br>- Robert Nganga — Creative Director &amp; Founder, Station 77ke</p><p><strong>Maureen Macharia</strong><br>Maureen is a Product Designer, situated at the intersection of design thinking and technology. She applies a human-centered approach to problem-solving aimed at pinpointing needs and opportunities for organizational growth and developing useful and contextually relevant solutions or products for the market.</p><p><strong>Max Ngari</strong><br>An award-winning creative director with over ten years experience specializing in mobile, social, UX and content; His goal is to attain disappropriate amounts of buzz, impressions and earned media for his clients and brands. Seeks to infuse a culture where the idea comes first, gut feelings reign over uncertainty and foster an environment where creatives can show up as themselves.</p><p>Notably, renown to have made the “World’s First Smellable Website”, retold Kenyan history through a “Whatsapp Conversation”, re-imagined Kenyan legends as new world super-heroes through an “interactive comic book”, convinced tweeps to have “blind dates using a single tweet” and recently put the last remaining “male white rhino on Tinder”.</p><p>Despite being one of the youngest creative directors in the region, his work has been awarded over 150 times at regional and international award shows. Festivals such as Cannes Lions, One Show, Clio Awards, the Dubai Lynx, African Cristal, APA/Loeries Awards, MSK Awards &amp; The Loeries in South Africa.</p><p><strong>Chandni Motwani</strong><br>Chandni is Head of Product at Mettā and is responsible for growing the online platforms. She is passionate about turning ideas into reality. Chandni uses her expertise in design thinking to empower teams to innovate.<br>Before joining the Metta team, she had over ten years of experience in technology and business development. Before Nest, she worked on product consumer strategy for the Google Docs team in Mountain View, California. Chandni also worked as a renewable energy consultant for six years at Booz Allen Hamilton, where she worked with corporates and government agencies to identify optimal energy solutions. Chandni has a strong background in social enterprise and startup development. She co-founded a social enterprise incubator, called Hatch International, in Washington, DC where she led the product development of small-scale technologies for the poor and designed business models for multiple enterprises under the Hatch umbrella.</p><p><strong>Robert Nganga</strong><br>Robert left Kenya’s biggest ad agency to fulfill his dream of building a world-class African content company that told African stories to come through art, film, music, and technology. This move comes after years of working for Kenya’s top agencies where he felt a great desire not just to be a creative but also a creator/maker and curator.</p><p>His drive and dedication to creating compelling commercial content have seen him become one of the most awarded creatives in Kenyan history working on some of the biggest brands across the continent including Safaricom, Google, Guinness, Visa, Tusker winning numerous awards along the way including Kenya’s first ever Grand Prix at the Loeries. The first one and only one won by a non-South African creative.</p><p>Limited slots are available on a first-come-first-serve basis. To RSVP please go to <a href="https://www.meetup.com/Nairobi-Design-Community/events/257031256/">https://www.meetup.com/Nairobi-Design-Community/events/257031256/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee56ad2a649b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/event-the-impact-of-design-leadership-in-building-successful-products-ee56ad2a649b">[Event] The Impact of Design Leadership, in Building Successful Products</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Event] Designing for Social Impact]]></title>
            <link>https://medium.com/nairobi-design-community/event-designing-for-social-impact-3cb3502664d5?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/3cb3502664d5</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-nairobi]]></category>
            <dc:creator><![CDATA[Kipkorir Arap Kirui]]></dc:creator>
            <pubDate>Wed, 26 Sep 2018 16:19:41 GMT</pubDate>
            <atom:updated>2018-09-26T16:37:03.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*4gTDhPtHYoAckZIbq4eIsQ.jpeg" /><figcaption>Figma Africa Nairobi &amp; NDC are partnering for the “Design for Social Impact” event</figcaption></figure><p>Figma Africa Nairobi in partnership with Nairobi Design Community (NDC) invites designers, developers, product managers and startup founders for Figma Africa meetup, Nairobi edition, themed ‘<strong><em>Designing for socio-economic impact</em></strong>’. The event will be on <strong><em>2nd October</em></strong> between <strong><em>6 pm and 8 pm</em></strong> at <strong><em>Metta, 14 Riverside Drive Belgravia Building, Nairobi.</em></strong></p><blockquote><strong>To reserve your spot, please RSVP on our </strong><a href="https://www.meetup.com/Nairobi-Design-Community/events/255026160/"><strong>Meetup.com page</strong></a><strong>.</strong></blockquote><p>We have an exciting line-up of topics &amp; activities to empower us with design-thinking skills, UI/UX design education, and networking. We shall also learn how to collaboratively design products using Figma.</p><p>On the programme we have:<br>*Kennedy Kirui, CEO Tanasuk Africa, speaking about why you should consider a career in product management.<br>*Dennis Muthuri, Lead Designer iHub Software Consulting, taking us through an iTax re-design they worked on recently<br>*Allan Minani, CEO portable voices, taking us through how design thinking and application of design principles influence product at portable voices.<br>*Isaiah Wakoli, an exemplary art director <a href="https://www.instagram.com/iwakoli/">https://www.instagram.com/iwakoli/</a>guides us through his design process for his afro-futurist &amp; cosmic style.<br>*A walk-through of the Figma tool by Njiiri and Lavet, Figma ambassadors, as well as sharing design education resources.<br>*A mingling session with our vibrant network of invitees :)</p><p>Don’t forget only limited tickets are available. RSVP <a href="https://www.meetup.com/Nairobi-Design-Community/events/255026160/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cb3502664d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/event-designing-for-social-impact-3cb3502664d5">[Event] Designing for Social Impact</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM Journey: Reflections on Building Digital Products]]></title>
            <link>https://medium.com/nairobi-design-community/pm-journey-reflections-on-building-digital-products-1c34548d5030?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/1c34548d5030</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startups-africa]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Tessie Waithira]]></dc:creator>
            <pubDate>Thu, 09 Aug 2018 07:34:09 GMT</pubDate>
            <atom:updated>2018-08-09T08:09:47.537Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learning the art of what it takes to get digital products up, running and in use.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ruSQAv5cXPkc8Gvm" /><figcaption>Photo by <a href="https://unsplash.com/@hckmstrrahul?utm_source=medium&amp;utm_medium=referral">Rahul Chakraborty</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s been over a year since I started out in product management as a real job. Well more like two years but in the first year, I didn’t actually know that product management was a thing. All I knew is that I enjoy creating, knowing how the web works, translating technology to the user and overall being on the online digital space. Having a technical and business background made this an easy move.</p><p>I happened to work closely with different startups and observe them build products from the ground up and I knew I wanted to be part of this. Right from the ideation stage, validation, developing MVPs and taking these products to market. All this while being a software entrepreneur at <a href="https://meltwater.org/">MEST </a>where we were required to validate and iterate on different business ideas for a period of one year. I had earlier on joined the program wanting to focus on the product development side (only)but working with a small team, the business and technical roles kept intersecting, hence the realization that a product alone without a business model or customers is of no use (well, in most cases)</p><p>I recently worked as an associate product manager at<a href="https://lynk.co.ke/"> Lynk Kenya</a>, where I got to learn more about the field and the processes of bringing several products to market. I was tasked with managing several mobile and web consumer apps, an e-commerce platform, and several other internal operation products.</p><p>While I’m still young in the field, I now know a thing or two about digital products management and would like to share some of the key things I have picked up along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-13MM0JQAhFptVrS" /><figcaption>Photo by <a href="https://unsplash.com/@emilymorter?utm_source=medium&amp;utm_medium=referral">Emily Morter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Ask questions </strong>especially when you are new to the product team. You need to be clear on what was done before your time and why the team did it so that you can know where to contribute in the future. Ask as many specific questions as you can to learn and be able to navigate the product. One great way I handled this when I was new to the team was setting up 1:1 meetings with several team members spanning the design team, engineers, stakeholders to the marketing team. This helped me connect with the team members on a personal level over time, know what they are working on and where I can come in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2QBMFJ0mUkwoArCg" /><figcaption>“A white pennant that says explore on a dark wooden floor” by <a href="https://unsplash.com/@andrewtneel?utm_source=medium&amp;utm_medium=referral">Andrew Neel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Be curious</strong> about the industry and technology that the product is in. This revolves around matters business, design, and technology wise. You want to be in a position where you contribute to the market research and the trends in the industry discussions in the team. This will also help you in creating the product vision so that the product is relevant to the customers and you build something that the customers will love.<br>To be able to work well with the engineers, it is great to understand the technology stack the products are built in. From this, you will find out that sometimes, rather than needing to create and assign a task for an engineer to correct a small typo, you can easily fix the issue when you have some time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6WTGSHIZevGgt87j" /><figcaption>Photo by <a href="https://unsplash.com/@josh23_sink_sink?utm_source=medium&amp;utm_medium=referral">Josh Adamski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Retrospect frequently</strong> to understand where the team stands compared to the target. Retrospection can be in many forms. Depending on what works best for you and the team. It can be a monthly team retrospection or you can do it on your own or with your manager. I mostly took the retrospection time to groom the backlog, create new upcoming milestones from the product roadmap or get clarity on some pending issues from different stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cy1IycX6qynWLUgc" /><figcaption>“Several white arrows pointing upwards on a wooden wall” by <a href="https://unsplash.com/@oowgnuj?utm_source=medium&amp;utm_medium=referral">Jungwoo Hong</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Define processes</strong> that work best for you and the team. There are different processes defined and written about how to manage different agile teams but there is never a right one way to do it. You can try different processes and mix some up until you find one that works well with the team. This could be Scrum, or Kanban or just set your own process and borrow something from the best processes.<br>One of the key things about processes is that everyone knows what they need to do and how to do it. This can be done by defining how features are requested, how bugs are reported, how new products are launched and communicated to the different stakeholders. If one process doesn’t work out, don’t be too stuck up, you can easily agree with the team to switch things up and try another one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mV_okvPx6X8mWNEb" /><figcaption>Photo by <a href="https://unsplash.com/@jasonrosewell?utm_source=medium&amp;utm_medium=referral">Jason Rosewell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Over-communicate</strong> both to emphasize important points and inform the team about the state of the product. This will help in keeping different teams at par so that there are no expectations for something that is currently not being worked on. Communicate to the developers on what features are a high priority and what is expected of those features. Let the different teams know how their feature requests are performing and when to expect them. This will help reduce friction between the teams.<br>Keeping a regular feedback loop is one way to handle this where you update different stakeholders on the status of the product, collect feedback from the customers and translate this into tasks for the engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fegNunxCuHCmsPCD" /><figcaption>Photo by <a href="https://unsplash.com/@verenayunita?utm_source=medium&amp;utm_medium=referral">Verena Yunita Yapi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Create excitement</strong> around product launches and learn to celebrate small wins with the team. Sometimes, everyone is too busy creating that the team forgets to celebrate the small wins. It is the work of the product manager to create excitement around a new feature to the extended teams so that before this is launched, the internal team has tested it out and ensured it works well before the changes are pushed to the customers. As a PM, you are basically the product hype king or queen!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ifv96VLoDzf0p4W7" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Document everything</strong> for future use. This is most important when in meetings and there are defined action points that need to be taken. When something is well documented, it is easy to compare notes at a future date and remember what was agreed on. When it comes to internal operation products, it is great to create and update documentation of how the system is used both for the existing teams and for new hires. This aids in speeding up product onboarding and making sure everyone is on the same page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EgUIDeVOhaTqwXv5" /><figcaption>“A man in a black suit loosening his tie” by <a href="https://unsplash.com/@spiritvisionstudios?utm_source=medium&amp;utm_medium=referral">Ben Rosett</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Take ownership </strong>of the products and the specific features and tasks that you have handed over to either the design or the engineering team. In small companies, you will find that the PM role is also the QA role. Ensure that a feature implementation was done as per the feature request through thorough testing and working with the stakeholders involved up until when the feature is launched and ready for use. You can also monitor the performance of the feature while in use to make sure the expected outcomes are being achieved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UOSsqfLNHOTuiwmM" /><figcaption>Photo by <a href="https://unsplash.com/@lautaro_iglesias?utm_source=medium&amp;utm_medium=referral">Lautaro Iglesias</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Protect your time</strong> to take ownership of your day. PM roles revolved around different tasks and working with almost all teams in the company. You might end up having meeting invites all day and a lot of unread messages. It is okay to turn down a meeting invite if you feel that your contribution will not be key. This also helps you to prioritize tasks both for yourself and for the team that you are managing. It is okay to push discussions for some feature requests that are not a priority to a later date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4oDUIzJdO4d6goJ4" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Take action</strong> and speak up when you have an opinion about something. The main role for a product manager besides setting processes for the product is ensuring actions are taken as planned. Motivate the team to deliver. Collaborate with the team proactively and organize the team such that you are creating value for the business and the customers at large.</p><p>I’m lucky to have worked with a startup where I was required to manage more than one product which equals more learning. While working as an associate product manager, I had no idea that I was about to embark on one of the most challenging, mind-blowing, inspiring and enriching experience of my career.</p><p>For anyone starting out in product management in the early career stage, its normally hard as most product managers are known to transition from other roles but if you have a skill set to offer, most other things are learnings on the job. It is also a role where you have to wear so many hats from business, technical, design, research and user experience and sometimes it is hard to keep up. It is, therefore, necessary to be adaptive and ready to learn and pick up tasks as they come.</p><p>Product management is an enlightening experience as you get to learn how products work end to end (business and tech inclusive). It also opens you up to collaborative work, empathy and immense personal growth. It has been a rewarding experience and I can’t wait to learn and do more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c34548d5030" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/pm-journey-reflections-on-building-digital-products-1c34548d5030">PM Journey: Reflections on Building Digital Products</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn how to use Design Sprints to solve some of your most pressing problems]]></title>
            <link>https://medium.com/nairobi-design-community/learn-how-to-use-design-sprints-to-solve-some-of-your-most-pressing-problems-5728c5e7c7fe?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/5728c5e7c7fe</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Maryann Wangari]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 10:21:00 GMT</pubDate>
            <atom:updated>2018-07-24T10:26:31.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HC1eZHcpA875uRUaxZBAoA@2x.jpeg" /></figure><p>About a month ago we (NDC) shared a Google form to gauge the level of interest in design sprints as a problem-solving approach. We got a lot of interests from NDC members and the general public and the sentiment was that many people would love to use the approach but they are not equipped with the necessary skills to do so.The Design Sprint is a three to five-day process to solve big problems and test ideas. A dedicated team discusses a challenge, designs potential solutions, and tests them with real users. You start with something vague and finish with real feedback and something extremely tangible in just five days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*riHYT_SdnhSrxW8BnofCmg@2x.jpeg" /></figure><p>NDC will be running a half-day design sprint training workshop on the 28th of July between 8.45 am and 1 pm at Metta. The aim of the workshop is to show the participants how design sprints run in practice so that they can start using the approach to solve some of their most pressing problems. Participants will identify a challenge and over a couple of hours use the design sprint approach to think through it.</p><p><strong>What will the workshop cover?</strong></p><p>The session will cover the following key topics:</p><p><strong>1) How do you prepare for a sprint?</strong></p><ul><li>What problems are ideal for sprints and which ones are not?</li><li>- How do you identify the challenge to tackle?</li><li>- Who should you invite to the workshop?</li><li>- How many days should you set allocate for the workshop?</li><li>- Who can facilitate?</li></ul><p><strong>2) How do you facilitate a design sprint?</strong></p><ul><li>What are the key activities during the workshop and how do you run each activity?</li><li>- What are some of the common challenges you will face during a sprint and how do you overcome the challenges?</li></ul><p><strong>3) What happens after the sprint?</strong></p><p><strong>Who should attend?</strong></p><p>The workshop is suitable both for participants with and those without a design thinking background. You don’t need to be working in the technology sector to be part of the workshop. However, a lot of the case studies used will be about the technology sector. We have 30 slots and they will be allocated on a first-come-first-serve basis.</p><p>The following key considerations stand:</p><ul><li>Preference will be given to groups that sign up as teams from one organization. 20 slots have been allocated for this.</li><li>• 10 slots have been allocated to individuals.</li></ul><p>Do you have to pay?</p><p>Yes, each participant is expected to pay KES 1,000 ($10) to help NDC facilitate the workshop. This will help us but the necessary supplies to run the workshop and the balance will go into the kitty for other NDC events (e.g. paying for our Meetup.com account). Once you are confirmed as an attendee we will reach out with payment instructions.</p><p>What do you need before the workshop?</p><ul><li>Check out the Sprint book https://www.thesprintbook.com/</li><li>• Start thinking of a challenge you will tackle during the design sprint</li></ul><p>Please click this <a href="https://www.meetup.com/Nairobi-Design-Community/events/253058360/">link</a> to RSVP.</p><p><em>Looking forward to see you on Saturday.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5728c5e7c7fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/learn-how-to-use-design-sprints-to-solve-some-of-your-most-pressing-problems-5728c5e7c7fe">Learn how to use Design Sprints to solve some of your most pressing problems</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[{Recap} Fireside Chat with Adam Reineck — Global Design Director at IDEO.org]]></title>
            <link>https://medium.com/nairobi-design-community/recap-fireside-chat-with-adam-reineck-global-design-director-at-ideo-org-2808f132970f?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/2808f132970f</guid>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[nairobi-design-community]]></category>
            <category><![CDATA[ideo]]></category>
            <dc:creator><![CDATA[Maryann Wangari]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 06:57:35 GMT</pubDate>
            <atom:updated>2018-06-26T09:21:44.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8RJVvYpej4iYL5PTwYOZYA.jpeg" /><figcaption>Maryann and Adam</figcaption></figure><p>On 19th of June between 6pm and 8pm, about 100 people gathered at the <a href="https://medium.com/u/101b097a15e3">iHub</a> for a fireside chat with <a href="https://www.linkedin.com/in/adam-reineck-2165123/">Adam Reineck</a> — Global design director at IDEO.org. This was Nairobi Design Community’s first event of event of 2018 (face palm) but we couldn’t have started the year better than this.</p><p><a href="https://www.ideo.org/">IDEO.org</a> mission is to improve the lives of people in poor and vulnerable communities through design. They use human-centered design to create products, services, and experiences that improve the lives of people living in poverty.</p><p>When we had that Adam is going to be in town for 4 days, we reached out for a possible event. When he confirmed availability Kirui and I went on to organize and aggressively market the event, we only had 2 days to do so. To our surprise 100 tickets sold out on the first day, we added 50 more which sold out over the weekend.</p><h3><strong>About Adam</strong></h3><p>As Global Design Director at IDEO.org, Adam Reineck focuses on guiding projects and initiatives through the lens of design excellence. Adam has broad experience in product design, service design, and brand strategy and has worked in partnership with social enterprises and foundations on challenges related to energy, water and sanitation, healthcare, and financial opportunity.</p><p>Before joining IDEO.org, he spent eight years as a principal designer at IDEO and worked on a diverse set of international projects with clients including the U.S. Department of Energy, Nike, Samsung, LG, HP, and the North Face. He first worked with IDEO.org in 2011 as a Fellow in the organization’s inaugural year. He founded New Factory, a design studio that bridges innovation and craft, in 2012. Adam’s work has been published in Fast Company, BBC, Wired, Cell Magazine, and the New York Times. He has received design awards from IDEA, ID Magazine, Red Dot, iF, and others. He studied Industrial Design at California College of the Arts.</p><h3>The Conversation</h3><p>This was my first ever event to moderate I was excited because design is close to my heart, I believe that through design we can change and improve lives. I had key talking points but my intention was to allow the audience to ask more questions and engage with Adam.</p><p>We talked about his education background, his transition into the design industry and his experience working with different brands. Adam started his career as an intern at IDEO.com.</p><p>What is the difference between <a href="https://t.co/0RecF3IU5U">IDEO.com </a>and <a href="https://t.co/pr5aohhJ1X">IDEO.org</a>? IDEO.org focuses on challenges around poverty while <a href="https://t.co/0RecF3IU5U">IDEO.com </a>works on all other types of projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1cMK8RooGcG7Ax3VXO2hZw.jpeg" /><figcaption>Attendees keenly listening to Adam</figcaption></figure><h3>Design Thinking</h3><p>Adam studied industrial design. This is common when it comes to design thinking. We have few people who actually studied design thinking. It is almost always a journey from other disciplines. When I asked Adam the difference between Human centered design and design thinking, he mentioned that he doesn’t like the use to use the terms to define what he does. Weird right? see when you brand something there is a big chance it loses the original meaning. Adam imagines a world where we can just say “We’re doing a great design that encompasses sustainability and impact.” Unfortunately we still have to use buzz words because the world around design hasn’t transitioned into this mind set.</p><p><strong><em>How do you sell design thinking to clients in emerging markets?</em></strong></p><h3>denomuthuri on Twitter</h3><p>Adam: &quot;At the heart of design thinking, lies relationships. It&#39;s a risky thing when working with someone for the first time? The more you can share a real story with real impact numbers, the more traction you&#39;ll get when trying to sell.&quot; @uxnairobi #nairobidesigns</p><h3>Afroshok on Twitter</h3><p>Impact and data metrics combined with design and &quot;magic&quot; is what you need to combine when working with social impact partners&quot; @uxnairobi</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*5AJ5P1b9YbuQLkcZmF8OMg.jpeg" /></figure><p><strong><em>How can designers brand and identify themselves for the market?</em></strong></p><h3>Maureen Macharia on Twitter</h3><p>Find a way to put your own passion and flavor to the work you do in thinking about your brand as a designer. #Design #UX @ihub #nairobidesign</p><h3>Kirui K. on Twitter</h3><p>Design is a portfolio field and not a degree portfolio. This was a key factor when I was choosing the school to get into - Adam Reineck Global Design Director @IDEOorg #nairobidesign @uxnairobi</p><p>We also talked about the opening of IDEO.org studio in Nairobi. IDEO.org does a lot of work in Africa and there was a need to bring and office closer to the people, they also plan to invest in local talents and the design community.</p><h3>denomuthuri on Twitter</h3><p>We want to build a team that&#39;s African lead, we want the studio in Nairobi to be no different from the New York one, we want a highly skilled team of designers for Africa. @uxnairobi #nairobidesigns</p><p>I paused a question about hiring and what Adam looks for as a design director when hiring new designers.</p><p><strong><em>Who is an ideal designer?</em></strong></p><h3>Mutiso on Twitter</h3><p>Ideal designer- despite their discipline, they constantly maintain curiosity to do things they really believe in and are optimists, experiments on their own apart from formal projects.&quot; - Adam Reineck- @uxnairobi #nairobidesigns</p><h3>denomuthuri on Twitter</h3><p>Listen: &quot;Design is a portfolio field, not a degree one.&quot; Work on what you can share, not too much theory. No matter how much the research, design is quite visual in the end. @uxnairobi #nairobidesigns</p><p><strong><em>What do you look for when hiring designers?</em></strong></p><h3>denomuthuri on Twitter</h3><p>Recruitment insights from Adam. In an Interaction Design portfolio full of apps and websites, I look for someone doing a weired side project which proves their curiosity as a person. They want more out of life than executing client briefs. @uxnairobi #nairobidesigns</p><p>The future of design</p><p>Adam shared a few insights on what he thinks the future of design is. Designers will need to maintain a multi disciplinary mindset while having a core skill and being able to solve problems at a high level.</p><h3>Afroshok on Twitter</h3><p>The future of Design: how will we design for people in motion, either refugees or immigrants? #nairobidesigns</p><p>Overall it was a great event as we allowed the audience to ask more questions. This made the conversation very engaging. Thanks everyone who made this event a success.</p><p><strong>Whats next?</strong></p><p>We had an overwhelming response (53 responses) to the design sprint workshop and we are currently planning to do conduct the half-day session in the first or second week of July. Most survey participants indicated that the weekend would be the most appropriate time slot and as a result, we are planning to have it on a Saturday morning. We will keep you posted, please follow us on <a href="https://twitter.com/uxnairobi">twitter</a> to ensure you don’t miss out on upcoming events.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2808f132970f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/recap-fireside-chat-with-adam-reineck-global-design-director-at-ideo-org-2808f132970f">{Recap} Fireside Chat with Adam Reineck — Global Design Director at IDEO.org</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Event] Chat with Adam Reineck — Global Design Director at IDEO.org]]></title>
            <link>https://medium.com/nairobi-design-community/event-chat-with-adam-reineck-global-design-director-at-ideo-org-2e95404f8083?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e95404f8083</guid>
            <category><![CDATA[ideo]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[adam-reineck]]></category>
            <category><![CDATA[nairobi-design-community]]></category>
            <category><![CDATA[nairobi]]></category>
            <dc:creator><![CDATA[Kipkorir Arap Kirui]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 13:09:38 GMT</pubDate>
            <atom:updated>2018-06-14T13:09:38.379Z</atom:updated>
            <content:encoded><![CDATA[<p>The Nairobi Design Community is excited to bring you its first event of the year (facepalm) and we don’t think there could have been any other way to start.</p><p>On <strong>Tuesday 19th June</strong> at <strong>iHub</strong> Nairobi between <strong>6 pm and 8 pm</strong>, we will be hosting <a href="https://www.ideo.org/bio/adam-reineck">Adam Reineck</a> Global Design Director at IDEO.org for a chat. To RSVP please check out the <a href="https://www.eventbrite.com/e/chat-with-adam-reineck-global-design-director-at-ideoorg-tickets-47059103044">event post on Eventbrite.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjqG6xLM5r7EHAkC0s5QGg.jpeg" /><figcaption>Adam Reineck — Global Design Director at IDEO.org</figcaption></figure><p>IDEO has had a huge impact in the design thinking space. Through IDEO.org they are seeking to improve the lives of people in poor and vulnerable communities through design.</p><h4>About Adam</h4><p>As Global Design Director at IDEO.org, Adam Reineck focuses on guiding projects and initiatives through the lens of design excellence. Adam has broad experience in product design, service design, and brand strategy and has worked in partnership with social enterprises and foundations on challenges related to energy, water and sanitation, healthcare, and financial opportunity.</p><p>Before joining IDEO.org, he spent eight years as a principal designer at IDEO and worked on a diverse set of international projects with clients including the U.S. Department of Energy, Nike, Samsung, LG, HP, and the North Face. He first worked with IDEO.org in 2011 as a Fellow in the organization’s inaugural year. He founded New Factory, a design studio that bridges innovation and craft, in 2012. Adam’s work has been published in Fast Company, BBC, Wired, Cell Magazine, and the New York Times. He has received design awards from IDEA, ID Magazine, Red Dot, iF, and others. He studied Industrial Design at California College of the Arts.</p><h4>The Event</h4><p>Structured as a fireside chat, the session will allow the audience to hear about Adam’s design journey, some of the interesting experiences along the way, and what Adam thinks is the future of design. In between, we will have time for questions.</p><p>See you all at iHub on 19th June between 6 pm and 8 pm. Remember to sign up for the event by going to the <a href="https://www.eventbrite.com/e/chat-with-adam-reineck-global-design-director-at-ideoorg-tickets-47059103044">Eventbrite page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e95404f8083" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/event-chat-with-adam-reineck-global-design-director-at-ideo-org-2e95404f8083">[Event] Chat with Adam Reineck — Global Design Director at IDEO.org</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using JTBD to Design a better voting experience for the Kalasha International Film Awards: Part 2]]></title>
            <link>https://medium.com/nairobi-design-community/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-2-8f95950a2e80?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/8f95950a2e80</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Dennis Muthuri]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 06:12:05 GMT</pubDate>
            <atom:updated>2017-11-21T06:12:04.667Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Using JTBD to design a better voting experience for the Kalasha International Film Awards: Part 2</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8u6-3StS7LWI3fLzDRKfQ.png" /><figcaption>Perspective Layout Overview of the Mockups.</figcaption></figure><blockquote>I recommend reading <a href="https://medium.com/nairobi-design-community/how-a-20-year-old-framework-can-refine-your-product-development-7cff3e724254">this article</a> and <a href="https://medium.com/nairobi-design-community/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-1-3740976b5105">this one</a>(Part 1), to understand the context of this one.</blockquote><p>In part one of this series, I broke down how the JTBD framework could be used to better the voting experience for the Kalasha International Film Awards. I dove into it’s ins and outs and applied the 5 step method Valiancy uses to implement the JTBD philosophy.</p><p>Today we’re going to get down and dirty with UI elements and wireframes describing how the experience could be implemented. The following assumptions were made while designing the mockups:</p><ul><li>The solution will be a web app accessible via a web browser given the fact that the current solution resides on the web.</li><li>The user will most likely be using a mobile phone to access the voting site.</li></ul><h4><strong>Plotting the User Journey</strong></h4><p>We distilled the entire user journey to the following phases:</p><ul><li><strong><em>Discovery:</em></strong> A users experience from clicking the link and what they meet as the first option. The moment they realise that voting exists and access the platform.</li><li><strong><em>Exploration:</em></strong> When a user has to view the contestants and identify whom they’re voting for.</li><li><strong><em>Promotion:</em></strong> The entire experience of voting for a contestant and leaving the platform.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VzRZ9W6ACWjh6kooVdFKg.jpeg" /><figcaption>Flow diagram showing the phases</figcaption></figure><p>These phases will give context to our visualisations and ensure that any features proposed go toward meeting a common goal.</p><h4><strong>Discovery Phase</strong></h4><p>The questions we struggled with at this point were</p><ol><li>Should we give a list of other contestants and allow the user to explore first? Or….</li><li>Should we allow a user to head straight into a category and vote immediately?</li></ol><p>One is great if someone just wants to explore, the other if a contestant would like to garner more votes from fans by giving them less friction during the exploration phase.</p><p><strong>Landing Page<br></strong>After a number of sticky notes and back and forth between team members, we settled that the elements on this screen which would allow the user to get the job done would be as follows.</p><ul><li>Probably a header indicating that this is the Kalasha awards voting for context purposes.</li><li>A search button which would display a search page allowing people to search for a contestant.</li><li>Listings of the nominees and their categories.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*JUytwgA0sELhXWQe7rG3kg@2x.png" /><figcaption>Homepage Mockup</figcaption></figure><p><strong>Search Page<br></strong>We figured that people would search for a movie or an artist rather than a category. However, the movie or the artist is nominated for a category. So to make results contextual and relevant, we would have the results display the context of the term to help people find the category from which they could vote.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*u5FKHeDi-y3QbVwFZ5B_uw@2x.png" /><figcaption>Search page as a separate overlay</figcaption></figure><h4><strong><em>Exploration Phase</em></strong></h4><p>By this step, the user has already selected the category and would like to view their contestants category with the intent to make a decision. At a high level, the main visual cues here are the category title and the contestants view.</p><p>Since the contestants can only be an actor or a movie, their respective cards will display different meta but will share a similar layout.</p><p><strong>Voting for actors<br></strong>The top visual cues being looked for when voting for the actors are:</p><ul><li>Actor Name</li><li>Actor Picture</li><li>Picture of movie actor was nominated for</li></ul><p>Secondary cues which may be great are:</p><ul><li>Their bio</li><li>Movies they’ve acted in.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*7UNPtL59IAZuAgzYTCabtA@2x.png" /><figcaption>Category List View for an Actor: Profile pic and a bio</figcaption></figure><p><strong>Voting for movies<br></strong>The top visual cues being looked for when voting for the movies are:</p><ul><li>Movie Name</li><li>Movie Cover Photo</li></ul><p>Secondary cues which may be great are:</p><ul><li>A synopsis of the movie</li><li>A trailer link to it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*wKpv2Gf5_ayk4Mo3aNYgww@2x.png" /><figcaption>Category List View for a Movie: The movie cover and a description</figcaption></figure><h4><em>Promotion Phase</em></h4><p>This is the part where the user has to select a contestant. Our goal here is to:</p><ul><li>Ensure the vote is made quickly.</li><li>Have the user verify their humanity to prevent dual voting.</li><li>Provide a great post voting experience.</li></ul><p><strong>Ensure the vote is made quickly.<br></strong>From the moment a user views the listings of actors and movies, the interface should clearly indicate where to Vote. The following suggestions came forth on how we could accomplish this:</p><ul><li>Have a Star icon with a vote label.</li><li>Have an explicit ‘Vote’ button.</li><li>Make the entire card a clickable entity and have a vote button slide from the bottom of the screen.</li></ul><p>We ended up settling for the explicit vote button because we didn’t want people to guess what to do. Making the entire card clickable was down voted because the risk of having “mistake” clicks when scrolling would have been to high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*TRLHrHYbJ76zMKo-RRlcLw.jpeg" /><figcaption>Vote button explicitly defined on Both Views</figcaption></figure><p><strong>Have the user verify their humanity to prevent dual voting.<br></strong>Now that the user has voted for their favourite contestant, they need to show human proof which includes submission of data which would both be:</p><ol><li>Hard to duplicate.</li><li>Time consuming to duplicate.</li></ol><p>Our choices were a combination of social login and phone number verification <em>(for those who have the patience to input a unique digit code that would be sent to the phone number, and don’t want to link their social account with the site.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*_HBXU1oYhWBEUQEezzJZDw@2x.png" /><figcaption>Humanity Verification as a modal</figcaption></figure><p><strong>Post-voting Experience<br></strong>How should it all end? We could either decide to leave the user hanging or create a loop to keep them within the site for more exploration and have them leave at their own volition.</p><p>We decided the screen should allow them to:</p><ul><li>Explore more categories.</li><li>Garner more support for the contestant they voted for by social sharing</li></ul><p>A social benefit of this voting experience is that exploration would be a great way to improve the voters knowledge of the Kenyan film industry. Whether a contestant get’s voted for or not, the visual exposure would hopefully allow visitors to find out more about them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/188/1*7guevhhJYEC8xx1XXKAOeQ@2x.png" /><figcaption>Post Voting Experience. A loop of delightful actions</figcaption></figure><p>Thanks for reading this far.</p><p><a href="https://valiancy.org/#contactus">Sign up for our bi-weekly mailing list </a>to receive a first peek on how to create an interactive prototype of the screens using <a href="http://www.adobe.com/africa/products/xd.html?scid=social58630676">Adobe XD</a>.</p><h3>Before you go</h3><p><strong>Clap</strong> 👏 👏 👏 if you enjoyed this article, so others can find it<br><strong>Comment</strong> 💬 if you have something to say<br><strong>Follow me</strong> <a href="https://medium.com/u/f312e72d852e">Dennis Muthuri</a> to keep up with my other articles</p><figure><a href="https://valiancy.org/?utm_source=medium_post&amp;utm_medium=cta_banner&amp;utm_campaign=subscriber_list#contactus"><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*pxArZPhBiBuKuati_76RPQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f95950a2e80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-2-8f95950a2e80">Using JTBD to Design a better voting experience for the Kalasha International Film Awards: Part 2</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using JTBD to Design  a better voting experience for the Kalasha International Film Awards: Part 1]]></title>
            <link>https://medium.com/nairobi-design-community/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-1-3740976b5105?source=rss----f8ce58153298---4</link>
            <guid isPermaLink="false">https://medium.com/p/3740976b5105</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[nairobi-design-community]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <dc:creator><![CDATA[Dennis Muthuri]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 11:55:18 GMT</pubDate>
            <atom:updated>2017-11-20T16:05:59.200Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using JTBD to Design a better voting experience for the Kalasha International Film Awards: Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIqtYyafg5k6DZ97nEzj0g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/OQMZwNd3ThU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Helloquence</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In my previous post — <a href="https://medium.com/nairobi-design-community/how-a-20-year-old-framework-can-refine-your-product-development-7cff3e724254">How a 20-year-old Framework can refine your product development </a>— I explained the essence of the Jobs To Be Done(JTBD) framework and how to apply it — mostly from a ten thousand foot view.</p><p>Today I’ll go deep into the practical use of the framework to increase product adoption, by knowing what job your users are trying to do and how to build on it. I will link the motivation, situations, and outcomes together in an interface to show how you can go about it.</p><h4>Our Current Predicament</h4><p>It’s the last quarter of the year and the <a href="http://kalashainternational.com/awards/">Kalasha International Film Awards</a> are around the corner. Films and actors have been submitted for nomination under various categories and the Kenya Film Commission invites the public to vote for their nominees.</p><p>A friend who happens to have a drama out sends me a link via a Whatsapp group I’m in to vote for her film. The link resembles this format(<a href="https://t.co/6wxcKZeP7Y?amp=1">https://t.co/6wxcKZeP7Y?amp=1</a>) and there’s no telling where it’ll lead to at first glance, given the lack of a legible domain name. I click on it…. my anticipation builds… and what loads up on my phone…..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvc_zdkCpeZa0lXUli20Kw.jpeg" /><figcaption>The official Kalasha International Awards Voting System as <a href="http://goo.gl/forms/jLSDrwkHsiPG8bMH2">Google Form</a></figcaption></figure><p>I vote for her, and try to submit the form. To my frustration, I have to select a contestant from EACH of the 29 categories listed. Patiently I guess my way through the nominees and finally, I submit the form.</p><p>Instead of diving head first into bashing the voting mechanism employed by the Kenya Film Commission, let’s explore why it seemed like a reasonable choice for them.</p><ol><li><strong>It’s a great low-cost way of solving the getting the job done.</strong> They need to gather data from the public and they’ll do it the best and most objective way they know how.</li><li><strong>No long tendering process for a system.</strong> The form in its simplicity doesn’t require a long tendering process to build some fancy voting system with flashy pictures, drama bios, awesome cover photos it just does the job. It collects the users’ opinions on who they like by giving them the most basic unit of information about that particular asset — their name, the program and that’s it. Pretty nifty if you ask me.</li><li><strong>It proves that the people voting are human</strong>. Given that it’s a Google form, you can only use it if you have a Google account. This adds a 98% assurance that the person voting is human (<em>the 2% accounts for evil bots that may be employed to simulate the same</em>). This adds to the integrity of the results.</li></ol><h4>Jobs To Be Done Thought Process to the Rescue</h4><p>If my <a href="https://valiancy.org/">consulting firm</a> — Valiancy — was contracted to build the next version of this solution, we would have followed the simple steps below to help us use the JTBD framework.</p><ol><li>Start with the high level job</li><li>Identify smaller jobs which help resolve the high level job</li><li>Observe how people solve the problem now (the tool they currently use).</li><li>Come up with a Job Story to investigate the causality, anxieties and motivations of what they do now.</li><li>Create a solution which resolves that Job Story.</li></ol><h4>1. Start with the high level job</h4><p>The high-level job of this solution is to accurately represent the participants of the awards in a positive light and give fans the opportunity to express love for their favorite shows/personalities.</p><p>Currently, the form does the core part of giving the participants a chance to get voted for by their fans but it doesn’t portray them as best as it could. Many fans may not recognize names of their favorite actors but would know their faces instead.</p><p>Contextual uses where a person is voting for only one or two people haven’t been well thought out. You have to fill out the entire form(which is really long) just to vote for 1 person.</p><h4>2. Identify a smaller job which helps resolve the high level job</h4><p>A user needs to select a show or actor they love, prove that they’re human and finish voting for that person.</p><p><strong><em>NB:</em></strong><em> The stopper where people have to vote for everyone is more of a technical imposition of the form rather than a requirement. Remember, we’re keeping our minds on the job here.</em></p><h4>3. Observe how people solve the problem now (the tool they currently use)</h4><p>The following is a thread where I got the link and these are some real reactions to the current solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x90EH2inntTN-n724vNZsg.jpeg" /><figcaption>Screenshot of real users reactions. Actual Names have been whited and greyed out.</figcaption></figure><p>We clearly see that people are voting, contestants are represented, but because they have to fill out everyone’s name, they are forced to LIE when choosing actors/films in categories they don’t know.</p><p>This poses a huge <strong>integrity</strong> problem to the final results for the owners of the form (Kenya Film Commission) and contestants. The probability of someone getting undeserved votes is real.</p><p>The current solution is also closed up to people who have Google accounts only. This may be a negotiable issue given the high Android Smartphone penetration in Kenya but it’s an issue which can’t be glossed over.</p><p>One other thing to note is how, the contestants are garnering votes, they’re using social media platforms and sharing through mobile. This automatically implies that this form will be opened and filled in by a mobile communication device.</p><p>When you couple this reality with the mandatory selection of a person from the 29 categories in the form, where each has at least 4 options to evaluate and the cognitive load on the user is too much. Drop off rates at the sight of the form will probably be high.</p><h4>4. Come up with a Job Story to investigate the causality, anxieties and motivations of what they do now</h4><p>Framing the current situation in a job story we will say:</p><ol><li>When fans want to vote for a contestant…</li><li>They will visit the google form presented to them where they’ll search for their contestants category and select the contestant…</li><li>And fill out every other category as well…</li><li>So that they can submit their vote to Kenya Film Commission.</li></ol><p>If we were to give a context where a fan doesn’t have a Google account, we’d say that</p><ol><li>When fans want to vote for a contestant…</li><li>….They will visit the google form presented to them where they’ll be asked to sign into Google…</li><li>And fill out every other category as well…</li><li>…So that they can search for their contestants category and vote for their contestant.</li></ol><p>Framing the current solution as a job story and adding context already surfaces the pain points to be solved.</p><h4>5. Create a solution which resolves the job story</h4><p>This is the point where the team at Valiancy decided to come up with the following considerations:</p><ul><li>A user has to have the capability to vote for just one person and not be forced to vote for people they don’t know or like</li><li>The user has to be able to vote only once, so some form of human proof will be required to ensure results are real</li><li>The user could use more contextual information on who the contestant they are voting for is:</li><li>For an actor that would be: Their name, the category being voted for and their picture. Additional information would be movies they’ve acted to help the users gauging their practical performance and know more about their work.</li><li>For a movie/drama/animation that would be: Its name, its category, the cover photo of the movie, the main actors in the movie and the director. Additional information would be a brief 200/160 word synopsis of the movie to ensure that the fan can gloss through and make a quick voting decision.</li></ul><p>Take time and soak in those points for now. In my next article, I’ll give detailed and contextual wireframes of what the potential interface would look like.</p><p><a href="https://medium.com/@dennismuthuri/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-2-8f95950a2e80?source=user_profile---------1----------------"><strong><em>Checkout part 2 of this article here.</em></strong></a></p><p>To learn more about the Jobs To Be Done Framework, you can checkout the following resources:</p><ul><li>Intercoms book: <a href="https://www.intercom.com/books/jobs-to-be-done">https://www.intercom.com/books/jobs-to-be-done</a></li><li>A talk from Intercom discussing how they adopted this method: <a href="https://www.youtube.com/watch?v=VNTW_9mFM7k">https://www.youtube.com/watch?v=VNTW_9mFM7k</a></li><li>Jobs To Be Done application in marketing: <a href="https://www.youtube.com/watch?v=k0NRo3yLqxM">https://www.youtube.com/watch?v=k0NRo3yLqxM</a></li><li>An in-depth talk of how Jobs-To-Be-Done can be used as a framework for Disruption<em>(actual name of the talk, not an article buzzword)</em>: <a href="https://www.youtube.com/watch?v=qBRw38Y06No">https://www.youtube.com/watch?v=qBRw38Y06No</a></li></ul><h3>Before you go</h3><p><strong>Clap</strong> 👏 👏 👏 if you enjoyed this article, so others can find it<br><strong>Comment</strong> 💬 if you have something to say<br><strong>Follow me</strong> <a href="https://medium.com/u/f312e72d852e">Dennis Muthuri</a> to keep up with my other articles</p><figure><a href="https://valiancy.org/?utm_source=medium_post&amp;utm_medium=cta_banner&amp;utm_campaign=subscriber_list#contactus"><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*pxArZPhBiBuKuati_76RPQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3740976b5105" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nairobi-design-community/using-jtbd-to-design-a-better-voting-experience-for-the-kalasha-international-film-awards-part-1-3740976b5105">Using JTBD to Design  a better voting experience for the Kalasha International Film Awards: Part 1</a> was originally published in <a href="https://medium.com/nairobi-design-community">Nairobi Design Community (NDC)</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>