<?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 Emily Waggoner on Medium]]></title>
        <description><![CDATA[Stories by Emily Waggoner on Medium]]></description>
        <link>https://medium.com/@emilywaggoner?source=rss-bb73f186db48------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nXTZDNK4jOG-PqOI.</url>
            <title>Stories by Emily Waggoner on Medium</title>
            <link>https://medium.com/@emilywaggoner?source=rss-bb73f186db48------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:38:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emilywaggoner/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[How to use design for good]]></title>
            <link>https://medium.com/@emilywaggoner/how-to-use-design-for-good-23326cc867c9?source=rss-bb73f186db48------2</link>
            <guid isPermaLink="false">https://medium.com/p/23326cc867c9</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[activism]]></category>
            <dc:creator><![CDATA[Emily Waggoner]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 15:49:22 GMT</pubDate>
            <atom:updated>2018-02-28T16:09:30.329Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>Donate your design skills, especially to organizations in your neighborhood. If you feel unsure about whether you should work for free, <a href="http://www.shouldiworkforfree.com/">follow this guide.</a></li><li>Design better <a href="https://www.sec.state.ma.us/ele/elepdf/IFV_2016.pdf">election pamphlets</a>. Read the convoluted proposed legislation until you understand it. Abstract the message and use design to help communicate the important points to other people in your community.</li><li>Process your thoughts and emotions through design. <a href="https://amycambercomics.com/2016/11/15/1023/">Illustration</a>, <a href="https://www.instagram.com/p/BMl7ppWDh5g/?taken-by=instachaaz&amp;hl=en">drawings</a>, user flows, data visualization, posters, whatever. Share it so others can feel seen. We are empowered when we realize others share our emotional experiences.</li><li>Use your voice and skills to <a href="http://helpoverhate.com/">highlight what others are doing</a>. Amplify voices of underrepresented groups.</li><li>Use things that already exist to build tools that help people. Google maps, Google docs, data visualization libraries, design kits. Don’t waste time making things from scratch unless you are super fast. People’s lives could be at stake.</li><li>If you understand something really well, teach it to others. Maybe you’ve been obsessively reading about the rise of fascism in the early 20th century or learning how the electoral college actually works or the origin of the police force in the United States. <a href="http://maeril.tumblr.com/post/149669302551/hi-everyone-this-is-an-illustrated-guide-i-made">Draw a comic about it</a>. <a href="http://www.nytimes.com/interactive/2016/12/01/us/politics/trump-conflict-of-interests.html?hp&amp;action=click&amp;pgtype=Homepage&amp;clickSource=story-heading&amp;module=b-lede-package-region&amp;region=top-news&amp;WT.nav=top-news">Build an interactive story about it</a>. <a href="https://www.splcenter.org/hate-map">Map it out</a>. It doesn’t matter if someone has done it before. People need to hear things multiple times in order for them to sink in, and the way you tell it will be unique to your experiences. Just make sure you’re sharing facts and citing your sources.</li><li>Speaking of which, cite your sources. <a href="https://www.technologyreview.com/s/602981/social-media-is-killing-discourse-because-its-too-much-like-tv/?utm_campaign=socialflow&amp;utm_medium=post&amp;utm_source=twitter&amp;set=602983">Link to things that you read</a>. That’s one of the best things about the internet.</li><li>Design words that communicate important messages.</li><li>Don’t profit off others’ suffering.</li><li><a href="https://muledesign.com/2017/07/a-designers-code-of-ethics">Take responsibility for your work.</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23326cc867c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retiring the Story Type]]></title>
            <link>https://medium.com/@emilywaggoner/retiring-the-story-type-a283a9ad9515?source=rss-bb73f186db48------2</link>
            <guid isPermaLink="false">https://medium.com/p/a283a9ad9515</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Emily Waggoner]]></dc:creator>
            <pubDate>Thu, 20 Jul 2017 17:17:48 GMT</pubDate>
            <atom:updated>2017-07-20T17:17:48.390Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A deep dive into a single user research insight that had a big impact.</em></p><p>This is an in-depth look into one of the key user research insights that drove major design decisions during the redesign of MIT Technology Review.</p><blockquote>Fore more context, read the <a href="https://medium.com/@emilywaggoner/the-great-redesign-25b392b5164d#.dax6xcf7hhttps://medium.com/@emilywaggoner/the-great-redesign-25b392b5164d#.dax6xcf7h">full case study on the MIT Technology Review redesign.</a></blockquote><h4>How the reader reads</h4><p>During the initial research phase of the redesign, my colleague Vanessa DeCollibus and I conducted an extensive research project where we surveyed around 2000 people and interviewed 19.</p><p>We found that when deciding what to read, people are interested in the topic, not the story type or format. In other words, it doesn’t matter if a story is classified as news, opinion, or photo essay as long as it covers something the reader is interested in. We heard and saw this confirmed over and over as people reported the behavior and we observed it when we asked them to find something to read.</p><p>This matters, because before the redesign, our entire site architecture was structured by story type. The primary navigation contained the following links (all story types!):</p><ul><li>News and Analysis</li><li>Features</li><li>Views</li><li>Multimedia</li><li>Discussions</li></ul><p>So—From the first scan of the page, we were making it harder for people to find a story they’d be interested in.</p><h4>Uncovering the editorial perspective</h4><p>We enlisted the excellent team at Upstatement to partner with us for the next phase of the redesign. We presented our research to them and had several deep discussions about our findings and what it could mean for the newly designed experience.</p><p>Fully informed and equipped, the next thing we did together was hold a series of stakeholder interviews with other departments to gather their input and learn about their points of view on the user experience. During one of the conversations, the editorial department revealed an illuminating insight:</p><p>Editorially, our content was categorized into six topics: Business, Biomedicine, Computing, Energy, Mobile, and Robotics. This much was well-known, at least internally, and was built into the site navigation (though buried a few layers deep and difficult to find).</p><p>But here’s what I didn’t know: Each topic had six themes which evolved a few times per year as markets shift and trends emerge. For example, the themes within the Robotics topic are practical robots, interfaces, automated cars, machine learning, robot breakthroughs, and tomorrow’s machines.</p><p>Together, the themes tell a story about what’s important to MIT Technology Review. They are signals for what matters in science and technology, where things are headed, and our editorial point of view. Yet they were completely invisible to readers.</p><h4>Platform problems</h4><p>We started to connect this new understanding of the nuance and intention within our editorial topics to the role that a story’s topic plays in how readers choose what to read… and as these things percolated, another problem came into focus, but this time it was with the publishing platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*7KJ3k5ACZXXL_Vnq0KQijA.png" /><figcaption>A story-type for every occasion</figcaption></figure><p>Before the redesign, we had a unique Drupal template with its own unique layout for each story type. The last time I counted there were over 25 templates.</p><p>We designed and built the Drupal system several years ago without anticipating the implications of having so many templates to maintain.</p><p>Intertwining design templates and story types created a structure that didn’t allow flexibility in how the editors could put a story together. When they wanted to make tweaks to a story that the templates didn’t allow, we’d write custom code to force the template to fit a specific scenario or create a new variation of the template that accommodated the request.</p><p>This kind of ad-hoc design and development wasn’t a very future-friendly practice and it created a bloated system that was difficult to maintain.<br>So with the opportunity to rebuild it better, we deconstructed the templates and broke them down into all their discreet parts.</p><p>Our new CMS would have a library of storytelling components that any article could use, no matter the story type or topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*US-fOFjaXqW1HuNFrS8STA.png" /><figcaption>Building blocks for stories</figcaption></figure><p>(By the way, we went with a headless Drupal setup with a custom publishing admin that controls the story layouts. Because the developers I work with are superb.)</p><p>We untangled the content and presentation, and suddenly there were many more possibilities for creating an engaging story.</p><p>With the content and design no longer beholden to story types behind the scenes, it made sense to tie this idea into how the user would discover content as well.</p><p>We removed the story type as an organizing principle in the information architecture and surfaced the topics and themes instead. Now, our taxonomy reflects the nuance and intention of the topics and themes, and allows users to more easily discover content they are interested in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3WUuYWGV-P0GR0zDIEJpVg.png" /><figcaption>Robotics section with themes exposed on each story</figcaption></figure><p>This one little research insight had a major impact, where the business goals, technical strategy, and user needs aligned perfectly. A UX dream.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a283a9ad9515" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Promosphere: A Hero’s Quest]]></title>
            <link>https://medium.com/@emilywaggoner/the-promosphere-a-heros-quest-75a8e735168e?source=rss-bb73f186db48------2</link>
            <guid isPermaLink="false">https://medium.com/p/75a8e735168e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[board-games]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Emily Waggoner]]></dc:creator>
            <pubDate>Wed, 08 Mar 2017 19:51:12 GMT</pubDate>
            <atom:updated>2017-03-09T21:45:02.030Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the story of how I invented a board game to help people better understand a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Ts3Yq66K_jaKN4Fqva2dw.jpeg" /></figure><h4>The backstory</h4><p>Fellow UX designer, <a href="https://twitter.com/jonakland">Jon Akland</a>, and I were each tasked with designing a few new components that could be used to promote new features on <a href="http://www.technologyreview.com/">MIT Technology Review</a>.</p><p>These new units were part of a sprawling collection of promotional content that lacked guidelines and logic, and I realized we needed to quickly get a handle on these new elements before it spun out of control. Requests for even more promotions were starting to roll in more frequently, and the user experience was worsening with every layer of promotional content we put between the reader and the story. We risked losing readers if we didn’t rein things in.</p><p>In order to figure out how to manage and contain the reading environment, we needed to better understand it. First, I came up with a name and definition:</p><blockquote><strong>Promosphere (noun): </strong>The mass of digital promotions, ads, and messages that surround and dwell within the MIT Technology Review environment but are not editorial content.</blockquote><p>Jon and I got to work auditing all of the existing and planned promotions, figuring out which department was promoting what, and assigning values for disruption to the user experience and priority within the organization.</p><p>The departments creating promotional messages were editorial, marketing, events, and ad sales. The people in those departments weren’t talking to each other about the nature and amount of promotions they were each hoping to run, or how a reader could potentially see thirteen different in-house promotions (not counting ads) in a single visit.</p><p>Rather than giving a presentation on empathy, we needed to figure out how to arrive at a shared understanding of the impact of our work. We also needed to empathize with our co-workers—they were doing their jobs to promote their products, events and initiatives, each with their own goals to meet. But in order for that effort to pay off, the messages and promotions shouldn’t be allowed to drown each other out.</p><p>I set out to come up with a collaborative design activity that would strike the right tone of light-hearted fun that might allow some empathetic reflection and understanding. My internet research didn’t yield what I was looking for, so I invented a board game instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*JyprjTL0GoNeErod5fAWfQ.jpeg" /><figcaption>Here I am about 7 hours into the board game design, wondering if I’ve made a huge mistake</figcaption></figure><h3>The Promosphere: A Hero’s Quest</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*o0ysZWSUZe5URpxEJb7fjA.png" /></figure><h4>Game Overview</h4><p>This game takes place in a faraway galaxy called the Internet. The creatures that live in The Internet are called Readers, and Readers thrive by consuming content. They use their jetpacks to travel from planet to planet on a never-ending quest for content to consume. There are thousands of planets to visit in The Internet that all have different flavors of content to try.</p><h4>Readers</h4><p>In this game, most of the players are Readers who have stumbled upon a little planet called The Promosphere, and it has a decent selection of interesting content for the Readers to consume.</p><p>The game board is shaped like an article, and the Readers consume the article by rolling the dice and advancing their game piece along the board. Their goal is to make it all the way to the end of the article before they activate their jetpack and fly off to another planet.</p><h4>The Gatekeeper</h4><p>One player has the role of The Gatekeeper. The Gatekeeper is the host of The Promosphere and is eager to have Readers visiting and show them all The Promosphere has to offer. The Gatekeeper’s goal is to show off all the different sights and features of The Promosphere in hopes that the Readers will decide to stay a little while. The Gatekeeper has to be careful when interacting with the Readers though, because…</p><h4>Shiny Objects</h4><p>The Readers each have an attention span which can hold up to twelve shiny objects. The Internet is a crowded galaxy and shiny objects are everywhere! If a Reader accumulates too many, their attention span reaches capacity, they become overwhelmed and activate their jetpacks, zooming out of the The Promosphere and back into The Internet where their attention span resets and they can try content from other planets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*mgKR4XM-mw0BlJ_xcvXJKQ.png" /><figcaption>Shiny Objects in a Reader’s Attention Span</figcaption></figure><h4>Variable cards</h4><p>Readers take turns rolling the dice to see how far they get in the article, and they may land on a space that asks them to draw a variable card. Variable cards are things that neither the Readers nor the Gatekeeper can control. They compete for the Readers’ attention, and can make it more difficult to get through to the end of the article, especially when they add shiny objects to the Reader’s attention span.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ru16Aw9Un6MFYJo4IZLgvg.jpeg" /><figcaption>Here are a few variable cards</figcaption></figure><h4>Promo cards</h4><p>During each Reader’s turn, the Gatekeeper can choose to present the Reader with a promo card. Promo cards highlight various features and attractions in The Promosphere, but handing them out is risky. Promo cards interrupt Readers’ progress through an article and add shiny objects to their attention span. So although the Gatekeepers intentions are good in wanting Readers to stay in The Promosphere, they risk alienating the Readers if the promo cards fill up their attention span too quickly.</p><p>The Gatekeeper’s goal is to hand out as many promo cards as possible without forcing Readers to activate their jetpacks before they reach the end of the article. Gatekeeper Enlightenment is achieved when they realize that Readers are in the Promosphere for its content, and will want to stay if they can have a mostly uninterrupted reading experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FXgjz79uwxUgYWMIq-sNDA.jpeg" /><figcaption>Here are a few promo cards</figcaption></figure><h3>How did it go?</h3><p>My fellow product development team members play-tested it with me several times and had many wise insights and suggestions for the game mechanics, world-building, and pace.</p><p>After making a some edits to the pieces and refining the rules, I played a few different times with stakeholders from other departments, and it was a lot of fun. I’m still not totally satisfied with the end-of-game scenarios or the pace, but I have to keep reminding myself that the purpose of this adventure wasn’t to make a perfect, airtight board game, but to create an environment that allowed people to understand a problem in a new way and talk about it openly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*tyHqY80pt4mWzVPolZZxrQ.jpeg" /><figcaption>The Promosphere: A Hero’s Quest in action. I forgot to make Reader pieces and bring dice, so we improvised!</figcaption></figure><p>It’s not wrong to have things we need to communicate with readers. But we risk creating a hostile user experience if we don’t choreograph the messages intentionally and with prudence. We are really only likely to meet our business goals when they align with what the users’ are.</p><p>It’s hard to measure the success of a project like this, but since introducing the game and playing it a few times, I can confidently say there is productive and sustained dialogue on the subject, and a collaborative, cross-departmental effort to become better stewards of The Promosphere.</p><p>And, importantly, the word “Promosphere” has entered the office lexicon!</p><p>If you are interested in checking out the full set of game pieces and rules, send me an email: emilyrwaggoner at gmail dot com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75a8e735168e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Great Redesign]]></title>
            <link>https://medium.com/@emilywaggoner/the-great-redesign-25b392b5164d?source=rss-bb73f186db48------2</link>
            <guid isPermaLink="false">https://medium.com/p/25b392b5164d</guid>
            <category><![CDATA[editorials]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Emily Waggoner]]></dc:creator>
            <pubDate>Tue, 07 Mar 2017 22:58:32 GMT</pubDate>
            <atom:updated>2017-03-08T01:07:45.403Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://www.technologyreview.com/">MIT Technology Review</a> is one of the oldest magazines in the United States. The first issue was published in the winter of 1899. It has since grown into a media company whose mission is to tell about science and technology in ways that enable everyone to better understand the world.</p><p>In the last 118 years, the magazine has undergone many redesigns. The website, which wasn’t around until the late 1990s, has been through a similar but more rapid evolution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_tJK2W75EWcd6QHRwAF1xA.png" /><figcaption>Covers from 1899, 1932, 1968, and 2016. I don’t design covers, but I do admire them.</figcaption></figure><p>In the fall of 2014, my team began planning a complete redesign and rebuild of the website. The redesign was my sole focus for a little more than a year, and is the largest and most complex project I’ve contributed to thus far in my career.</p><h4>Goals of the redesign</h4><ul><li>Create a more thoughtful and enjoyable digital reading experience no matter the device</li><li>Provide readers with clear pathways to content they are interested in</li><li>Increase engagement with readers and make it easier for them to become paying subscribers</li><li>Build better tools that empower editors to make well-designed stories</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RxoPkdmVqEdtJBdeQIiVTg.png" /><figcaption>New home page for MIT Technology Review</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9K3HhV-VVHrFVC2e2QHnuA.png" /><figcaption>Read the stories: <a href="https://www.technologyreview.com/s/603026/four-huge-cities-are-banning-diesel-cars/">Diesel car ban</a> / <a href="https://www.technologyreview.com/s/602491/can-crispr-save-ben-dupree/">CRISPR and Ben Dupree</a> / <a href="https://www.technologyreview.com/s/603721/insect-zapping-laser-fence-prepares-for-first-enemy-contact/">laser fences</a></figcaption></figure><h3>Design Research</h3><p>We kicked off the project with a design research phase in which, over the course of several months, my colleagues and I asked readers many questions:</p><blockquote>How do you read online? Why do you choose to read a particular story? Where are you when they are doing most of your reading? What else do you read? How do you choose what to read after you finish an article?</blockquote><p>We wrote and distributed a 62 question survey and interviewed 19 people. We got around two thousand survey respondents, many of whom were familiar to MIT Technology Review, whether a subscriber or social media follower. The interviewees were a mix of subscribers and non-subscribers, but all highly engaged online readers.</p><p>I led my team through collaborative design activities in which we analyzed the data and distilled several key insights to form the foundation for the subsequent design phases. We documented our research and analysis and presented it to the company and design partners in early 2015. We return to the findings often, presenting them again as new team members join and referencing them for input on new design projects.</p><h3>Design Collaboration</h3><p>As our research phase came to a close, we joined forces with the wonderful and talented design firm, <a href="http://upstatement.com/">Upstatement</a>, to begin the next part of the redesign.</p><p>As Upstatement led the design of the reading experience and visual identity, I designed the surrounding experiences: the subscription flow, search, account management, customer support, and the publishing admin, to name a few, and eventually extended the visual design to all the parts of the experience as well.</p><p>In the next section, I’ll give a quick overview of a few pieces of the redesign project and share a few deliverables I created for each as well.</p><h4>Master sitemap</h4><p>First, I made a master sitemap that audited the existing site architecture, and formed the basis of the new website’s structure. We were able to retire several sections of the navigation and move content into groups that better reflect how readers browse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ObyTeaMa2hoQmoB8puepCg.png" /></figure><h4>Subscription and product purchase flows</h4><p>A third-party fulfillment vendor handles the transactions and distribution of magazine subscriptions and other editorial products that MIT Technology Review sells, which means there are many technical and experiential constraints to work with in these flows.</p><p>Purchasing a subscription should feel like a seamless experience when the user moves from pages hosted on our site to those hosted by the third-party vendor. These interactions are vital to the experience and represent a key business goal: increasing conversions on the subscription forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBtTrV9utZAV7TYHhqQkDQ.png" /><figcaption>User flows for the subscription purchase flows</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKHpvgcTkBV78AlMPXfz7g.jpeg" /><figcaption>Visual designs for initial steps in the subscription purchase flow</figcaption></figure><h4>Account settings</h4><p>Because of the multiple systems in place that store and transmit our users’ data, there are a few different places they need to visit to view or edit their information. The success of these pages depends heavily on clearly written copy to help people find what they’re looking for.</p><p>The following are wireframes from a few screens in the account settings section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNIvLq-frZ_3-45Eu35rPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WvjAdyQD_xasYWK8Dfcd6Q.png" /></figure><h4>Rhino: Publishing interface</h4><p>One of my favorite improvements of the redesign is how we changed the publishing process. Previously, the site was managed by a Drupal system with a template for every variety of story type.</p><p>The templated approach became problematic over time because though the templates were many, they were rigid and difficult to customize. When the editorial and art teams wanted to make design tweaks, we had to either create a new template, or write custom code at the story level to accommodate the changes. Neither of those solutions is ideal or easy to maintain.</p><p>We rebuilt the site using a headless Drupal setup with a custom story editor and publishing interface, called Rhino, sitting in front. Rhino provides a library of components that the editors can combine in an infinite number of ways with a drag-and-drop interface (and previews at multiple responsive breakpoints built in!) to tell stories.</p><p>Decoupling the story-type from the layout allowed us to create a design system of flexible, responsive components. It’s a better experience on the editorial side, and a more sustainable and future-friendly product for my team to manage.</p><p>During the redesign, I consulted with Rhino’s lead developer often on flows and layout for the various features of Rhino, and made an icon library that represents the story components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*US-fOFjaXqW1HuNFrS8STA.png" /><figcaption>Icons used in the interface that represent the building blocks of a story</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QzwWJaC5fB3Lezm5lzNWQ.png" /><figcaption>Wireframe for the section of Rhino that allows editors to curate the home page</figcaption></figure><h3>Stories</h3><p>Here are some of my favorite stories that have been published in the new design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/1*OLmlGfqd1os-uEOg8r0DGg.png" /></figure><p><a href="https://www.technologyreview.com/lists/technologies/2017/">1o Breakthrough Technologies</a>. This list is published annually, and this year the artwork and video content for each story in the list came together to make an engaging package. The story above is <a href="https://www.technologyreview.com/s/603494/10-breakthrough-technologies-2017-paying-with-your-face/">Paying with Your Face</a> by Will Knight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/1*QtoC4BIfYohQjH9SBHFNTQ.png" /></figure><p><a href="https://www.technologyreview.com/s/602468/the-one-and-only-texas-wind-boom/">The One and Only Texas Wind Boom</a> by Richard Martin. The gorgeous photography holds the spotlight in ways that were impossible before the redesign, and it’s a great story about the future of a state that’s better known for its oil.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/387/1*ciFuvPqV--jEOJEUVRhT6Q.png" /></figure><p><a href="https://www.technologyreview.com/s/602492/what-to-know-before-you-get-in-a-self-driving-car/">What to Know Before You Get In a Self-driving Car</a> by Will Knight. The author takes a ride in self-driving Uber and lived to tell the tale. I really like how the illustration at the top takes advantage of its surrounding environment and sneaks a car into the white space.</p><h3>The Results</h3><p>We launched the redesign in February 2016. Before the redesign, page load time was 7.4 seconds, and now it’s 2.1 seconds. This is an achievement due in part to better code and image-handling, but also an ongoing effort to help other departments understand their responsibility in keeping the file sizes down, especially on story pages. Performance is design!</p><p>The redesign effort has had major impact on user behavior too: Overall site traffic has increased 25% YoY, and <strong>mobile traffic has exploded, increasing by 91% YoY</strong>. The growth rate of our daily newsletter subscribers in the year since the redesign was 26.5%, compared to only 7% growth during the previous year.</p><p>We’ve seen a slight uptick in return visitors and the number of paying subscribers has increased by 18%.</p><p>Design does not end when a project does, and we’ve been monitoring, testing and building on the experience since last year’s launch.</p><p>There were a lot of awesome people involved in this project who should be recognized for their efforts.</p><ul><li>Nate Haas, Tito Bottitta, and the Upstatement design team</li><li>Product Development Engineers at MIT Technology Review: Shaun Calhoun, Molly Frey, Jason Lewicki, DJ Hartman</li><li>Erik Pelletier, Chief Digital Officer at MIT Technology Review and Vanessa DeCollibus, Product Manager at MIT Technology Review</li></ul><p>If you haven’t yet, <a href="http://www.technologyreview.com/">check it out</a>! And please let me know if you have any feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b392b5164d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>