<?xml version="1.0" encoding="UTF-8"?><feed
	xmlns="http://www.w3.org/2005/Atom"
	xmlns:thr="http://purl.org/syndication/thread/1.0"
	xml:lang="en-US"
	>
	<title type="text">Mandy Brown | The Verge</title>
	<subtitle type="text">The Verge is about technology and how it makes us feel. Founded in 2011, we offer our audience everything from breaking news to reviews to award-winning features and investigations, on our site, in video, and in podcasts.</subtitle>

	<updated>2016-10-21T18:00:03+00:00</updated>

	<link rel="alternate" type="text/html" href="https://www.theverge.com/author/mandy-brown" />
	<id>https://www.theverge.com/authors/mandy-brown/rss</id>
	<link rel="self" type="application/atom+xml" href="https://www.theverge.com/authors/mandy-brown/rss" />

	<icon>https://platform.theverge.com/wp-content/uploads/sites/2/2025/01/verge-rss-large_80b47e.png?w=150&amp;h=150&amp;crop=1</icon>
		<entry>
			
			<author>
				<name>Mandy Brown</name>
			</author>
			
			<title type="html"><![CDATA[Refreshing The Verge: no platform like home]]></title>
			<link rel="alternate" type="text/html" href="https://www.theverge.com/2016/10/21/13331208/refreshing-the-verge-no-platform-like-home" />
			<id>https://www.theverge.com/2016/10/21/13331208/refreshing-the-verge-no-platform-like-home</id>
			<updated>2016-10-21T14:00:03-04:00</updated>
			<published>2016-10-21T14:00:03-04:00</published>
			<category scheme="https://www.theverge.com" term="Verge Archives" />
							<summary type="html"><![CDATA[The Verge turns five on November 1st, and we&#8217;re in the process of refreshing our entire brand for the next five years. In Refreshing The Verge, we&#8217;ll be looking at how that refresh process works, and what it&#8217;s like to adapt a brand like The Verge to a world where media platforms have become dominant. [&#8230;]]]></summary>
			
							<content type="html">
											<![CDATA[

						
<figure>

<img alt="" data-caption="" data-portal-copyright="" data-has-syndication-rights="1" src="https://platform.theverge.com/wp-content/uploads/sites/2/chorus/assets/2829635/19b012aca93511e2bb6b22000a9f3c09_7.jpg?quality=90&#038;strip=all&#038;crop=0,0,100,100" />
	<figcaption>
		</figcaption>
</figure>
<p>The Verge<em> turns five on November 1st, and we&rsquo;re in the process of </em><a href="http://www.theverge.com/2016/10/3/13149464/the-verge-redesign-refresh-five-intro"><em>refreshing our entire brand for the next five years</em></a><em>. In </em>Refreshing<em> </em>The Verge<em>, we&rsquo;ll be looking at how that refresh process works, and what it&rsquo;s like to adapt a brand like </em>The Verge<em> to a world where media platforms have become dominant.</em></p>

<p><em>One of the biggest advantages The Verge has always had is Vox Media&rsquo;s own proprietary publishing platform, Chorus. As we think about building The Verge for a future where other media platforms command more and more of our audience&rsquo;s attention, the needs and demands of Chorus have also changed &mdash; what started as an efficient tool for writing articles and publishing a website now needs to become a system for creating a wide range of formats and managing distribution to multiple platforms. In this installment, I&rsquo;ve asked Mandy Brown, Vox Media&rsquo;s Director of Publishing, to talk about the future of </em>our<em> platform &mdash; and really, the future of publishing tech.</em></p>

<p><em>&mdash; Nilay</em></p>
<hr class="wp-block-separator" />
<p>In writing <a href="http://www.theverge.com/2016/10/13/13271182/refreshing-the-verge-writing-a-new-mission-statement">a new mission statement for <em>The Verge</em></a>, Nilay notes that the core difference in media between today and five years ago is the preponderance of platforms: we are no longer building a single platform where our audience will find us, but must instead populate content across many platforms, each with their own unique proclivities. That doesn&rsquo;t mean that <em>The Verge</em>&rsquo;s website no longer matters, it means it&rsquo;s now only one among many platforms that we have to attend to.</p>

<p>With Google AMP among the fastest growing of those platforms, Nilay is <a href="http://www.theverge.com/2016/10/6/13188306/refreshing-the-verge-facebook-video-google-amp-future-of-the-web">understandably skeptical</a> about the open web&rsquo;s future. I&rsquo;m sympathetic to that &mdash; and as the one leading a redesign of the publishing tools on Vox Media&rsquo;s platform, Chorus, I have to make publishing to AMP and other platforms one of my highest priorities. But I also believe that <em>The Verge</em> (and indeed all of Vox Media&rsquo;s brands, as well as many other publishers) will find opportunities to experiment on the open web such that it remains a compelling component of the overall platform ecosystem.</p>

<p>Our website is where we have the biggest opportunity to develop new ways of telling stories, independent of the constraints of other platforms. So while it&rsquo;s very likely that many members of our audience will find that the primary way they read or watch <em>The Verge</em> is via Google AMP or Facebook video, our own platform will inform those experiences, and will continue to be core to everything we do.</p>
<p><q class="center">our stories have to be resilient</q></p>
<p>What does that mean for a publishing platform like Chorus? To start, our stories have to be resilient. A single story may present one way on our own site, another way in the AMP version, and yet other ways in a Facebook Instant Article or on Apple News. Each of these platforms has a lot in common as far as basic storytelling components go, but they also diverge in non-trivial ways: interactions, typographical systems, the presentation and behavior of ads, and the elements we have to play with to express our brand&rsquo;s identities may all differ from platform to platform.</p>

<p>Perhaps ironically, we&rsquo;ve found that the best way to create that resiliency is by harking back to the web principle of <em>progressive enhancement</em>: each story created in Chorus begins as a platform-neutral collection of text, images, and video. That foundation ensures that we can publish that story as easily to our own platform as to, say, AMP or Apple News, and be confident that our audience will experience that story in a way that fits whichever platform they are using. On our own platform, we&rsquo;re then free to enhance up, adding stylistic or experiential flairs that elevate the experience of the story. This practice &mdash; which I refer to unoriginally as <em>progressively enhanced storytelling </em>&mdash; also has the added benefit of helping us make our content more <a href="http://accessibility.voxmedia.com">accessible</a> to more kinds of users, especially those with disabilities. (It wouldn&rsquo;t be inaccurate to consider speaking browsers one among the many platforms we must publish to.)</p>

<p>There&rsquo;s another core change in media over the past five years, which Nilay has also noted: our audience is spending as much time <em>watching</em> content as reading it, if not more. The explosive growth of Facebook video has many in the news business sobbing over the death of text, but I am again unconvinced: I think video growth is expanding the ways we can reach our audience, not cannibalizing time spent reading. Words will always have the benefit of speed, both in terms of time spent composing and time spent reading. That said, we still produce an order of magnitude more text content than video, and it&rsquo;s past time for video to do some catching up.</p>
<p><q class="center">we have to <em>remix</em> stories instead of enhancing them</q></p>
<p>In addition to prioritizing tools for video creators alongside other editorial needs in the months ahead, we&rsquo;re also facing a shift in how we think of content creation overall. We can progressively enhance stories for platforms like AMP and Instant Articles which take as their core assumption something shaped more or less like an &#8220;article.&#8221; But that breaks down for Facebook video, Instagram, Snapchat, or any number of other platforms. Even video has many different outlets: what makes a Facebook video successful is different from what makes a good YouTube video or an especially shareable Vine. Here we need a different tactic: we have to <em>remix</em> stories instead of enhancing them, expressing a common message across different media while reusing words, images, video, and brand elements in both coherent and delightful ways. This means a new set of tools and mental models and best practices not only for composing and distributing content, but also for reusing it and reimagining it into different forms. That makes the work of publishing more complex, more generative, and more exciting.</p>

<p>And yet it still needs to be <em>fast</em>. The speed of publishing is like one of those famed startup growth charts &mdash; a hockey stick shape showing a rapid, even exponential, increase. As <em>The Verge</em> relaunches, we&rsquo;re also about to take a newly redesigned and refactored Chorus publishing tool out of beta. That beta has many new features to support the new universe of platforms: version control, simultaneous editing, an entirely new data model, platform-agnostic design tools, and more. But our biggest challenge in the months ahead is to simultaneously empower our editorial teams to create more content, across more platforms, without slowing down or losing any of the verve and personality that have made <em>The Verge</em> (and our other editorial brands) so popular. As the platform ecosystem becomes more complex, Chorus has to be simultaneously more expressive <em>and</em> easier for our teams to use. (In case it&rsquo;s not already clear, this is a huge fucking challenge, and I <em>love</em> my job.)</p>
<p><q class="center">More platforms means more places to reach our community</q></p>
<p>And there&rsquo;s yet another big shift underway, one which we are still evolving to address: that of <em>community</em> in a multi-platform, multi-device world. A site on Chorus is actually referred to as a &#8220;community,&#8221; and collections of communities are known as &#8220;networks.&#8221; That was intentional, and reflects core beliefs going back to the early days of <em>SB Nation</em> and <em>The Verge</em> about how a brand (n&eacute;e publisher) was expected to operate. We weren&rsquo;t &mdash; we <em>aren&rsquo;t </em>&mdash; designing systems where an audience passively consumes our content, but are inviting them in to talk and share and push back and expand. More platforms means more places to publish; it also means more places to reach that community, more places for those discussions to happen, more opportunities for amazing connections to be made. And, alas, many more vectors for abuse.</p>

<p>Neither <em>The Verge</em> nor Vox Media generally are the only ones facing this problem, of course, but given that our own platform&rsquo;s foundation takes community as a critical ingredient, we have an obligation to face it head-on. Even more importantly, the very concept of &#8220;community&#8221; has changed dramatically in recent years, both with the arrival of significant numbers of orchestrated and persistent harassment campaigns across every platform, and with a seemingly unending election cycle that has made public expressions of white supremacy and misogyny commonplace. This, maybe more than anything, is why our own platform remains so important to what we do: it&rsquo;s where we have the biggest opportunity to really connect with our audience, to build relationships that go deeper than likes, and to cultivate a space where more people can safely talk about the news or tech or sports.</p>

<p>As we continue to evolve Chorus, no other challenge we face is harder than this one. But then no other challenge is more important either.</p>
						]]>
									</content>
			
					</entry>
			<entry>
			
			<author>
				<name>Mandy Brown</name>
			</author>
			
			<title type="html"><![CDATA[Byron the bulb: how the velocity of journalism is changing]]></title>
			<link rel="alternate" type="text/html" href="https://www.theverge.com/2014/8/18/6030921/byron-the-bulb-how-the-velocity-of-journalism-is-changing" />
			<id>https://www.theverge.com/2014/8/18/6030921/byron-the-bulb-how-the-velocity-of-journalism-is-changing</id>
			<updated>2014-08-18T12:58:17-04:00</updated>
			<published>2014-08-18T12:58:17-04:00</published>
			<category scheme="https://www.theverge.com" term="Features" /><category scheme="https://www.theverge.com" term="Report" />
							<summary type="html"><![CDATA[As part of Verge Hack Week, we&#8217;ve invited great minds from around Vox Media to contribute their thoughts on the future of everything &#8212; from food to fashion to the written word. In this installment, we welcome senior product manager Mandy Brown, co-founder of Editorially, which joined the Vox team earlier this year. In Thomas [&#8230;]]]></summary>
			
							<content type="html">
											<![CDATA[

						
<figure>

<img alt="" data-caption="" data-portal-copyright="" data-has-syndication-rights="1" src="https://platform.theverge.com/wp-content/uploads/sites/2/chorus/uploads/chorus_asset/file/14811551/verge_hackweek_filler_img.0.0.1408410467.jpg?quality=90&#038;strip=all&#038;crop=0,0,100,100" />
	<figcaption>
		</figcaption>
</figure>
<div class="label"> <div><a target="_blank" href="http://www.theverge.com/label/verge-hack-week-2014"><img src="https://platform.theverge.com/wp-content/uploads/sites/2/chorus/uploads/chorus_asset/file/658592/hackweek_badge.0.png" class="small" alt="Hack Week Badge" width="100%"></a></div> <p>As part of <a target="_blank" href="http://www.theverge.com/label/verge-hack-week-2014">Verge Hack Week</a>, we&#8217;ve invited great minds from around Vox Media to contribute their thoughts on the future of everything &mdash; from food to fashion to the written word. In this installment, we welcome senior product manager Mandy Brown, co-founder of Editorially, which <a href="http://product.voxmedia.com/2014/6/24/5837406/editorially-joins-vox-media">joined the Vox team earlier this year</a>.</p> </div>
<p>In Thomas Pynchon&rsquo;s famous and famously unreadable 1973 novel, <em>Gravity&rsquo;s Rainbow</em>, a short story about a sentient and immortal light bulb named Byron includes a moment when a technician is sent out to test Byron for irregularities. Wearing seven-inch spiked heels in order to extend her reach, she gently unscrews Byron from the sconce he&rsquo;s plugged into. At that moment, a hush goes out across the electrical grid, as every bulb everywhere &#8220;at something close to the speed of light,&#8221; knows what has happened.</p>

<p>Information traveling at the speed of light was largely fantastical in the time period in which the novel is set, though it&rsquo;s commonplace today. But as fast as we can distribute information, we are still figuring out how to <em>learn</em> from it at anything close to the speeds at which it can be conveyed.</p>
<p><!-- extended entry --></p><hr class="widget_boundry_marker hidden page_break"><p><q class="right">We can create and share information at speeds much faster than we can comprehend it</q></p>
<p>The past week&rsquo;s events in Ferguson hint at this: thousands of tweets a minute were shared from people on the ground and elsewhere, many conflicting with each other, reflecting entwined and complicated perspectives. Some information was false &mdash; both intentionally so and otherwise &mdash; but once distributed it bounced and careened across the network, often two steps ahead of any retraction. We can create and share information at speeds much faster than we can comprehend it.</p>

<p>The future &mdash; of news, of storytelling, of <em>knowing</em> &mdash; has to, in some way, address this. The methods by which we filter and evaluate and accumulate information need to be transparent and readily interrogated. Not because openness is a panacea &mdash; it isn&rsquo;t &mdash; but because knowing something is an iterative process which depends upon collaboration, and collaboration can&rsquo;t happen in a dark room.</p>

<p>Stories have traditionally been presented as final, fixed things. The paper that prints a story on the front page doesn&rsquo;t share the rough drafts, the corrections, the anxious notes to self, the agonizing over word choices (&#8220;should we call this person a &lsquo;looter&rsquo; or a &lsquo;protestor&rsquo;?&#8221;) that are part of that story coming together. Only if a change is deemed important enough, and only if it&rsquo;s decided upon after going to press, is any revision shared or explained. But we&rsquo;re long past the point where stories are published once (and only once), at only one time. Who&rsquo;s to say the revisions that happen <em>after</em> a certain point are any more important than the ones that came before? Who&rsquo;s to say that all of the decisions that went into that story aren&rsquo;t part of the story itself?</p>

<p>Why does a Wikipedia post reveal more about its creation than a story from the <em>New York Times</em>?</p>
<p><q class="center">A better future would open the comments writers and editors make with one another, and invite readers in</q></p>
<p>The basic tools are already here: version control and comments. But the former are oriented inward (and rarely, if ever, shared) and the latter are relegated to the pews: comments are for outsiders to make, and for writers and editors to defend. A better future would open the comments writers and editors make with one another, and invite readers in. (Here I&rsquo;ll add that my work at Editorially &mdash; and, now, Vox Media &mdash; has centered around laying the groundwork for this kind of open collaboration and experimentation.)</p>

<p>Byron&rsquo;s compatriots could only know one thing &mdash; that he was gone. Beyond that they were ignorant. We have an obligation to know considerably more about what&rsquo;s going on in the world, and we have the tools to participate in that knowledge coming together. What we don&rsquo;t have is a framework for seeing how disparate bits of information are gathered together into something more &mdash; for a way to share not only the story, but the mechanics of it. <em>Yet</em>.</p>
						]]>
									</content>
			
					</entry>
	</feed>
