<?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 Jieyun Yang on Medium]]></title>
        <description><![CDATA[Stories by Jieyun Yang on Medium]]></description>
        <link>https://medium.com/@Jieyun?source=rss-36ddb993d0a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LWoedkN361elhNggoxANiA.png</url>
            <title>Stories by Jieyun Yang on Medium</title>
            <link>https://medium.com/@Jieyun?source=rss-36ddb993d0a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:48:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Jieyun/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[4 factors of user]]></title>
            <link>https://medium.com/@Jieyun/4-factors-of-user-db210fc44c30?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/db210fc44c30</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Wed, 11 Mar 2020 13:40:26 GMT</pubDate>
            <atom:updated>2020-09-26T11:57:57.021Z</atom:updated>
            <content:encoded><![CDATA[<h3>4 traits of user</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*o2kmcpPYNku3fEaW.png" /></figure><p>Over the past few years, I’ve been conducting user research to understand users. Although each project targeted different users, they share some patterns that can be summarised into 4 traits.</p><h3>1. Individuality</h3><p>Not only does the distinction of users exist between personas, but every user is distinct in light of unique character, perception, behaviour and need. Therefore, although modelling users by creating personas and customer journey maps helps to efficiently consolidate and align the understanding about the users, it’s still important to emphasise that your personas ≠ your users, your user journey maps ≠ your users’ interactions.</p><h3>2. Contextuality</h3><p>Without context, “user” is just a word. Context has a significant impact on a user’s behaviour, perception and need. For instance, If I needed to get a ride, I normally would choose UberPool to save money as opposed to UberX. But if I had an important meeting at 9 am and I was in a rush, I would go for UberX rather than UberPool. The priority of my need changes, so does my behaviour and perception.</p><h3>3. Plasticity</h3><p>Users are plastic. Despite both social and physical environments mould their needs, perception and behaviour, they can be still easily shaped by product. As in the previous example, if I had received a 10% off voucher for UberX, I would choose it even if I wasn’t in a rush.</p><h3>4. Bounded rationality</h3><p>Humans are born rational and irrational. Everyone desires to maximise utility and minimise cost, thus we are rational in the way of weighing up returns and investments when we make decisions. However, our rationality is bounded as it consumes energy and we have limited knowledge, experience and skills, we often tend to follow our gut, for things are less important or less costly in particular. Let’s go back to the Uber example one more time. I would end up paying more for UberX than UberPool regardless of whether I had a 10% off voucher or not. But I still wouldn’t bother calculating if the time I could save worth the money.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db210fc44c30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Users are not the centre of design]]></title>
            <link>https://medium.com/@Jieyun/users-are-not-the-centre-of-design-8ea009fd2328?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ea009fd2328</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usdc]]></category>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 05:12:50 GMT</pubDate>
            <atom:updated>2019-09-19T05:12:50.321Z</atom:updated>
            <content:encoded><![CDATA[<p>Users are not the centre of design. It might make you feel like going back to 90s when there’s no such a thing called user experience. You didn’t get it wrong. Users are crucial for design, but they are not THE most important, at least not THE only important part.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/0*5-jIHKg4K65TIJad.jpg" /><figcaption><a href="https://upload.wikimedia.org/wikipedia/commons/7/77/Leonardo_da_Vinci_-_Bicycle_-_Pedretti_2.jpg">https://upload.wikimedia.org/wikipedia/commons/7/77/Leonardo_da_Vinci_-_Bicycle_-_Pedretti_2.jpg</a></figcaption></figure><p>Let me begin with the role of a firm. Why does a firm exist? In 1937, Ronald Coase wrote an essay “The Nature of the Firm”, which was awarded him the Nobel prize for economics. In that essay, Coase explained that firms exist because they reduce the transaction costs that emerge during production and exchange, capturing efficiencies that individuals cannot. For example, why does Google exist? Because Google reduces the costs of people obtaining information. Compared with asking someone or looking up in newspaper or books, there are only need a few clicks required to reach the information.</p><p>If a firm exists to reduce the transaction costs of society, here comes another question, why do many firms exist? Is it possible that only one firm exists? That’s what happened to China in the planned economy era when we found out that the transaction costs of society significantly increased rather than decreased. Why? Because the transaction costs are not only external but also internal. Coase concluded that the internal transaction costs increase when a firm expands. As long as internal transaction costs exceed external ones for the same kind of exchange, a firm stops expanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*JDSh9EC4R_dxYOCz.png" /><figcaption><a href="https://upload.wikimedia.org/wikipedia/commons/thumb/a/ad/Market-Hierarchy-Model.png/500px-Market-Hierarchy-Model.png">https://upload.wikimedia.org/wikipedia/commons/thumb/a/ad/Market-Hierarchy-Model.png/500px-Market-Hierarchy-Model.png</a></figcaption></figure><p>Therefore, as long as a firm exists, it has to face a challenge — minimise both external and internal transaction costs. It also means that the role of each function in a firm can be summarised as either minimising external transaction costs or minimising internal transaction costs.</p><p>As for design, to reduce external transaction costs, we research to understand users and design solutions to meet their needs. In this case, users are indeed the centre. However, to minimise internal transaction costs, the organisation is the centre. To make sure design is excusable and aligns with the expectations of the organisation, we facilitate the stakeholders’ decision-making process, influence and motivate the teams. (<em>To some extent, it can also explain why Product Designer role emerges and becomes more and more popular, as it reduces the collaboration costs between roles.)</em></p><p>However, based on my experience, regardless of experience, many designers don’t realise the importance of their roles in reducing internal transaction costs. It shouldn’t be something owned by a manager or team lead, nor something you can avoid by going to an early-stage startup. The more complex and challenging problems you try to solve, the more collaboration required, the more important to balance or shit the centre from users to business and organisation. It’s an essential part of design.</p><p>Hence, for designers, we also need to develop the business and organisation mindset. Some tips I would like to share:</p><ul><li>Identify the stakeholders you need to engage as early as possible.</li><li>Try to collect information about the organisation’s priorities, constraints, risks and concerns. Also, adjust the design approach accordingly.</li><li>Get a sense the stakeholders’ interests in the project and their benefits or sufferings from the success or failure of your work</li><li>Collaborate, facilitate and nudge the design with the stakeholders. Better ideas are usually generated in a collaborative environment.</li><li>Evaluate the costs required for changes. We are living in a world full of bad designs, and they exist not because no one has better ideas or no one cares. Instead, they probably are the most rational and affordable solutions for now.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ea009fd2328" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating certainty and embracing uncertainty]]></title>
            <link>https://uxdesign.cc/creating-certainty-and-embracing-uncertainty-8cd0d6d19f5?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cd0d6d19f5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[certainty-and-doubt]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Thu, 20 Dec 2018 21:36:33 GMT</pubDate>
            <atom:updated>2018-12-21T13:08:22.880Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nabjgIOpSRpfmExhjIhHHw.jpeg" /></figure><p>Certainty and uncertainty are both important and we need to be able to balance them well — Certainty is the foundation of trust, you need to create certainty for other people. Uncertainty is the foundation of growth, you need to embrace uncertainty for yourself.</p><h3>Create certainty to build trust</h3><p>In UX design, people talk about intuitive design all the time. Do you often hear that “<em>I don’t know why, but I just feel it’s not intuitive…</em>”. But what does “intuitive” exactly mean? My interpretation is to create certainty for users.</p><h4>Certainty is the foundation of trust</h4><p>People always prefer certainty and dislike uncertainty.</p><p>In 1986, Amos Tversky and Daniel Kahneman introduced a psychological phenomenon called <a href="https://en.wikipedia.org/wiki/Certainty_effect">certainty effect</a>, where<strong> </strong>a customer pays more attention or picks deals wherein they are certain to benefit rather than taking deals where the profit is not certain.</p><p>For example, what would you choose:</p><ul><li>​​A. A sure gain of $200</li><li>B. An 80% to win $350 (20% chance to win $0)</li></ul><p>If you’re like most people, you will choose option A — a sure gain. However, if you do the math, an 80% probability of winning $350 carries an expected value of $280 (0.8 x 350). So, most people would give up an expected $80 of value just for certainty.</p><p>Certainty really matters when people make decisions, it can give them a sense of security and it earns trust. Nobody would like to invest time and money on an uncertain thing.</p><p>On <a href="http://airtasker.com/">Airtasker</a>, we’ve found that the tasks with more detailed description will get more offers compared with the ones with vague details. Also, Taskers with high completion rate, good reviews and corresponding experience are more likely to get assigned.</p><p>Therefore, to make the users trust the product and behave as expected, you should create certainty for them.</p><p>Take Youtube as an example, it allows users to skip the ad after 5 secs. On the one hand, compared with other products that users can’t skip the ad or they have to wait for a few mins to be able to do so, it offers a better experience.</p><p>On the other hand, 5 secs are pretty short, users are more likely to wait and watch it rather than go away and do something else. In this way, those who are interested in the ad can be more likely to have their attention captured and continue watching it.</p><p>As Youtube only charges when someone chooses to view the ad for at least 30 seconds or engages with the ad, it provides such great certainty with the advertisers that they can make sure every penny will count. Advertisers put great trust in this service, which makes it so popular.</p><h4>Start with empathy to create certainty</h4><p>A designer’s responsibility is to create certainty for the customers, with fewer efforts required and more delights offered. To achieve that, the first step is to empathise with customers, understand what specific certainty they need in each particular scenario.</p><p>Survey, Desktop Research, Customer Interviews, Contextual Inquiries, Empathy Map, Persona, Customer Experience/Journey Map, etc. These are some methods I usually use to create empathy and synthesise information to understand what certainty customers need.</p><p>For example, by creating the Customer Experience Map, you can understand what customers expect to do, to know and to feel so that in next step, you can create corresponding content to deliver the certainty they need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o7sNzT1ODSOTz5Nc.jpg" /><figcaption>Image source: <a href="https://web.archive.org/web/20150825070205/http://www.adaptivepath.com:80/ideas/the-anatomy-of-an-experience-map/">Adaptive Path</a></figcaption></figure><h4>Create content with certainty</h4><p>There are some fantastic insights from the <a href="https://en.wikipedia.org/wiki/Information_theory">Information theory</a> proposed by <a href="https://en.wikipedia.org/wiki/Claude_Shannon">Claude Shannon</a> that can guide us to create content with certainty.</p><p>Shannon pointed out that the amount of information is determined by not only the length but also the amount of uncertainty it overcomes.</p><p>For example, which message contains the largest amount of information:</p><ul><li>A. Mfljalkdjfadlfjsddsfansdfou1lk2fa3.</li><li>B. Mst ppl hv lttl dffclty n rdng ths sntnc.</li><li>C. Most people have little difficulty in reading this sentence.</li></ul><p>The answer is A, just some random words there. It has the most enormous amount of uncertainty that makes it the hardest one to predict the meaning. Compared with C, some words are missing in B, although most people can still understand it, it still contains somewhat uncertainty. Therefore, the ranking is A &gt; B &gt; C.</p><p>This theory tells us that to create content with certainty, you need to reduce the amount of information. There are two ways:</p><ol><li>Reduce the amount of uncertainty, give customers hints/instructions, answer their questions or concerns.</li><li>Reduce the content. Reduce the length if it’s a message, and reduce the elements if it’s an interface.</li></ol><p>№1 has a higher priority than №2, as sometimes it requires more content to deliver certainty. Think about the example above. For option B and C, although they have the same meaning, C creates more certainty.</p><p>However, efficiency is critical as well, as customers generally lack patience. So that you need to balance certainty and efficiency. In the previous article “<a href="http://90s0e.com/p/0Zd1v1XZihDqLggkJIcVS">Design for simplicity</a>”, I talked about some ways to simplify the content and improve efficiency, feel free to have a read.</p><h4>Create certainty to collaborate better</h4><p>Certainty is the foundation of trust, you need to create certainty not only for customers but also for colleagues.</p><p>Creating certainty can help teams to collaborate more efficiently. Many agile activities are designed to gain certainty of team members. E.g., standup, sprint planning, story kickoff, code review, retro, etc. All these are to keep everyone on the same page, so that the whole team can manage the expectations and dependencies better, and reduce waste caused by any uncertainties such as guessing, different expectations, etc.</p><p>Creating certainty can help to assemble a winning team. In the book “<a href="https://www.principles.com/"><em>Principles</em></a>”, <a href="https://en.wikipedia.org/wiki/Ray_Dalio">Ray Dalio</a> describes the <a href="http://nymag.com/daily/intelligencer/2012/06/ray-dalios-baseball-card-collection.html">baseball card system</a> his company <a href="https://www.bridgewater.com/">Bridgewater</a> uses to outline the strengths and weaknesses of each employee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*QPgqbXDqWRRBwFEG.png" /><figcaption>Image Source: <a href="https://www.businessinsider.com.au/bridgewater-ray-dalio-radical-transparency-app-dots-2017-9?r=US&amp;IR=T#/#dalio-pulled-up-footage-of-a-research-team-meeting-held-a-week-after-donald-trumps-presidential-victory-where-they-forecasted-economic-results-of-his-upcoming-presidency-1">Business Insider</a></figcaption></figure><p>Since people have different skills and talents, “<em>you wouldn’t have a great fielder with a .160 batting average </em><a href="https://en.wikipedia.org/wiki/Batting_order_(baseball)"><em>bat third</em></a><em>, you wouldn’t assign a big picture person a task requiring attention to detail.</em>” With this system, they can find the right person for the right job.</p><h3>Embrace uncertainty to grow</h3><p>It’s crucial to create certainty for others to build trust. However, to achieve personal growth, you need to be “special” — Don’t fear uncertainty, instead, embrace it.</p><h4>Gain unfair advantages through uncertainty</h4><p>In general, the more uncertain something is, the harder it is to achieve, the fewer people are willing and able to do that, the more gains it creates. Therefore, to gain unfair advantages, you need to embrace uncertainty, travel “the road not taken”.</p><p>Also, from Shannon’s information theory, we know that the more uncertain something is, the more enormous amount of information it contains. To create more information to make your life more meaningful, you need to embrace uncertainty.</p><h4>Build a system and keep evolving it</h4><p>To overcome uncertainty and achieve personal growth, you should build your own system and keep evolving it.</p><p>In “<a href="https://www.principles.com/">Principles</a>”, <a href="https://en.wikipedia.org/wiki/Ray_Dalio">Ray Dalio</a> also points out that you need to think of yourself as a machine operating within a machine. Unlike most people make right decisions by good luck. You increase the certainty of making right decisions by building and keeping evolving the system through a learn — practice — measure feedback loop.</p><h4>Introduce uncertainty to produce innovation</h4><p>To keep your system from being rigid, you need to introduce uncertainty proactively, and this might produce innovation.</p><p>In <a href="https://en.wikipedia.org/wiki/Tim_Harford">Tim Harford</a>’s book “<a href="http://timharford.com/books/messy/">Messy</a>”, he gives an example that there was a transport strike in London a couple of years ago. Most of the London underground stations got shut down for 48 hours, and people had to change to a new route during the strike.</p><p>The economist studied this found that, after the strike finished, about 5 percent of people still stayed with the new route. Which means that 1 in 20 of them discovered that when they were forced to find a new way, they found a better way.</p><p>Tim names this phenomenon to “arbitrary shock” — no elaborate planning, no specific direction, just merely an arbitrary shock, which then creates a great chance for innovation.</p><p><em>Originally published at </em><a href="http://90s0e.com/p/3rgcxxgnAmpqeDMzxww8q"><em>http://90s0e.com/p/3rgcxxgnAmpqeDMzxww8q</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cd0d6d19f5" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/creating-certainty-and-embracing-uncertainty-8cd0d6d19f5">Creating certainty and embracing uncertainty</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designer for simplicity]]></title>
            <link>https://medium.com/@Jieyun/designer-for-simplicity-3fbf3458045c?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fbf3458045c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Sun, 25 Nov 2018 11:39:36 GMT</pubDate>
            <atom:updated>2018-12-21T12:18:24.010Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design for simplicity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZCTBC_6UQErdWNKA_OhBg.jpeg" /></figure><p>I read an article recently that brought back my memories of mobile phones that people used ten years ago. Unlike the whole industry in today which is dominated by the iPhone and all the phones are similar, there were so many different kinds of phones in the market before 2008. Slab, flip, slider, etc. Not only was the appearance ever-changing, but also the product positioning was various from game phones, multimedia phones, fashion phones, etc.</p><p>Although some might complain that Apple keeps raising the price but lacks innovation, the iPhone is still king of the smartphones. I certainly wouldn’t attribute the success of iPhone to its simple design. However, compared with other competitors, one of Apple’s superiority lies in its ultimately simple product philosophy: as a consumer, you don’t need to choose among diverse models. Also, you don’t need to spend a lot of time and effort on learning how to use a smartphone.</p><h4>Simplicity meets both user’s and company’s pursuit of efficiency</h4><p>As a product designer, I treat simplicity as the core product design principle due to two main reasons from the efficiency point of review:</p><ul><li><strong>A simple product can help the user to achieve the goal efficiently.</strong></li></ul><p>Most products in everyday life are used to help users achieve specific goals, such as a microwave oven is used for heating food and the pen is used for writing. Making the product simple will help the user to achieve their goals efficiently by saving time and efforts.</p><ul><li><strong>A simple product can help the company to achieve the goal efficiently.</strong></li></ul><p>Profitability is the primary goal of any company. Given limited resources, making the product simple will improve the company’s operation efficiency by reducing unnecessary waste.</p><p>For example, when building an app, rather than spending resources to create an attractive on-boarding guide to teach users how to use it step by step, you should consider simplifying the process first, in order to make it easy and intuitive to use.</p><p><strong>As simplicity meets both user’s and company’s pursuit of efficiency</strong>, I treat it as the core principle of product design*.</p><p><em>*This is based on the fact that most products we use in our daily lives are tool products, efficiency is a critical indicator. However, simplicity is not the only pursuit of product design. I will talk a little about other considerations besides simplicity. If you are eager, feel free to move on to the last part — Simple, ain’t enough.</em></p><h3>Simple product = Precise need + Streamlined flow</h3><p>The two components of simplicity are precise user need and streamlined user flow.</p><h4>The precise user need is to specify which need to meet and to what extent</h4><p>There are two aspects in “precise”:</p><ol><li><strong>Selective</strong>. Find and select the need that is valuable to the users, and you have capabilities to meet well.</li><li><strong>Focused</strong>. The fewer needs you are trying to meet, the more potential the product has to be excellent.</li></ol><p><strong>Only when the user need is precise enough</strong> can you make a product simple from the origin.</p><p>Last year, a friend asked me for some feedback to his startup product. He started to envision the bright future from the very beginning of our talk: “we will build a service platform and create an ecosystem where people can get all kinds of info they need in daily life…”. Not even one word mentioned about user needs and I couldn’t help thinking that isn’t he the typical entrepreneur who “holds a hammer to find a nail”? Not to say the user needs are not precise, for their small team, such a vast platform is going to take a few years to build.</p><p>Moreover, a platform more evolves from a vertical domain than being built all at once. For example, Amazon started by selling books and expanded to include more categories later on. Nowadays, when most of our needs can get met well by existing products, it is almost impossible to create a platform from scratch.</p><p>Jacks of all trades, master of none. <strong>Nothing can be done well if you want to do everything</strong>. I never heard of his news again. I think he probably has given up already.</p><p>When it comes to the precise user need, it includes discovering and prioritising needs. There are already many methodologies for discovery. I will focus on prioritisation this time.</p><p>The granularities of need are different at various stages of product development. To make the product simple, designers should be able to prioritise the needs with different granularities at different stages.</p><h4>When the product is from -100 to 0, select a need with huge market potential and huge user value</h4><p>At this stage, the needs are more general. Prioritisation is mainly based on the potential of the target market and the value provided to the target users. Here are two important formulas.</p><p>From the perspective that whether we should meet this need, we can refer to the market potential formula: <strong>Market potential = Market size × Frequency × Impact</strong>. Focus on the one that many people (large market size) often have (high frequency) and must get met (significant impact).</p><p>The market with huge potential may have already been a red ocean, so it is necessary to think from the user value point of view. We can use the user value formula: <strong>User value = New experience — Past experience — Replacement costs</strong>.</p><p>I have the following interpretations for this formula:</p><ol><li>People’s needs don’t change too much over a long time. In fact, product innovation is more about using better methods to meet those needs. Usually, “better” equals more efficient.</li><li>The need to select is the one that can bring higher user value. Which means that by meeting this need, the new experience provided to users is better than the experience offered by past products. What’s more important is, there are replacement costs for users to shift to the new product. So the new experience needs to be greater than the sum of the past experience and a series of replacement costs, such as brand recognition, acquisition cost, learning cost, use cost, and social contacts cost, etc.</li><li>The first-mover advantage is significant. After accumulating enough replacement costs, it is almost impossible for an opponent to challenge in the same dimension. However, on the other hand, innovation is also crucial. As long as it can provide users with an excellent experience, the high replacement costs are not a problem.</li><li>If one market is already mature enough unless it is too big to occupy by one product, otherwise, it is a wise option to avoid competition and go try a blue ocean market. <strong>Being different rather than being better</strong>.</li><li>As a comparison with the new experience, the past experience does not have to be the horizontal experience. It can be a vertical experience. So you can aim at a specific segment as a breakthrough. It’s not necessary to build up your constitution on one mouthful; A blue ocean market sometimes hides inside of a red ocean market.</li></ol><h4>When the product is from 0 to 1, select the needs that can provide sufficient user value</h4><p>After the product conception, it comes to the process of building the Minimum Viable Product (MVP).</p><p>According to the user value formula, the MVP should offer a user experience that is relatively good to a certain extent. Otherwise, it’s just a temporary gimmick, hard to be sustainable. As a startup usually has limited resources, when creating an MVP, compared with “what we should do”, it is more difficult to decide “what’s a higher priority?” and “to what extent”.</p><ul><li>It comes down to deciding which needs must get met, which have a lower priority and to what extent we should meet. On the one hand, we can’t only select those that are easy to implement, missing the key ones. On the other hand, we shouldn’t overrate them and waste resources.</li><li>We need to make sure the experience offered by the MVP is better than the one provided by the existing products, so that the target users can have an internal drive to continue using it, not relying on external drives such as subsidies.</li></ul><p><strong>MVP, shouldn’t just be “minimum”, it needs to be “viable” as well.</strong></p><p>We can use the Kano model to help us analyse and prioritise the needs.</p><blockquote>The Kano model is a theory for product development and customer satisfaction developed in the 1980s by Professor Noriaki Kano. Although the inventor Professor Kakuno has nothing to do with the Internet industry, the Kano model is now widely used in product design because it is well suited for needs analysis.</blockquote><p>The Kano model classifies customer preferences into five categories: Basic Attributes, One-dimensional Attributes, Delight Attributes, Indifferent Attributes, and ReverseAttributes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*lE0NnEe0VArb9Hjc.png" /></figure><ul><li><strong>Basic Attributes</strong>: These are the requirements that must be included and the price of entry into a market. When they are done well, customers are just neutral, but when they are done poorly, customers are very dissatisfied.</li><li><strong>One-dimensional Attributes</strong>: These are attributes that are spoken and the ones in which companies compete. These attributes result in satisfaction when fulfilled and dissatisfaction when not fulfilled.</li><li><strong>Delight Attributes</strong>: These are attributes that are generally not expected. These attributes provide satisfaction when achieved fully, but do not cause dissatisfaction when not fulfilled.</li><li><strong>Indifferent Attributes</strong>: These attributes refer to aspects that are neither good nor bad, and they do not result in either customer satisfaction or customer dissatisfaction.</li><li><strong>Reverse Attributes</strong>: These attributes refer to a high degree of achievement resulting in dissatisfaction and to the fact that not all customers are alike.</li></ul><p>Take the iPhone as an example, Steve Jobs described it as Phone + iPod + Internet.</p><p>The phone is a basic attribute that should be included as a mobile phone. Regarding this attribute, iPhone can’t be worse than the mobile phone at that time, but it doesn’t have to be much better, because even if it performs very well, users won’t feel it.</p><p>The iPod is a one-dimensional attribute. In those days, many products focused on multimedia phones, so the iPhone not only needs to meet this need but also has to do better than the many other mobile phones.</p><p>The Internet is a delight attribute that exceeds the users’ expectations of the day. It is also the key to Apple’s ecology and differentiation innovation.</p><p>Despite that the iPhone didn’t include some “basic attributes” such as replacing the battery and having a long standby time. However, because it has implemented the one-dimension and delight attributes well enough, the overall user value provided is so much greater than the replacement costs.</p><p>That’s also why Jobs was a great product designer. He can sensitively identify that some “basic attributes” such as replacing batteries are actually indifferent attributes. They’re not what users really need, should be abandoned affirmatively. <strong>Deciding to implement those delight attributes rather than wasting resources in indifferent attributes</strong>, that’s what has made iPhone become an innovative product. Looking at today’s mobile phones, replacing the battery has become a reverse attribute. Although customers still expect long standby time, they will not discard the iPhone. Instead, they use power bank to meet this need.</p><p>I have the following interpretations of this model:</p><ol><li>To help understand the differences among these attributes, we can separate them by two dimensions: users need it or not, users are aware of or not.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h09WZd4b4sgknjuuEbgV4g.jpeg" /></figure><ul><li>Note here is need instead of want. What users want, is not necessarily what they need. For example, we mentioned above that users don’t really need to replace the battery on mobile phones. It’s an indifferent attribute.</li><li>The difference between a one-dimensional attribute and a basic attribute is that the better a one-dimensional attribute is implemented, the more satisfied a user will be. So a one-dimensional attribute should be achieved as well as possible. For a basic attribute, if you meet the standards and don’t pursue perfection, users won’t feel satisfied by it.</li></ul><p>2. The entry-level quality of product designer is to understand the users, understand what they need and what they don’t. There are two superior qualities. One is to think from the “God view”, can sensitively find those delight attributes that users are not aware of. The other is to categorise different levels of need. Prioritising and making rational decisions about what to do, how many, and to what extent, to improve the efficiency of product development.</p><p>3. These attributes are not static and will change dynamically with people’s mindsets, technology evolution and market competition. The past delight attribute may become the current one-dimensional attribute, the previous one-dimensional attribute may become the current basic attribute, and the previous indifferent attribute may also become the current delight attribute.</p><ul><li>For example, web responsive design. It was an indifferent attribute more than a decade ago. Seven or eight years ago, it was a delight attribute. And it became one-dimensional attribute four or five years ago. Now it is a basic attribute.</li><li>On the one hand, I have to exclaim that it’s not easy to stand on the shoulders of giants. It’s hard for the one who starts late to survive. On the other hand, it makes sense that it’s critical to respond to the changes.</li></ul><p>4. The differentiation of products determines by the different understanding of needs:</p><ul><li>A delight attribute of your product is a basic attribute of mine. There are more than 100 colours in a Hermès crocodile leather Birkin bag. Whereas, in MUJI, black, white and grey are the most common colours.</li><li>An indifferent attribute of your product is a delight attribute of mine. The MagSafe magnetic charger on MacBook has significantly reduced the risk of a laptop being dragged and dropped to the ground.</li></ul><p>5. Users won’t feel satisfied even if basic attributes are implemented well enough. So when you have invested many resources in fulfilling a need, but the feedback is not reasonably positive, it’s not because the need is not essential that you should stop spending more resources. On the contrary, it is possible that this is a basic attribute, not a one-dimensional attribute. So it would better if you continued implementing it until it meets the standards. You also need to pivot to some one-dimensional attributes or delight attributes.</p><p>When prioritising, the principle is to cut reverse attributes and indifferent attributes.Basic attributes must be included*. For one-dimensional and delight attributes, how many to implement, and to what extent, it depends on the strategic planning, competitors status, and own resources. Overall, the experience MVP offers needs to be greater or at least equal to the sum of the past experience and replacement costs.</p><p><em>*Note: Basic attributes almost equal to must-be attributes. Therefore, it is not recommended to cut corners on basic attributes. However, there are the possible following exceptions:</em></p><ol><li><em>Misjudging the basic attributes, and treating those basic attributes of non-target users or the indifferent attributes of target users as basic attributes. It’s miserable and needs to stop right away.</em></li><li><em>The product has accumulated substantial replacement costs. When people found the iPhone 4 antenna problems, although Apple didn’t lose its market position as a result of its accumulated innovation advantages, brand reputation and user habits, it was still terrible damage for them.</em></li></ol><h4>When the product is from 1 to 100, select the need can create higher user value and business value</h4><p>After the product is released, we will collect needs and requirements from different aspects, including direct feedback from users, user research, data analysis, boss’s idea, colleagues’ idea, your idea, etc.</p><p>In fact, ideas are very cheap, let alone designers or programmers who personally build the product, even if a stranger on the street can give you many ideas. As a designer, the most important thing is not to come up with ideas, but to come up with good ones andprioritise them rationally.</p><p>When faced with a bunch of so-called “needs” or “requirements” from all sides, we shouldn’t accept all of them or make casual decisions. The correct way is understanding, grouping, verifying, and prioritising.</p><ol><li><strong>Understanding</strong>. One of the most basic qualities of a designer is to understand the need. The need is not a solution, but a problem. When faced with a bunch of”needs” that are mixed with problems and solutions, the first thing is to split and revert the solutions to problems. Then ask a few “why”s to uncover the root of the problem.</li><li><strong>Grouping</strong>. Group the restored problems. Usually, many ideas solve the same problem.</li><li><strong>Verifying</strong>. Verify the actual scenarios of the problems appropriately according to the understanding of problems, users, and the progress of the project. Some methods could be desktop research, competitive analysis, data analysis, and user interviews. In fact, this step may have been completed already when collecting the needs.</li><li><strong>Prioritising</strong>. Use the Kano model mentioned earlier to categorise the needs into different five categories. The difference here is that the business needs will increase at this stage, while we mainly focus on user needs in the MVP phase. Most business needs are consistent with user needs, after all, the user experience is paramount. However, there are also some business needs belong to the indifferent and reverse attributes.</li></ol><ul><li>Because it is different from the MVP stage, the goal is not to maximise user value with limited resources only. We also need to maximise business value. Therefore, we need to include basic needs. For one-dimensional and delight attributes, it still depends on the strategic planning, competitors status, and own resources to decide how much to implement and to what extent.</li><li>For reverse and indifferent attributes, if there is no business value, still discard them as the same. If there is business value, stick to the dignity as a user spokesman, reject the reverse attributes as much as possible. Select a few indifferent attributes. After all, the company has to sustain.</li></ul><p>It’s mainly about prioritising the needs above. When it comes to the solution space, to make the product simple, the key is to make user flow streamlined.</p><h3>Streamlined flow — Don’t make users think</h3><p>Streamlined user flow can help users achieve their goals without thinking.</p><p>In behavioural design, Stanford University professor B.J. Fogg proposed a classic behavioural model <strong>B = mat</strong>. Which means if you want someone to act as you expected, three conditions are required:</p><ol><li>Motivation. The person must have the will to do it.</li><li>Ability. It should be easy enough so that the person has the ability to do it.</li><li>Trigger. You need to remind the person to do it.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*0xACAW6BtosKdFMEfGuKAw.jpeg" /></figure><p>The reminder works only if the first two requirements get met. If a person has no intention at all, the advertisement you post will be spam. If they are willing to do it, but the flow is too complicated, then they won’t bother continuing and will just give up.</p><p>It’s hard to change someone’s willingness, and it’s not feasible to create a non-existing need. As a product designer, you should focus on serving those who need your product and streamlining the flow, so that they can easily achieve their goals.</p><p>There are three main points to streamline the flow: <strong>simplifying user journey, optimising usability, and reducing cognitive loads</strong>.</p><p><strong>1. Simplifying user journey is to make the flow short.</strong></p><p>Some ways:</p><ul><li><strong>Automatic processing</strong>. On WeChat, after the user has entered the password, the payment request can be automatically sent without pressing the confirmation button on the keyboard.</li><li><strong>Set frequently used options to default</strong>. On Amazon, you can set the default shipping address, so you don’t have to re-enter it each time.</li><li><strong>Undo instead of prompting for confirmation</strong>. Provide an undo action when sending a message instead of asking for approval every time.</li><li><strong>Remove extra paths</strong>. In the same scenario, do not provide two different flows to achieve the same goal.</li><li><strong>Provide shortcuts</strong>. On Android, users can pull down the panel to turn on the mobile data. While on the previous iOS, you have to go to settings to turn it on.</li></ul><p><strong>2. Optimizing usability is to make the flow natural and smooth</strong></p><p>Mainly based on the usability principles accumulated over the years. Here are a few common ones:</p><ul><li><strong>Give status feedback</strong>. There’s an underline for text when hovering on a link.</li><li><strong>Within a reasonable range, make the main actionable elements as large as possible</strong>. Typical actionable elements like CTA, the size must comply with industry regulations.</li><li><strong>Offer options instead of typing</strong>. Instead of presenting users a blank text area, try to give options that they can select directly.</li></ul><p><strong>3. Reducing cognitive loads is to make the flow easy to understand</strong></p><p>The presentation of information should minimise the cognitive loads of users, and help them reduce the learning effort. The requirement is to let the user clearly understand how to achieve the goal at first glance:</p><ul><li><strong>Delete</strong>. Delete any unnecessary, unreasonable information.</li><li><strong>Organise</strong>. Group similar, related information.</li><li><strong>Hide</strong>. Hide useful but not critical information and provide an entry for the user to find out more.</li><li><strong>Prevent errors</strong>. Use real-time validation to give users timely feedback.</li><li><strong>Help</strong>. Provide users with appropriate assistance and tips.</li><li><strong>Consistent</strong>. The presentation of information should be as consistent as possible, including copywriting, components, styles, etc.</li></ul><h3>Simple, ain’t enough</h3><p>For most products, being simple is already good enough, especially when it grows, staying simple is not easy. However, we should note that in addition to helping users achieve their goals efficiently, <strong>designers also need to consider some emotional needs</strong>.</p><p>Taking the payment scenario as an example, users will worry about whether they have successfully paid the money. In this case, efficiency is not that important. So even though the system can immediately make the transaction, before jumping to thedifferent new page, we should inform users that they have completed the payment. It will make them feel more secure.</p><p>Efficiency is important, but extreme simplicity can make users feel tedious. <strong>We can try to add some personalities to the product at the right time</strong>. It will make the product more adorable. For example, on Dropbox paper, users can insert some interesting emojis when adding comments. It is in line with the online chatting habits of people nowadays, which considerably increases the fun of collaboration.</p><p>All the above are about tool products with clear user goals. <strong>For some service products, especially those involved offline scenarios, customers usually would rather enjoy the experience of quality services than seek to achieve goals efficiently</strong>. In that case, what we should focus on is not to make the service as simple or efficient as possible, but to enhance some momentary experience.</p><p>In “Strong Moments”, the Heath brothers pointed out that people’s feelings about an experience come from the impression of a few key moments, not from long, long details. As a business, you don’t have to be considerate about everything to satisfy your customers. The only thing to achieve is “<strong>mostly forgettable and occasionally remarkable</strong>”: Most of the services can be just so-so, neither too bad nor too good. Only make the experience at a few key moments extraordinary.</p><p>IKEA offers the customer an ice cream cone for only $1 at the exit. It will leave customers with a good impression at the end of shopping. In this way, even if there are some bad experiences during the shopping process, such as moving goods from the shelves, long queues, etc. Customers will still feel satisfied when they recall the shopping experience.</p><p>For entertainment products, such as games, movies, etc., users don’t have any clear goals at all. What they pursue are not efficiencies, but feelings, emotions, etc. In this case, simplicity will make users lose the fun. So on the contrary, adding some certain degrees of complexity and setting some challenges will give users immersive experience.</p><p>Therefore, for tool products, designers need to take care of emotional needs while pursuing simplicity. For service products, it is important to pay attention to a few key moments. For entertainment products, on the contrary, consider adding some complexity to deliver an immersive experience.</p><p>In conclusion, simplicity is the core design principle for most efficiency-driven products. I hope that within the controllable scope, product designers can aim at making the product simpler, to help the users, the company, and yourself improve efficiency.</p><p><em>Originally published at </em><a href="http://90s0e.com/p/0Zd1v1XZihDqLggkJIcVS"><em>http://90s0e.com/p/0Zd1v1XZihDqLggkJIcVS</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fbf3458045c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dropbox Paper for blogging]]></title>
            <link>https://medium.com/@Jieyun/dropbox-paper-for-blogging-240688e61554?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/240688e61554</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[dropbox-paper]]></category>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Mon, 08 Oct 2018 04:55:38 GMT</pubDate>
            <atom:updated>2018-12-21T08:57:18.555Z</atom:updated>
            <content:encoded><![CDATA[<p>I love Dropbox Paper. It’s such an excellent tool for writing and collaboration.</p><p>In this post, let me share my experience of setting up personal blogging with Dropbox Paper.</p><h3>Why Dropbox Paper</h3><p>When it comes to a blog, I have these needs:</p><ul><li>Easy to record ideas and update post. No matter on the train, at home, or in the office, I keep coming up with ideas all the time. I need an easy way to record these fragile ideas. After the blog gets posted, I need an easy way to keep reviewing and updating it.</li><li>Easy to share. Reading, writing and sharing, that’s a positive loop of learning. So I need an easy way to share my posts.</li><li>Easy to implement. I have basic front-end skills, but I’m not a pro. With the tight schedule I have, I don’t want to spend too much time learning to code. Also, I want to integrate it into my existing website, so that I don’t have to rebuild the whole site.</li></ul><p>After doing some research, I choose Dropbox paper over other options:</p><ul><li>Ghost and Wordpress are too professional and complicated. It requires somewhat efforts to learn and set up. Also, they’re challenging to integrate into my website, and I have to start everything from scratch.</li><li>Medium is a great blog platform for reading and sharing, and it provides API for developers. But there’s so much content in the platform which makes people hard to immerse in writing. It also lacks basic capabilities to manage docs, it’s important when you have hundreds of ones.</li><li>Dropbox Paper is born for writing. It has almost everything I need:</li><li>1. Simple text editor, no complicated and unnecessary features.</li><li>2. Both desktop site and mobile app are available. I can write whenever I have ideas.</li><li>3. Easy to manage docs. I can keep my notes, drafts, posts all in one place.</li><li>4. API provided. I don’t have to reinvent the wheel, to rebuild a text editor for writing. Only need to focus on the “View” and “Controller”.</li></ul><h3>How to set it up</h3><p>There’s a handy tool to explore the APIs provided by Dropbox — <a href="https://dropbox.github.io/dropbox-api-v2-explorer">Dropbox API Explorer</a>.</p><p>I only use 2 APIs: “docs/list” to get the id of all the docs under my blog account. “docs/download” to get post’s HTML by its id.</p><p>The APIs are basic, I have to find a few workarounds to meet some specific needs:</p><ul><li>Drafts and posts control. “docs/list” returns the id of all the docs under one account. Since it doesn’t support to get specific docs, I have to create another account to split posts and drafts. Once the blog is ready to post, I only need to share it with the blog account. It would be accessible from my website immediately.</li><li>Tags. There’s no direct way to add tags in Dropbox Paper. I create tags in specific paragraphs, then I can split and handle it by javascript. I use this way to add the date and intro as well.</li></ul><h3>Basic, but enough</h3><p>I have to admit the blog is very basic, but it’s enough for me. I’m a total pragmatist. I fancy the efficiency of writing, posting and updating more than powerful but unnecessary features.</p><p>For people only need simple blogging, I would definitely recommend trying Dropbox Paper.</p><p><em>Originally published at </em><a href="http://90s0e.com/p/4CCKQqzzfGryo0jvqXrSO"><em>http://90s0e.com/p/4CCKQqzzfGryo0jvqXrSO</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=240688e61554" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[90S0E]]></title>
            <link>https://medium.com/@Jieyun/90s0e-213be0e30091?source=rss-36ddb993d0a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/213be0e30091</guid>
            <dc:creator><![CDATA[Jieyun Yang]]></dc:creator>
            <pubDate>Sun, 26 Aug 2018 05:51:29 GMT</pubDate>
            <atom:updated>2018-08-26T05:51:29.688Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to my little corner of the world. As it is the first post, I’d like to introduce a little about this blog.</p><p>“90S0E”, it has nothing to do with my generation, nor does it mean any song or band names. Originally, the idea is to use the geographic coordinates of the South Pole. But unfortunately, I can’t register the domain name “90s”, that’s why I added it to “90S0E”. It’s not a big deal if you think different :)</p><p>Why the South Pole? It’s so mysterious that keeps attracting people to explore. Unlike the North Pole, it’s surrounded by oceans, and no human activity exists. If you google “90S0E”, the result is:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*StAPEis-2btmFFU2.png" /></figure><p>It’s almost a new location for us. That’s why I love it that much.</p><p>In this blog, I’d like to share something I have explored with you, some thoughts, ideas, and stories of mine, as a designer, a man, an average person.</p><p>Please feel free to <a href="/service/mailto: hi.jieyun@gmail.com">contact</a> me if you’d like to discuss anything with me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=213be0e30091" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>