<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Conde Nast folds two magazines Elegant Bride and Modern Bride</title>
	<atom:link href="http://weddingmarketing.net/2009/10/05/conde-nasts-folds-magazines-elegant-bride-modern-bride/feed/" rel="self" type="application/rss+xml" />
	<link>http://weddingmarketing.net/2009/10/05/conde-nasts-folds-magazines-elegant-bride-modern-bride/</link>
	<description>Andy Ebon &#124; Wedding University ® &#124; 702~510~4938</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:39:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy Ebon</title>
		<link>http://weddingmarketing.net/2009/10/05/conde-nasts-folds-magazines-elegant-bride-modern-bride/comment-page-1/#comment-755</link>
		<dc:creator>Andy Ebon</dc:creator>
		<pubDate>Tue, 06 Oct 2009 20:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://weddingmarketing.net/blog/?p=4333#comment-755</guid>
		<description>Jeff,

I have a theory that &#039;times of prosperity&#039; allow for all kinds of excesses and inefficiency.

In this case, when the economy contracted in a big way, the bloated nature of the &lt;strong&gt;Conde Nast&lt;/strong&gt;wedding publication model became apparent.

In a different market, look at the contraction that &lt;strong&gt;Starbucks&lt;/strong&gt; made, within the last year. They shut down almost 1000 stores (I think that number is pretty close). They had been opening a new store at incredible speed. They were popping up like mushrooms. Suddenly, a huge cutback.

There are many examples like these to choose from. Better to reframe the business model or cut out unprofitable areas than have to fold up completely, for lack of doing so.

Andy</description>
		<content:encoded><![CDATA[<p>Jeff,</p>
<p>I have a theory that &#8216;times of prosperity&#8217; allow for all kinds of excesses and inefficiency.</p>
<p>In this case, when the economy contracted in a big way, the bloated nature of the <strong>Conde Nast</strong>wedding publication model became apparent.</p>
<p>In a different market, look at the contraction that <strong>Starbucks</strong> made, within the last year. They shut down almost 1000 stores (I think that number is pretty close). They had been opening a new store at incredible speed. They were popping up like mushrooms. Suddenly, a huge cutback.</p>
<p>There are many examples like these to choose from. Better to reframe the business model or cut out unprofitable areas than have to fold up completely, for lack of doing so.</p>
<p>Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff James, Bridaluxe</title>
		<link>http://weddingmarketing.net/2009/10/05/conde-nasts-folds-magazines-elegant-bride-modern-bride/comment-page-1/#comment-754</link>
		<dc:creator>Jeff James, Bridaluxe</dc:creator>
		<pubDate>Tue, 06 Oct 2009 15:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://weddingmarketing.net/blog/?p=4333#comment-754</guid>
		<description>I suppose this news shouldn&#039;t come as a total surprise given that Condé Nast had already rolled the ModernBride.com and ElegantBride.com websites into a single Brides.com operation.

I am left wondering why it ever made sense at all for one publisher to own three titles in the same vertical – especially since there appeared to be such little brand/editorial differentiation.

Jeff</description>
		<content:encoded><![CDATA[<p>I suppose this news shouldn&#8217;t come as a total surprise given that Condé Nast had already rolled the ModernBride.com and ElegantBride.com websites into a single Brides.com operation.</p>
<p>I am left wondering why it ever made sense at all for one publisher to own three titles in the same vertical – especially since there appeared to be such little brand/editorial differentiation.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
</channel>
</rss>

