<?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: How do you blog when your business has two separate audiences?	</title>
	<atom:link href="https://www.groovehq.com/blog/friday-qa-march-17-2017/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/friday-qa-march-17-2017</link>
	<description></description>
	<lastBuildDate>Sat, 16 Feb 2019 11:41:16 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>
		By: InnMind Community		</title>
		<link>https://www.groovehq.com/blog/friday-qa-march-17-2017#comment-883</link>

		<dc:creator><![CDATA[InnMind Community]]></dc:creator>
		<pubDate>Sat, 18 Mar 2017 06:28:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=769#comment-883</guid>

					<description><![CDATA[Thanks for this post, Alex! We have 4 different customer segments on innmind.com They are: startups, investors, corporations and experts. And we also had such a question some time ago on how to deal with specific content needs of each audience. Finally we came to the similar solution you proposed and started to prepare content to the different segments, having different editorial calendar for each of them. The only thing is that we didn&#039;t start 4 separate blogs, we combine all the content in one blog and classify it with tags and context menu. It works for us perfectly :)]]></description>
			<content:encoded><![CDATA[<p>Thanks for this post, Alex! We have 4 different customer segments on innmind.com They are: startups, investors, corporations and experts. And we also had such a question some time ago on how to deal with specific content needs of each audience. Finally we came to the similar solution you proposed and started to prepare content to the different segments, having different editorial calendar for each of them. The only thing is that we didn&#8217;t start 4 separate blogs, we combine all the content in one blog and classify it with tags and context menu. It works for us perfectly 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Scott Mitchell		</title>
		<link>https://www.groovehq.com/blog/friday-qa-march-17-2017#comment-885</link>

		<dc:creator><![CDATA[Scott Mitchell]]></dc:creator>
		<pubDate>Fri, 17 Mar 2017 16:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=769#comment-885</guid>

					<description><![CDATA[Our nonprofit has six (6!) different audiences that we need to engage. Part of our point of view is that these six disciplines are more similar than different -- and that they all will be more successful by taking an integrated, interdisciplinary approach to their jobs.

In other words, we are trying to make the case to 6 disciplines that they will be better off if they look at their job via our integrated point of view.

In the past, we took an approach that was something like, &quot;Hey, you are in discipline X ... so you&#039;re really gonna love our integrated point of view.&quot; All of our resources and communication were geared to someone who was sympathetic with our integrated point of view.

After reading this article, I wonder if we should take a more focused approach.

Perhaps we should have 7 publications. 

One for each discipline that shows that we understand their issues and how our integrated point of view can help. These discipline-specific publications would be something like 80% discipline-specific content / 20% integrated point of view content.

Then we can have our integrated point of view publication that is 80% integrated point of view content and maybe 20% discipline-specific content.

I suspect that the integrated point of view publication will still be the most active and voluminous. However, just by having some more discipline-specific publications, even if they are light, might make it easier for us to connect with our various audiences, and ultimately help them level up their performance.

Thanks again for another great article!]]></description>
			<content:encoded><![CDATA[<p>Our nonprofit has six (6!) different audiences that we need to engage. Part of our point of view is that these six disciplines are more similar than different &#8212; and that they all will be more successful by taking an integrated, interdisciplinary approach to their jobs.</p>
<p>In other words, we are trying to make the case to 6 disciplines that they will be better off if they look at their job via our integrated point of view.</p>
<p>In the past, we took an approach that was something like, &#8220;Hey, you are in discipline X &#8230; so you&#8217;re really gonna love our integrated point of view.&#8221; All of our resources and communication were geared to someone who was sympathetic with our integrated point of view.</p>
<p>After reading this article, I wonder if we should take a more focused approach.</p>
<p>Perhaps we should have 7 publications. </p>
<p>One for each discipline that shows that we understand their issues and how our integrated point of view can help. These discipline-specific publications would be something like 80% discipline-specific content / 20% integrated point of view content.</p>
<p>Then we can have our integrated point of view publication that is 80% integrated point of view content and maybe 20% discipline-specific content.</p>
<p>I suspect that the integrated point of view publication will still be the most active and voluminous. However, just by having some more discipline-specific publications, even if they are light, might make it easier for us to connect with our various audiences, and ultimately help them level up their performance.</p>
<p>Thanks again for another great article!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Nicholas Caplan		</title>
		<link>https://www.groovehq.com/blog/friday-qa-march-17-2017#comment-890</link>

		<dc:creator><![CDATA[Nicholas Caplan]]></dc:creator>
		<pubDate>Fri, 17 Mar 2017 15:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=769#comment-890</guid>

					<description><![CDATA[Great post. Do you think it makes sense for smaller startups to just start with one side? Or try to speak to both audiences?]]></description>
			<content:encoded><![CDATA[<p>Great post. Do you think it makes sense for smaller startups to just start with one side? Or try to speak to both audiences?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
