<?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 Lauren Gilchrist on Medium]]></title>
        <description><![CDATA[Stories by Lauren Gilchrist on Medium]]></description>
        <link>https://medium.com/@lgilchrist?source=rss-7d48025ebede------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3y4ENBK9x6PLhvhf.jpeg</url>
            <title>Stories by Lauren Gilchrist on Medium</title>
            <link>https://medium.com/@lgilchrist?source=rss-7d48025ebede------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:00:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lgilchrist/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[Equal Opportunity Product Development]]></title>
            <link>https://medium.com/built-to-adapt/equal-opportunity-product-development-aab812a898b1?source=rss-7d48025ebede------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab812a898b1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Lauren Gilchrist]]></dc:creator>
            <pubDate>Mon, 21 Nov 2016 17:28:55 GMT</pubDate>
            <atom:updated>2017-04-06T22:41:57.928Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building accessible products for everyone</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*X0NkC6hZ04XLOPXf0LasZA.jpeg" /><figcaption>DC Pivots Gabriel Ramirez (L) and Adam Bray (R) testing features while listening to JAWS screenreader.</figcaption></figure><p>What is it like to use the web without a mouse? Imagine navigating your inbox with a screen reader, like many legally blind do. These and other questions about impairments are a daily part of how we understand user needs in Pivotal’s Washington D.C. offices.</p><p>By law, most US federal agencies — civilian, defense, or intelligence — must build software that meets <a href="https://www.section508.gov/content/learn">508 compliance standards</a>. These stipulate that software must be useable for those who access the web through assistive technologies such as screen readers, voice-to-speech controls, and screen magnifiers, or who have specific vision or mobility needs. A full 100% of our current clients in Washington D.C. are government institutions, so 508 compliance has significantly influenced our teams and their expertise.</p><p>Here are five principles you can take away now for projects with 508 or similar accessibility requirements:</p><h4><strong>1) Start with the basics</strong></h4><p>We’ve found it best for the entire team to get a crash course on basic principles and best practices upfront. Check out <a href="https://medium.com/salesforce-ux/7-things-every-designer-needs-to-know-about-accessibility-64f105f0881b#.31tffz7fj">7 things every designer should know about accessibility</a>, and <a href="http://blog.invisionapp.com/guide-web-content-accessibility/">Invision’s blog post</a> on web accessibility, for starters. <a href="https://pages.18f.gov/accessibility/">18F’s accessibility guide</a> and <a href="http://accessibility.voxmedia.com/">Vox’s product accessibility guide</a> are good additional resources.</p><h4><strong>2) Understand what “done” looks like</strong></h4><p>Most government institutions have existing processes to ensure that 508 standards are met before an application goes into production, though they are often vague and confusing. Does someone test the app? To what standards (WCAG, AA, AAA)? Are they able to be part of the process of identifying what success looks like? Can they delegate someone who is? Often, 508 compliance is a waterfall process that tests compliance at the end of a large cycle; in understanding how this currently works, we often find committed volunteers who are eager to make it more iterative.</p><h4><strong>3) Identify targets upfront</strong></h4><p>Which browsers, assistive technologies, and devices are you using for acceptance? JAWS, VoiceOver, and NVDA are the most popular screen readers, and their behavior can vary significantly depending on their version and the version of the browser they are used with. Agreeing on which browsers, assistive technologies, and versions you are using for acceptance upfront saves time and energy squashing strange behavior later. It is also worth noting that it’s virtually impossible to understand which screen readers your users use, as they leave no trace in browser analytics. You’ll likely need to make an educated guess.</p><h4><strong>4) Bake 508 into practices early</strong></h4><p>The longer you wait to bake in 508 criteria into your user stories and design process, the more rework you’ll do. If you embrace 508 as a constraint upfront and modify processes to ensure that a user leveraging an assistive technology is treated as a first-class citizen, you will save a lot of frustration for your team and client (we’ve learned this the hard way). This likely entails user stories that include accessibility criteria, and accessibility tests in your test suite (tools such as <a href="http://pa11y.org/">Pa11y</a> can help with this).</p><p>If possible, have the agreed upon assistive technologies installed on everyone’s machines for faster feedback loops. Otherwise, developers must deploy before testing, which adds time.</p><h4><strong>5) Bring in an expert</strong></h4><p>We find that a 508 subject expert is needed full-time during discovery and the first few weeks of writing user stories, with that commitment decreasing quickly as the team ramps up. We’ve evolved to point where we bake the acceptance criteria for an unsighted user (screen reader), a low vision user (zoomtext), and low-mobility user (voice-to-navigate technology) directly into our user stories. While this adds scope at first and can be a steep learning curve, it saves a ton of rework later on.</p><p>At Pivotal we are constantly teaching, learning, and adapting our processes to meet new constraints. This is especially true for 508 compliance, which has broadened our empathy and understanding of digital user access needs, and stretched us to adapt a traditionally waterfall process into a lean, agile, user-centered, and iterative lifecycle. We look forward to continuing to share out our best practices as we learn; Pivots in our DC office have given talks on the basics of 508, created starting guides, and we are constantly sharing resources on our Slack #accessibility channel.</p><p>If you have any resources you turn to for building accessible products, best practices, or great examples of an accessible product, please tell us in a response to this post.</p><p><em>Special thanks to Laurel Gray and Adam Bray who helped with this post.</em></p><figure><a href="http://builttoadapt.io/"><img alt="" src="https://cdn-images-1.medium.com/max/71/1*9fg8oHTkroGjylRUKyKQAw.png" /></a></figure><p><em>Change is the only constant, so individuals, institutions, and businesses must be </em><a href="http://builttoadapt.io/"><em>Built to Adapt</em></a><em>. At</em> <a href="http://pivotal.io/"><em>Pivotal</em></a><em>, we believe change should be expected, embraced and incorporated continuously through development and innovation, because good software is never finished.</em></p><figure><a href="http://pivotal.io/"><img alt="" src="https://cdn-images-1.medium.com/max/300/1*z9lcnjksUjJ7wuEH-H0R8A.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab812a898b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/equal-opportunity-product-development-aab812a898b1">Equal Opportunity Product Development</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Users Miss the Front Door]]></title>
            <link>https://medium.com/product-labs/when-users-miss-the-front-door-c2a9e7b93dcb?source=rss-7d48025ebede------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a9e7b93dcb</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Lauren Gilchrist]]></dc:creator>
            <pubDate>Tue, 02 Sep 2014 13:18:51 GMT</pubDate>
            <atom:updated>2017-05-01T20:26:18.879Z</atom:updated>
            <content:encoded><![CDATA[<h4>How weeSpring Converted Organic Traffic<br>Into Return Users</h4><h4><strong>Helping New Parents Make Smarter Buying Decision</strong>s</h4><p>What’s the hardest thing about becoming a new mom? According to Ally Downey, it was knowing what to buy. “The first time I walked into a Babies R Us, I burst into tears,” she said. “I looked up at a ten-foot wall of baby bottles and saw — in all of those options — a metaphor for how completely unprepared I was for the hundreds (thousands!) of choices I’d have to make for my baby.”</p><p>She turned to her friends for help and found they were to share what to buy and what to skip. “…[A]s my inbox flooded with advice from my in-the-trenches friends, I started to feel a little less overwhelmed and a little bit more ready. By the time my baby arrived, I’d become one of the ones sending the instructive emails (Get Triple Paste in the tub, not the tube!).”</p><p>She saw not only a tremendous pain point for parents, but a huge business opportunity, with new parents spending roughly $5,000 on baby products in year one alone. So soon after her first child was born, Ally launched <a href="http://www.weespring.com/">weeSpring</a> — a place for expecting parents to find reliable advice on what to buy, and for new parents to share what they had learned. A year and a half later, weeSpring is a vibrant community of new and expecting parents with over 150,000 product ratings. Expecting parents can log in via Facebook to see what their friends have reviewed, save products for later, and build lists like “Newborn Necessities,” “Teething Time, and “Best Gifts for a One-Year Old.” New parents can share their own tried-and-true advice and learn about new products as their baby grows.</p><h4>User Acquisition Experiments</h4><p>Like any growing startup, weeSpring has been experimenting with ways to reach new users. By writing a <a href="http://blog.weespring.com/">blog</a> that details their favorite products and tips, building a strong <a href="http://www.pinterest.com/weespring/">Pinterest presence</a>, and experimenting with paid advertising, they are seeking out the most effective channel to reach new and expecting parents that convert to registered users. As they sat down to analyze which experiments were converting the best, however, Ally and her co-founder Jack found a pattern they didn’t expect.</p><ul><li>First time users were arriving at individual product pages deep within weeSpring via search (e.g. google) and referral (e.g. through a blog post, an email from their mailing list, or a Pinterest page)</li><li>First time users were overwhelmingly arriving on mobile devices</li><li>First time users who came to deep linked pages were not signing up at a comparable rate to first time users who landed on the the homepage</li></ul><h4>Front Door vs. Back Door User Acquisition</h4><p>weeSpring had stumbled into a classic startup challenge: new users coming in through the “back door” (from search or referral) did not understand what weeSpring was and how it offered value. They were not signing up and they were not reviewing products. In short, they weren’t behaving the same as new users who came in through the “front door” (from weeSpring’s homepage, which has a strong onboarding flow).</p><p>weeSpring signed up for <a href="http://productlabs.io/">Product Office Hours</a> to get some advice on what to do next. Product Office Hours is an hour of free consulting offered by <a href="http://pivotallabs.com/">Pivotal Labs</a> for startups who want advice on how to move forward when confronting a particular challenge or feature.</p><h4>Developing a Back Door Acquisition Strategy</h4><p>We (the team at Pivotal Labs) helped weeSpring identify that they were ready to dedicate design and development resources to address the needs of their new back door users. We then led them through two activities to design an experiment to focus on converting back door users.</p><p>First, we determined the goals of a back door new user who had clicked onto a weeSpring product page (e.g. Aden and Anais swaddle blankets) from a blog post, a Pin, or a newsletter, but had not yet signed up. We concluded that back door users wanted to:</p><ul><li>Learn more about the product (read a quick summary and see other photos)</li><li>Buy the product (redirects to Amazon)</li><li>Save the product</li><li>Learn what other parents think of the product</li></ul><p>Second, we needed to figure out what had to be on the page so that a back door user could achieve his or her goals. We determined this in four steps:</p><ol><li><strong>List out existing calls to action. </strong>We wrote each call to action on a separate index card. We listed out nearly 20 separate prompts, such as “view Q&amp;A,” “share on Facebook,” and “ask a question.”</li><li><strong>Remove what is not relevant. </strong>Certain prompts, such as indicating that a user has a product or seeing what her friends think of it, are irrelevant to a user who has not yet signed up for an account.</li><li><strong>Prioritize user goals. </strong>Focus on actions that are contextually relevant. For weeSpring, this meant prioritizing calls to action that matched a new user’s intents, such as buying and saving a product.</li><li><strong>Don’t forget conversion. </strong>When is the right time to ask a user to create an account? After the new user understands what they are looking at, why it is for them, and how it adds value. We all agreed that if a new user clicks “save this” on a product page in weeSpring, he or she “gets it” and should be prompted to create an account.</li></ol><p>Ally and Jack walked out of Product Office Hours intending to roll out an experiment with the goal of improving conversion on logged out product pages for first-time mobile users.</p><h4>Back Door Users Buy More</h4><p>Several weeks later, they rolled out small changes to their logged out mobile page. Since the change, they are seeing two positive signals:</p><ul><li>New users who arrive via the back door are now converting at a comparable rate to those that come in through the front door</li><li>New users that come in through the back door are 4x as likely to click buy as new users that come in the front door.</li></ul><p>You can see the changes that the team made in the screenshot below, which compares a logged in (L) versus logged out (R) product page on mobile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*1ThSnUrgBRplzQ25Ddp1Pg.png" /></figure><p>By making small, pointed design changes to focus on purchase, conversion, and communicating their value proposition, weeSpring has been able capture more new users to sign up and buy. They can now feel confident making bigger changes to product page because they have validated the basic concepts.</p><p>We’re looking forward to seeing their new product page, as well as new experiments to encourage back door users to complete front door activities (such as rate and review products).</p><p><em>Need Product Advice? Pivotal Labs now offers Product Office Hours. </em><a href="http://productlabs.io/"><em>Learn more or sign up here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a9e7b93dcb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/when-users-miss-the-front-door-c2a9e7b93dcb">When Users Miss the Front Door</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>