<?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 Kai on Medium]]></title>
        <description><![CDATA[Stories by Kai on Medium]]></description>
        <link>https://medium.com/@huangchikai?source=rss-fc2c3a26ed1f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f6atDl7WAxoS2KBtzzl3mQ.jpeg</url>
            <title>Stories by Kai on Medium</title>
            <link>https://medium.com/@huangchikai?source=rss-fc2c3a26ed1f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:59:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@huangchikai/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[Designing a New Way to Get Cash While Travelling Phase 1: Inspiration]]></title>
            <link>https://medium.com/@huangchikai/designing-a-new-way-to-get-cash-while-travelling-phase-1-inspiration-344a0914a944?source=rss-fc2c3a26ed1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/344a0914a944</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Kai]]></dc:creator>
            <pubDate>Mon, 16 Jan 2017 09:23:45 GMT</pubDate>
            <atom:updated>2017-04-14T11:06:06.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q5lyWjK9SX6yFopIl8qY8w.jpeg" /><figcaption><a href="https://unsplash.com/photos/r4He4Btlsro">https://unsplash.com/photos/r4He4Btlsro</a></figcaption></figure><h4>A series of 3 articles showcasing the product development process that I learnt and practised at <a href="https://www.alphacamp.co/sg/">Alpha Camp</a></h4><p>In this article, I have documented the <strong>Inspiration </strong>phase of the product development process. It includes topics like collaborative innovation, user research, research synthesis and research deliverables.</p><h3>A Serendipitous Insight</h3><p>I travelled to Seoul in early October 2016. Towards the end of the trip, I ran out of cash and needed $15 take a bus to the airport. I didn’t want to withdraw cash from the ATM because my bank would charge me a $5 fee. In the end, I wasted 1 hour getting money changed at a local bank and I was forced to change $50 worth of cash because the teller was unable to provide change in my home currency. Then I thought to myself,</p><blockquote>“Today, we can get a ride from a stranger in a foreign place by tapping a button on our phone, so why can’t we do the same with cash?”</blockquote><p>Basically, we need a simple way to buy cash (in local currency) with our credit cards. This is because most travellers have credit cards but most transport services and small businesses only accepts cash.</p><h3>Alpha Camp Pitch Night</h3><p>The timing could not have been better. Just before the trip, I was offered a spot in an accelerated <a href="https://www.alphacamp.co/sg/full-time-product-design/">product design course</a> operated by Alpha Camp. The core deliverable of this course is to work on a startup project with other students who were attending the accelerated coding courses. The team formation process was very similar to how things work at startup weekend events.</p><p>Basically, each student (16 of us) had to pitch a product concept or a problem that he/she would like to tackle. After that, we needed to anonymously vote for the most promising ideas. The goal was for Alpha Camp to identify 4 most voted ideas to be the startup projects for our cohort.</p><p>During my pitch, I spoke about my encounter in Seoul and proposed the product concept of <a href="http://www.peerex.co/">Peerex</a>, which stands for “peer to peer money exchange”. Fortunately (and apparently), Peerex came in as one of the most voted ideas. As the founder of a product idea that was accepted by the course, I had to recruit and lead a team to turn this idea into a reality. After about 20 minutes of networking, the Peerex team was formed. It consists of the following awesome people:</p><ul><li><a href="https://sg.linkedin.com/in/camillelayugan">Camille Layugan</a> from product design course</li><li><a href="https://sg.linkedin.com/in/gabrielecastaldo/en">Gabriele Castaldo</a> from iOS mobile app development course</li><li><a href="https://sg.linkedin.com/in/poondaqian">Poon Da Qian</a> from web full stack development course</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ReeOeE1P1e2BGO_K0zSwZQ.jpeg" /><figcaption>Everyone anticipating which 4 ideas would be selected at the Alpha Camp pitch night</figcaption></figure><p>On hindsight, this casual and simple (also rather random) process turned out to be an elegant way for collaborative innovation. As I study more about design processes, I realised that the pitch night itself was like the design thinking process which involves divergence and convergence. Getting every student to pitch was basically a divergent process in which we crowdsource ideas and perspectives. Then we prioritise and converge to the strong ideas through anonymous voting.</p><p>Generally speaking, the team formation process also act as an early indication on the desirability of the idea. If a few guys are equally excited to work hard on something for months without getting paid, I guess we are probably onto something :)</p><h3>Design Research Preparation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/391/1*PDbr9zIdhzHctSWPWWjXDQ.jpeg" /><figcaption>IDEO Human-Centred Design (HCD) Design Process</figcaption></figure><p>So… our team was in place, and we had attended the human-centred design classes taught by <a href="https://www.linkedin.com/in/keithoh">Keith</a>, former IDEO design lead. This was where sh*t got real. Time to put what we have learnt into practice.</p><p>Since the Peerex concept is based on a typical transaction mechanism used by ride hailing or food delivery apps, we knew that it’s technically <strong>feasible</strong> for sure. But we can’t be sure that it’s <strong>desirable</strong>, and this is why we need design research.</p><p>First things first, we needed to come up with a research plan.</p><p>A huge part of human-centred design requires conducting in-depth interviews with potential users. A research plan is used to provide guidance on who we should talk to and what we would like to learn from them.</p><p>Below are the steps we took to create a research plan.</p><h4>Step 1: Decide on a starting design challenge</h4><p>As far as I know, a design challenge is also known as a problem statement. It is in the format of a question starting with the phrase “How might we”.</p><p>Camille and I came up with the following.</p><blockquote>How might we provide easier access to cash for travellers?</blockquote><h4>Step 2: Create an affinity diagram</h4><p>As a team, we used the affinity diagram exercise to capture a rich diversity of thoughts towards the starting design challenge. This is also a great opportunity to engage the developers during the research phase. By letting their voices heard earlier on, we would get their emotional buy in on what had to be built later on.</p><p>The goal of this step was to get everyone to consider the design challenge and respond to the following questions:</p><ol><li>What do we already know?</li><li>What questions do we have?</li><li>What early ideas do we have?</li></ol><p>This exercise is typically done by getting everyone to write their responses on different coloured post-its and paste them on a foam board. To provide better visual distinction and consistency, a specific coloured post-its is dedicated to each question.</p><p>Without the luxury of waiting for everyone to be available to do this together in one place, I decided to get things moving with a <a href="https://trello.com/">Trello board</a>. This allowed us to contribute our responses to the board at our own time. Each response was capture with a Trello card and labelled with a dedicated colour. We gave ourselves a few days to populate this board and agreed to meet in person for the next step.</p><h4>Step 4: Organise the affinity diagram into themes</h4><p>After creating our virtual affinity diagram on Trello, we had to make sense of it by clustering the related cards together. It is really important for teams to do this together in person because this is a tricky process which requires clarification, discussions, debates and etc. We were aware that this would take time. Therefore we told ourselves that it was perfectly normal to go back and forth, arrange and rearrange the cards as the we talked through what was emerging.</p><p>What we did exactly was to create a couple of new lists on the same Trello board. Then each team member took turns to pick out 3–5 cards they find most interesting, and move them under the new lists. We tried our best to put related cards into the same list, and if the card was not compatible with any of the existing lists, we were free to create a new list. Once we noticed that a list has about 3 to 5 cards under it, we would give that list a name so that it would save us time just by looking at the list name as we continue with clustering. We were also free to rename the lists as we added more cards to them. It took us about 1.5 hours for everyone to be satisfied with the outcome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nen2tbLACHz2nTkSU6SLtQ.png" /><figcaption>Affinity diagram arranged into themes on a Trello board</figcaption></figure><h4>Step 5: Decide who to interview</h4><p>This was when we asked ourselves who can help us explore the major themes that emerged from our design challenge. In other words, what kind of user profile would feel strongly about these themes?</p><p>Our guess was it would be people who make frequent short trips to different parts of Southeast Asia (SEA) because,</p><ol><li>There are still many places in SEA that only accept cash.</li><li>Since these travellers are “country hopping”, they are unlikely to go to the same country more than once.</li></ol><p>In the end we decided on the following user profiles:</p><ul><li>Backpackers who have travelled in SEA before</li><li>Digital nomads based in SEA</li><li>International students based in Singapore</li></ul><h4>Step 6: Create an interview discussion guide</h4><p>It’s important to note that an interview is not a survey with a checklist of multiple choice questions. Instead, it’s an open ended conversation in which we explore the view points of the interviewee. This also means that the discussion guide is not script.</p><p>A discussion guide is basically a list of potential talking points or conversation starters, usually group into the following sections:</p><ol><li>Introduction on why we are doing this interview</li><li>Getting to know the interviewee’s demographics and psychographics</li><li>Talking points for the each major theme for the design challenge</li><li>Explain/show product concept to get some early feedback (optional)</li></ol><p>To get a clearer picture, do check out the <a href="https://www.evernote.com/l/AB1NhfxMbadJob1kTB4OYh-lUToY2M9qQY8">discussion guide</a> that I created.</p><p>To sum up, the output of step 5 and 6 make up the research plan and it would be good to involve the developers from step 2 to 5.</p><h3>Get Out of the Building</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lP90lzYvPJkXgXZRfrawBA.jpeg" /><figcaption>A startup mantra popularised by innovation guru Steve Blank</figcaption></figure><p>We had done enough work in the building, it was time to get out and talk to real people!</p><p>Camille and I must have spoken to more than 20 travellers in total. Out of these conversations, we managed to conduct 5 formal in-depth interviews. Here is how these formal interviews were planned and conducted:</p><ol><li>Everyone including the developers reached out to their personal network to identify prospects who were willing to speak with us.</li><li>Camille and I followed up with these prospects to schedule for a meet up in a cafe. If the prospect was based overseas, we would schedule for a Skype call.</li><li>For each interview, one of us would be fully engaged in the conversation and the other person would just take notes.</li></ol><p>A good in-depth interview would last 40 to 60 min. Instead of trying to go through the entire discussion guide, we should take the time to listen intently and decide when to go deep.</p><blockquote>Pro Tip: A good heuristic is to ask “why” repeatedly whenever we hear something new or interesting.</blockquote><h3>From Learnings to Insights</h3><p>One of the most challenging parts of the human-centred design process is to transform our research into meaningful and actionable insights. The affinity diagram technique was used again to help us make sense of the stories that we have collected from the interviews.</p><h4>Step 1: Capture Learnings</h4><p>To set this up, I created a new Trello board and have one list for each interview. The top of each list was a card that contains the name, photo and profile summary of the interviewee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrYGAymmezrVFdGDmh2aig.png" /><figcaption>Setting up the Trello board to capture learnings</figcaption></figure><p>Then Camille and myself got together to reflect on the interviews by thinking through the following questions:</p><ol><li>What’s the most memorable or surprising thing they told us?</li><li>What did this participant care about the most? What motivates him/her?</li><li>What frustrated him/her?</li><li>What other questions would we like to explore if we had another conversation with this person again?</li></ol><p>As responses popped into our heads we would quickly capture them in Trello cards under the corresponding lists. Note that this capturing process could be done right after completing 1 or 2 interviews so that the learnings remain vidid in your mind.</p><p>Here are some of the most interesting comments we have heard:</p><blockquote>“Never trust money changers on the street. If a marketplace is not online, something must be wrong.”</blockquote><blockquote>“Not sure how much cash to carry. Even the locals can’t advise me, cos they don’t do touristy things.”</blockquote><blockquote>“Not safe to carry too much cash. I learnt it the hard way, my money for the entire trip was stolen.”</blockquote><blockquote>“I’m worried that I might get stranded if I don’t have enough cash”</blockquote><p>We also took the opportunity to tell the interviewees the idea of getting cash from a nearby person. They responded with questions like:</p><blockquote>“How do I know if the currency is real?”</blockquote><blockquote>“How do I know if the cash pick location is safe?”</blockquote><blockquote>“Would the coverage of this service be as good as ATMs?”</blockquote><h4>Step 2: Identify Major Themes</h4><p>After all the capturing was done, we took about another hour to organise the cards into lists of themes. This was just like what we did earlier when preparing for the research plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUZQq13TxjIbprD4BXGBtQ.png" /><figcaption>Learnings clustered into major themes</figcaption></figure><h4>Step 3: Create Insight Statements</h4><p>This is where the magic happens. The process of creating insight statements is hard to grasp because there is no fixed formula for creating the perfect insight statements. Nevertheless, this is also what makes design fun and exhilarating :)</p><p>An insight statement is a succinct expression of our learnings around a certain theme. It is used to support our core assumptions, offer new perspectives or provide focus towards our design challenge.</p><p>A great insight statement would have all or a combination of the following qualities:</p><ul><li>Actionable</li><li>Human-centred</li><li>Counter-intuitive</li><li>Highlights the tension between users and systems</li><li>Explains why a theme presents an important challenge</li></ul><p>Camille and I took about 20 minutes to draft 1 to 3 insight statements for each theme on our own. Then we got together to share what we have produced and experimented with various wordings and structures to best communicate the insights. This also involved getting rid of redundant points and merging the most compelling points.</p><p>In the end, we managed to agree on a key insight statement for each theme:</p><p><strong>CONVENIENCE</strong></p><blockquote>They are many apps for travellers to get around a city and find places to stay, but there are no apps to help travellers with getting cash.</blockquote><p><strong>PAYMENT PREFERENCE</strong></p><blockquote>Most travellers have credit cards but very often public transport and small businesses only accept cash.</blockquote><p><strong>COST</strong></p><blockquote>Banks are trustworthy and offers convenience with ATMs but travellers struggle to decide if they should pay the high ATM fees (typically $5)</blockquote><p><strong>SAFETY</strong></p><blockquote>It’s not safe to carry too much cash when travelling but travellers are worried about running out of cash at the same time</blockquote><p><strong>TRUST</strong></p><blockquote>Money changers are easily found at airports and touristy locations but travellers are afraid of getting ripped off by them</blockquote><p>I have to admit that it’s quite easy to get distracted during this process because our brains are naturally tuned to come up with solutions right away. Fortunately, <a href="https://sg.linkedin.com/in/keithoh">Keith</a> had shared a little hack to help us turn this distraction into progress.</p><blockquote>“When a solution or idea pops into your head, ask yourself why you came up with this solution. Your reasoning would form the basis of your insights.”</blockquote><h3>A New Design Challenge</h3><p>Starting with a broad design challenge earlier in the process gave us opportunity to diverge so as to avoid the local maxima problem. The purpose of creating insight statements was really to develop the confidence to converge to a narrow and focused design challenge.</p><p>Armed with the insights statements and feedback on the Peerex concept, we managed to refine the design challenge.</p><p><strong>FROM:</strong></p><blockquote>How might we provide easier access to cash for travellers?</blockquote><p><strong>TO:</strong></p><blockquote>How might we allow travellers to access cash in small amounts with confidence and convenience?</blockquote><h3>Meet Mike the “City Hopper”</h3><p>By this point we were super eager to start with the ideation process and sketching out our designs. However, in order to wrap up the research deliverables, we needed to be internally aligned on exactly who we are designing for. This had to be much more specific and concrete than the user profiles we came up with earlier.</p><p>Basically, we needed to create 2 simple documents: user persona and user scenario.</p><h4>User Persona</h4><p>This a document in which we describe a psychological real character by integrating what we have learnt from the various user profiles. On hindsight, the benefits of user persona was much clearer in the later part of the design process. It basically acted as the north star for us to prioritise or discard features. Whenever we had doubts about a feature, we would just ask ourselves, “would [persona name] really find this useful?”.</p><p>We created the user persona as Trello card and here is what it looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XqNPHLd223lndrxejy8h3A.png" /></figure><h4>User Scenario</h4><p>This is a document that focuses on a specific story around the user persona. It helps to understand the following:</p><ol><li>What do they want to do?</li><li>Why do they what to do that?</li><li>What are they expecting?</li></ol><p>User persona helps with feature decisions whereas user scenario helps with determining the ideal user flow.</p><p>We documented our user scenario on a Trello card as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFUSpbmX4Eb5UPk44lCIVw.png" /></figure><h3>Summary</h3><p>So this is it! We have come to end of the <strong>Inspiration</strong> phase.</p><p>To recap, the real work of this phase started with a broad design challenge and ended with the following deliverables:</p><ol><li>Insight statements</li><li>A more focused design challenge</li><li>User persona and user scenario</li></ol><p>In practice, these are essential deliverables for us to keep our colleagues or clients in the loop before moving into the next<strong> </strong>phase.</p><p>Please stay tuned for my next article on the second phase of product development, <strong>Ideation</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=344a0914a944" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>