<?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 Muchao on Medium]]></title>
        <description><![CDATA[Stories by Muchao on Medium]]></description>
        <link>https://medium.com/@muchao?source=rss-c857d1600bba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EXqyJLw9NF8ABxJENxsIPw.jpeg</url>
            <title>Stories by Muchao on Medium</title>
            <link>https://medium.com/@muchao?source=rss-c857d1600bba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:56:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muchao/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[Disruptive innovation and the death of growth hacking]]></title>
            <link>https://medium.com/@muchao/disruptive-innovation-and-the-death-of-growth-hacking-66a3ee9cbbb5?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/66a3ee9cbbb5</guid>
            <category><![CDATA[coinbase]]></category>
            <category><![CDATA[disruptive-innovation]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Sun, 05 Apr 2020 00:39:24 GMT</pubDate>
            <atom:updated>2022-08-05T02:38:01.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>What’s growth hacking?</h3><p>The term “growth hacking” first appeared in Silicon Valley startups in 2010, including companies such as LinkedIn, Twitter, Dropbox, Snapchat, Evernote, Instagram, Uber, Airbnb, YouTube, and Facebook. These companies built growth teams within the company to enhance its Website traffic and company revenue.</p><p>Growth hacking has profound effect on Silicon Valley. Almost all the companies of a certain size have built their very own growth team. The influence, however, is more than the existence of the growth teams. Growth hacking as a mindset has been blended perfectly into the forming process of all the product teams.</p><p>The most common product teams in tech companies are built around PMs. If a tech company is a machine, PMs are probably the largest cog wheels. They are the ones that initiate the correlated movements of all the other functions. PMs divide the ownership of multiple different parts of a product, and then the multiple KPIs of the product. Therefore, any one who has questions about the “onboarding” space, or the “first Uber trip in 14 days” metric, he’ll know exactly that Amanda is the POC. As a result of this team forming process, people naturally over-pivot towards the improvement of the metrics, arrange frequent product updates and A/B testings.</p><p>The problem is obvious. It is extremely hard for the team to carry out any disruptive innovation. Disruptive innovation requires a long exploration period. It requires people to have a certain amount of freedom outside of arranged projects, and then they can explore some seemingly impossible ideas. But why spend time on some uncertain explorations, when your performance gets judged by the speed and quality you get assigned projects done?</p><p>There is hardly any good solution for this in the tech industry. We know that Google asks employees to put aside 20% of their working hours for side projects, sounds like a solution, isn’t it? The fact is, just like any idealistic solutions, few people give a damn about it. Most people use this time to catch up on projects, or to attain better Work-life balance.</p><p>The extreme pursuit of metric lift, could be one of the reasons that mature companies can hardly create the next disruptive product.</p><h3>What’s a disruptive innovation?</h3><blockquote>In business theory, a <strong>disruptive innovation</strong> is an innovation that creates a new market and value network and eventually disrupts an existing market and value network, displacing established market-leading firms, products, and alliances.[2] The term was defined and first analyzed by the American scholar Clayton M. Christensen and his collaborators beginning in 1995,[3] and has been called the most influential business idea of the early 21st century.[4]</blockquote><blockquote>Christensen distinguishes between “low-end disruption”, which targets customers who do not need the full performance valued by customers at the high end of the market, and “new-market disruption”, which targets customers who have needs that were previously unserved by existing incumbents.[22]</blockquote><blockquote>— — Wikipedia</blockquote><p>Look at the examples below of a mature product and a disruptor. What kind of disruption is the disruptor aiming for?</p><p>Fidelity <strong>Vs</strong> Robinhood</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/0*HD_-UI7DdRKQdmtN.png" /><figcaption>Fidelity</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*37ojc7HoIVSBY97z.png" /><figcaption>Robinhood</figcaption></figure><p>Let alone the visual aesthetics, the core of the disruption lies in the upgrade in usability and product concept. The users of the old generation have been hoarding and managing all their capital on the old platforms. They are satisfied with the vast variety of investment features those platforms can provide. For Fiat products, take Fidelity for example, it has built an ecosystem of investment including stocks, 401k, funds, etc., and more advanced features for pro traders. Even though the user experience is not so ideal, there is a lot of friction if they want to move to a new product.</p><p>In comparison, users of the new generation are just starting to accumulate their wealth. They start adopting new platforms like Robinhood, for better usability and lower fee to get started with investment. Both the cost and the learning curve are much lower to start investing in these new products.</p><p>Similar comparison exists in cryptocurrecy products. Old products like Bitfinex provides more variety of coins to trade and advanced features for pro traders, while new companies like Coinbase provides way better user experience.</p><p>Bitfinex <strong>Vs</strong> Coinbase</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*4IosL7O3T9eXbhNt.png" /><figcaption>Bitfinex</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*b35VVXcNsBKcsPSR.png" /><figcaption>Coinbase</figcaption></figure><p>Robinhood can pretty much seen as a “low-end disruption”, while Coinbase can fit in both categories. Because of these disruptors, the Fidelity-s have to acquire or invest in some of these disruptors to catch up. For example, Morgan Stanley acquired E-trade, Fidelity invest in crypto companies, and so forth.</p><p>However, there was no time to chill for Robinhood and Coinbase. The new disruptors are already showing up like “bamboo shoots after a spring rain”(A Chinese idiom describing the phenomena that <strong>bamboo shoots</strong> grow very fast and in large quantities <strong>after</strong> a <strong>rain</strong> in <strong>spring</strong>).</p><p>The disruption is on the variety of investment products and gamification. Companies who used to focus on Fiat investment products, and those who focused on emerging investment products like crypto, are starting to blur the line and evolve together.</p><p>Robinhood started to provide pseudo crypto trading, I’m calling it “pseudo” since users can’t send or receive the crypto they purchased. Outside US, there are companies like currency.com who allow users to pseudo purchase U.S. stocks with cryptos.</p><p>Public is ahead of Robinhood in fractional shares and social trading among all the latest generation of disruptors. There is nowhere to confirm it, but the concept of fractional shares likely comes from crypto trading. There are so many people thinking that bitcoin is so pricey, that 1 bitcoin can cost around $5k-$10k. What they don’t know is you can buy half of a bitcoin, or 5%, or 0.001% of a bitcoin. This is real “fractional shares”. On Public, you can get half a unit of Apple stock, 0.1 unit of Amazon stock. Therefore you can just focus on investing in the companies you have faith in, without worrying about the high price of a whole unit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*bFGb0GlnOFwkAAeB.png" /><figcaption>Public app</figcaption></figure><p>The concept of social trading can trace back to those online forums where people discuss their strategies. Public merges the core feature — following other people’s portfolio and trading activities — to an app. If you don’t understand some trades that someone did, you can comment and ask for explanation. It’s just like interacting with people on Twitter. For new investors, following someone they see as an expert could be a low-cost way to ease into stock trading. Public took a big, bold move into social interaction between investors. They are saying to the VCs, hey look, there is not just one way to enjoy stock trading!</p><p>Earning, joy, usability, feeling of accomplishment. If a product thrives with any of these aspects, it has a chance to attract new users, and even disrupt the whole industry.</p><h3>Takeaways for builders</h3><p>We tend to over-pivot towards what’s measurable, because it’s the easiest to improve on these aspects. Julie Zhuo mentioned this data pitfall in her <a href="https://medium.com/the-year-of-the-looking-glass/the-agony-and-ecstasy-of-building-with-data-56215764d67c">article</a>. We need to understand UX, and the fact that building a good product is not only about growing the metrics.Only when we understand the often-neglected parts of product development, we start to really enhance the product performance.</p><blockquote>How users feel about your product is one of the most critical things to understand, and whether those feelings are changing based on the decisions you’re making. But — because it’s hard to measure, it’s easier to stick to numbers that feel more real and concrete, and as a result, roadmaps regularly tend to undervalue the things that don’t show up in a metric.</blockquote><p>When doing quarterly planning, think about what this product will be like in a year. When doing yearly planning, think about the next 3–5 years. Make space for the next disruption.</p><h3>Reading recommendation</h3><ol><li><a href="https://www.goodreads.com/book/show/19203217-disruptive-innovation">Disruptive Innovation: The Christensen Collection</a></li><li><a href="https://medium.com/the-year-of-the-looking-glass/the-agony-and-ecstasy-of-building-with-data-56215764d67c">The Agony and Ecstasy of Building with Data</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66a3ee9cbbb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make design decisions that give developers nightmares]]></title>
            <link>https://medium.com/@muchao/how-to-make-design-decisions-that-give-developers-nightmares-2edd2e078cba?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/2edd2e078cba</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Fri, 20 Mar 2020 23:25:55 GMT</pubDate>
            <atom:updated>2020-03-23T16:37:47.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1wWZ6quGQI3JC3RVt3f0BA.png" /><figcaption><a href="https://pixabay.com/vectors/man-angry-anger-computer-portable-2822206/">Image source</a></figcaption></figure><h3>How to effortlessly make design decisions that piss developers off</h3><p>It’s not that hard to make a design decision that pisses your fellow developers off. I&#39;m talking from experience here. All you need to do really is to over-index the user experience, and throw out “it’s all about UX”.</p><p>For example:</p><blockquote>Users like this animation / icon / layout, we have to build it. What? It conflicts with the existing system? Not helpful for product experience? Well, if the users like it, there’s no need to follow the design system. Also, it improves the experience. It’s all about user experience.</blockquote><p>The example is obviously made up. I believe most designers have basic communication skills. But, if you insist on saying “it’s all about user experience”, then … congratulations! You have mastered the class of “How to effortlessly get fired”.</p><p>Joking aside, let ’s get down to our topic.</p><h4>What should you consider when making design decisions?</h4><p>The hero for today’s case study, interviewee M, is a great designer. The next morning following M’s interview, the interviewers meet up to discuss his performance.</p><p>T is a product manager. He gives a “soft no”, meaning that he tends to reject M. In their 1-on-1 interview, T asked how would a specific design decision would affect other aspects, like product development and business metrics. “Of course I have to speak for the user, I think the user experience is the best with my design”, and then the topic came to an abrupt end. M replied without any hesitation. T thinks that it is a good thing for the designer to speak up for the user. He just hopes that M can discuss this decision with him in more depth. How would the decision impact metrics? How would it impact development? Later on, another product manager also gave supporting views and examples.</p><p>Here’s Julie Zhuo’s view on elaborating design decisions:</p><blockquote>“A great designer starts with the whys. She conveys the principles behind her thinking and leaves you feeling like you understand the core values from which all her design decisions flow.”</blockquote><p>As a designer, we need to be proactively prepared to respond to the questions of our design decisions from all stakeholders.</p><p>Taking this info into consideration, my notes for M becomes, “During the presentation, he talked about the metrics change after the product launch. However, further interpretation is lacking. He could be more open to deep conversations around business metrics and development. ” It’s important to understand business metrics and product development, and let them weigh in on design decisions. This ability is a must-have for designers, especially the ones working in tech companies. Let’s talk about how development could influence a design decision.</p><h4>How development could influence a design decision</h4><p>Assuming that the width of web products in a company is set to 1200px, and the position of the logo on the nav bar is left-aligned. Now you are designing a new product on the web. The content is not enough to fill the width of 1200px. After a lot of consideration, the width of the content is set to 950px, and the it’s divided into two columns. The final candidates are the three options below. The left one is the standard 1200px-width layout of existing products, and the right three are your designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ZOHduwCMtQALK7mA6xXgg.png" /></figure><p>From a visual perspective, the centered layout of option A is more balanced. It also looks better when scaled to other devices with different screen sizes. The logo on option B looks like it’s hanging itself on the top left corner. Option C is not bad, just not as balanced as A.</p><p>So it’s option A then.</p><p>Or no?</p><p>Let’s take a step back. In this case, assuming most people find A visually very pleasant. If we build the product based on option A, we’ll be facing these consequences:</p><ol><li>The consistency of other web products from your company is broken.</li><li>Every time the development team see this product, they have to keep in mind that this is the black swan. It’s different from all other web products. If they are to push a site-wise change, this product will need additional attention.</li><li>Raised maintenance cost. Whenever there’s a new developer or designer joins the team, they will ask about this design decision. If the POC is not in the company any more, and nobody is able to answer the question, then it’s gonna be raised up again and again.</li><li>The new comers will have to guess why this decision was made, even though it was totally different from all the other products. The conclusion will be something like, “The decision was not thought through, so we think a redesign is needed”. Boom, this is how resource gets wasted on some problem that could have been tackled from the begining.</li></ol><p>After rounds of back-and-forth, we went with option C. On a scale of 100, if option A gets 100 points on user experience and 80 on development cost, option C can get 95 and 100 accordingly. UX and dev cost reach a good balance with option C.</p><h3>How to take development cost into consideration?</h3><p>This is an inspirational case to me. Every time I start designing a product, I will ask myself a question. Can this deviating proposal be widely applied to other existing products to improve user experience?</p><p>The answer is likely to be “no”, because when I was designing this product, I probably did not proactively adapt the new patterns to all the other products.</p><p>Then the question becomes this. Is the proposal worthy of being built out with different standards?</p><p>The answer is, again, likely to be “no”. This is the case with option A mentioned above. If you are convinced that the value of your proposal can overcome all these drawbacks, then try hard to persuade your team. This is not a battle that is totally impossible to win.</p><h4>End note</h4><p>At last, I’m leaving a question here. Assuming that you apply the new design pattern to all the other products and it seems to work. Will it become a new pattern that everyone else is going to use?</p><p>Comment your thoughts below!</p><h4>Appendix</h4><p><a href="https://medium.com/the-year-of-the-looking-glass/a-matter-of-principle-4f5e6ad076bb">A Matter of Principle — Julie Zhuo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2edd2e078cba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I picked Coinbase over FANG — How I evaluated opportunities]]></title>
            <link>https://medium.com/@muchao/why-i-picked-coinbase-over-fang-how-i-evaluated-opportunities-c644c552e679?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/c644c552e679</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 17:23:40 GMT</pubDate>
            <atom:updated>2022-02-12T04:47:59.498Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I bet on Coinbase, not FANG</h3><p>TLDR: If you want steady growth, good stability, top-notch pay, go for tech giants like FANG(FB, Amazon/Apple, Netflix, Google). If you have a strong belief in the mission, enjoy a hustling vibe, startups are the place to make big impacts at.</p><p>**</p><ol><li>What’s the situation?</li><li>What about FANG?</li><li>What about Startup?</li><li>What about Coinbase?</li><li>Endnote</li><li>Appendix</li></ol><p>**</p><h3><strong>What the situation?</strong></h3><p>Long story short, I’m joining Coinbase to build products for identity and onboarding. Before this final decision, I was debating with myself whether to join Coinbase, or one of FANG to design for Ads, or other startups. To be honest, that was not easy. I was trying to make the best decision as a designer early in my career.</p><p>Here is my radar graph comparing the offers. Remember the comparison is not between the companies, but the opportunities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BofXGZm0LP_pCcclXXbbWQ.png" /></figure><h3><strong>What about FANG?</strong></h3><p>FANG have 3 key advantages: steady growth, good stability, and top-notch pay.</p><p>It’s always an easy choice to join FANG because they are like a safety net, where things rarely go too wrong. The most fascinating benefit is well-established mentorship and learning programs. They also provide gym services, free massage, even free haircuts. And hey, don’t forget about the vast selection of free food that you can’t complain about. Man, for a student with little savings who just walked out of campus, this is too hard to turn down.</p><p>At one point, I was close to signing the FANG offer. But I hold off the rush and I asked myself, is there really no downside for FANG?</p><p>Will I be working on the project I wanted to work on?</p><p>Am I leading an interesting and/or impactful project?</p><p>When I work in a big team, does my work get a fair amount of exposure to my manager and leadership?</p><p>When I sit on the campus with more than 20,000 people, will I ever ask myself, do I even matter?</p><p>Do I see this company grow 50% or even more in the next 5 years?</p><p><strong>The downside might not be that obvious, but it will come out if you dig deeper into your thinking.</strong> Just a common sense, when there is an upside, there’s always a downside<em>. </em>I’ll leave the questions for you yourself to figure out.</p><h3><strong>What about Startups?</strong></h3><p>When hiring designers early in their careers, FANG are more open to generalist talents and do team-match later. Unicorns are more likely to be selective of specific talents. The talents could be domain knowledge, specific work experience or certain design skills. If you have some talents that match the need of an employer, you can expect to start making impacts very soon. For me, that was the case with Coinbase.</p><p>When it comes to personal finance, the risk is obvious. Smaller team, changing priorities, possibility to fail. I worked at Pre-IPO Uber, and it apparently hasn’t worked out in the best way for my financial gain. The liquidity that FANG provides is far better than almost any Unicorn at a similar job level.</p><p>Joining a startup is usually a harder choice to make. Yet, if you believe in the company, if you enjoy the hustling vibe, startups are worth considering. There is challenging work that feeds your growth. There is a chance to disrupt an industry. You’ll build solid relationships with the people you fight together with. And, of course, the potential high rewards if things take off. It’s an upside risk I’m willing to take.</p><p>I’m still early in my career, and I’m willing to make the bet.</p><h3><strong>What about Coinbase?</strong></h3><p>Like many people, I stepped into the Cryptocurrency world through Coinbase. Unlike what I had imagined, I didn’t make any money during the first year. Instead, I lost 75% of my investment because I entered right after the bust at the beginning of 2018. Even though I didn’t invest a lot, that became a huge reflection and learning moment for me. Turns out Bitcoin was not just an investment, but already playing a significant role in tons of cross-regional businesses. The more I learned about how people are using cryptocurrency and blockchain tech, the more I see the value of it. At the end of 2018, my friend and I figured that was an opportunity so we got back on the scene again. Coinbase has since been 1 of the apps that I interact the most with.</p><p><a href="https://www.coinbase.com/join/tang_gd?src=ios-link"><strong>Coinbase</strong></a> is the world’s largest Bitcoin (BTC) broker. They have solid products for wallet, exchange, and now custody. On top of that, I am super pumped about their <a href="https://www.youtube.com/watch?reload=9&amp;v=nh6oPFZ4pXw"><strong>Mission</strong></a>: to create an open financial system for the world. The challenge is intrinsically for social good: extend access, reduce inequality, improve efficiency.</p><p>During my onsite, I got a good feeling about the culture at Coinbase. Everyone works in a collaborative way and cares about the products they are building. Each round of conversation went great. I got to hear the stories of how people get into crypto and why they joined the company. The design exercise was fun and fruitful, and the ideation was highly in line. At the end of it, I felt a stronger bond with this place.</p><p>At the offer stage, I was fortunate to get insights from a couple of Coinbase employees. Here are a few highlighted opinions:</p><ol><li>Coinbase has a long runway.</li><li>Crypto community has been growing very fast, and Coinbase keeps evolving with the community.</li><li>Coinbase wants to be a platform that provides full-blown crypto services, not only an exchange.</li><li>Coinbase works collaboratively with legislatures to legalize the applications of cryptocurrency.</li><li>If a recession is coming, it might be Crypto currency’s chance to shine.</li></ol><p>Read the <strong>Appendix</strong> if you want to read about insiders’ thoughts on CB.</p><h3>Endnote</h3><p>There is no denying that this article is biased since I have always favored startups. I’m writing this down mostly to document my thoughts at this moment. I want to look back at this article 5 years later, and see if I happen to get anything right.</p><p>Plus, people, get on the rocket ship while you still can, no matter where it is going. Coinbase is worth considering for your next career move.</p><p>Subscribe to my <a href="https://uxdesigner.substack.com/"><strong>Newsletter</strong></a><strong> </strong>to receive the latest articles.</p><p>Connect with me on <a href="https://twitter.com/Muchao94"><strong>Twitter</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/muchao/"><strong>Linkedin</strong></a><strong>.</strong></p><h3>Appendix</h3><h4>More on Cryptocurrency</h4><ul><li><a href="https://www.forbes.com/sites/matthougan/2019/08/21/bitcoin-vs-gold-is-bitcoin-really-a-new-safe-haven-asset/#574a2f477ba1">Bitcoin vs. Gold: Is Bitcoin Really A New &#39;Safe Haven&#39; Asset?</a></li><li><a href="https://www.coindesk.com/coinbase-to-pay-users-1-25-interest-on-usdc-stablecoin-holdings">Coinbase to Pay Users 1.25% Interest on USDC Stablecoin Holdings - CoinDesk</a></li><li><a href="https://www.nytimes.com/2019/02/23/opinion/sunday/venezuela-bitcoin-inflation-cryptocurrencies.html">Opinion | Bitcoin Has Saved My Family (Published 2019)</a></li></ul><h4>More on Product Design</h4><ul><li><a href="https://uxdesign.cc/lean-ux-the-ultimate-design-method-5e983d84ef1e">Is Lean UX the ultimate design method?</a></li><li><a href="https://uxdesign.cc/product-design-junior-vs-senior-what-do-we-lack-3a9c615c6f05">Product Design Junior Vs Senior — what do we lack?</a></li></ul><h4>Insiders’ thoughts on Coinbase</h4><p><a href="https://medium.com/@kenzanboo">Kenzan Boo</a>: “We are partnering with Dapps, several of my personal friends have reached out asking to work with Coinbase using Coinbase Connect and Wallet. Crypto is still in its early days in terms of the community and potential with Dapps.</p><p>A: “I actually think our current valuation is fair but we could prob raise at a little more and I do agree that long term we have a long runway when looking at values of companies like Charles Schwab”</p><p>B: “Was a Fintech VC — my two cents. I would say two major things with FAANG vs. CB.</p><p>1. CB is about 1k employees vs FB is 45k, so you’d be a bigger deal there, have better career opps, cooler projects (probably)</p><p>2. Coinbase is very undervalued compared to competitors (e-trade, scott trade, exchanges) — they made (I think) about 1.5B in the past two years in Rev with very small headcount. This means they’re crazy profitable which is very rare in the valley, and will make them an attractive IPO compared to non-profitable recent IPOs like Uber, Lyft, Slack, etc. — IMO equity upside is much, much higher here than FB would be</p><p>3. Coinbase model isn’t really predicated on crypto asset price, only really on volume. More and more DApps are coming out, which means regardless of crypto value, volume will be there, which means that CB is very resilient against crypto market shocks. Also, geopolitical instability is a driver of crypto value, so if there’s a recession, Brexit, impeachment, etc. that’s actually good for Crypto — not bad, unlike all other things.</p><p>4. Coinbase appreciates in value every time a regulation around privacy comes out because crytpo is inherently protective of privacy — FB is the opposite and is looking at anti-trust issues.</p><p>To me, it would be a no brainer assuming you’re early(ish) in your career. In terms of work-life balance, FAANG companies are notoriously bad. They don’t design those crazy campuses with dorms on-site so that their employees go home. That said, if you’re further along in your career, and are past the sweat work stage, FB could be a good place to collect a safdr (prob slightly larger) paycheck with (arguably) less risk (but way less upside) on the equity side.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c644c552e679" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Lean UX the ultimate design method?]]></title>
            <link>https://uxdesign.cc/lean-ux-the-ultimate-design-method-5e983d84ef1e?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e983d84ef1e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 18:34:06 GMT</pubDate>
            <atom:updated>2020-03-23T19:03:52.566Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tl;dr: it&#39;s not.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tuSWi3Y_nVJH2zJGq3372g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/YJxAy2p_ZJ4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charles Deluvio 🇵🇭🇨🇦</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Recently I was listening to a <a href="https://soundcloud.com/ux-and-growth/lean-ux-organization-design-with-jeff-gothelf-author-of-lean-ux-sense-and-respond">podcast</a> with the author of <a href="https://www.jeffgothelf.com/lean-ux-book/"><em>Lean UX</em></a><strong> </strong>on the show. It was not the first time I heard of this term since I read <em>Lean Startup</em> a few years ago, but I was not so sure about the clear definition. Fact is, if you are working in UX, you probably have already been using part of Lean UX methodology for a long time, even if you never heard of it.</p><h3><strong>What is Lean UX?</strong></h3><p>Lean UX is, as the author Jeff Gothelf explained on the show,</p><blockquote>“Take all the tools in a designer’s toolbox, use on an as-needed bases, but only to the depths that are necessary for us to take the next step forward in the evolution of this product or service.”</blockquote><p>In other words, <strong>DO LESS, MORE OFTEN.</strong></p><p>It struck me immediately when I heard this as I started to recall, wasn’t this exactly what I did during my internship at Uber last year? Only back then I didn’t know that, there was this design methodology behind the product development process. My mentor and PM would check in with me constantly once in a while, informally or during presentations, and give me feedbacks. <strong>Their suggestions were usually not only about the product itself, but also who else to reach out to for further advice.</strong> These people could be designers and researchers in relevant teams, content strategists who were in charge of that product line, engineers who could see potential technical issues or sometimes even give you an estimated timeline of deployment of an MVP.</p><p>As a result, all these opinions from other parties played a certain part when I was weighing the pros and cons of different design options. Then I iterate, get feedback, and iterate again.</p><p>During the 8 weeks I was working on the primary project that was assigned to me, there were in total 15 iterations, each with 3–4 concepts that significantly differentiate from each other, and each concept with a variety of visual treatments. Beyond static wireframes and mockups, I’m a firm believer in understanding interactions through motion, so I made interactive prototypes for concepts worth exploring.</p><p>I’ll give you some numbers just to understand what I did that is tangible in this “Lean” process. For this project, I made ~350 interfaces and ~30 hi-fi interactive prototypes for 25 concepts, plus 2 interactive prototypes of the whole user flow of the 2 final concepts for testing in Invision. Sounds like a lot but it’s totally reasonable when you break the number down to 8 weeks.</p><p>But this was not only my work. It was team efforts with all the people I interacted with, which is the intangible part of work. A core mindset of Lean UX is to keep in mind that you are a team player, not a UX lone wolf. Lean has changed the way UX works, for we are no longer the kind of designer that sit at the desk all day and come up with designs. We have extra responsibilities in facilitation and collaboration. We need to be proactive to gather feedbacks form related parties ourselves, instead of waiting for some sort of “boss” to come in and give you the ultimate instruction like old times. By involving ourselves in feedback gathering and product planning, we can better lead the product with firsthand information. Just like PMs, now product designers should also have clear understandings of what is important for the product, but from a different perspective. Thanks to Lean, leadership can no longer be a nice-to-have for UX designers. That said, it would be a disaster if we cannot clearly justify our product decisions, or share our understanding and vision with the whole team.</p><h3><strong>When to move forward in Lean UX?</strong></h3><p><strong>In Lean UX methodology, designers should do just enough work that is necessary to move on to the next step forward. No more, no less, just enough.</strong></p><p>As Jeff mentioned in the podcast, there used to be times he compiled 200-page design spec documents that listed everything of design details, and later on only 20–30% of the content is implemented, which was a huge waste in the process. That kind of unpleasant experience eventually inspired the creation of Lean UX. Through his original starting point, it’s not that difficult to infer that the essence of Lean UX is to reduce waste and make design process in corporate environment more efficient.</p><p><strong>But how much work exactly could be defined as “just enough”?</strong></p><p>Short answer is, it depends.</p><p>I know it sounds vague, and it truly is when you get started at any new project. It depends on the product roadmap, on related people’s schedules, and on the designer’s ability. However, just like everything else, you become clearer of what you are doing over time. I can vouch for it through my own experience.</p><p>Tracing back to when I got started with my previous project at Uber, I didn’t know who to approach right from the beginning, except for my mentor and PM. I had no idea what the final deliverables would be like, or to which extent the prototypes would be. I was also not sure about how much work is worthy of communicating, so that I tried to touch base with my mentor every single day, till one day he said to me, “You know, you really don’t have to check in with me this often.” I still find it amusing when I recall at that time, he held back a little bit, but eventually turned out to speak up and explain to me a lot later on so as not to hurt my feelings.</p><p>So as you can see, I started quick and dirty, but it didn’t take me long to figure out the appropriate pace of work. Naturally, I figured it felt just enough to move on to the next iteration after I updated design options till there would be 3–4 new concepts based on the previous batch and feedbacks gathered from major stakeholders. It worked very well for this project as the quality of work kept getting better after each round, and finally grabbed a lot of attention of product leaders in Driver and UberEats team.</p><p>So yah, it depends. Most likely, you are going to figure out the amount and pace yourself. Throughout all the projects I’ve done with Lean UX mindset, the processes have never been exactly the same.</p><h3><strong>Lean UX is not the ultimate design method</strong></h3><p><strong>Lean UX was born out of Lean Startup, design thinking and Agile. It suits what tons of corporations need for now because of the tremendous popularity of Lean Startup and Agile.</strong></p><p>The whole article I’ve been talking about how amazing Lean UX is, and how much benefit it can bring to product design process. I have no doubt that Lean UX will still work well and keep evolving for years to come, for it perfectly fits most modern-day B2C services. But I’m absolutely not saying it is the one true ultimate design method. Just as we ditched the good old ways for Lean, Lean will be replaced by new methods when there is a new disrupting business model, or technology.</p><p>It is already happening. And that disrupting thing which will surely push design methods to change significantly again, is called Artificial Intelligence. Imagine when AI can automatically localize content strategies, handle user testings, or even create smart design systems, what can UX fellas do to adapt to the new era?</p><p>Subscribe to my <a href="https://uxdesigner.substack.com/"><strong>Newsletter</strong></a><strong> </strong>to receive the latest articles.</p><p>Connect with me on <a href="https://twitter.com/Muchao94"><strong>Twitter</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/muchao/"><strong>Linkedin</strong></a><strong>.</strong></p><h3><strong>Reference</strong></h3><p>Subscribe to my <a href="https://uxdesigner.substack.com/"><strong>Newsletter</strong></a><strong> </strong>to receive the latest articles.</p><ol><li><a href="https://www.jeffgothelf.com/lean-ux-book/"><em>Lean UX</em></a></li><li><a href="https://www.nngroup.com/videos/does-agile-destroy-ux/"><em>Does Agile Destroy UX?</em></a></li><li><a href="https://soundcloud.com/ux-and-growth/lean-ux-organization-design-with-jeff-gothelf-author-of-lean-ux-sense-and-respond"><em>Lean UX &amp; Organization Design with Jeff Gothelf</em></a></li><li><a href="https://uxdesign.cc/how-ai-will-impact-your-routine-as-a-designer-2773a4b1728c"><em>How AI has started to impact our work as designers</em></a></li></ol><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=5e983d84ef1e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/lean-ux-the-ultimate-design-method-5e983d84ef1e">Is Lean UX the ultimate design method?</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[Product Design Junior Vs Senior — what do we lack?]]></title>
            <link>https://uxdesign.cc/product-design-junior-vs-senior-what-do-we-lack-3a9c615c6f05?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a9c615c6f05</guid>
            <category><![CDATA[uber]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Tue, 29 Aug 2017 03:45:44 GMT</pubDate>
            <atom:updated>2020-03-23T19:01:55.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*8167dBxdg50PSOUyd8yzJw.png" /><figcaption>How to draw an owl</figcaption></figure><p>This article is my reflection on T3(Top3)B3(Bottom3) evaluation after 6 weeks of being a product designer at Uber. The “T3” means the 3 most outstanding abilities, while “B3” means the aspects for more efforts to improve. The interns receive T3B3 evaluations from their mentors at the mid-point and the end of their internships. Based on the reflection, I start to understand more deeply about some of the most critical abilities that junior designers are lacking compared to a senior.</p><p>If you only want to see the conclusion and highlights, just jump over to — “What should junior designers do to grow up fast?”</p><p><strong>T3B3 evaluation</strong></p><p>It always feels good when some of your abilities have been recognized. I really appreciate my mentor Adnan in that he went over the T3B3 evaluation that he was going to give me, and ask me if I had any opinions on any of them. After discussion, he gave me the final version of my mid-point T3B3.</p><p><strong><em>T’s</em></strong></p><p><strong><em>T1:</em></strong><em> </em><strong><em>Quick Study: </em></strong><em>Quickly dived into rich prototyping and learned new tools such as Principle, Framer, which he has used throughout his intern project, and actively learns new skills when he has downtime.</em></p><p><strong><em>T2: Proactive and eager to take on new challenges</em></strong></p><p><em>Has pro-actively taken on new projects beyond his intern project. Quick ran with smaller projects like Driver Showcase, Bliss profiles, created a new R2D logo, and showing progress on major projects.</em></p><p><strong><em>T3:</em></strong><em> </em><strong><em>Out of the box product and experience insights</em></strong></p><p><em>He comes up with creative and out of the box product insights — that we sometimes have to scope down due to team/org constraints. He shouldn’t be discouraged by this — keep proposing them.</em></p><p><strong><em>B’s</em></strong></p><p><em>NOTE: B’s are not necessarily flaws or big problems, but often-times opportunities to develop and improve. Have already seen him make progress on these as internship has gone on:</em></p><p><strong><em>B1: Creative exploration: </em></strong><em>Want to see him better execute on doing wider range of upfront explorations to explore problem space, rather than jumping to a few solutions.</em></p><p><strong><em>B2: Clarity and Complexity in presentation:</em></strong><em> Develop ability to better contextualize, lay out, structure, and present design options and flows in ways that are clearly understood by others (both in slide deck form and informally). Put yourself in the shoes of others and ask — is this clear?</em></p><p><strong><em>B3:</em></strong><em> </em><strong><em>Developing self-sufficiency and ability to refine</em></strong><em>:</em></p><p><em>He is working on a fairly self contained project without a lot of voices of feedback — he does well with quick daily feedback, but I would like him to better develop the ability to refine his own work if he’s getting more sporadic feedback. Would a project stall if he only got 2x a week feedback (fairly common full time employee cadence)? I’m not entirely sure.</em></p><h4><strong>Reflection as a junior</strong></h4><p>Apart from noticing the aspects I could improve on, we could take a peek on the criteria that a senior designer have in mind for design capability.</p><p>For junior designers who just step into the industry, I strongly believe many of us has some strong design skills in certain aspects, together with passion in contributing to great products, and eagerness to become more professional. However, practicing design in large corporations is much different from doing school projects in terms of the process and ideation scopes.</p><p>My mentor did not give me very specific evaluation regarding design skills. It does not mean that design skills is totally ignored, but that good visual design/prototyping skills are not necessarily the key of a good design solution. According to Xiaoxue, a product designer in Uber,</p><p>“In Tech companies like Google or Uber or Facebook , there are already existing UI kits and design guidelines, which leaves only a little room for designers to showcase their design skills in most inner projects. Under this circumstance, user experience has become the more critical problem for designers to tackle. Thus, a product designer’s value is recognized more by his/her ability to leverage user experience and improve product value from a business perspective.”</p><p>In terms of designing for business, extra value is a significant scope to take into consideration. It is not that it sounds good to say I have this business thinking in mind. There are many design options that could work for a certain project goal, yet extra value is what makes the best proposal stand out, and also a strong rationale when communicating with engineers and PMs. Keep in mind the questions that PMs always ask, like “what extra value do you provide with this option?”, “does it hurt the performance of a feature that is currently working well?”; also from the engineers’ side, “what is the extra value of this design that is worthy of much more efforts in building a new module, instead of just applying the existing one?”</p><h4><strong>What should junior designers do to grow up fast?</strong></h4><p><strong>1.Holistic view of projects</strong></p><p>When exploring various design options, do not only think from our own perspectives. Instead, also put yourselves in other’s shoes. in other words, think like a product manager, think like an engineer, think from the perspectives of all the other relevant teams.</p><p><strong>2.Contextualization of the deliverables</strong></p><p>At different stages of a project, understand what fidelity should the presentation be in. Should the design options be in wireframes, hi-fi static mockups, or interactive prototypes? How much efforts should I put into toning the presentation slides? Especially at the initial exploring stage of a project, it is smart to explore wider range of options, instead of wasting large chunks of time on visual effect or even animations.</p><p><strong>3.The ability to communicate efficiently wherever and whenever</strong></p><p>At school, we most likely will not start to comb through all the works we have done for a project until the mid-term or final presentation date is approaching. While at work, 90% of the communication about projects happen without a fully-prepared presentation. Since the engineers, product managers, designers and operations are seated very close to each other within a team, it is convenient to just walk over to the another team member and communicate. Smooth work-related communications are just not going to happen without a good understanding of the works we are doing, and readiness to get key points through efficiently within only a couple of minutes.</p><p><strong>4.The ability to constantly iterate projects individually</strong></p><p>It is not realistic to get feedbacks all the time. We need to improve the ability to constantly criticize design works by ourselves from different perspectives, thus we can handle more complex projects in the future.</p><p><strong>5.Ability to apply more frameworks/scopes/perspectives of thinking</strong></p><p>Why is the click-through rate so low for this button? Is the hierarchy clear on this screen? What layout could fit the current info arch better? Is there other ways to organize the information other than the current info arch? There are so many scopes in product thinking that, when you feel stuck sometimes, thinking from a different angle may lead you to some previously ignored issues.</p><p><strong>6.Proactivity to learn and reflect and reach out to co-workers</strong></p><p>This is probably the most straightforward suggestion I could think of. Take on challenging tasks and try to accomplish more within the same amount of time without sacrificing quality. When you have questions or new ideas for projects, do not hesitate to reach out to the people who are strong in these fields. Thanks to Maria who helped me a lot in carrying out usability testings, I really started to understand what is mentioned in the book “How Google works” by Eric and Jonathan, that Smart Creatives love to put efforts into something they recognize as being worthwhile to try out, even though there might not be any instant profit for themselves. Taking risks, contributing more efforts, This is how we grow and how creative organizations grow.</p><p>Thanks for reading.</p><p>Subscribe to my <a href="https://uxdesigner.substack.com/"><strong>Newsletter</strong></a><strong> </strong>to receive the latest articles.</p><p>Connect with me on <a href="https://www.linkedin.com/in/muchao/"><strong>Linkedin</strong></a><strong>, </strong><a href="https://twitter.com/Muchao94"><strong>Twitter</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*aNPBhln7iDMY8qRcmoyCfA.jpeg" /></figure><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=3a9c615c6f05" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/product-design-junior-vs-senior-what-do-we-lack-3a9c615c6f05">Product Design Junior Vs Senior — what do we lack?</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[从我在Uber做产品设计的实习中期评价，谈谈Junior和Senior的差距在哪里，以及做产品设计/用户体验设计怎样快速成长。]]></title>
            <link>https://medium.com/@muchao/%E4%BB%8E%E6%88%91%E5%9C%A8uber%E5%81%9A%E4%BA%A7%E5%93%81%E8%AE%BE%E8%AE%A1%E7%9A%84%E5%AE%9E%E4%B9%A0%E4%B8%AD%E6%9C%9F%E8%AF%84%E4%BB%B7-%E8%B0%88%E8%B0%88junior%E5%92%8Csenior%E7%9A%84%E5%B7%AE%E8%B7%9D%E5%9C%A8%E5%93%AA%E9%87%8C-%E4%BB%A5%E5%8F%8A%E5%81%9A%E4%BA%A7%E5%93%81%E8%AE%BE%E8%AE%A1-%E7%94%A8%E6%88%B7%E4%BD%93%E9%AA%8C%E8%AE%BE%E8%AE%A1%E6%80%8E%E6%A0%B7%E5%BF%AB%E9%80%9F%E6%88%90%E9%95%BF-a78655dbc5b2?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/a78655dbc5b2</guid>
            <category><![CDATA[uber]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Sat, 08 Jul 2017 18:41:02 GMT</pubDate>
            <atom:updated>2017-07-08T18:41:25.202Z</atom:updated>
            <content:encoded><![CDATA[<p>从我在Uber做产品设计的实习中期评价，谈谈Junior和Senior的差距在哪里，以及做产品设计/用户体验设计怎样快速成长。</p><p>文章内容如下：</p><ul><li>背景</li><li>T3B3评价</li><li>作为Junior的反思</li><li>Junior如何快速成长</li></ul><p>喜欢直接看重点的同学请直接翻到<strong>Junior如何快速成长</strong>。</p><p>预计阅读时间：5分钟<em> — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</em></p><h3>背景</h3><p>Uber每年年中进行员工的T3(Top3)B3(Bottom3)评价。T3是指表现最突出的特质，B3并不一定是非常大的问题，指的是需要更加努力去提升的地方。实习生在中期也会收到一份T3B3评价。</p><h3>T3B3评价</h3><p>两个礼拜前刚刚完成我的实习中期汇报以及中期评价，一开始对老板给自己的T3评价高兴了一阵子；直到细细琢磨了B3，才发现有不少值得玩味的地方。 老板提交我的实习中期T3B3评价之前，在1对1开会的时候跟我讨论了其中的每一条评价以及他的理由；大部分比较客观，也有地方没有考虑到，我提出了意见；最后修改过之后给了我确定下来的T3B3评价。</p><p><strong>T3</strong></p><p><strong>快速学习能力</strong> 快速制作效果丰富的交互原型，快速掌握新工具并贯穿实习项目持续使用，在不太忙的时候主动学习新技能</p><p><strong>主动性及对接手新挑战的渴望</strong> 主动要求接手/参与超出实习项目之外的新项目，在大项目间隙快速完成各类小项目，并保证主要项目的进度。</p><p><strong>跳脱框架的产品/体验洞察力</strong> 他提出创造力的跳脱框架的产品理解 — — 我们有时因为团队/公司的限制，不得不把他们收缩到可操作的范围。他不应该被这些限制挫败，要争取一直提出有创造力的见解。</p><p><strong>B3</strong></p><p><strong>创造性探索</strong> 希望他在进入较高保真度的原型制作阶段之前能探索更广范围的解决方案</p><p><strong>演示汇报的明晰性</strong> 培养更好的把演示内容融入上下文，布局，架构，以及演示设计方案、流程的能力。换位思考，如果是一个对这个项目没有很多了解的人在看演示，会觉得清晰吗？</p><p><strong>独自进行项目迭代</strong> 他正在做一个比较独立的项目，没有很多来自不同声音的反馈 — — 在快速的每日反馈的工作模式下，他做的很好，但我希望他能培养更强的独自反馈、迭代设计的能力，在只能得到不定时的、零星的反馈的时候，也能高质量地迭代项目。</p><h3>作为Junior的反思</h3><p>除了看到自己需要补足的地方，从老板给我的实习中期评价，也能一窥一个入行7年多的设计师对设计能力评价的标准。</p><p>对于很多刚刚进入行业的Junior设计师们来说，相信很多都是设计技能还不错，有干劲儿，有强烈学习欲望，并且思维时常比较跳脱的。但真正工作的时候跟自己做概念作品很不一样；要学会把握项目进程，要使巧劲儿，学习Senior们思考项目、展示项目的方式。</p><p>对具体设计技能方面，老板并没有给出非常具体的评价；不是说不重视，而是在产品设计/用户体验设计工作的评价体系中，惊艳的视觉设计/原型制作能力并不是方案好坏的关键。借用厉害的@<a href="https://www.zhihu.com/people/miyukizhang/answers">张小雪</a> 在问题 <a href="https://www.zhihu.com/question/56799826/answer/161080642">商业作品与练习作品，哪一种更能体现设计师的真实水准？</a>，</p><blockquote><em>现在很多公司都有组件库，比如说Uber，Google等等大型科技公司，其实设计师的发挥空间很小了，主要就是协调沟通，看看按钮摆哪里比较好。这种情况下，用户体验和信息架构就尤为重要。所以商业作品中我看中设计师的设计怎样能提高产品用户体验和提升产品商业价值。</em></blockquote><p>做商业设计，附加价值（extra value）是产品设计师做设计决策需要纳入考量的重要维度之一。绝不是因为做presentation时提到附加价值显得“高大上”，而是因为它会成为与工程师和产品经理沟通时的利器。设计师要不时问问自己，pm常问的问题，”你的设计增加了什么附加价值？”以及工程师的想法，“这个设计有什么附加价值，需要我抛弃现有的模块，去大费周章开发新的模块？”</p><h3>Junior如何快速成长</h3><p>所以，注重培养哪些方面的能力会让Junior快速成长呢？</p><p><strong>1. 项目全局观</strong> 做方案不仅要有自己对项目的理解，也要从pm和工程师角度看问题，从其他相关项目团队角度思考可行性，多沟通，迭代性地达成共识。</p><p><strong>2. 交付物的情境化（contextualization）</strong> 在项目不同阶段，对展示内容做到怎样的保真程度把握好，考虑是线框图，还是高保真，需不需要动效，需不需要可交互。尤其在探索阶段，工作内容的大头是更广的尝试，避免花大量的时间在视觉效果/交互动画上。</p><p><strong>3. 随时快速交流传达的能力</strong> 在学校里，项目往往都是到了期中期末要准备做大的presentation了，才会把项目从头到尾好好梳理总结；工作环境里，交流大多是在非正式的情况下发生的。一个团队的工程、pm、设计、运营坐的很近，常常是有疑问就直接走到旁边交流。如果没有对项目理解的很透彻，没有在边做方案边总结边思考怎么传达，很可能沟通就会不顺畅。</p><p><strong>4. 独自迭代项目的能力</strong> 有很多时候不是随时能得到Senior和pm的反馈，这时就需要持续从不同维度批判自己的设计。这也引出另一个需要提高的方面。</p><p><strong>5. 归纳并掌握更多的思考框架/维度</strong> “这个按钮点击率低的原因有哪些”，“信息层级是否清晰”，“什么样的布局更适合当前的信息架构”，“除了这样的信息架构，还有没有其他的组织方式”。对产品的思考有很多不同的维度；项目停滞的时候，换个维度想问题，常常会发现可以改进的地方。</p><p>如果你也喜欢这篇文章，请随手点个赞，让世界充满爱。</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — 对怎样应对ux面试有疑惑？</p><p>请移步<a href="https://zhuanlan.zhihu.com/p/26239645">【UX面试篇1】从拒信一箩筐到Uber实习offer，我学到了什么 — 知乎专栏</a></p><p>设计练习/设计挑战面试不知从何下手？</p><p>请移步<a href="https://zhuanlan.zhihu.com/p/26351879">【UX面试篇2】设计挑战解题及面试思路 — 框架vs创造力 — 知乎专栏</a></p><p>ps: “设计能力”究竟是什么？最近在思考这个问题，欢迎分享你的看法。</p><p>未经授权，不得转载。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a78655dbc5b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[设计挑战是考验综合能力的面试形式，主要以两种形式进行，一种是在给定的时间内独自完成设计练习，之后在面试中和面试官展示方案，这种比较常见；另一种是当面或者视频面试，面试官可能会在设计挑战的过程中跟你互动…]]></title>
            <link>https://medium.com/@muchao/%E8%AE%BE%E8%AE%A1%E6%8C%91%E6%88%98%E6%98%AF%E8%80%83%E9%AA%8C%E7%BB%BC%E5%90%88%E8%83%BD%E5%8A%9B%E7%9A%84%E9%9D%A2%E8%AF%95%E5%BD%A2%E5%BC%8F-%E4%B8%BB%E8%A6%81%E4%BB%A5%E4%B8%A4%E7%A7%8D%E5%BD%A2%E5%BC%8F%E8%BF%9B%E8%A1%8C-%E4%B8%80%E7%A7%8D%E6%98%AF%E5%9C%A8%E7%BB%99%E5%AE%9A%E7%9A%84%E6%97%B6%E9%97%B4%E5%86%85%E7%8B%AC%E8%87%AA%E5%AE%8C%E6%88%90%E8%AE%BE%E8%AE%A1%E7%BB%83%E4%B9%A0-%E4%B9%8B%E5%90%8E%E5%9C%A8%E9%9D%A2%E8%AF%95%E4%B8%AD%E5%92%8C%E9%9D%A2%E8%AF%95%E5%AE%98%E5%B1%95%E7%A4%BA%E6%96%B9%E6%A1%88-%E8%BF%99%E7%A7%8D%E6%AF%94%E8%BE%83%E5%B8%B8%E8%A7%81-%E5%8F%A6%E4%B8%80%E7%A7%8D%E6%98%AF%E5%BD%93%E9%9D%A2%E6%88%96%E8%80%85%E8%A7%86%E9%A2%91%E9%9D%A2%E8%AF%95-%E9%9D%A2%E8%AF%95%E5%AE%98%E5%8F%AF%E8%83%BD%E4%BC%9A%E5%9C%A8%E8%AE%BE%E8%AE%A1%E6%8C%91%E6%88%98%E7%9A%84%E8%BF%87%E7%A8%8B%E4%B8%AD%E8%B7%9F%E4%BD%A0-f62974ca6019?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/f62974ca6019</guid>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Sat, 15 Apr 2017 01:36:05 GMT</pubDate>
            <atom:updated>2017-04-15T01:52:25.528Z</atom:updated>
            <content:encoded><![CDATA[<p>设计挑战是考验综合能力的面试形式，主要以两种形式进行，一种是在给定的时间内独自完成设计练习，之后在面试中和面试官展示方案，这种比较常见；另一种是当面或者视频面试，面试官可能会在设计挑战的过程中跟你互动。</p><p>文章内容如下：</p><ul><li>设计挑战的目的</li><li>我的Uber设计挑战解题回顾</li><li>总结</li><li>附录</li></ul><h3>设计挑战的目的</h3><p>关于设计挑战的目的，Uber给出的解释是：</p><p>我们希望通过设计挑战了解你作为设计师的三个方面</p><ol><li>我们好奇你分析设计问题的过程</li><li>我们想了解你评估潜在方案的探索方式</li><li>我们想了解你是怎么处理交付物和方案展示的</li></ol><p>对应设计过程，就是调研、设计、评估、展示。这里以我的Uber设计挑战案例做个方法论总结。</p><h3>解题过程回顾</h3><p><strong>Uber的UX设计挑战题目（原文见附录）</strong></p><p>提升Expedia（全球最大的在线旅游公司）移动端网页用户体验，重新设计用户是怎样选择旅行的日期的。假设人们可能在日期选择上有一定的弹性，思考如何帮助他们选择最佳的旅行日期。</p><ul><li>考虑流程中的所有情况，以及需要支持的极端情况</li><li>保证和现有用户体验的功能对等</li><li>不限制使用低保真原型</li><li>推荐使用Keynote/Invision/Flinto/PDF 进行展示</li></ul><h3>1. 破题 — — 主观角度出发的调研</h3><p>我是第一次使用Expedia，不过用其他旅行网站订过机票，所以对流程比较熟悉；而习惯了流程的问题在于，痛点反而不明显了。所以我决定画出流程图，一步一步解析整个过程。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*YloeR-XkoRWjGzSH.png" /></figure><p>制作流程图的过程基本上就是一次自己的<strong>认知演练(Cognitive Walkthrough)</strong>。认知演练是用户测试的一种方式，主要目标是对不熟悉系统的用户进行测试，评估系统的可习得性（learnability）。所以自己做的时候，尽量从对系统不熟悉的角度出发，完成这个购买机票的流程。</p><p>给自己设定一个合适的目标，比如购买下个礼拜任何一天从三番飞到亚特兰大的机票。自己在过程中不断提问自己，”在点击这个按钮后预期会发生什么“，”在这个输入框里进行输入预期会发生什么“，”在这个界面预期会获知那些信息“，等等，以及，”网页的响应是否符合预期“。以自己真实的心态去演练整个过程，把痛点记录下来，整理之后选择和题目关系最紧密的，标注到流程图上。</p><p>完成了认知演练，按照流程从头再使用一次。不过这一次，目的是根据<strong>10项启发式评估原则（10 heuristics）</strong>对使用流程进行评估；我发现使用体验有悖10 heuristics中的4条到了不能忽视的程度，并且对具体的体现做了记录。</p><ul><li>系统状态可见性（已输入的旅行具体信息可见性不佳，需要的时候要滑动到顶部才能看到）</li><li>用户控制及自由度（日期选择受限，没法在主页选择舱位等级，没有到达时间的选项）</li><li>一致性（选择买来回机票的时候，我期望会在同一页面看到来回航班的信息，但Expedia把信息分到了两页展示）</li><li>使用的可变通性（flexibility）及效率（系统推荐的航班可能会一直不符合用户需求）</li></ul><h3>2. 验证 — — 目的明确的快速采访</h3><p>为了验证我使用系统遇到的问题是否具有普遍性，我在微信上迅速地问了6个小伙伴，其中有设计师，有程序员，有学电子的，有学化学的；同时也有全职工作的，也有学生。采访对象的选择上，我希望在数量有限的样本中依旧能体现出人群的多样性。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*-QYaTIVO86nJSMvQ.png" /></figure><p>采访中有意想不到的收获：</p><ul><li>除非是商务旅行，<strong>所有</strong>受访者的出发日期和回程日期都有一定的可变通性</li><li>学生和全职人士的可变通性<strong>有区别</strong>；学生的可变通性范围有时可以是<strong>1–2个月</strong>，全职人士的可变通性则大多在<strong>1–2周</strong></li><li>所有受访者选择旅行日期都是基于旅行目的（纯旅游/探亲友/参加活动）、价格、飞行时间等因素的<strong>综合考虑</strong></li><li>其中4位受访者认为在具体某天的<strong>到达时间</strong>比起飞时间更重要（而大部分）</li><li>所有受访者都认为<strong>价格是top2的考虑因素</strong>，除非是紧急情况</li></ul><p>这一步在设计挑战用的不多，纯粹属于自己对觉得快速且有效的收集信息方式的一次尝试，可以用“quick &amp; dirty”来形容。因为Uber的设计挑战时间不是硬杠，我稍微多花了一点时间进行这一步是希望能加强之后设计决策的效力（validity）。如果时间是严格限制在4小时左右，我依旧会进行这一步，信息可能不那么全，不过采访4–5个朋友还是没问题，耗时会在30分钟左右；明白自己想收集的信息，采访甚至可以和其他步骤穿插进行，不会耗费很久。</p><h3>3. 极端情况</h3><p>考虑不同类型的用户会怎样进行购买机票的流程，探索可能会出现的极端情况。做完之后我发现，这一步实际上对整体流程的影响不大，对产品后期细节的优化比较有价值。</p><p>这里举几个例子：</p><ul><li>Expedia不提供以周/月为单位的机票的查看，可变通性体现在系统会根据你的搜索推荐机票。这就可能会引发“系统推荐一直不符合用户需求”的极端情况，因为推荐的随机性比较大，用户不好控制自己想看到的信息</li><li>网站提供的可变通性不符合用户自己的可变通性</li><li>Expedia不提供到达时间的筛选条件</li><li>用户不知道去哪旅行</li><li>用户忘记输入有些必填的信息</li><li>用户输入的回程日期先于出发日期</li></ul><h3>4. 竞品分析</h3><p>根据在过程中发现的问题，我选择了主页、价格日历和筛选页面进行了竞品分析，分别截了图分析其他产品的使用流程。</p><p>主要发现：</p><ul><li>大部分网站只提供前后三天也就是以周为单位的选项，而skyscanner提供了以月为单位的可变通性选项，对于有更多可变通性的用户提供更有价值的信息，值得参考</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*af41pXPZdx_56Gkb.png" /></figure><ul><li>到达时间通常被认为没有出发时间那么重要，经常出现在筛选条件的隐藏选项中，Expedia甚至都不提供到达时间的选项（这与我的调研结果是相悖的；我决定尊重调研结果，基于调研改进筛选条件）</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*5au62JOMAqInrAX6.png" /></figure><h4>5. 用户流程再设计</h4><p>基于调研，我希望在以下方面改进用户流程</p><ul><li>区分并满足有不同可变通性用户人群的需求（提供可变通性的选项，提供以周/月为单位的可变通性选项）</li><li>改善重要基本信息的可见性</li><li>提供更便捷的回到上一级的选项</li><li>在筛选条件的重要位置中添加到达时间的选项</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*XQHklKCP_S6wQpN4.png" /></figure><h3>6. 设计挑战展示</h3><p>之后做展示时，面试官可能会抛出他们自己作为用户在使用产品中遇到的问题，不一定在这个设计挑战命题的范围之内。比如我被问到，“我是维珍航空的忠实用户，只想坐他们的飞机；但是我在Expedia上有积分，所以我想在Expedia上买他们的机票。你会怎么设计这个流程？”</p><p>这个时候就需要你对产品有更深的理解，不只是在命题的重点 — — “选择日期”上。实际上，整个用户流程是不能分隔开的；所以如果对流程进行过分析，你会知道航空公司 — — “维珍航空”是可以在Expedia提供的筛选条件里勾选的。需不需要为了这个面试官（一个典型/非典型用户）来把维珍航空的选项放到更高优先级的地方，显然不能因为他一个人就下决定。我的做法是，对接下来需要做什么样的调研/测试，可能的结果有哪些，根据不同的结果可以做出什么样的设计改进，讲出了自己的看法。想要做出一个有理有据的设计决策，显然需要更多的用户输入。</p><p>应对面试官的问题，也是一次对设计思路的考验。</p><h3>总结</h3><p>总的来说完成设计挑战的形式不限，没有所谓定式；完全可以根据自己的知识和技能体系选择不同的调研、设计以及验证方式。</p><p>四个关键点：</p><ul><li>时间很紧的情况下，不要想着把一个步骤做到完美；清晰的大框架+逐渐明确的设计方向是完成高质量设计挑战（甚至也是很多产品设计项目）的关键</li><li>灵活运用调研/验证方式获取想得到的信息，有用户输入更具效力</li><li>设计交付物尽量清晰、美观（Axure/Balsamiq还是尽量避免使用吧，Sketch比较容易做好看）</li><li>回答问题时，重点不要放在结论；要注重的是探索解决方案的过程</li></ul><p>祝挑战愉快！</p><h3>附录</h3><p><strong>Uber设计挑战原题</strong></p><p>Expedia’s mobile website provides the starting point for many magical journeys around the world yet parts of the UX are far from magical. Redesign how someone chooses the dates for a trip. Assume people may have flexibility in their schedule, so think about how you could help someone choose the best dates.</p><p>● Consider all states that could exist in this flow and any edge cases that should be supported.</p><p>● Be sure to have feature parity with the existing UX.</p><p>● Feel free to work at a lower level of delity such as sketches or wireframes.</p><p>● We recommend you present your work in a format that allows for a walkthrough — Keynote,</p><p>Invision, Marvel, Flinto, or even clickable PDFs are all acceptable options.</p><p><strong>文中出现的专业词汇</strong></p><p>认知演练: Cognitive Walkthrough</p><p>可习得性: Learnability</p><p>可见性：Visibility</p><p>可变通性：Flexibility</p><p>效力：Validity</p><p>10项启发式评估原则: 10 heuristics</p><p>如果你也喜欢这篇文章，请随手点个赞，让世界充满爱。</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>对怎样应对ux面试有疑惑？</p><p>请移步<a href="https://zhuanlan.zhihu.com/p/26239645">【UX面试篇1】从拒信一箩筐到Uber实习offer，我学到了什么 — 知乎专栏</a></p><p>在这些地方可以找到我<br><a href="https://www.zhihu.com/people/tang-mu-chao-tommy">知乎</a>/<a href="https://dribbble.com/McTang">Dribbble</a><br>同步更新的知乎专栏<br><a href="https://zhuanlan.zhihu.com/designtihu">设计醍醐</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f62974ca6019" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[【UX面试篇1】从拒信一箩筐到Uber实习offer，我学到了什么]]></title>
            <link>https://medium.com/@muchao/ux%E9%9D%A2%E8%AF%95%E7%AF%871-%E4%BB%8E%E6%8B%92%E4%BF%A1%E4%B8%80%E7%AE%A9%E7%AD%90%E5%88%B0uber%E5%AE%9E%E4%B9%A0offer-%E6%88%91%E5%AD%A6%E5%88%B0%E4%BA%86%E4%BB%80%E4%B9%88-666a6e1791b3?source=rss-c857d1600bba------2</link>
            <guid isPermaLink="false">https://medium.com/p/666a6e1791b3</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Muchao]]></dc:creator>
            <pubDate>Sat, 08 Apr 2017 02:22:08 GMT</pubDate>
            <atom:updated>2017-04-08T15:22:14.843Z</atom:updated>
            <content:encoded><![CDATA[<p>这篇文章记录了我申请UXD实习，经历20+面试后的体会。主要包括以下内容：</p><ul><li>UX面试流程</li><li>我的个人套路</li><li>总结</li><li>附录</li></ul><p>从去年10月第一次在北美电面到3月中的最后几波面试，我走了非常长的一段路。总共和10+公司进行了面试，按轮数算大概有20+。尽管和前5，6家面的方式有很大的问题，总的来说我还是挺享受整个过程的，尤其是面完总结的时候，每次都能发现做得不够好的地方，然后慢慢找到适合自己的面试风格。如果不是有前面茫茫多挂掉的面试，后面的offer很难说还会不会拿到。以下是正文。</p><h3>UX面试流程</h3><ol><li>如果是海投，简历关过了后，第一通电话通常是HR主导的行为面试；搜索“behavioral interview question”，大概了解一下套路就行。之后的面试过程基本上跟内推的申请者一样。</li><li>有些公司会要求做设计挑战，根据时限的不同，完成度也不一样；我做过1个小时的和4个小时的。这里先不具体探讨，我计划之后具体梳理一下做设计挑战的思路。</li><li>内推进面试很可能就没行为面试了，直入正题，第一轮一般是视频面试，如果是本地公司，也有可能直接到公司面。这一轮一般是由高级设计师主导的作品集展示，会要求你深入讲述1–2个作品。之后一轮可能是设计主管或者还是设计师，同样会涉及到作品集展示；也可能加上app批判，要求你选择一款app，一边使用一边讨论使用体验，比较像是朋友之间对app的探讨。过程中经常会有一些关于设计宽泛的讨论，包括但不限于对设计流程中某一环节的探讨，原型工具的使用习惯，和程序员/产品经理/设计师的合作体验。</li><li>一般面1–3轮之后就会出结果了。</li></ol><h3>我的个人套路</h3><p><strong>自我介绍</strong></p><p>我写过不下5个版本的自我介绍，主要分为讲故事版，中规中矩版，以及说出你的梦想版。最后全都试验下来，发现还是中规中矩版比较适合作为一个面试的开端。这里中规中矩并不是沉闷的同义词，但自我介绍表达清楚自己的背景，经历是第一要务，不要让自己觉得fancy的内容抢了重点。这也是我一开始犯的一个错误。由于自己的一些经历，我在从AKQA面试官那获得反馈之前，一直把面试当成是一个秀，自我介绍直接开启讲故事模式，讲我怎么样从小对设计有兴趣，进入工业设计专业，又决定深入人机交互领域学习。</p><p>这里咱们退一步，想一下，面试官让你自我介绍是做什么。他们已经有了你的简历，为什么还要你再做自我介绍？</p><p>不就是为了打开个话匣子嘛。</p><p>既然面试是要评估你的专业能力，那自我介绍就不如讲和专业更相关的内容，简要地概括一下自己的教育、实习经历，做过什么样的项目，主要负责过哪些环节。我通常会再讲两点自己在设计过程中最喜欢做的事情，以及为什么。一是体现对做设计的热情，二是抛出一个暗示“我擅长这个（些）环节”的引子。抛出这个引子是因为，设计的视觉表现还有工具的掌握情况，通过作品集就能看出个大概，对设计流程的理解则需要靠交流来展示。这个重在真实，一定要是自己真正有体会的事情，这样如果面试官真的有兴趣问下去，你也能拿出相应的例子来佐证。</p><p>举个例子，我会说我喜欢采访，非常重视每一次和目标用户面对面沟通的机会，因为通过采访我可以对他们更有同理心，了解他们在使用产品过程中的真正痛点。我碰到过面试官听完后说，听上去很有趣，能不能讲一个你从用户采访中获得信息而后影响你的设计决策的具体的例子。我确实在项目中有体会，所以就能很顺利地接下去话。这时候就可以很自然地开始讲准备好的一个项目了。</p><p><strong>项目讲述</strong></p><p>自我介绍完，面试官会让你选一个自己的项目讲述。<br>我的流程一般是:</p><ol><li>项目背景</li></ol><ul><li>一句话概括，这个设计项目为谁，通过什么方式，解决了什么问题（who, how, what）</li><li>实习项目/学校项目？个人项目/团队项目？</li><li>在项目中的角色是什么？主要负责哪些工作？</li></ul><ol><li>用户调研</li></ol><ul><li>定义问题</li><li>怎样发现问题的？目标人群是谁？</li><li>用了哪些调研方法来定义问题？(方法主要包括文献研究，采访，问卷等。讲清楚是怎样一步步通过调研，对定量数据或定性数据的分析，从较大的问题范畴缩小到具体的设计目标）</li><li>定义的主要问题是什么？（我的习惯是讲2–3点）</li><li>细化场景</li><li>用户画像（通常为1–2个，可分主次，讲清楚为什么这么选择这两个用户画像；我的个人习惯是从采访和问卷中挑取具有代表性的用户语录，引用到用户画像上，来增加用户画像的真实度和信度）</li><li>故事版（讲述重在痛点清晰，情境真实，还有一点点趣味，排名分先后）</li></ul><ol><li>产品调研</li></ol><ul><li>竞品分析（风格、亮点功能、信息架构，根据具体项目决定分析哪些方面）</li><li>其他调研</li></ul><ol><li>设计</li></ol><ul><li>信息架构（解释清楚就好，我的个人习惯是分开说最小可行产品MVP和为解决具体问题设计的创新功能模块，Twitter面试官特别欣赏这点，强调有MVP的重要性；如果使用了Card sorting等调研方法指导信息架构的设计，会更有说服力）</li><li>设计原则（该产品的设计指导准则）</li><li>用户流程（个人习惯是，着重讲流程中具体的设计是怎样体现设计原则的）</li><li>解决痛点的功能（叙述清楚具体功能，说明白解决了之前提到的哪些问题）</li><li>视觉设计（因为是ux面试，所以主要讲一些设计决策的原因，并不是重点）</li></ul><ol><li>评估<br>这一点是大部分学生项目所缺乏的，即使是HCI专业的学生项目，做的评估也大都相当有限。当然，项目中有这一环节绝对是面试的加分项，可以体现对整个设计流程的掌握程度，以及设计思维的完整度。这里简要说一下我在面试的时候怎么去讲述验证的环节，</li></ol><ul><li>启发式评估（说清楚找了几个专家，依照Jakob Nielsen的10项可用性原则做了评估，得到的结果是怎样）</li><li>A/B测试（找了几个用户做了怎样的测试，满意度问卷和系统可用性度量结果是什么，选择哪个原型继续迭代及其原因）</li><li>可用性测试（说清楚找了几个用户做测试，发现哪些问题）</li><li>其他评估（具体项目采用的评估方式不尽相同，有时甚至需要根据项目需要自己设计评估方式）</li></ul><p>必须强调展示评估过后做了哪些设计上的改进！评估是为了指导设计迭代，如果评估过后没有改进，那评估的效用就很有限，更不用说面试时候的效果会打折扣。</p><p><strong>App批判</strong></p><p>这一环节有多种形式，有的面试官会在聊天的时候抛出问题“你有没有特别喜欢的一款app？为什么？”，然后根据你选择的app展开一段对话。有的比较正式，会提前告知你有app批判环节。准备方式都一样，备好几个玩得烂熟的app，自己从多个角度（交互，视觉，商业）走几遍分析。</p><ul><li>简要概括app的商业模式</li><li>Landing page（其他页面也一样）是怎么设计的，给你什么样的感觉，交互清晰吗，能否预测按下某个按钮会出现什么？</li><li>点击一个tab的时候你觉得那个tab会包含哪些内容？实际是否符合期望？</li><li>哪些元素符合/不符合iOS/Android设计规范？好/坏？</li><li>有没有体现哪些具体的UX/UI趋势？（Skeleton loading, Duotone等等）</li><li>有哪些特别的设计元素，为什么好/坏？（我喜欢讲Uber 2017年改版后的app，整体概念和滑动卡片的元素）</li><li>总说，喜欢这款app的哪些方面，为什么？（个人习惯是不光讲app，还会提运营上的亮点，务求真实体会）</li></ul><p>这一块可以深入到很具体的某个视觉元素，也可以对商业模式进行探讨，取决于你跟面试官的互动情况。</p><h3>总结</h3><p>以上完整的项目叙述流程是理想情况，实际面试中不需要每一条都讲得非常详细，时间上也不允许；具体怎么讲述，根据情况自行斟酌。个人有个人的面试风格，我只能尽力提出一个可以通用化的讲述模式。</p><p>好的结构可以保证你在面试中思维清晰，但讲述的内容仍旧是需要日积月累的。想在ux面试中做到游刃有余，可能需要数十次的梳理、练习。把自己的项目里里外外吃透了，对整个设计过程烂熟于心，跟面试官的交流会顺畅无比。合适的时候，要敢于表达自己对设计流程的理解，有切身体会的观点很容易引起面试官的共鸣。Practice makes perfect。</p><p>关于需要准备的量：<br>自我介绍，中规中矩版，有一点点趣味更好；<br>作品集展示，完整地准备2–3个项目的讲述；<br>app批判，准备4–5个app的分析，最好全面了解该品牌的产品、运营、设计。</p><p>下一篇文章计划继续探讨在UX面试中，有哪些Dos &amp; Dont’s。</p><p>就这么多。享受你的面试！</p><h3>附录</h3><p><strong>文中提到术语的中英文词汇</strong><br>问题范畴: problem scope<br>设计挑战: design challenge<br>app批判: app critique<br>主要/次要人物画像: primary/secondary persona<br>用户语录: user quote<br>启发式评估: Heuristic Evaluation<br>系统可用性度量: System Usability Scale (SUS)</p><p><strong>推荐阅读</strong></p><p><a href="https://medium.com/the-year-of-the-looking-glass/how-to-do-a-product-critique-98b657050638">Julie Zhuo — How to do a Product Critique</a></p><p>Facebook Product design VP手把手教你产品批判的正确姿势</p><p><strong>在这些地方可以找到我</strong><br><a href="https://www.zhihu.com/people/tang-mu-chao-tommy/answers"><em>知乎</em></a><em>/</em><a href="https://dribbble.com/McTang"><em>Dribbble</em></a><em>/</em><a href="https://medium.com/@hellotommy1994"><em>Medium</em></a><br>同步更新的知乎专栏<br><a href="https://zhuanlan.zhihu.com/designtihu"><em>设计醍醐</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=666a6e1791b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>