<?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[Design Notebook - Medium]]></title>
        <description><![CDATA[Sketching of thoughts and ideas - Medium]]></description>
        <link>https://medium.com/design-notebook?source=rss----65f2605e4820---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Design Notebook - Medium</title>
            <link>https://medium.com/design-notebook?source=rss----65f2605e4820---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:48:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/design-notebook" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Backward Thinking in Problem Solving — Part 2: Start with Objectives, not Problems]]></title>
            <link>https://medium.com/design-notebook/start-with-objectives-not-problems-210904985446?source=rss----65f2605e4820---4</link>
            <guid isPermaLink="false">https://medium.com/p/210904985446</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Ryan Nguyen]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 05:29:42 GMT</pubDate>
            <atom:updated>2020-02-04T02:54:17.538Z</atom:updated>
            <content:encoded><![CDATA[<p>This is <strong>2nd article </strong>of series <strong>Thinking Backwards in Problem Solving</strong>. You can read <a href="https://medium.com/design-notebook/backward-thinking-in-problem-solving-part-1-introduction-75ee71829abb">Backward Thinking in Problem Solving — Part 1: Introduction</a> to have an overview understanding first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-QvTTBvQrpZ6o3G4L-PWSQ.jpeg" /><figcaption>Start with Objectives, not Problems (Photo by <a href="https://unsplash.com/photos/aOYA7D3fse8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/@ryanntt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>)</figcaption></figure><p>The first step of any project is planning, which include setting objectives. Not only when we work backwards but also in any problem-solving framework, objectives are critical to the success of project as good objectives describe what success look like and will be used as north star through out the process.</p><p>If you start a project by dwelling into problems, you might get bogged down by numerous issues at the end of analysis phase. Only a few of these are worth solving or can be solved within your time frame. You want the problem analysis to help you find promising solution, not just root causes.</p><h4>Stay relevant</h4><p>It feels good to analyse problems when we start any project.In a past project that has a new knowledge domain, I made the mistake of exploring all related topics. Having many problems in the end, I had to spend more time on prioritising them and the work required more billable hours. I definitely learnt about the domain but something wasn’t right when client had to pay for all those hours. I should have had understood which specific problems contribute to the problems and final solution. The mistake can be avoided if I set out to collect data with clear objectives.</p><p>It is comfortable to think about problems without the constrain of objectives. However, in working backward we make having solution as first priority by planning our objectives. With objectives, we are better at choosing the method to collect and analyse data. The dilemma of trying to understand the root cause and collecting a wide range of data in analysis phase will be discussed further in the next article.</p><h4>Use Design Criteria</h4><p>Design criteria often act as the intermediaries between objective and solution. You don’t want to have tunnel vision when focusing on solution early, but also want something more specific that help you come up with solutions digging deeper into a problem. You might want to ask more question to validate whether design criteria works for your customers. Think about what kind of solution (instead of what solution) might help solve the problem.</p><blockquote>Use design criteria to stay broad enough, before focusing on specific solutions.</blockquote><h4>Focus on the Unchanged</h4><p>Many companies have their missions remain unchanged for a long time, even decades but their product portfolio change. The reason is because their mission is tied to human behaviours. The solution change quickly but human behaviour change much slower.</p><h4>Good objectives</h4><p>As objectives are not solutions, they rather describe the goals and ambition you want to achieve without limiting the scope by indicating which technology we have to use. As these ambition can be vague, a good objective need to have three factors:</p><ul><li>Direction: E.g.We want to expand our insurance business to New South Wales farming community.</li><li>Measurable Target: In 5 years, we want to own 70% market of farming insurance nationwide.</li><li>Design criteria: We want to focus on medium and large-size farming business firstly and build customer base through broker and financial advisors.</li></ul><h4>Case study: Amazon</h4><p>Working backwards is practiced in Amazon. New products by Amazon start with customer first. Werner Vogels mentioned this in his article <a href="https://www.allthingsdistributed.com/2006/11/working_backwards.html">Working Backwards</a>.</p><ul><li><strong>Start by writing the Press Release</strong>. Nail it. The press release describes in a simple way what the product does and why it exists — what are the features and benefits. It needs to be very clear and to the point. Writing a press release up front clarifies how the world will see the product — not just how we think about it internally.</li><li><strong>Write a Frequently Asked Questions document</strong>. Here’s where we add meat to the skeleton provided by the press release. It includes questions that came up when we wrote the press release. You would include questions that other folks asked when you shared the press release and you include questions that define what the product is good for. You put yourself in the shoes of someone using the product and consider all the questions you would have.</li><li><strong>Define the customer experience</strong>. Describe in precise detail the customer experience for the different things a customer might do with the product. For products with a user interface, we would build mock ups of each screen that the customer uses. For web services, we write use cases, including code snippets, which describe ways you can imagine people using the product. The goal here is to tell stories of how a customer is solving their problems using the product.</li><li><strong>Write the User Manual</strong>. The user manual is what a customer will use to really find out about what the product is and how they will use it. The user manual typically has three sections, concepts, how-to, and reference, which between them tell the customer everything they need to know to use the product. For products with more than one kind of user, we write more than one user manual.</li></ul><h4>Using Lean Startup</h4><p>Lean Startup by Eric Ries, a popular startup framework, has some similarities with Amazon principles. When we combine them together, we have following steps in defining objectives of product development:</p><ul><li>Create landing page containing information similar to Press Release, and describe the customer experience.</li><li>Validate the product further with customer research. Use the insights to figure out the customer experience of the product. Describe it to customer in the landing page. Dropbox did this in a video. You need to figure how the product can be valuable and usable.</li><li>Improve the landing page with FAQ and User manual after validating the product. The FAQ and USer Manual contain product requirement for engineering.</li></ul><h3>Think slower to go faster</h3><p>It feels comfortable to go with objectives passed by stakeholder without reiterating them to fulfil important details. The next time you start any project, make sure to spend time on setting clear objectives before doing doing research or development of solution. My preferred ways is to practice asking following questions and redefine objectives until they check all Yes boxes:</p><ul><li>What does success look like?</li><li>Can I describe the success to people outside the project team (to make sure it is understandable)?</li><li>Is the objectives quantifiable in any measurement?</li><li>What are the hypotheses in your objectives that I can validate?</li><li>Are the objectives focused on something unchanged in future or might it be irrelevant soon?</li><li>Are my customers part of the success? What do they look like when using the solution?</li></ul><p>In the following article, I will talk about Analytical Framework in helping you measure process logically when working backwards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210904985446" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-notebook/start-with-objectives-not-problems-210904985446">Backward Thinking in Problem Solving — Part 2: Start with Objectives, not Problems</a> was originally published in <a href="https://medium.com/design-notebook">Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Backward Thinking in Problem Solving — Part 1: Introduction]]></title>
            <link>https://medium.com/design-notebook/backward-thinking-in-problem-solving-part-1-introduction-75ee71829abb?source=rss----65f2605e4820---4</link>
            <guid isPermaLink="false">https://medium.com/p/75ee71829abb</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Ryan Nguyen]]></dc:creator>
            <pubDate>Wed, 04 Jul 2018 17:19:53 GMT</pubDate>
            <atom:updated>2020-02-04T02:55:55.843Z</atom:updated>
            <content:encoded><![CDATA[<h3>Backward Thinking in Problem Solving — Part 1: Introduction</h3><blockquote>Sometimes, if you do not begin at the end, you end at the beginning (Ginat, 2005).</blockquote><p>Backward thinking in problem solving can be observed frequently in my life and design career, either happening to me or some one else. I have learnt many lessons about it and want to write about it here.</p><p>Following are the definitions of forward and backward thinking <em>(terms </em><strong><em>thinking</em></strong><em> and </em><strong><em>working</em></strong><em> can be used interchangably).</em></p><blockquote>Working forwards is the way of approaching a problem by starting from initial state and advancing forwards, towards the goal state (Polya, 1957 in Ginat, 2005).</blockquote><blockquote>Working backwards is the way of advancing backwards from the goal state (Polya, 1957 in Ginat, 2005).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d4X0K-RhI1W9Fxl77DsfkA.png" /><figcaption>The goal state can be defined by you, and presence sometimes is not fully known as you thought.</figcaption></figure><p>It is easy to see why people often choose the forward option: from Initial state to Goal state. However, the reverse might be more logical and often optimal.</p><p>People tend to think they understand what they have at the presence and constrain themselves to that understanding when planning for the future. Without defining the desired goal, it’s easy to limit yourself and miss out ambitious targets.</p><p>When designing a new product, people start from it being a sucess and work backward what they need to achieve to reach that goal. However, other people prefer to look at the past performance and current state of product and work forward what success they might reach. We will compare these two ways in the subsequent articles of this series.</p><h3>You have used backward thinking before</h3><p>Though fancy as it sounds, backward thinking is what you actually have used since you were a kid. Remember the last time you lied to someone? For example, when you didn’t come on time. You started with not coming on time, went backwards to seek excuse and settled with reason that there was a traffic jam. Your friend might have asked why she shared the same route and didn’t see any traffic jam. You started with the fact that she didn’t see the jam and thought backward to seek another explanation.</p><p>Math is one of the first domains where we learn how to work backward. Let’s consider 2 math problems.</p><blockquote>Problem 1: A car park has a maximum capacity of 75 cars. What is 2/3 of its capacity?</blockquote><blockquote>Problem 2: A car park currently has 50 cars parking. We know that this is only 2/3 of its maximm capacity. What is its maximum capacity then?</blockquote><p>In the first problem, 75 cars is the known initial state, the relation to goal state is operation with 2/3. The solution is times 75 and 2/3, which is working forward.</p><p>In the 2nd probem, 50 cars is the known goal state, the relation to maxium capacity (unknown initial state) is 2/3. The solution is to know 1/3 of maximum capacity first and then derive the whole, which is working backward.</p><h3>Why I care about Backward Thinking?</h3><p>As more and more people, including me, say we are problem solvers, I reflected and recognized gaps in my knowledge and skills required to solve problems, especially in UX design. I decided to learn problem solving from foundation. I started with which concepts and framework people use to solve problems in case studies. The next step is to undersand those concepts and frameworks. Problems requiring backward thinking like problem 2 mentioned earlier represent many case studies I have read.</p><h4>Exercise</h4><p>After knowing the concepts of backward and forward thinking, I reflected on what happened in my past projects and notice that I used both methods under different circumstances.</p><p><em>In the following articles, I’m going to talk about the fundamentals of backward thinking. Meanwhile, you can start looking at how you solve daily problems from perspective of working forward and backward. Prepare to be surprised!</em></p><h3>Next</h3><p><a href="https://medium.com/design-notebook/start-with-objectives-not-problems-210904985446">Backward Thinking in Problem Solving — Part 2: Start with Objectives, not Problems.</a></p><h4>References</h4><p>Ginat, David. <a href="https://www.thefreelibrary.com/The%20suitable%20way%20is%20backwards,%20but%20they%20work%20forward.-a0128170454">“<em>The suitable way is backwards, but they work forward.”</em></a><em> </em>Journal of Computers in Mathematics and Science Teaching, vol. 24, no. 1, 2005.</p><p>This article was originally writtern at <a href="https://ryanntt.com/blog">ryanntt.com</a>.</p><p><strong>If you have enjoyed this article, it would be great if you press on the button 👏 below. I truly appreciate it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75ee71829abb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-notebook/backward-thinking-in-problem-solving-part-1-introduction-75ee71829abb">Backward Thinking in Problem Solving — Part 1: Introduction</a> was originally published in <a href="https://medium.com/design-notebook">Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does Clap measure?]]></title>
            <link>https://medium.com/design-notebook/what-does-clap-measure-172b20c58371?source=rss----65f2605e4820---4</link>
            <guid isPermaLink="false">https://medium.com/p/172b20c58371</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ryan Nguyen]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 13:38:59 GMT</pubDate>
            <atom:updated>2017-11-07T14:24:28.149Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This was published as part of Design Notebook, a publication documenting my thoughts when working as UX Designer.</em></p><p><em>This article reflects my opinion of Clap button on Medium.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U08eNGXNNpEIXphw9zOGrA.jpeg" /><figcaption><em>What it means when you clap an article? </em>Photo by <a href="https://unsplash.com/photos/pPquxoraq_M?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ezra Jeffrey</a></figcaption></figure><h3>An Intentional Action</h3><p>When I reach the end of an interesting article, I generally feel inclined to click Clap, but after clicking once, whenever I want to click more, I find myself questioning my motivation of doing that.</p><p>Clapping reflects the (almost) irreversible intention of wanting to show appreciation when you press the button. After doing that you might want to reverse the action, thinking ”I don’t like this article anymore”. But is it equivalent to saying “I regret clapping this article”? Maybe. <strong>Like </strong>reflects a state of mind while <strong>Clap</strong> is one of many actions that result from that liking intention. You can change your mind, but you can’t undo the action. I think it also raise a point about people doing different things when they want show their appreciation for the article.</p><blockquote><strong>Like</strong> reflects a state of mind while <strong>Clap</strong> is one of many actions that result from that liking intention.</blockquote><h3>Measurement of Engagement</h3><p>People can do a quick action such as Like or Clap, or leave a comment, which, in my opinion, reflect the conversational nature of Medium. We see more and more Medium articles having opinionated, and even provocative voices. You can agree, disagree with parts of the article, which is what Medium should encourage people to do: <strong>have your own voices on Medium</strong>. And it is very critical to show the original point you refer to. These behaviours can be observed in the form of highlighting and commenting. Sometimes, highlighting just means you find this point interesting and want others to think about it. From all those points mentioned, its hard to conclude the more claps there are, the better Medium community is going to be. I would argue there are many level of engagement and Medium want to have both quantitative (claps) and qualitative (highlights, responses) metrics in place.</p><h3>Measurement of Satisfaction (of Reader)</h3><p>Personally, my satisfaction comes at 2 moments:</p><p>- Right after reading it: I judge whether I should reread it, bookmarked it or simply feel that I grasp enough information from the article.</p><p>- After rereading it: I reflect upon the details in the article and might give a second judgment.</p><p>People have different reading habits. Therefore, if we assume the quality of article is measured by the satisfaction of reader, how can the satisfaction of different reading style be measured fairly?</p><p>I find some articles interesting, but reading them again may change my opinion. Also I found myself reading the same article again sometimes, and realized that I already gave it a Like. Should I Like it one more time? Yes, but I couldn’t. In this case, it makes more sense with Clap.</p><p>Having time to reflect upon the article and reread to extract more details from it is difficult to be measured by Like. Clap does this better by allowing people to record satisfaction at first, second, nth time of reading. Clap not only measures an instant moment of satisfaction after reading an article, but an incremental satisfaction after reading, reflecting and eventually, in my case, bookmarking for re-visiting in the future. I imagine that when we look at data of reading habits, we can see how many subsequent claps people give when they revisit the article and have a fairer conclusion after considering this pattern.</p><blockquote>Clap not only measures an instant moment of satisfaction after reading article, but an incremental satisfaction</blockquote><p>In the another context, when I attend a play or speech, I don’t simply clap once but many. Introducing “fake” Clap provide more opportunities to understand social phenomenon on digital platforms like Medium. I’m concerned that people are more generous with clapping as a courtesy act as they subconsciously think about clapping in other social context.</p><h3>Measurement of Appreciation (to Writer)</h3><p>From a business perspective, Clap has a huge potential to differentiate further how different people value articles. Medium articulates this clearly at the end of every article: <strong>“By clapping more or less, you can signal to us which stories really stand out.”</strong> The more people claps, the more appreciation the writer receive in the form of monetary rewards.</p><h3>Conclusion</h3><p>From user perspective, clapping holds different meaning to different person and so introducing such a new pattern will require people to build a new behavioural model. It would be interesting to look at the relationship between number of clap, satisfaction of reader and revenue from Medium membership to judge whether the feature works as intended.</p><p>I was intrigued by the Clap button initially, but got used to it by treating it as Like button, which defeat the intended purpose of Clap. I am curious to know if anyone else is hesitant in clapping multiple times, or if this is due to my subconscious resistance to a new behavioural model.</p><p><em>Thank you for reading!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=172b20c58371" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-notebook/what-does-clap-measure-172b20c58371">What does Clap measure?</a> was originally published in <a href="https://medium.com/design-notebook">Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[App Updates that are Fun to Read]]></title>
            <link>https://medium.com/design-notebook/app-updates-that-are-fun-to-read-346aaedcaa2c?source=rss----65f2605e4820---4</link>
            <guid isPermaLink="false">https://medium.com/p/346aaedcaa2c</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Ryan Nguyen]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 12:44:32 GMT</pubDate>
            <atom:updated>2016-02-15T03:03:23.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zk1FRdGKpODZj1McLV3HCA.jpeg" /></figure><p>App update is a place that people hardly pay attention to. It is mostly filled with a long list of bug fixes and new features that are similar to the product backlog of product development sprint. <em>Maybe it is the product manager that writes the copy</em>, which includes common key words such as:</p><ul><li>This release includes following updates</li><li>Bug fixes, performance improvements, enhancements, <em>minor improvements </em>(Really? so why did you guys bother to release?), fixed</li><li>New features, what’s new, new</li></ul><h3>It’s not about being interesting</h3><p>The main problem with highly technical copies is that they are hardly read by user, which is unfortunate since users do need a reason to press the button Update. The feeling of owning something better when pressing the button is being ignored. Is it because it take less than 1 minutes to update the app so no user bother reading it?</p><p>Developers push updates with new features, which rely on user on-boarding to be introduced to users. People spent a big budget on on-boarding new user and user retention while skipping one of the most cost-effective place, the app update.</p><blockquote>In (content) design, the aha moment can come at the time and place that no one else has ever thought of or no courage to venture in.</blockquote><h3>The blend of information and personality</h3><p>I love app updates that are playful and engaging. For example, when you are a StarWars fan boy, you can feel the awesomeness in this brilliant copy from <strong>Hipmunk</strong>. Darth Vader was mentioned!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Kqf8VcosKUSwvM1aVl_1Q.png" /></figure><p>Hipmunk personality is always fun and witty. It makes me think H in Hipmunk stands for Hipster. Pay attention to their choice in copy:</p><ul><li><strong>Casual</strong>: s***, sexy, awesome, wicked, love, super, cool.</li><li><strong>Cultural references</strong>: Mighty Ducks, PeeWee, Team USA, Anakin Sky Walker, Darth Vader, Discovery-y.</li></ul><blockquote>Good app update can represent the product’s personality</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*EraFwCgfP4ZNIi4w6Pn9Fw.png" /></figure><p>Using a different approach,<strong> Medium</strong> gave little exercise to your brain and introduced important changes at the end. They sure love Scramble.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGjFZR9CMlc-bvsr9PEhhg.png" /></figure><p>Medium app updates have a consistent sense of humour with stories. The summary of new features and changes at the end is always helpful. To me, Medium has this cool vibe that welcome people to update the app with ease of mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d60rr_GIQMZRJ49_qqJ7lw.png" /></figure><p>And this was their gift for Star Wars fans as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*VyZ61icQW8htcG2xqADqCw.png" /></figure><p>Someone was cooking and writing this update. I guess Medium may have different people writing app updates. <em>Otherwise, who is this cool person? Must be someone love cooking, telling witty joke and a Star Wars fan.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3wcgqL0wCz9nWnev-FSGw.png" /></figure><p>I love using <strong>Tumblr</strong> app update. It has the best update with Friends stories. I can immediately see that the update was to support iPad Pro, fix bugs, and smooth animation. A nice blend of humour and important information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2RL2USf1mZsSw5VHhiz8Nw.png" /></figure><p>I hope to see frequent update of these apps so that I can read the copy. App updates can be fun, even when they are to inform the user of new features and changes. People do read it.</p><h3>A moment before pressing Update</h3><p>Maybe after reading this article, you will start checking the updates one by one instead of pressing “Update All”, which will remove all the excitements.</p><p><strong>If you see any fun app updates, please let me know.</strong></p><h4>Update on 13 Feb 2016</h4><p>Many apps have engaging copy in the updates. Following apps (on iOS) are mentioned in the comments by readers:</p><ul><li><strong>Citymapper</strong>: its updates are clever in introducing new features in an understandable language. Thanks to <a href="https://www.designernews.co/stories/63538-app-updates-that-are-fun-to-read">Louis B on Designer News</a>.</li><li><strong>Trello</strong>: long but very good copy, not for impatient readers. Love its watch release in update 2.9.1 — Apr 23,2015.</li><li><strong>Slack</strong>: usually very long list of bug fixes and features in updates but you can still see many witty remarks.</li><li><strong>Pocket Casts</strong>: a podcast app mentioned by <a href="https://medium.com/@jasonbereklewis">Jason Berek-Lewis</a>. Really like the update 4.6.3 (Aug 6, 2014).</li></ul><h4><em>If you have enjoyed this article, it would be great if you press on the button ❤ below. I truly appreciate it.</em></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=346aaedcaa2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-notebook/app-updates-that-are-fun-to-read-346aaedcaa2c">App Updates that are Fun to Read</a> was originally published in <a href="https://medium.com/design-notebook">Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools and The Illusion of Better Design]]></title>
            <link>https://medium.com/design-notebook/tools-and-the-illusion-of-better-design-3761bf0b4836?source=rss----65f2605e4820---4</link>
            <guid isPermaLink="false">https://medium.com/p/3761bf0b4836</guid>
            <category><![CDATA[design-tools]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ryan Nguyen]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 12:44:06 GMT</pubDate>
            <atom:updated>2015-11-10T03:06:38.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HNmL9AyjBA9XixQPDlSMg.jpeg" /></figure><p><em>There are many design tools while you may have little time to master them all. How do you choose the “right” one?</em></p><h4>The Problem with Tools</h4><p>In photography, there is a syndrome called <a href="https://en.wikipedia.org/wiki/User:GreyCat/Gear_Acquisition_Syndrome">Gear Acquisition Syndrome</a>, aka GAS. GAS is a term used to describe an urge to acquire and accumulate lots of gear (Wikipedia). When people with GAS see great art work, <em>they focus mainly on the contribution of tool</em>. They forget who choose the tool and how that person made the choice. I first learnt about GAS in <a href="http://erickimphotography.com/blog/2014/04/06/fk-gas-gear-acquisition-syndrome/">this blog post</a>, written by Eric Kim, a street photographer. I used to be one of those people. I bought and tried out different camera and lens. I never felt satisfied with my cameras.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oXHK9k7VlMt6Bhe8ZykGdw.jpeg" /></figure><blockquote>The truth is that I don’t create better works with better tools.</blockquote><p>The more tools I have, the more I think about which tool to use in which situation. I used to feel curious about the tools used to create nice design. But having the tool, I didn’t know how to start creating. The truth is that I don’t create better works with better tools. What I thought previously as better is simply more fancy-looking design. <em>But the core of design is decided by me, not the tools I choose.</em> What I should have done is to choose one tool and think about how to deliver the best result regarding requirement of situation and limitation of tool, which are always existing regardless of tool I choose.</p><h4>The Path through (Overwhelming) Choices</h4><p>When I was in university, Photoshop(CS4) was my choice for anything related to design. I remember that it got things done but is slow in iterating, especially with interface design. I tried out other tools as well. Illustrator was fast but lack of certain functionalities to fit to my workflow. Firework was right for the job until <a href="http://blogs.adobe.com/fireworks/2013/05/the-future-of-adobe-fireworks.html">Adobe stopped supporting it</a>, which led to its sluggishness on Mac OSX. Then I discovered <a href="http://www.sketchapp.com/">Sketch</a> and immediately saw it as the right fit to my workflow.</p><p>The same thing is happening with prototyping tools. <a href="http://www.invisionapp.com/">Invision</a>, <a href="http://marvelapp.com/">Marvel</a> are good enough for me. But <a href="http://framerjs.com/">Framer</a>, <a href="https://www.flinto.com/">Flinto</a>, <a href="http://principleformac.com/">Principle</a> open more possibilities to achieve a higher level of deliverables. This makes me feel that what was enough is not enough any more. People on all social medias are asking each other what tools they should be using. People feel overwhelmed with choices.</p><p>I don’t want to have an illusion that if I can change tool, I can design better. The best design tool is already installed in my machine. I just need to master it.</p><blockquote>It’s not about choosing the right tools but using the available ones in right way.</blockquote><p>I felt excited learning new tool knowing that it will improve my workflow. But sometimes, the new tool comes with a learning time to master it and the deadline is coming. I was reluctant to learn and retreat back to what I am more comfortable with. Sometimes, it’s not about choosing the right tools but using the available ones in right way. I guess that’s why a lot of designers start creating design with pen and paper.</p><p><em>Am I lazy?</em></p><p>Yes, but <em>being lazy forces me to be selective with what I spent time on</em>. Learning a new tool means less time on mastering my current tool. Is it a fair trade-off? Only when I can justify this point, I will start to master that new tool.</p><h4>Which design tool should I choose?</h4><p>It boils down to answering 3 questions:</p><ul><li>What is your workflow?</li><li>Can you get support from community?</li><li>Do product makers listen to your feedback?</li></ul><p><strong>Stay sane with a workflow</strong></p><p>Workflow is not about a particular tool but how different tool can contribute to your productivity. You should try out different tools and find the right combination and improve the workflow. If you want to use a tool, you should think about how it fit into your workflow and your team’s workflow also. Since I started using Sketch, I find it suitable for my workflow due to <a href="http://www.sketchapp.com/plugins/">extensive collection of Sketch’s plugins</a>.</p><p><strong>Community is the best support</strong></p><p>Community is a source of help that is faster than the product’s customer support. A strong community provide advice and tips on how to maximise the usage of the product. Everyone is willing to help each others.</p><p><strong>The product makers listen to feedback from users/community</strong></p><p>A good customer support means a strong relationship between users and people creating products. Framer has <a href="https://www.facebook.com/groups/framerjs/">an active Facebook group</a> where everyone including Framer creator talk with each other and help improve the product. A lot of products use Twitter as a channel to communicate with users, which I find very effective and engaging. <a href="https://twitter.com/marvelapp">Marvel’s Twitter channel</a> is helpful in updating news about design trends, feature updates, as well as sharing tips for better prototyping. Invision has <a href="http://blog.invisionapp.com/">a fantastic blog</a> with a weekly email that is now my favourite read.</p><blockquote>Stop hopping and start creating. Now is the right time.</blockquote><p>After reading this article, you can start creating the design you are holding back waiting for the “right” tools. Y<em>ou already got the right ones installed in your machine.</em> Now is the right time.</p><p><em>If you have enjoyed this article, it would be great if you press on the button ❤ below. I truly appreciate it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3761bf0b4836" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-notebook/tools-and-the-illusion-of-better-design-3761bf0b4836">Tools and The Illusion of Better Design</a> was originally published in <a href="https://medium.com/design-notebook">Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>