<?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 Jon Nguyen on Medium]]></title>
        <description><![CDATA[Stories by Jon Nguyen on Medium]]></description>
        <link>https://medium.com/@athst?source=rss-fc7f23332144------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*neZ6572NZNaZOYQukUOwLQ.jpeg</url>
            <title>Stories by Jon Nguyen on Medium</title>
            <link>https://medium.com/@athst?source=rss-fc7f23332144------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:41:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@athst/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[Book Notes: The Paradox of Choice by Barry Schwartz]]></title>
            <link>https://medium.com/product-work/book-notes-the-paradox-of-choice-by-barry-schwartz-f555b2eb4125?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/f555b2eb4125</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[book-review]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Fri, 25 May 2018 01:03:15 GMT</pubDate>
            <atom:updated>2018-05-25T01:03:15.257Z</atom:updated>
            <content:encoded><![CDATA[<p>The Paradox of Choice is an idea that comes up quite often in product development. Are we giving people too many options? Is this confusing? Are we giving people the right amount of information to make their choice, or is it too much? While it’s a useful concept to have in the back of your mind, this book wasn’t as compelling as I had hoped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaPYlzGxKme_iZxLLbn0jA.png" /></figure><p>On the positive side, the core idea of the book is useful. You shouldn’t just shove more and more options in front of people without a good understanding of how it will affect them. While filling out his thesis, Schwartz also explains a lot of psychological concepts that are useful to know — things like prospect theory, second-order decisions, and adaptation.</p><p>But after getting past the core concepts, I found the book to be somewhat lacking. To go beyond the starting point of “sometimes too much choice is bad,” Schwartz attempts to extend that much further to assert how choice is bad for a number of other reasons, and not always very well supported with data or scientific studies.</p><p>Too often when I was reading the book, it felt like “too much choice” was being used as a hammer to explain all the ills of developed societies.</p><p>Another problem I have with the book is how easy it lends itself to misinterpretation. Because he tries to always say that choice is almost always bad, it’s easy to try and apply that by saying that you should always be decreasing choice for your users. In reality, however, the best thing to do will really depend on the situation. Indeed, I’ve seen in practice how “paradox of choice” will be invoked as some sort of incontrovertible truth to justify a product decision rather than using it as a starting point to discuss if and how it may apply.</p><p>Overall, it’s not as an essential book as I had hoped, but I will take away a basic lesson: Whenever you’re working on products, you should think more seriously about how much responsibility you’re shifting onto the user’s shoulders. While it’s often easier to shift decision making, it’s your job to accept responsibility for a good result.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f555b2eb4125" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/book-notes-the-paradox-of-choice-by-barry-schwartz-f555b2eb4125">Book Notes: The Paradox of Choice by Barry Schwartz</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mental Models for Product Management]]></title>
            <link>https://medium.com/product-work/mental-models-for-product-management-e67e4c1ba54a?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/e67e4c1ba54a</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Thu, 10 May 2018 18:02:15 GMT</pubDate>
            <atom:updated>2018-05-25T01:03:41.884Z</atom:updated>
            <content:encoded><![CDATA[<p>See: <a href="https://www.fs.blog/mental-models/">https://www.fs.blog/mental-models/</a></p><ol><li>Disruption Theory</li><li>Commoditization/De-commoditization</li><li><a href="https://en.wikipedia.org/wiki/Kano_model">Kano Model</a></li><li>Modularity and Integration (Christensen)</li><li>Overshooting</li><li>The Paradox of Choice</li><li>Social Proof</li><li>Threshold Timeline (Chipchase)</li><li>Trust (Chipchase)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e67e4c1ba54a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/mental-models-for-product-management-e67e4c1ba54a">Mental Models for Product Management</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading List: 2018]]></title>
            <link>https://medium.com/jons-blog/reading-list-2018-d243dfef7cf7?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/d243dfef7cf7</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[readinglist]]></category>
            <category><![CDATA[reading]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 16:49:43 GMT</pubDate>
            <atom:updated>2018-10-02T20:55:35.964Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are the books that I’m reading, or have read, in 2018. Last year, I did end up reading more than I have in the past, and I’d like to continue building on that this year. For the 2017 one, see <a href="https://medium.com/jons-blog/reading-list-2017-45c5ca8a15ea">Reading List: 2017</a>.</p><p>You’ll find links for the books for which I’ve typed up some notes or other thoughts.</p><h3>Currently Reading</h3><ul><li><em>A House for Mr. Biswas </em>by V. S. Naipaul</li><li><em>Streetfight: Handbook for an Urban Revolution</em> by Janette Sadik-Khan</li><li><em>Mindset</em> by Carol S. Dweck</li></ul><h3>Finished</h3><ul><li><em>Why I Write</em> by George Orwell</li><li><em>Thinking in Bets</em> by Annie Duke</li><li><em>Of Mice and Men</em> by John Steinbeck</li><li><em>India: A Wounded Civilization</em> by V. S. Naipaul</li><li><em>Keep the Aspidistra Flying</em> by George Orwell</li><li><em>How to Speak, How to Listen</em> by Mortimer J. Adler</li><li><em>On Composition and Improvisation</em> by Larry Fink</li><li><em>When Coffee and Kale Compete</em> by Alan Klement</li><li><em>American Witness</em><strong><em> </em></strong>by R. J. Smith</li><li><em>literally show me a healthy person</em> by Darcie Wilder</li><li><em>Camera Lucida</em> by Roland Barthes</li><li><em>The Prince</em> by Niccolo Machiavelli</li><li><em>Meditations</em> by Marcus Aurelius</li><li><em>On Grand Strategy</em> by John Lewis Gaddis</li><li><em>Bad Blood</em> by John Carreyrou</li><li><em>Talking to Humans</em> by Giff Constable</li><li><em>The Paradox of Choice</em> by Barry Schwartz</li><li><em>The Elements of Style</em> by William Strunk Jr. and E.B. White [reread]</li><li>Jobs-to-be-Done: The Handbook by Chris Spiek and Bob Moesta</li><li><em>Pretentiousness: Why it Matters </em>by Dan Fox</li><li><em>Jobs to Be Don</em>e by Stephen Wunker, Jessica Wattman, David Farber</li><li><em>The Innovator’s Solution</em> by Clayton Christensen and Michael E. Raynor <strong>(recommended)</strong></li><li><em>Christopher Hitchens: The Last Interview</em> by Christopher Hitchens, Stephen Fry</li><li><em>Hidden in Plain Sight </em>by Jan Chipchase</li><li><em>Intercom on Jobs-to-Be-Done</em> by Des Traynor</li><li><em>Meeting Design</em> by Kevin M. Hoffman <strong>(recommended)</strong></li><li><em>Jobs to Be Done: Theory to Practice</em> by Tony M. Ulwick</li><li><em>Do the Work! </em>by Steven Pressfield</li><li><em>A Higher Loyalty</em> by James Comey</li><li><em>In Praise of Slowness</em> by Carl Honoré</li><li><em>Good Strategy, Bad Strategy</em> by Richard Rumelt<strong> (recommended)</strong></li><li><em>An Area of Darkness</em> by V. S. Naipaul</li><li><em>Project Future</em> by Chad Denver Emerson</li><li><em>The People vs. Democracy</em> by Yascha Mounk</li><li><em>Eat Bacon, Don’t Jog</em> by Grant Petersen</li><li><em>Inherit the Wind</em> by Jerome Lawrence and Robert E. Lee</li><li><em>The Checklist Manifesto </em>by Atul Gawande</li><li><em>A Truck Full of Money</em> by Tracy Kidder</li><li><em>India: A Million Mutinies Now</em> by V.S. Naipaul</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d243dfef7cf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jons-blog/reading-list-2018-d243dfef7cf7">Reading List: 2018</a> was originally published in <a href="https://medium.com/jons-blog">Jon’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Notes: The Airbnb Story]]></title>
            <link>https://medium.com/product-work/book-notes-the-airbnb-story-b90d8497f3d5?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/b90d8497f3d5</guid>
            <category><![CDATA[hospitality]]></category>
            <category><![CDATA[airbnb]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 04:09:01 GMT</pubDate>
            <atom:updated>2017-09-11T04:09:01.135Z</atom:updated>
            <content:encoded><![CDATA[<p>To me, the biggest lesson of <em>The Airbnb Story</em> by Leigh Gallagher is the disproportionate amount of leverage that exists at the early stages of a company. Once you have the core insight with value and are able to build a product around it, the rest just sort of plays itself out. Sure, “the rest” isn’t easy by any means, but, at that point, your job is just to not screw it up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pOi6dZ0xO6W7R_fsiAt7zw.png" /></figure><p>Building on that, the second lesson to take from this book is the importance of persistence (or hustle, if you prefer). It is clear from the narrative that the founders worked pretty hard to get the concept off of the ground — they didn’t just stumble into a business.</p><p>Other than that, I found the book to be pretty much as expected — a light overview of the company’s history. I thought that it tended to overrepresent the views of Airbnb, its founders, and its investors a little too strongly, without going very deeply into some of the more interesting issues brought up by the company’s existence. But, overall, it was a decent survey of the company up until its current state.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b90d8497f3d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/book-notes-the-airbnb-story-b90d8497f3d5">Book Notes: The Airbnb Story</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In search of a scientific model of A/B testing]]></title>
            <link>https://medium.com/product-work/in-search-of-a-scientific-model-of-a-b-testing-7a0135c63aaf?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a0135c63aaf</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scientific-method]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 11:47:18 GMT</pubDate>
            <atom:updated>2017-09-08T11:58:56.496Z</atom:updated>
            <content:encoded><![CDATA[<p>I enjoyed the sentiment of this recent Nature article (found on <a href="https://news.ycombinator.com/item?id=15192610">HN</a>):</p><p><a href="https://www.nature.com/articles/s41562-017-0189-z.epdf">Redefine statistical significance</a></p><p>If only we could propose the same kind of rigor in the kind of work we do with A/B testing in product development. However, the moment I read the suggestion, I shook my head at how impossible it would be to suggest such a thing for online experiments. If we did so, so few A/B tests would be considered “successful” that, organizationally, it would be near impossible to justify, not to mention the time it would take to get that kind of certainty relative to the demand for showing results.</p><p>On the other hand, the idea of calling anything under a P-value threshold of 0.005 as “<strong>suggestive</strong>” feels like a great step in promoting a more scientific mindset in a company and reminding people that it is better to think probabilistically than in absolutes. In my everyday work I’m going to start using “suggests” and “suggestive” a lot more in language to see if it makes a difference.</p><p>It’s always been disappointing about how promoters of A/B testing often have a pretense of being scientific, but in practice that rarely is the case. The testing program usually just becomes about scoring hits and being able to show that you made the company extra money.</p><p>But is this really the right way to go about it? If medical experiments were only gauged by the percentage of people who died or didn’t die, got cured or didn’t, we’d be much farther behind in our understanding than we are today. So why does it work that way in product development?</p><p>What if we used A/B testing with the primary aim of better understanding? The change is subtle, but important — instead of just trying to rack up hits, we could instead run experiments to test the underlying models of how people interact with our products. By building up the knowledge we get from that experimentation, we could then design new product changes from a stronger base over time rather than just throwing tests against the wall to see what sticks.</p><p>So, instead of running A/B tests directly to get money, run A/B tests with a scientific mindset to gain understanding. Once you have that, then you can design new things get the money.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a0135c63aaf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/in-search-of-a-scientific-model-of-a-b-testing-7a0135c63aaf">In search of a scientific model of A/B testing</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A small note to readers]]></title>
            <link>https://medium.com/product-work/a-small-note-to-readers-b4d05825d67b?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4d05825d67b</guid>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 07:06:51 GMT</pubDate>
            <atom:updated>2017-09-06T07:06:51.087Z</atom:updated>
            <content:encoded><![CDATA[<p>The handful of writings I had collected so far in a previous publication have been moved into a new one, Product Work. What’s the reason for this change? Well, I forgot to renew the domain name of the previous one, so why the hell not? 🤗</p><p>With this change, however, I hope to be writing with a greater regularity. Let me know what you think!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4d05825d67b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/a-small-note-to-readers-b4d05825d67b">A small note to readers</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading List: 2017]]></title>
            <link>https://medium.com/jons-blog/reading-list-2017-45c5ca8a15ea?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c5ca8a15ea</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[readinglist]]></category>
            <category><![CDATA[reading]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 22:48:05 GMT</pubDate>
            <atom:updated>2018-01-07T16:43:21.335Z</atom:updated>
            <content:encoded><![CDATA[<p>This year, I’m trying to read a lot more.</p><p>Here is the list of books to track what I’ve been reading, inspired by the lists of others such as <a href="https://www.farnamstreetblog.com/reading-2017/">Shane Parrish</a>, <a href="https://www.kennorton.com/books/">Ken Norton</a>, and <a href="https://www.susanjfowler.com/reading-list/">Susan Fowler</a>.</p><p>Last updated: 1/7/2018</p><h3>Currently Reading/Didn’t Finish</h3><ul><li><em>Inspired</em> by Marty Cagan</li><li><em>The Obree Way</em> by Graeme Obree</li><li><em>Deep Thinking</em> by Garry Kasparov</li></ul><h3><strong>2017</strong></h3><ul><li><em>To Kill a Mockingbird</em> by Harper Lee</li><li><em>How to Read a Book</em> by Mortimer Adler and Charles Van Doren</li><li><em>Waypoint Kangaroo</em> by Curtis C. Chen</li><li><em>Growth Hacker Marketing</em> by Ryan Holiday</li><li><em>Spark Joy</em> by Marie Kondo</li><li><em>Ghachar Ghochar</em> by Viven Shanbhag</li><li><em>The Airbnb Story</em> by Leigh Gallagher</li><li><em>Just Ride</em> by Grant Petersen</li><li><em>The Confessions of Young Nero</em> by Margaret George</li><li><em>Tragic Design</em> by Jonathan Shariat and Cynthia Savard Saucier</li><li><em>The Art of Cycling</em> by Robert Hurst</li><li><em>Managing</em> <em>Oneself</em> by Peter F. Drucker</li><li><em>The Apprentice</em> by Jacques Pépin</li><li><em>The First 90 Days</em> by Michael D. Watkins</li><li><em>The Looking Glass War</em> by John le Carré</li><li><a href="http://designingtogetherbook.com/"><em>Designing Together</em></a> by Dan Brown</li><li><em>A Murder of Quality</em> by John le Carré</li><li><em>Decode and Conquer</em> by Lewis C. Lin</li><li><a href="http://www.crackingthepminterview.com/"><em>Cracking the PM Interview</em></a> by Gayle Laakmann McDowell and Jackie Bavaro</li><li><em>Call for the Dead</em> by John le Carré</li><li><em>The Death of Expertise</em> by Tom Nichols</li><li><em>The Mask of Dimitrios</em> by Eric Ambler</li><li><em>Jiro Philosophy</em> by Jiro Ono and Masuhiro Yamamoto</li><li><a href="http://rosenfeldmedia.com/books/why-we-fail/"><em>Why We Fail: Learning from Experience Design Failures</em></a> by Victor Lombardi [<a href="https://medium.com/working-journal/book-notes-why-we-fail-by-victor-lombardi-28c33a4c14c3#.36lat7gvd">my review</a>]</li><li><em>Designing for People</em> by Henry Dreyfuss [<a href="https://medium.com/working-journal/book-notes-designing-for-people-by-henry-dreyfuss-52bba6fc20e2#.kd3rr1jqg">my review</a>]</li><li><em>The Spy Who Came in From the Cold</em> by John le Carré</li><li><em>Alice’s Adventures in Wonderland</em> by Lewis Carroll</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c5ca8a15ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jons-blog/reading-list-2017-45c5ca8a15ea">Reading List: 2017</a> was originally published in <a href="https://medium.com/jons-blog">Jon’s Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Notes: Why We Fail by Victor Lombardi]]></title>
            <link>https://medium.com/product-work/book-notes-why-we-fail-by-victor-lombardi-28c33a4c14c3?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/28c33a4c14c3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 21:24:53 GMT</pubDate>
            <atom:updated>2017-03-24T21:24:53.214Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*dqwBCjOWkdk2KR9xR7qQXA.png" /></figure><p><em>Why We Fail</em> is a book that, yes, aims to analyze failure. However, unlike many of the recent proponents of the Cult of Failure (thankfully it seems to have died off a bit?), this one tries to take a more thoughtful, holistic approach to the issue.</p><p>In service of the investigation of failure, it focuses largely around case studies of failed products. Indeed, I don’t think there are enough good case studies available, written from an objective point of view, for people involved in product development to learn from.</p><p>Often, when we read about failure in books, news articles, or Medium posts, the explanations are too simplistic, and many times too self-serving. Or they’re just wrong. The reality is much more complex. Failure doesn’t happen because of a single problem with the design, the technology, the marketing, or the business — it’s the cumulative effect of all of those things on the customer experience.</p><p>The theme that runs through <em>Why We Fail</em> is that products succeed or fail based on that total experience, not just a single part of it. As Don Norman says in the forward to the book, “Products do not exist in isolation: they need a supportive surrounding environment.”</p><p>As people working on a product, it can be difficult to keep the perspective of an entire experience. We must do our jobs and improve our piece, but we must also realize that ours are only one component of an entire system. How can we work on a specific part, but still serve the whole?</p><p>Case studies are useful in this regard. I like the idea of embracing the complexity of a situation when analyzing past successes and failures, because, as product managers or other members of a team, it’s that complex system of interactions and competing priorities that we really have to contend with in our day-to-day jobs.</p><p>With the huge number of companies and products that fail every year, it’s a shame that they just disappear or fade away quietly when so much could be learned from their experiences. Despite the outward rhetoric by many companies about how they fail fast, how many are actually taking the time to do a serious, in-depth postmortem, honestly deconstructing their failed projects to understand what went wrong? And how many make changes based on that analysis? I suspect that the vast majority just bury the project and move on, so that they’re wide open to making the same mistake the next time.</p><p>In <em>Why We Fail</em>, it was fun to read about all of these products that I hadn’t thought about in a long time. Remember Classmates.com? Plaxo? Google Wave? In popular discussion we tend to look back at these failures rather one-dimensionally, but in the book we learn that there was a lot going on inside these companies that caused them to make the decisions they made.</p><p>The case studies are interesting, and they allow us to think through what we might have done in the same situation. Unfortunately, I found the conclusions of the book a little mixed.</p><p>On one hand, it’s important to deeply analyze failure and structure your organization in a way that it can really learn from the past. That includes postmortems, structuring incentives in a way that failure isn’t swept under the rug, and fostering a culture of openness. On the other hand, I didn’t like the author’s final recommendation to adopt some sort of variation of the Lean Startup/Customer Development loop. Of course, the scientific method is important, but adopting a specific development process seemed to be beside the larger point of the book, and it’s doubtful it would have helped any of the failures previously described. And wasn’t it the unquestioning embrace of those kinds of iterative loops what caused the idea of “fail fast” to fail in the end?</p><p>Overall, the larger point about the importance of designing entire experiences to be successful was well taken. Product development is complex, and unless we take a serious look at our past failures and the failures of others, it is very difficult to know how to do the right thing today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28c33a4c14c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/book-notes-why-we-fail-by-victor-lombardi-28c33a4c14c3">Book Notes: Why We Fail by Victor Lombardi</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Notes: Designing for People by Henry Dreyfuss]]></title>
            <link>https://medium.com/product-work/book-notes-designing-for-people-by-henry-dreyfuss-52bba6fc20e2?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bba6fc20e2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Fri, 17 Feb 2017 08:20:25 GMT</pubDate>
            <atom:updated>2017-02-17T08:20:25.390Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Designing for People</em> is a classic design book that I wish I hadn’t waited so long to read. It was originally published over 60 years ago, but somehow its advice is still completely relevant to any teams who are developing products today. And even though Henry Dreyfuss was specifically talking about industrial design when he wrote it, now it can apply to the design of basically anything, especially digital products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*qSevgUAsSXuvfXlqKP7q3A.png" /><figcaption>Designing for People</figcaption></figure><p>When you’re reading the book, it’s hard to get over how timeless so many of the lessons are. They are too numerous to put here, but many of them are critically important to designing good products. Design with real people in mind. Immerse yourself in the subject matter. Design from the inside out (e.g. with a car). Or, to put it another way, design the product around the humans who will be using it, rather than making something pretty and leaving users as an afterthought.</p><p>In fact, if you internalize the knowledge in this book, it probably negates the vast majority of new, trendy business and design books that come out. Most of those try to front like they’re saying something new, but essentially what they all boil down to is “you need to test this thing with real people.”</p><p>The book itself is quite pleasant to read. It is very accessible, and Dreyfuss’ voice comes through as being friendly but also with a confidence that is informed by vast experience. Hearing about the range of products is also fun, and really impressive. Telephone handsets, ocean liners, tractors, anti-aircraft guns. With the demand for specialization that most people have to deal with today, how many get to work on such a wide array of projects? And are we missing something from that?</p><p>In all, this should probably one of those essential books in a designer or product manager’s library.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bba6fc20e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/book-notes-designing-for-people-by-henry-dreyfuss-52bba6fc20e2">Book Notes: Designing for People by Henry Dreyfuss</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Review: Competing Against Luck]]></title>
            <link>https://medium.com/product-work/review-competing-against-luck-9d122700fc22?source=rss-fc7f23332144------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d122700fc22</guid>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[clay-christensen]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jon Nguyen]]></dc:creator>
            <pubDate>Sat, 07 Jan 2017 06:24:52 GMT</pubDate>
            <atom:updated>2017-09-06T06:51:05.401Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Competing Against Luck</em> (Christensen, Hall, Dillon, and Duncan) is a book that‘s been a long time coming. I initially heard about it from Horace Dediu, who has been talking about Jobs-To-Be-Done (JTBD) theory for years. Until now, the best materials I could find on the theory were Dediu’s <a href="http://5by5.tv/criticalpath/19">podcasts</a> and the <a href="http://hbswk.hbs.edu/item/clay-christensens-milkshake-marketing">dribble</a> of HBR <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">articles</a> that have come out. But there had been nothing comprehensive that describes the entire concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*JB8Kb-iXZbCaopFy9pxmaQ.png" /></figure><p>Is <em>Competing Against Luck</em> that document? From a theory standpoint, yes, but from a practical standpoint, no. The book gives a thorough description of the theoretical framework of JTBD, but is pretty light on practical advice for those of us who might want to put it to actual use.</p><h3>JTBD is awesome</h3><p>Jobs-To-Be-Done is emerging as a superior lens through which to view customers and product development compared to previous approaches like market segmentation and personas. In the past, I always found that viewing users as segments or personas was extremely problematic in practice. Those approaches make very easy to stereotype users and for everyone in the room to project their own beliefs and biases, resulting in a huge, unfocused mess.</p><p>But what if we thought about the <em>job</em> that a person needs a product to help them complete in their life? That’s a concept that, if pursued, lends a lot more focus. From a product perspective, I think targeting the job is a much more useful way to judge new ideas and guide what you should be working on. Think about companies that make really good product — instead of trying to serve all purposes for a specific segment of people, they crush a specific use case that is shared across a range of different types of people.</p><p>In order to figure out what job people are hiring your product to do, it essentially comes down to talking to individual users. To be sure, isn’t that what a lot the other approaches coming out now, such as <a href="http://www.thesprintbook.com/"><em>Sprint</em></a> or the increasing emphasis companies are placing on user research, essentially boil down to? At the end of the day, it’s really about getting out there and <em>talking to real people</em>.</p><p>Unfortunately, other than a list of ideas on how to uncover customer jobs and a transcript of an example user interview, the book doesn’t provide a whole lot of tactical advice on how to find these. It seems this is still an area that will require development. As a starting point, I’d recommend <a href="http://5by5.tv/criticalpath/146">this interview</a> on the Critical Path podcast from a couple years back. Also worth watching was <a href="http://www.mindtheproduct.com/2016/11/building-high-growth-products-using-jobs-done/">Jay Haynes’ talk</a> at the <a href="https://www.meetup.com/ProductTank-SF/">Product Tank SF</a> Meetup, who describes a much more structured approach of finding a job and breaking it down into many different tasks involved in that job.</p><h3>Organizing around the job</h3><p>One of the points that really made an impression on me from the book is the need for the <em>entire organization</em> to align around delivering on a customer job. The processes of the organization need to be carefully formed to ensure that the job is always at the center, which is an extremely difficult thing to to do.</p><p>If that’s the case, can you bring in the JTBD approach to an organization without executive support? I think it might be possible — as a product manager, you could start aligning your team around a job and get some wins on the features that come out of it to build the case. But in the long term, it seems that execs would need to be committed to JTBD to really make the organizational changes to really achieve what the book is talking about.</p><p>It also struck me that a lot of what Christensen talks about here sounds a lot like the discipline of Service Design. Instead of optimizing the specific piece of the product you own, it’s about looking across the entire experience of touch points where a customer interacts with your product to complete their task, and making that better. It’s funny how all these things seem to be converging.</p><p>In summary, I’d recommend <em>Competing Against Luck</em>. It’s a good primer on JTBD theory and will give you a good lens through which to view the world. But when it comes to putting rubber to the road? Well that’s another story…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d122700fc22" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-work/review-competing-against-luck-9d122700fc22">Review: Competing Against Luck</a> was originally published in <a href="https://medium.com/product-work">Product Work</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>