<?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 Nick Kroetz on Medium]]></title>
        <description><![CDATA[Stories by Nick Kroetz on Medium]]></description>
        <link>https://medium.com/@nicholaskro?source=rss-37e85e945c80------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*0Ezn_0lvk_GziB5JqzRoPg.png</url>
            <title>Stories by Nick Kroetz on Medium</title>
            <link>https://medium.com/@nicholaskro?source=rss-37e85e945c80------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:48:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicholaskro/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[Designing a future for real estate investing]]></title>
            <link>https://medium.com/@nicholaskro/designing-a-future-for-real-estate-investing-6cbf51100a7f?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cbf51100a7f</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Thu, 30 Sep 2021 18:38:10 GMT</pubDate>
            <atom:updated>2021-09-30T19:34:35.860Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KS8fntUebICoT3nM1WWr5w.png" /></figure><p>I started at <a href="https://fundrise.com/">Fundrise</a> a couple weeks ago now, and have only just begun settling in. There’s still a lot to learn about how they’ve cut through all the complexity of real estate investing to create an offering that feels as familiar as any other modern fintech platform. I just joined as the company’s first ever Director of Product Design, with the task of amplifying the talented product designers that are already here, while figuring out how this team could grow with the company.</p><p>I’m writing to chronicle some of my early thoughts, because fresh eyes are only fresh for so long, and also document some of the reasons why I’m excited about this team.</p><h3><strong>A unique offering</strong></h3><p>Investing in real estate has something that has long been accessible to the super-wealthy, through hedge funds or other big institutional investors (accredited investors only), and has historically been an attractive way to minimize risk while increasing income and stability when compared to investing with only stocks [<a href="https://fundrise.com/why-private-real-estate">source</a>]. The challenge is being able to put money into the market on a scale that is big enough to minimize risk, and minimize the operational costs that come with purchasing and managing properties, which is huge. That’s where Fundrise comes in. They’ve found ways to be more efficient with unique tax processes and home-grown technology. They acquire and manage properties, and allow anyone to ‘buy in.’ So everyday folks like me can start diversifying into real estate at a much lower cost without having to be super-wealthy already.</p><blockquote><strong>Can an App Renovate a Neighborhood?</strong> Fundrise, an online platform for individuals to collectively invest in real estate projects, is seeking to transform an entire neighborhood in Los Angeles.</blockquote><blockquote>-<a href="https://www.bloomberg.com/news/articles/2021-07-08/fundrise-takes-on-a-neighborhood-renovation">Bloomberg</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gXSMnm8plM8jSJSh.jpg" /><figcaption>West Jefferson Boulevard, Los Angeles</figcaption></figure><p>So why does this matter to me? I’ve seen friends, colleagues, and family earn the ability to improve their quality of life by making smart choices and building equity with their home. Folks in my parents’ generation often saw home-ownership as an important way to build their wealth, but it has felt out of reach for me. As a poster-child millennial, I chose the best (and most expensive) college I could get into, and have prioritized career growth since then, which had me living in the<a href="https://gothamist.com/news/nyc-surpasses-san-francisco-most-expensive-rental-market-country-report"> nation’s most expensive rental market</a>. Now with my priorities shifting toward ownership,<a href="https://www.businessinsider.com/housing-market-forecast-millennials-buying-homes-crisis-2021-4"> so is everyone else my age</a>. Being able to help build this product that allows anyone to invest in real estate regardless of their ability to buy property satisfies a personal desire I share with our investors to have a choice in how we build wealth to support our financial goals.</p><h3>Brittany Meiling on Twitter: &quot;You guys ever think about how millennials graduated college into an epic recession, scraped and clawed our way into finally having a downpayment by age 30ish only to enter a housing market that&#39;s lost its gd mind? @PhillipMolnar @jbruin https://t.co/EV8U2g1eu8 / Twitter&quot;</h3><p>You guys ever think about how millennials graduated college into an epic recession, scraped and clawed our way into finally having a downpayment by age 30ish only to enter a housing market that&#39;s lost its gd mind? @PhillipMolnar @jbruin https://t.co/EV8U2g1eu8</p><h3><strong>Customer-first, and customer-owned</strong></h3><p>Fundrise has come a long way since it was founded in 2012, and has grown to over $1.7 billion in assets under management (AUM) for 171,000+ investors. One thing that was especially interesting to me, was how they’ve chosen to take investments not just for the real estate funds themselves but also for the growth of the company. Our customers have the opportunity to become fellow shareholders of the company, in what we call a ‘little- i iPO’. This helps us minimize our dependency on outside capital and helps keep our incentives aligned with our customers. For someone who’s worked at startups that were solely dependent on venture capital, both at early and later stages, I’ve seen firsthand how such complete dependence can perpetuate unrealistic demands for growth at any cost, and be bad for employees in the long-run. Instead, Fundrise is held accountable to fast, yet <em>responsible</em> growth by our customers and employees, which is something I’m very excited by.</p><h3><strong>A Bias for action</strong></h3><p>The people I’ve met here are also a big reason why I made the jump to Fundrise. The product org is comparatively new when you look at the history of the company, and many of the product managers and designers have been on board less than 2 years. Before that, company leadership played lots of dual roles. They recognize we need to really double down on working smarter, not harder, but those early days of grinding it out have created an environment that celebrates a bias for action. It feels like a company of ‘do-ers.’</p><p>With the newness of these teams comes opportunities to shape how we work. So far, folks are not overly concerned with rigid explanations of “this is how we do things here.” Instead, I’m hearing a lot more “how should we do it?” My first few weeks here have been full of brain-stretching conversations about how we can change processes to get work done smarter and more efficiently. It’s not the wild west — the product and design leadership across the board is extremely experienced and qualified — but it does certainly feel more green-field and opportunistic to me.</p><h3><strong>All-in on Remote Work</strong></h3><p>As someone who enjoys becoming connected to company culture, committing to remote work has been scary for me. I live in Brooklyn, but the HQ is in Washington DC. So far the design team is made up of folks that live in Pennsylvania, Florida, Chicago, Atlanta, New York, and of course the DC area. Currently, the entire team is remote, and we’ll continue to prioritize remote-friendly processes and norms. The office will be there when we’re ready, and we’re encouraged to set our own expectations and preferences for when and how often we come into the office physically. The result is that work is remote by default, instead of remote folks feeling left out. To combat my own needs of being around people during the day, I’ve signed up for a dedicated desk at a co-working space that’s a 10 minute walk from my home, and so far my pandemic-era productivity has never been higher.</p><h3><strong>Come build the future of real estate investing</strong></h3><p>I’ve been a designer, product manager, ux researcher, etc. for almost 10 years, and have been working on fintech products for the past ~6 years. I joined from Betterment (who just announced their 1.3bn valuation and <a href="https://www.bloomberg.com/news/articles/2021-09-29/betterment-valuation-rises-to-1-3-billion-on-new-funding-round">unicorn status</a> from their latest round), before that an early-stage business and financial management tool for educators called Clark that was acquired, and was also one of the early designers at <a href="https://www.policygenius.com/">Policygenius</a>. I’ve fallen in love with solving these kinds of complicated problems, making financial tools easier to access and understand, and creating experiences that have the potential to change the established, antiquated systems that only benefit certain people, and I’m thrilled that I get to now learn about real estate investing in the pursuit of my own long-term financial success.</p><p>Fundrise is <a href="https://fundrise.com/education/opening-the-doors">opening the doors</a> with a new, lower minimum investment amount, and we need talented product designers to help us figure out how to serve a bigger audience of investors. We’re hiring designers this year, next year, and probably the year after that too. We’re going to be making some big investments in our team across product, design, and engineering, and we need more thinkers and do-ers who are excited by these kinds of challenges. If that sounds like you, let’s talk!</p><p>Hiring: <a href="https://jobs.lever.co/fundrise/1de618b5-1186-4933-98c9-6e40f5b0ffa8">Growth Product Designer</a></p><ul><li><a href="https://fundrise.com/jobs">Careers</a></li><li><a href="https://fundrise.com/the-distance">The Distance Newsletter - a Fundrise Publication</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cbf51100a7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we found Clark’s design principles to empower educators.]]></title>
            <link>https://medium.com/@nicholaskro/how-we-found-clarks-design-principles-to-empower-educators-6aece72edcc0?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aece72edcc0</guid>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[tutoring]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Tue, 12 Nov 2019 20:22:42 GMT</pubDate>
            <atom:updated>2019-11-12T21:13:02.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-rNzHU8bUzDaPmikGHCkg.png" /></figure><p><a href="http://hiclark.com/">Clark</a> is the first ever future of work platform built specifically for tutors with the mission to empower educators so they can run their own businesses more effectively. So how did we get here?</p><h3>Starting in the hole</h3><p>The Clark platform was ~2 weeks into a beta release when I joined. We were in a mad dash to finish off functionality, and deliver on the promises we made to our first customers. The product showed amazing potential, but was still a bit frustrating to use. For example, a tutor could create a student record in Clark, but not edit it or delete it — those actions still had to be done manually by an engineer. As a result, our engineers were buried with simple support tickets.</p><p>Additionally, most incumbent softwares in the space had at least an 8 year lead on us, which meant it would take time before we would stack up on a feature-by-feature comparison. Our opportunity though, is that these softwares are bloated, poorly designed, and difficult to use. Tutors hated using them.</p><p>To win new customers away from competitors, we had a few options. We could try to offer more features, make a few things really good, or build something complimentary to existing products. We were quickly falling into a feature race trap, and couldn’t develop fast enough to close that 8 year gap. We collectively realized we needed to switch our focus from the “build everything” trap to a “build only few things better than anyone” strategy, and we needed principles to guide us.</p><h3>How do you find a product vision?</h3><p>Step 1: Talk to your customers (and let them do the talking).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F711846178%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fnickkroetz%2Ftutoring-clips&amp;image=https%3A%2F%2Fsoundcloud.com%2Fimages%2Ffb_placeholder.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/776d0aa27860f03d937c53c4d0d4f411/href">https://medium.com/media/776d0aa27860f03d937c53c4d0d4f411/href</a></iframe><p>From spending a lot of time with our tutors, we knew <strong>they value flexibility</strong> and want to do things their own way. They also don’t tend to think of themselves as business people. Rather, they’re mission-driven people who believe they can make a bigger impact on a student’s future by connecting with families, and taking the individual needs of the student into account. <strong>They’re relationship builders</strong>.</p><p>As for determining our role in those relationships, we still had some existential questions to answer before we could establish a compelling vision. How much flexibility should our product offer? Should we force them adopt better practices, or let them operate any way they please? How visible should we be to the paying families? How do we make tutors more efficient, without detracting from the quality of their relationships?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnQOYL4V8e2FOCQ9G8IMzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7AGDAHjtPmjvt7dJXi8e2Q.png" /></figure><p>To answer these questions as a team, I facilitated a structured workshop where everyone could contribute and rally around new design principles. We wanted principles that 1.) express a clear perspective and are possible to disagree with (ie, something like ‘easy to use’ doesn’t cut it, because thats a given), 2.) are things we will always strive for, and not necessarily qualitatively achievable, and 3.) can serve as guiding principles for product development &amp; roadmapping decisions.</p><p>In this workshop, we talked a lot about our customers and reflected on what we were uniquely able to do for them. <a href="https://medium.com/@mikeybrand/creating-design-principles-301e2531a099">We created dozens of dichotomies</a> to explain those values, and then broke them down to a set we were most excited about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OiN9EWhvgtAWU0dGoVT7nA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iH0EPwNnV23TWjm_V809bA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODAq_PuomnDQZkCzXaXfTQ.jpeg" /><figcaption>Brainstorm over breakfast: discussing the principles that would shape our product vision at a company offsite.</figcaption></figure><h4>The new principles we aligned on are:</h4><ul><li><strong>Less Stressing, more teaching</strong> — prioritize automation for business management. We want tutors to spend <em>less</em> time in the product.</li><li><strong>Guiding not rigid </strong>— There are different ways to use Clark, but we’ll prioritize features that help tutors run their business more effectively.</li><li><strong>Sticky with parents</strong> — Anything we build must directly benefit the end customer, the parents</li><li><strong>Gives you the credit</strong> — Clark wants the educators be the heroes, and doesn’t take the credit for a seamless and professional digital experience. We’re not airbnb — we can be invisible to the end payer.</li><li><strong>No comparisons</strong> — Clark offers you something no other product can because we understand your business better than anyone else.</li></ul><p>These principles would later echo through later design reviews, marketing materials, roadmapping discussions, and investor decks. They became a way of thinking about ourselves, and allowed us to carry a perspective into our decision making and problem solving.</p><p>For more on creating principles, check out some of the resources that helped me at the bottom of this article.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F328540431%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F328540431&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F773090555_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/c119f21e4c2ec376dbf5dcfd163db345/href">https://medium.com/media/c119f21e4c2ec376dbf5dcfd163db345/href</a></iframe><h3><strong>The quest to build the best invoicing tool.</strong></h3><p>Period. Not just the best invoicing tool for tutoring businesses.</p><p>With these new principles in mind, we set out get out of the feature-race trap, and build something no one else had done yet. So we focused on the most difficult, and stressful part of a tutor’s relationship with a family — asking for money.</p><p>Tutors, and tutoring small businesses have a million different ways of operating. Most of these businesses were not built for scale or by digitally savvy individuals, and many are still cash businesses. As a result, they’re burdened by complicated payment policies and administrative overhead. Many of them operate their business out of google sheets, or even physical binders, and don’t have the best record-keeping practices. As a result, processing all the invoices at the end of the month is very stressful, and takes them several days. Often times, sessions would go unpaid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e69VAkMslPL4KqEtd8RwGA@2x.png" /></figure><p>By creating a ‘set it and forget it’ invoicing system that uses a pre-paid session billing and autopay, we guide administrators to save time and reduce the number of sessions that go unbilled. They can easily ask for payment up front, instead of spending their time chasing down parents to write checks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xybda2p5PweetVeRf5E1tg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lQq4tWXnX930wBQY4JxKRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sxFEXo-MQ6tnDXM8b0O7vw.png" /></figure><h3>Fully integrated with session scheduling</h3><p>We conducted a 12-week discovery, design, and prioritization phase around scheduling while we were building out the invoicing functionality. We conducted ~25 interviews and prototype tests with tutoring small business owners, and learned (among other things) that the tutor’s calendar is often the best source of truth for knowing when and how long they worked with a student. We realized a good invoicing tool for tutors could not exist without integrated scheduling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZ6YpJPOqMyfDxLS_S1Ysg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81unzT2haWzOt1CgKPC-mQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hzuPgqEwPK81jf45eo4-JA.jpeg" /><figcaption>In earlier stages of research, paper prototypes helped us get more conceptual feedback from tutors. User research is a team-wide responsibility, so we synthesized our insights as a team too.</figcaption></figure><p>Tutors and parents need more flexibility with their scheduling tools. The job of scheduling many sessions per week is a complex workflow that never ends and is always changing. Tutor’s and parent’s availability isn’t always balanced, and sometimes tutors need to move things around in order to bring on a new student. This flexibility is only possible when the administrator has an accurate picture of both parties availability. Accuracy for that availability comes from clear and timely communication between everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaa-w9u0ewix8tZA7naQXg@2x.png" /></figure><p>We ended up designing and building a scheduling tool that would integrate fully with the on-platform payment system, so tutors and students can keep on top of their sessions, and transact in a timely manner. Tutors could designate who receives the automatic sessions reminders, and how many hours before the session they want it sent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CL210a804K7TG-741pybyg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hygWFBdI2RwulBV3v8VlPg@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soowdBtmg3DDKTP8GqrPow@2x.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bhtHuKwNt3KBvb-ahU0zg.png" /><figcaption>Instead of building a stand-alone calendar tool, we layered a ‘past and future’ concept (marked in blue) on to our existing experience.</figcaption></figure><h3>Outcomes</h3><ul><li>Ease of use cited as our #1 reason for switching customers</li><li>Net retention over 100%</li><li>Nice reviews, like these:</li></ul><blockquote><em>“What really sets Clark apart is their commitment to understanding our business, responding to our feedback, and continuously refining their product.”</em></blockquote><p><em>-Sarah Gonzales, Tungsten Prep, Washington D.C. Area</em></p><blockquote>“It used to take me up tot two days to figure out what everyone had done, how much to pay them. Now, with Clark, I can do all of that in a matter of an hour.</blockquote><p><em>-Fred Tabeek, the FRED center, Greater Boston Area</em></p><p>Update: Clark has been acquired by <a href="https://www.noodle.com/home">Noodle</a>: a network of companies solving marketplace problems in the education. Clark will continue on as an independent brand, providing best-in-class business management software for tutoring small businesses.</p><h4>Helpful resources for developing your own design principles:</h4><ul><li><a href="https://principles.design/">Design Principles</a></li><li><a href="https://articles.uie.com/creating-design-principles/">Creating Great Design Principles: 6 Counter-intuitive Tests</a></li><li><a href="https://medium.com/@mikeybrand/creating-design-principles-301e2531a099">Creating Design Principles</a></li><li><a href="https://medium.com/salesforce-ux/defining-principles-to-drive-design-decisions-b647b68fb057">Defining Principles to Drive Design Decisions</a></li><li><a href="https://blog.prototypr.io/designing-the-mendeley-experience-principles-a0059bcf3e52">Designing the Mendeley Experience Principles</a></li><li><a href="https://medium.com/the-year-of-the-looking-glass/a-matter-of-principle-4f5e6ad076bb">A Matter of Principle</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aece72edcc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 things you can do to win the heart of your user researcher]]></title>
            <link>https://medium.com/policygenius-stories/4-things-you-can-do-to-win-the-heart-of-your-user-researcher-d5adcc08a132?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5adcc08a132</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Fri, 16 Mar 2018 14:08:07 GMT</pubDate>
            <atom:updated>2018-03-16T14:12:58.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Dg4YjN0Tugc11bHCy-hDA.jpeg" /></figure><p>So you were sent this post, which hopefully means you’re going to be joining some user research sessions soon! How exciting! Either that, or you just love your user researcher and are eager make their lives a little easier. My goal with this post is to encourage all digital product people to gain direct access to their users, and demystify some of what goes into conducting a user research session for those that might not have experience conducting them.</p><p><strong>Why this is important:</strong> In horse race betting, tips would circulate on which horse is in the best form. The best and most trusted tips would come from those who are in the inner circle — the jockeys, trainers, etc. — i.e., those that have had direct contact with the horse. Hence <a href="https://www.phrases.org.uk/meanings/straight-from-the-horses-mouth.html">the idiom</a> “From the horses mouth,” which we know means “reliable information from the highest authority.” For those of you who make products, you know that we bet on ideas. Talking to directly to users is one way we can gain confidence for which ideas will or will not win.</p><p>I’m a big believer that user research is for everyone, and all roles benefit from getting product feedback straight from the horse’s mouth. A true team-wide effort. That said, there is a right way and a wrong way to do user research. If your team’s designated researcher is protective of letting just anyone join the sessions, just know they might have their reasons — such as overwhelming the participant with a 5 on 1 interrogation situation. But they should always want other perspectives on what’s happening in the room. Try to get a <a href="https://medium.com/@AukeMolendijk/create-your-own-professional-usability-lab-16987ac0bb2">one way live share</a> going to another room so you can listen remotely if that’s the case.</p><p>If you ask to join a session, or are requested to, here’s a few tips to make sure everyone gets the most out of that session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeaOZwSxIi1fLfuiahLHLw.png" /><figcaption>Theres a lot out there on this topic, but most of it is written for the researcher. More often than not, observers are designers, product managers, and stakeholders.</figcaption></figure><h3><strong>1. Take good notes.</strong></h3><p>Are you an observer or a note taker? In the room, or out of the room? Not everyone needs to be a note taker — just one person. In fact, it will work better if only one person takes notes. (Think about 10 cursors on one google doc all firing away at the same time… nope. Or worse, 10 different documents with more or less the same thing and having to merge them into one. Double nope.) Your job as the note taker is just that — take notes. If your job is to be an observer, just listen and jot things down that stand out.</p><p><strong>Why: </strong>omg, it saves <em>so</em> much time. Transcribing from a recording is tedious. Ask any researcher — it’s the worst part of the job. Plus we have to sit and listen to our own voices later, which also sucks.</p><p><strong>How to do it:</strong> Ask the moderator how they want it done. Hopefully, they have some kind of expectation for you, like where to to take notes, or in what format; do they want it chronological or topical, etc. If not, it’s best to try to get everything down as close to verbatim as possible and from the perspective of the participant (for easy quote-pulling later), and with as little personal bias as possible. I find it’s way easier to do this chronological, instead of jumping around the page. Try to get the questions down too — sometimes the context of what was asked is just as important as the response.</p><p>The reason why we take notes on the sessions is to analyze the patterns later, therefore you shouldn’t assume you know what the patterns are in the session. If you’re making decisions about what is and is not important, you might miss jotting something down that ended up being the key to something you weren’t necessarily thinking about.</p><p>I’ve heard (and experienced myself) a hundred times from startup founders, designers, and user researchers who said 20 sessions in they suddenly had a new question or noticed a new pattern, and had to go back through every session to see if it came up elsewhere. If your notes are incomplete, the outcomes are very costly: you can either listen back to every single one, do more interviews to prove the hypothesis, or abandon the search.</p><h3><strong>2. Let the moderator moderate.</strong></h3><p>Sitting in on a session doesn’t mean you get to interject whenever you want. This can throw the participant off, or even make them feel interrogated.</p><p><strong>How to do it:</strong> If you’re in the room and visible to the participant, it’s best to politely introduce yourself, and tell them you’re just there to take notes so they don’t feel like they have to give their attention to more than one person. For interjections, it’s best to wait until the moderator asks you if you have any other questions to add. (Note, If you’re the researcher here, it is best practice to ask your note taker in the room if they have any questions to add, and you’ll likely benefit from doing so. See number 3).</p><h3><strong>3. Request follow-up questions (discreetly)</strong></h3><p>Not out loud, obviously because of reason number 2, but if you have a way of asking the moderator discreetly, do it!</p><p><strong>Here’s why:</strong> Moderating isn’t easy. You’re battling your biases and combating the normal rules of conversation that are otherwise second nature; you’re carefully trying to make sure all the questions that need to get asked are asked in the allotted time; you’re actively trying to signal that you’re listening (which, spoiler alert, means you do have to actively listen); you’re queueing up the next question in your head; and all the while you’re processing and realizing patterns from past sessions. Anyone who’s had experience running user interviews will tell you it’s exhausting. We hit the moderation mode button, and go. Sometimes we miss things! Sometimes we don’t ask that one follow-up we should have, and don’t realize it until we listen to the recording later. Nothing sucks harder than a missed opportunity to uncover the thing that cracks the case wide open, and the moderator will likely appreciate the efforts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*vAWNGgL2ELtMWvmqRjDS5A.gif" /><figcaption>Me after moderating a research session</figcaption></figure><p><strong>How to do it:</strong> I’ve found it’s really helpful to have a chat window open, and receive questions there. A simple “Ask why they said x” is great. Or if the session is remote, signal non-verbally with a shruggy shoulder and mouth the word ‘WHY?’ to prompt the follow-up question. Make sure the moderator is comfortable with this first, but they’ll likely appreciate it. Also, don’t maniacally pound rapid-fire questions in all caps at the moderator mid session, which I actually had a former co-worker do. It’s incredibly distracting.</p><h3><strong>4. Be a good collaborator</strong></h3><p>If you’re joining a session, listen! Multi-tasking and cherry picking the conversation for information that stands out to you will only confirm your own biases, and skew the results. Stick around for the debrief, and share what you heard, and tell the team what your highlights were. Hearing from all perspectives is super valuable for mitigating any one person’s bias and improving the quality of the research. Lastly, spend 3 minutes to tidy up your notes, and share them with the team. Taking the extra couple minutes to clean it up, and making sure to tie up every sentence so that expresses a complete thought goes a long way toward drawing out those insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*fdEc0iwGUSa5YDHmKkIInA.gif" /><figcaption>Team work makes the dream work.</figcaption></figure><p>—</p><p>I realize this was written to observers and note takers, but all this advice goes to researchers too. It’s important to keep the door to this research open and accessible, so extend the invite. Safeguarding your insider tips doesn’t do anyone any favors, and you’d be surprised by who actually does want to join. In the end, giving your teammates access to hear it for themselves is only going to improve their trust in the ‘insider tips’ you bring back from users.</p><p>As the user research moderator, it’s your job to level set on what’s expected from observers in this process. Too many times I’ve forgotten to do that, or just assumed people would ‘follow the rules’ listed above and then had to double back to re-set expectations. It makes research slower and harder, but we all know the first step to recovery is admitting it was all your fault. Kidding, but not really…I’m guilty of it all the time.</p><p>To the researchers out there, feel free to send this out to your observers and note takers before your session to get all that level-setting out of the way early.</p><p>Am I missing anything? What have your research collaborators done that have helped you?</p><p>Header photo by <a href="https://unsplash.com/@noahsilliman">Noah Silliman</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5adcc08a132" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/4-things-you-can-do-to-win-the-heart-of-your-user-researcher-d5adcc08a132">4 things you can do to win the heart of your user researcher</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[One thing I’ve learned from my teachers that has helped me be a better designer]]></title>
            <link>https://medium.com/policygenius-stories/one-thing-ive-learned-from-my-teachers-that-has-helped-me-be-a-better-designer-77c273f074?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/77c273f074</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[insurtech]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Fri, 19 Jan 2018 15:29:13 GMT</pubDate>
            <atom:updated>2018-01-22T04:03:42.428Z</atom:updated>
            <content:encoded><![CDATA[<p>Humans are constantly learning, and constantly seeking out patterns to make sense of the world. It’s part of what has kept humans alive — you don’t need to put your hand in the fire to know it’s going to burn, because you’ve learned somewhere in your past that it hurts, and you need to avoid it. That’s an easy choice. But what do you do when you are faced with making decisions about things you don’t know anything about, and have never had to consider before?</p><p>At <a href="https://www.policygenius.com/">Policygenius</a>, we not only have to teach our users how to use our products, we also have to teach them how to make the right financial protection decisions, so they can feel good about it. Making financial decisions about stuff you don’t know anything about can be really scary, and let’s be honest — most people don’t know much about insurance. What’s more, the behemoth insurance industry hasn’t worked to make it any easier. How do I know I’m getting the right coverage for me?</p><p>For example, this is AIG’s life insurance calculator. Which is supposed to answer that question, and tell me how much I need to be covered for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*v8OW6ZhumN1tjRuEAwHixg.gif" /><figcaption>I mean, what am I even looking at here? I didn’t go to school for this…</figcaption></figure><p>If that was the only resource I had to answer this question, I’d give up pretty quick. There’s way too much to learn here.</p><p>Understanding how humans experience new information, learn, and make decisions has been both the most challenging, and interesting part of being a product designer for me. Ultimately, other people will have to learn how to use our products to get the thing done, and it’s our job to teach them.</p><p>Luckily, we’re not the first to traverse this territory. We’ve all experienced experts at helping humans learn—our teachers. Teachers are experts at helping us take in new information, and there are a few learning concepts we can use to help our users do the same.</p><h3>A<em>ccommodation</em> and <em>assimilation.</em></h3><p>Accommodation happens when an individual receives new information, and applies it to an existing framework. Accommodation is when you confirm what you know and expected to be true. This is the classic pattern recognition that humans do all the time that reinforces our opinions and makes them stronger. The more data you have to support an opinion, the harder it is to change that opinion. For example, our users expect life insurance to be complicated, confusing, full of fine print, and frustrating to deal with. Unfortunately a lot of the big insurance dinosaurs haven’t prioritized implementing good designs that make these concepts easier. So one visit to their website would likely confirm that expectation, and reinforce how confusing insurance probably is. “I better just leave it to an expert and call.” That’s how they get ya. In reality though, it doesn’t have to be that complicated, and it is something consumers can learn on their own.</p><p>Therein lies the challenge: Simplicity in design is never really simple to make, is it?</p><p>Assimilation is a learning process of taking new information that might not fit into your existing worldview and <em>changing</em> the framework to fit that new information. This is how we learn new things. As a product designer, my goal is to help shoppers learn that buying insurance doesn’t have to be hard, and give them the information they need to make an informed decision. The process of assimilation is a lot tougher to facilitate because it doesn’t line up with what they were expecting. The idea that life insurance can be straightforward and simple is a new idea.</p><p>This is because our brains naturally reject information that doesn’t support our existing cognitive frameworks. One recent public example of this phenomenon is the <a href="https://web.stanford.edu/~gentzkow/research/fakenews.pdf">fake news echo chambers on social media</a>, where tons of people were more likely to remember false headlines that supported their ideologies, than actual truth. Our brains naturally want to ignore information that might prove ourselves wrong.</p><p>In a much smaller scale, when we tell users “hey, insurance can be easy, you can do this on your own.” they’re likely to respond with “Wait, what’s the catch? There must be something I’m missing. I’m not qualified to do this on my own” and possibly even abandon the experience.</p><p>But there is a way around this natural cognitive blocker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*jVXC31dvEAml-jP0pcKZ4g.gif" /></figure><p>One way teachers facilitate assimilation in the classroom is by <em>activating prior knowledge</em>. It basically means that when the teacher starts with a concept the student already knows to be true, it literally turns on areas in the brain where that information is stored. From there, the teacher can introduce new information on top, and <em>scaffold</em> up to new information that is more complex. This anchors that new information into the brain, helping it sink in faster, and be retained longer.</p><p>To help our customers understand life insurance, we take cues from other industries that have made hard things easier for consumers. Most of our customers have never bought life insurance before, but they have done things like buying a flight online, doing their taxes with turbotax, and comparison shopping on amazon.</p><p>There are three things we do to help users get through this new territory.</p><ol><li>Reference experiences people already know and emulate them</li><li>Break these new insurance concepts like ‘coverage’ and ‘term’ down into language everyone can understand with analogies to familiar things.</li><li>Shape our user flows to gradually layer on new information, and scaffold from simple to complex.</li></ol><p>If we can do that right, this new information doesn’t seem so foreign and scary after all, and we get to help people feel good about their decisions.</p><p>If you’re interested in learning more about these concepts, Khan Academy has a couple of quick videos that explain these cognitive theories in a way that doesn’t sound scary or complicated at all. <a href="https://www.khanacademy.org/test-prep/mcat/processing-the-environment/cognition/v/schemas-assimilation-and-accommodation-2">Check em out!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77c273f074" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/one-thing-ive-learned-from-my-teachers-that-has-helped-me-be-a-better-designer-77c273f074">One thing I’ve learned from my teachers that has helped me be a better designer</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[You’ll never guess what they said after I discovered this one thing about responsive grids…]]></title>
            <link>https://medium.com/policygenius-stories/youll-never-guess-what-they-said-after-i-discovered-this-one-thing-about-responsive-grids-f58cdb0ad7cf?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/f58cdb0ad7cf</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[grid]]></category>
            <category><![CDATA[responsive-design]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Thu, 14 Dec 2017 00:53:11 GMT</pubDate>
            <atom:updated>2017-12-19T15:41:40.297Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ViiQRZxcfowaVDqY-jgsLA.gif" /><figcaption>Step 1. Add more babies.</figcaption></figure><p>Okay, grids are probably boring to a lot of people. There’s no magic trick, no ‘one thing’ I discovered that no one else has, but I did figure some things out that I think might be helpful for anyone who’s designing on a grid for web. It’s just math, but the real magic is delivering fluid, accessible designs that look good for everyone (or… most everyone).</p><p>So <a href="https://www.policygenius.com/">Policygenius</a> just rolled out a big rebrand. After <strong>months</strong> of branding work, <strong>dozens</strong> of sketch files, <strong>hundreds</strong> of artboards, and <strong>thousands</strong> of engineering tickets, we launched a full rebrand of Policygenius.com to the world this week, along with a substantial ‘out of home’ campaign (Look for us on buses, trains, and billboards in NYC, SF, Chicago, and LA!).</p><p>We literally redesigned every single page, and touched every dark corner of legacy code. Luckily, we have a crack team of designers, engineers, and PMs who made it all happen. The toughest thing about this rebrand, was staying organized — which means everyone needed to get on the same page very quickly, and use the same components.</p><h3>One grid to rule them all</h3><p>As we were working out those first designs, our use of the grid was one of the first things we had to define to ensure every designer was working with consistent layouts. It seemed as though our old system could use some dusting off- an initial audit of the existing website turned up tons of layouts, with different grid rules. This was our chance to fix it all, so it had to be done right.</p><p>There are a lot of <a href="https://medium.freecodecamp.org/the-100-correct-way-to-do-css-breakpoints-88d6a5ba1862">opinions</a> out there for where your breakpoints should be, and we know that <a href="https://techcrunch.com/2012/04/11/move-over-1024x768-the-most-popular-screen-resolution-on-the-web-is-now-1366x768/&#39;">screens are getting bigger</a>, and <a href="https://techcrunch.com/2016/11/01/mobile-internet-use-passes-desktop-for-the-first-time-study-finds/">mobile traffic is increasing</a>. It seems like the <a href="https://responsivedesign.is/strategy/page-layout/defining-breakpoints/">general theme</a> coming out of the industry is ‘don’t use screen sizes to dictate your breakpoints, because screen sizes are going to always be changing.’ A quick scan through <a href="https://mydevice.io/devices/">this table</a> will prove how true that is…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wD_2kq6-61_D_RRoi8JZgA.gif" /></figure><p>So whats the right answer? Google probably knows right? They’ve documented how material works responsively, and provided optimal breakpoints: 480, 600, 840, 960, 1280, 1440, and 1600. Great! Except… if you resize <a href="https://material.io/guidelines/layout/responsive-ui.html#responsive-ui-breakpoints">this page</a> where they define those rules, you’ll notice they’re not even following their own rules, with their designs breaking at 375, 800, 1240, and 1480… curious. Everyone seems to have different ‘best practices.’</p><p>Ultimately, I realized that there is no right answer; however, the more breakpoints you have, the more control you have as a designer to keep things looking good (like how Google suggests 7 breakpoints). It doesn’t really matter where they are, as long as you’re considering every size. So for those of you who have nice, big design and engineering teams and deadlines to create and maintain 7 layouts for every page, go for it. For us though, we needed to optimize because we were up against a tight timeline, and we did that the same way we optimize everything else — look at our own data, and design for the most common uses first.</p><h3>Here’s what we found.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*dxa6SqpB5V88fp_6ZSiSYg.gif" /></figure><p>There’s a long tail of device sizes, but ~80% of visitors could be categorized by the most common device sizes. The usual, 375, 768, 1280, 1366, 1920 that we’re used to seeing.</p><p>Here’s where we settled on our breakpoints:</p><p>Mobile: 320 (the smallest most common)</p><p>Tablet: 768 (the size of the most common tablet)</p><p>Desktop 1025 (1 pixel up from Tablet landscape, and smaller desktops)</p><p>Since the desktop span is so huge though (now 1025 and up), we ended up deciding to design at 1280, and every new layout we create would need to be checked at 1025, and 1440 before passing to engineers, so we can be sure we’ve thought out how different elements need to scale, shift, or wrap. 1920 monitors just get more whitespace on the left and right. Eventually, I’d like to add a bigger breakpoint for these larger screens.</p><p>The overall idea here, is to <strong>design for the highest number of people</strong>, and <strong>consider worst case scenarios by designing at the lowest end of the breakpoint</strong>. As long as we know how it will scale up, more space isn’t as likely to cause more problems. Theoretically, these breakpoints could have been arbitrarily set, but why not define them by common devices?</p><h3>Rolling it out</h3><p>To ensure our new design language had clear and replicable rules across all the different possible layouts, and to make sure all designers are working at consistent sizes, it had to be as easy as possible to use. One thing that helped us stay organized within our design team throughout this rebrand, when our components were constantly being tweaked and changed, was consistency in our sketch files. We used Sketch’s <a href="https://blog.sketchapp.com/introducing-libraries-and-smooth-corners-in-sketch-47-2abc5dfc1fb3">Libraries</a> feature (back when it was still in beta) to make sure we were all using the right elements.</p><h3>Making the grid fluid</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*k7cTRlKiXtkZqHfwoi7pyA.gif" /><figcaption>This is the goal: Isn’t she beautiful?</figcaption></figure><ol><li>Set your gutter to a fixed width. 24 is what The Google uses, and all our components are sized to a factor of 6, so hey that’s good enough for us.</li><li>Build your symbol components</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cclwakGlk4vNVBdP3cjLxw.png" /><figcaption>I made my gutters 5% opacity, and my column 20% opacity so I could tell them apart</figcaption></figure><p>Your left and right gutters will be their own symbols (make them half the width of your total gutter), and take a fixed width. Your right gutter pins to the right when resized, and your left gutter pins to the left.</p><p>3. Nest those symbols into another symbol, and add your center column in between. If you’re designing at 12 columns, the individual column width will be determined by the following formula:</p><p>([<strong>viewport or artboard size</strong>] - [<strong>left and right outer margin</strong>] x 2) / 12 (<strong>columns</strong>) - 24 (<strong>gutter</strong>).</p><p>So in my case, since I’m designing at 1280, its {[1280 - (64 x 2)] / 12} - 24 = 74. My column starting width. Ideally, this will be a number that was evenly divisible by 12, resulting in no decimal point values.</p><p>So for example, if I wanted to design at 1920, I would choose to make my margins something like 168 {[1920 - (168 x 2)] / 12} - 24 = 108. Play with the margins to get a reasonably divisible number.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*t1vwEKUqHOaBxjhKQbhCtQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*EVb-VTIDTKWwiN7WSoseJQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*reVhES54nYR6YYDWeYyVQg.gif" /><figcaption>1.) make your gutter symbol, and put those in a column symbol; 2.) drop that into a new symbol, and copy/paste it 12 times. 3.) Remove the two outside gutters. 4.) make it a symbol</figcaption></figure><p>When you’re finished, you’ll have your symboled fixed width left and right gutter in another symbol with your column (not fixed width), repeated 12 times in another symbol. So, its a symbol, in a symbol, in a symbol.</p><p>Then repeat this process for as many breakpoints as you have.</p><p>Now with Sketch Library, all our grids live in a global pattern library file, and we can drop one in from anywhere, giving no one any excuses for using the wrong grid or artboard size.</p><p>Note: Sketch isn’t great at doing math. Even if you’re doing a lot of resizing resizing your grid, a simple ‘round to pixel’ isn&#39;t going to make it perfect. Your gutters may get off a tiny bit, so it’s best to double check them after resizing. Thats why we still use one grid for each breakpoint — unfortunately, one grid to rule them all for every size just isn’t possible in Sketch yet (that I’ve seen).</p><p><strong>Benefits of making a fluid grid:</strong></p><ul><li>Available to every designer from our symbol library</li><li>Standardizes the size of our artboards at each size, which reduces engineering churn</li><li>The Fluid Grid resizes to allow for nested grids, while preserving static gutters</li><li>Helps you predict what designs will look like between breakpoints</li></ul><p>How did you determine your breakpoints and grid? Know a better way? Let me know!</p><p><a href="https://www.dropbox.com/s/f16f9l12l8op662/Fluid_Grid.sketch?dl=0">Download the sketch file</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f58cdb0ad7cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/policygenius-stories/youll-never-guess-what-they-said-after-i-discovered-this-one-thing-about-responsive-grids-f58cdb0ad7cf">You’ll never guess what they said after I discovered this one thing about responsive grids…</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[Staying Personal Across Omnichannel Experiences]]></title>
            <link>https://medium.com/@nicholaskro/staying-personal-across-omnichannel-experiences-9e354955898?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e354955898</guid>
            <category><![CDATA[retail]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[omnichannel]]></category>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Fri, 02 Oct 2015 16:46:17 GMT</pubDate>
            <atom:updated>2015-10-02T17:53:03.856Z</atom:updated>
            <content:encoded><![CDATA[<p>Omnichannel. It’s a vague word to describe all the possible touch-points a customer can have with a brand, in hopes of landing on one seamless experience through every possible medium. A lot of articles I’ve read recently on the subject talk about consistency across devices — how customers can browse, compare, save, and purchase items while switching from tablet to mobile, to desktop, back to mobile, to in-store. It’s a display of how consistent user flows across platforms can broaden and unify the purchasing process.</p><h3>It’s Not an Advertiser’s World Anymore.</h3><p>While seemingly a new trend, maintaining a consistent omnichannel experience technically always existed as a concept within modern retail. In the past, advertising, in-store experience, customer support, and catalogues were the only players. Now, the world of retail has grown to include mobile, desktop, delivery and fulfillment, social media, geolocation, beacons, wearables…the list goes on, and will continue to grow. The more interfaces we come into contact with, the more complex managing all these channels becomes. This begs the question — what do we do next?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHjGBDLVt-q09qFNrVEKjg.jpeg" /></figure><p>Let’s look to the TV show <em>Mad Men</em>. Peggy Olsen, a character on the show, hit a turning point in her career when she took her first stab at copywriting. A lipstick brand that offered 100 different shades wanted to emphasize just how many options they had. Peggy told the ad executives, “I don’t think anyone wants to be one of a hundred colors in a box.” At first, the stakeholders couldn’t see past the “more is more” mentality, but Peggy challenged them with a new perspective — and ultimately a new idea for an ad — that made their customers feel unique. She wrote to women, “there’s only one shade for you” and, “it’s your calling card color.” It was this idea that eventually sold the new lipstick ads. Peggy brilliantly showed that personalization matters, but it now takes more than a vision and smart copy to move the needle.</p><h3>Not All Channels are Created Equal.</h3><p>Retailers might argue that a native mobile app is just one channel out of many, another device that lives alongside desktop, tablet, mobile web, and social media. However, trends are increasingly pointing towards native mobile becoming not just one of, but the primary method by which a company can more effectively communicate with its customers. A 2013 study by the Google Shopper Marketing Council <a href="https://ssl.gstatic.com/think/docs/mobile-in-store_research-studies.pdf">found</a> that 79% of smartphone owners are smartphone shoppers, meaning they use their devices to inform their purchasing decisions. Of those smartphone shoppers, 84% use their devices while in the store to help them shop, actually resulting in higher average spend. With mobile adoption growing at an exponential rate, it’s undoubtedly higher today. That’s an incredible amount of influence mobile has on retail. Without understanding how people are using those devices, we may miss a huge opportunity.</p><p>Unified design languages, a growing number of mobile engineers, increased documentation and case studies, and access to usable data are all contributing to a brand’s ability to get into our devices’ hard drives and stay there.</p><blockquote>The bigger the role our mobile devices have in our lives, the more gravity they have in the omnichannel universe.</blockquote><p>As other forms of brand-to-customer communication draw closer to mobile, and as people become more comfortable with utilizing the power our devices can offer us, the more opportunity we have as an agency to translate those interactions to the screens we carry in our pockets.</p><h3>You are All Beautiful, Unique Snowflakes</h3><p>Mobile isn’t just growing, it will soon be the channel of communication between businesses and people. It’s your loyalty membership, your recommendation engine, your fast checkout utility, and its all personalized to you — your calling card. Big-box, one-size-fits-all solutions that standardize the shopping experience for the masses will become less and less effective. They will be replaced with smart data, personal touches, and a customer base full of VIPs who all get special treatment. Right now, our phones are perfectly poised to unify this vision of retail, because they’re the most personal and widely adopted devices we have. This means a better, more convenient shopping experience that lets us discover the things we want and buy them in the way we want to buy them.</p><p>Just like nobody wants to be one shade in a box of 100 colors, nobody wants to be a number in a dataset of millions. Customers want to be treated like people with specific needs, and that is what will keep us focused on the human aspect in the work we’re doing to help our partners unify their experiences through the power of the most personal channel yet: mobile.</p><p><em>Originally posted September 28th, 2015 on the </em><a href="http://blog.prolificinteractive.com/2015/09/28/staying-personal-across-omnichannel-experiences/"><em>Prolific Interactive Blog</em></a><em>.</em></p><p><em>Nick Kroetz is a User Experience Designer at </em><a href="http://prolificinteractive.com/"><em>Prolific Interactive</em></a><em>. Prolific works with retailers and high-growth lifestyle brands to create mobile experiences that aim to connect customers with brands in new and meaningful ways.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e354955898" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridging the Gap]]></title>
            <link>https://medium.com/@nicholaskro/bridging-the-gap-c4204da1ae3d?source=rss-37e85e945c80------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4204da1ae3d</guid>
            <dc:creator><![CDATA[Nick Kroetz]]></dc:creator>
            <pubDate>Wed, 16 Apr 2014 17:06:13 GMT</pubDate>
            <atom:updated>2015-04-23T14:32:02.934Z</atom:updated>
            <content:encoded><![CDATA[<h4>6 steps for creating data-driven personas without guesswork</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOKIrZbISqvGeGxih5dn7A.jpeg" /></figure><p>Okay, so you have all this data. You’ve run your tests; you’ve given away all your Amazon and Starbucks gift cards and thanked your participants for their valuable time. You <em>might </em>have even run your data through some visualizers, and have some beautiful graphs to show your client those hard-earned insights. You can gather and visualize data until the cows come home, but unless you know how to apply it to the next steps in the process, all your beautiful pie charts will be useless.</p><p>This is especially true for anyone working on a team (which is everyone, unless you’re designing something for only yourself, in which case, why are you reading this? Go build it). Very often, there is a pass-off of information between researchers or from researchers to the design team. Effectively facilitating that process allows your team to bridge the gap between data analysis and persona development without falling into that dangerous black hole between fact, conjecture and assumption (Conjecture itself is not a bad thing, as long as it is recognized for what it is).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WgiGb4qP6XIlOQy4egijnA.jpeg" /><figcaption><a href="http://www.dangerzone.me/">http://www.dangerzone.me/</a></figcaption></figure><p>Developing personas is a crucial part of the user-centered design process because they are used to influence almost every decision you make moving forward. A persona is a fictional character that is used to represent a larger body of target users. They represent your customers, and they are made up of actual qualities your target users have. They are assigned names and faces, and serve as reminders for making user-centered design decisions. Team members can bounce opinions off of their personas as a quick test and use the point of view of a persona to suggest alternate courses of action.</p><p>They serve as our guide map, keep the project on its rails, and offer a user-centered point of view to validate or invalidate decisions that must be made in the design process. Their purpose is to inject objectivity into our design process and can help prevent the team from falling apart or killing the project with their own design goals and agendas. Making sure those personas are based on real data gives your research the weight it deserves and ensuring that the injected objectivity is informed by reality can mean the difference between a successful product or a flop.</p><p>There are many ways to make sure research can generate valid solutions, but here are a few techniques to that will help make sure that the persona development process is not left up to chance.</p><h4>1. Gather Stories</h4><p>Collect your notes, photographs, post-its, drawings, audio, or footage together — every artifact that describes the stories you collected during your research. Avoid injecting generalizations about your research participants’ opinions, needs, and wants. It is very easy to interpret the statements of our research participants and implement our own opinions of what they really mean or how we think we can solve their problem. Constantly questioning whether a piece of information is an inference, observation, or a gathered fact will aid you down the line. Throw out the inferences for now and focus on the observations and gathered facts.</p><h4>2. Break it down</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IhhdQmO2MA2--kywBzc0Aw.jpeg" /><figcaption>Yes, these are Post-its. Put them on a wall.</figcaption></figure><p>Take those artifacts and piece them into single bits of information that, for the sake of this post, we’ll call “fact bits.” Use quotes from your research participants, when possible, to keep these fact bits as objective and granular as possible — which will be important for the next step. Write them down, list them out, or put each fact bit on a post-it note or a single cell of a spreadsheet — anything that helps you see the information from a high level. For example, “Doesn’t like using small screens” or “has kids” could be pieces of information you identified and isolated from your participant surveys.</p><h4>3. Create a framework</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnQxEMbZGFyH7Cogesrqjw.jpeg" /><figcaption>Mind map, affinity map, or relational framework, whatever you want to call it…</figcaption></figure><p>This is also called affinity mapping. Take the information you’ve parsed out — your fact bits — and figure out how to sort it. Place things that are related to each other in the same piles and begin building associations between the bits of information. You can make Venn diagrams, relationship maps, information silos, or timelines. Put all those Post-its up on a wall and organize them into logical groups. If you’re using a spreadsheet, assign different colors to different meanings to visualize your information. Try different ways of sorting all those pieces and go with what works best. There is no right or wrong way to do this part. As long as you are experimenting with multiple methods, you’ll be able to determine what makes sense for your data. It is so important to break down your insights into granular observations, because each fact bit should only fit into one group. Ideas that are too broad or complex will be difficult to sort. After you’ve sorted, look at your piles/categories/columns/circles/silos and figure out why things are grouped together the way they are. Apply terms to each category to understand how each category relates to each other. For example, did you group all habits together? Pain-points? Wishes? Were there similar, or duplicated fact bits that were pulled from multiple research participants? Which groups of information stand out as important to you?</p><h4>4. Separate your data into behavior variables</h4><blockquote>“If you understand what the extremes are, the middle will take care of itself.”<br><em>-Dan Formosa, Smart Design</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1AlKKeTFyP3q87bXcE7Ew.jpeg" /><figcaption>Design for YOUR 80%. Not to be confused with THE 80%.</figcaption></figure><p>Using the Pareto Principle in the design process makes sure you’re focusing as much as possible on the core of your user base. The Pareto Principle, also known as the 80/20 rule, when applied to product design, “tells us that 20% of the functionality and features in any one environment will be responsible for 80% of the results, or actions taken within that environment” <a href="http://www.webdesignerdepot.com/2011/02/the-8020-rule-applied-to-web-design/">(webdesignerdepot.com)</a>. When applied to our users, 20% of the product will accommodate 80% of users. If you know who that 80% is, you’ll be able to design a more focused product for a wider majority. This step helps determine the breaking point between the outer 20% and the 80% majority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*nNXVtCDrzwhmRTKq9rGfhA.jpeg" /><figcaption>Break down your users down into an X-Y plane that helps visualize where your extremes are, so you can focus on the 80% majority of your users.</figcaption></figure><p>Boil your data down into two behavior variables. Choose variables based on how important they are to the product you’re designing. Is tech savviness important to your product? Income? Geography? Age? Volume of social interaction on a daily basis? Map the two variables on an X-Y plane.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBAo0mYyART3n5gmNQUVOw.jpeg" /></figure><p>For example, X could be tech savviness, and Y could be level of education. Choose variables that can, more or less, divide your user base in half but also have attainable endpoints. For example, biological gender might not be the best variable choice because this variable lacks a full spectrum of options between the two. If you pick the right variables, each axis should resemble a bell curve with your target user base occupying space surrounding the origin of your X-Y plane. You’re now looking at 4 quadrants, which will be the early makings for your personas. You could drop a pin on any point in your X/Y spectrum, and it could describe a user.</p><p>Mapping in this way helps to ensure that your personas are all diverse enough to cover the necessary user groups. It also helps to prevent researchers and designers from putting too much of their own opinions, assumptions, and design goals into the personas. If you’ve already created your personas, this is also a great tool to use to validate whether or not your personas are too similar. If they are too closely grouped on one side of the spectrum, you’ll know your personas are too similar, or that your behavior variables need to change.</p><h4>5. Link the data with the variables</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uw6Y_tGvAWv7s-cF9b7AQ.jpeg" /></figure><p>This is where you bridge the gap! Take those fact bits of information and sort them onto your behavior variable spectrum. You are essentially dropping each of those fact bits of information into one of the four quadrants, which, in our example, is divided up into 4 themes: “tech savvy and highly-educated,” “tech savvy and non-education,” “non-tech savvy and highly-educated,” and “non-tech savvy, and non-educated.” Go back to your framework, or affinity map, and make sure every quadrant has at least one fact bit from each of your framework categories. Part of this process might seem arbitrary at first, but as you group items together that make sense with the behavior variables, it will begin to make sense. The goal is to build associations between the fact bits and turn each quadrant into a cohesive whole, with detailed aspects that contribute to the overall theme of the quadrant.</p><h4>6. Create a story to back up the applied characteristics</h4><p>You should now have 4 categories of behavior variable combinations, each one filled with facts. You can now use these facts to flesh out your characters. Now give them a name! Now that you have the important framework for each persona, you can add in information to make the character come to life. Building personas should not be confused with character development in fictional storytelling. It’s important to only consider the facts that are relevant to the problem you’re solving. Think of the facts that make up that persona and ask the question “Why?” Sam doesn’t like using small screens. Why? What about Sam makes him averse to small screens? Including extra information about your persona should seek to answer those questions. The fuller the persona’s character, the easier it is to use them as a point of view to validate your decisions.</p><p>You’ll end up with 4 personas in the end if you followed this pattern exactly. You could choose only two quadrants in your behavior variable X-Y plane if you don’t need that many. You might also find that your personas must fill multiple needs. For example, if you’re designing for an e-commerce platform, you may need a vendor persona and a buyer persona. This process can be done quickly for each need. By building a strong relationships between the research data and the personas who help guide the rest of the design process, you are ensuring that your data continues to be impactful long after the research team hands off their insights.</p><p><em>Illustrations done very quickly and sloppily with </em><a href="https://www.fiftythree.com/paper"><em>Paper by 53</em></a><em>.<br>Special thanks to Diogo Lemos Pereira, Haya Odeh, Tina Israni, Genevieve Gaudet, and Celine Celines</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4204da1ae3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>