<?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 Natalie Colburn on Medium]]></title>
        <description><![CDATA[Stories by Natalie Colburn on Medium]]></description>
        <link>https://medium.com/@natalie.colburn?source=rss-54ef678bb530------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GbcFzrgifUuRUl5I9x6XbQ.jpeg</url>
            <title>Stories by Natalie Colburn on Medium</title>
            <link>https://medium.com/@natalie.colburn?source=rss-54ef678bb530------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:12:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@natalie.colburn/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[Noted: UX is not an ingredient]]></title>
            <link>https://medium.com/policygenius-stories/noted-ux-is-not-an-ingredient-a24cadf734e5?source=rss-54ef678bb530------2</link>
            <guid isPermaLink="false">https://medium.com/p/a24cadf734e5</guid>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Natalie Colburn]]></dc:creator>
            <pubDate>Fri, 19 Jan 2018 13:06:36 GMT</pubDate>
            <atom:updated>2018-01-26T21:53:45.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQbxn2RBzfHOLTv3VkcZaw.jpeg" /></figure><p>At Policygenius, we’re trying to make sure our product (UX) design team is more heavily involved in our planning process, so I’ve recently been doing research on how to more accurately estimate product (UX) design work.</p><p>In the past, our engineering team has always been looped into the project planning process to both give insights and opinions into an idea, and help estimate how much work it would take to bring that idea to life. Then it was given to the design team so they could e̶s̶t̶i̶m̶a̶t̶e̶ ̶t̶h̶e̶ ̶c̶o̶m̶p̶l̶e̶x̶i̶t̶y̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶i̶r̶ ̶e̶n̶d̶ be told how long they have to design something.</p><p>So, what’s the problem? The product (UX) design work that will go into the project is being treated as an afterthought; an ingredient that can just be tossed in at the end of a recipe. That’s why I want to praise the website <a href="http://uxrecipe.github.io/">UX Recipe</a> which I came across while searching for guidelines on estimating design work.</p><p>Essentially, UX Recipe is a tool for freelancers to use to both help estimate what they should charge their clients as well as outline all the work that goes into designing something. It forces their clients to treat design as the complex process that is is, rather than just an ingredient.</p><p><a href="http://uxrecipe.github.io/">Check out the tool here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a24cadf734e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/noted-ux-is-not-an-ingredient-a24cadf734e5">Noted: UX is not an ingredient</a> was originally published in <a href="https://medium.com/policygenius-stories">Policygenius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Noted: UX for blockchain]]></title>
            <link>https://medium.com/policygenius-stories/noted-ux-for-blockchain-944e614a61e8?source=rss-54ef678bb530------2</link>
            <guid isPermaLink="false">https://medium.com/p/944e614a61e8</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Natalie Colburn]]></dc:creator>
            <pubDate>Fri, 19 Jan 2018 05:43:48 GMT</pubDate>
            <atom:updated>2018-01-19T21:46:15.744Z</atom:updated>
            <content:encoded><![CDATA[<p>By now, everyone and their mother has heard about Bitcoin, Ethereum, and the steep rise in popularity of cryptocurrency. But what less people are talking about is the technology behind it all: blockchain.</p><p>If you’re not familiar, here’s a <a href="https://www.wired.com/video/2017/10/blockchain-explained/">video from Wired</a> that gives a quick explanation in plain English.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*geEKU21RMBbyAwlJ34zwfA.jpeg" /></figure><p>So, what does this have to do with UX design?</p><p>The <a href="https://hbr.org/2017/03/the-blockchain-will-do-to-banks-and-law-firms-what-the-internet-did-to-media">Harvard Business Review</a> stated last year that “the blockchain will do to the financial system what the internet did to media.” The reality is that this technology is growing, but with its own unique pain-points, designing a great user experience will become essential to its adoption.</p><p>But how? For starters, take a look at this <a href="https://blog.prototypr.io/disruptive-ux-of-blockchain-what-you-should-focus-on-647cf5f9de89">insightful article</a> written by the UX Team Lead at <a href="http://www.prototypr.io/">Prototypr</a>. It walks you through the specific challenges and opportunities to anticipate when designing an experience for blockchain technology.</p><p>As a UX designer in the Fintech industry, I’m excited to see how the experience for using blockchain technology will evolve in the coming years. Here’s to the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=944e614a61e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/noted-ux-for-blockchain-944e614a61e8">Noted: UX for blockchain</a> was originally published in <a href="https://medium.com/policygenius-stories">Policygenius</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 Principles: Beyond Table Stakes]]></title>
            <link>https://medium.com/policygenius-stories/product-design-principles-beyond-table-stakes-46e8f2442a84?source=rss-54ef678bb530------2</link>
            <guid isPermaLink="false">https://medium.com/p/46e8f2442a84</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-principles]]></category>
            <dc:creator><![CDATA[Natalie Colburn]]></dc:creator>
            <pubDate>Thu, 31 Aug 2017 21:27:52 GMT</pubDate>
            <atom:updated>2018-01-19T21:46:53.271Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product design principles: beyond table stakes</h3><p>When you go out to eat at a restaurant, what do you expect? At the very least, you probably expect to browse a menu, give someone your order, and subsequently have that selection brought to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VjtUHHGV9a2yvwa46ePQyg.jpeg" /></figure><p>For a restaurant, these are <a href="https://en.wikipedia.org/wiki/Table_stakes">table s̶t̶e̶a̶k̶s̶ stakes</a>. This is the minimum of what is expected and acceptable to<em> be</em> a restaurant. But there’s a big difference between your local fast food joint and that swanky place that changes its menu every season. Why? Their principles.</p><p>On the one hand, take the fast food place. What drives their product?</p><ul><li><strong>Speed &amp; convenience.</strong> It’s not called fast food for nothing…and there’s probably one on every block.</li><li><strong>Consistency</strong>. I expect the Big Mac I order in Los Angeles to taste <em>exactly</em> the same as the one I order in New York.</li></ul><p>Now what about that fancy restaurant?</p><ul><li><strong>Quality.</strong> I don’t care how long it takes or how much it costs, because it’s probably the best meal I’ll eat all year.</li><li><strong>Exclusivity.</strong> It’s impossible to get a reservation because everyone and their mother wants a chance to try that 3-course meal from the world-renowned chef that will be taken off the menu next month.</li></ul><p><strong>So how does this relate to design?</strong></p><p>In J<a href="https://medium.com/the-year-of-the-looking-glass/a-matter-of-principle-4f5e6ad076bb">ulie Zhou’s piece about design principles</a>, she brings clarity to the fact that ubiquitous and generic principles like “design should be simple” or “design should be pleasing to look at” are essentially meaningless to a brand. These are the table stakes of design much as serving food is to a restaurant.</p><blockquote>A good set of design principles, on the other hand, does the following:</blockquote><blockquote>Helps resolve practical and real-world questions around specific design decisions.</blockquote><blockquote>Applies to an entire class of design decisions, both things we can think of today, as well as questions that will pop up in the future.</blockquote><blockquote>Imparts a human-oriented sense of “why?” that is easy for everybody — including non-designers — to understand.</blockquote><blockquote>Has a point of view and a sense of prioritization that a rational person could disagree with.</blockquote><blockquote>Is generally paired with illustrative examples that show how the principle applies to specific decisions.</blockquote><p><a href="https://www.policygenius.com/">Policygenius</a> is about to go through a huge rebrand, so we’ve been revisiting our own principles. In the past, these have been more about what the product aims to achieve and less about how the design makes it happen.</p><p><strong>So how did we choose our design principles?</strong></p><p>First, we acknowledged the table stakes. They’re still the basis for great design, and they remind us that these are NOT our principles.</p><p>Our principles are our design values. They keep the team aligned on what makes a <a href="https://www.policygenius.com/">Policygenius</a> design, and help guide our decisions. Most importantly, <em>they have a perspective</em> — they’re not generic platitudes created to induce head nodding.</p><p>We’re still working out the kinks, but with a growing team and thousands of design decisions to make, our design principles will not only be crucial in ensuring consistency across our rebranded product, but in driving design decisions from here on out.</p><p>And in case you need help remembering…</p><p>A restaurant that serves food? Table stakes</p><p>A restaurant that serves high-quality meats? Steak at your table</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46e8f2442a84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/product-design-principles-beyond-table-stakes-46e8f2442a84">Product Design Principles: Beyond Table Stakes</a> was originally published in <a href="https://medium.com/policygenius-stories">Policygenius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>