<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digitalfishbowl</title>
	<atom:link href="http://digitalfishbowl.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalfishbowl.net</link>
	<description>A sea of thoughts.</description>
	<lastBuildDate>Sun, 29 Jan 2012 11:14:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How Do We Better Engage Using Social Media?</title>
		<link>http://digitalfishbowl.net/how-do-we-better-engage-using-social-media/</link>
		<comments>http://digitalfishbowl.net/how-do-we-better-engage-using-social-media/#comments</comments>
		<pubDate>Sun, 29 Jan 2012 05:35:21 +0000</pubDate>
		<dc:creator>joefish</dc:creator>
				<category><![CDATA[Ministry]]></category>

		<guid isPermaLink="false">http://digitalfishbowl.net/?p=14</guid>
		<description><![CDATA[How do we better engage with those who matter to our local campus movements, using social media (SM) tools? Before I go any further, those who matter: Involved students. Potentially involved students (including the lost). The University (university staff, other &#8230; <a href="http://digitalfishbowl.net/how-do-we-better-engage-using-social-media/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>How do we better engage with those who matter to our local campus movements, using social media (SM) tools?</p>
<p>Before I go any further, those who matter:</p>
<ul>
<li>Involved students.</li>
<li>Potentially involved students (including the lost).</li>
<li>The University (university staff, other clubs, our general reputation on campus, etc).</li>
<li>Donors.</li>
</ul>
<p>I&#8217;m not going to argue here why social media matters, that&#8217;s been done by many others. Some of the tensions I feel are:</p>
<ul>
<li>Students are using SM, and expect others to engage them with it.</li>
<li>As a man wearing many hats, I don&#8217;t always have the time to engage everybody listed above using SM.</li>
<li>I want our staff and involved students to engage others with SM; I need to demonstrate that to them.</li>
<li>Not all of our staff see the value in SM.</li>
<li>The “content” of my engagement isn&#8217;t the same for each group.</li>
</ul>
<p>Let&#8217;s simplify and assume for a moment that individual staff manage communication with their own donors well, which leaves the first three groups. Let&#8217;s also focus on three tools for now:</p>
<ul>
<li>Facebook.</li>
<li>Email.</li>
<li>Twitter.</li>
</ul>
<p>So, how do we effectively use these tools to engage effectively with these interest groups? Here are a few ideas:</p>
<ol>
<li>The content disseminated using each of these tools should be different. The same information repeated over different mediums isn&#8217;t effective.</li>
<li>Email is targeted towards those who are already involved, since they have to sign up to the list if they want it. We should be sending out regular (once a week) updates during the campus year.</li>
<li>Our involved students already use Facebook, and to some extent Twitter; why not get them to help with our campus Facebook and Twitter accounts? What if we chose a student volunteer once a week/fortnight who had permission to update our Facebook/Twitter?</li>
<li>A private Facebook group for our CSLs (Committed Student Leaders) could not only be used to help us engage with them, but also for them to engage with each other through the sharing of praise points and ideas, etc. I think this would be a huge win on a campus like Auckland where CSLs don&#8217;t necessarily see each other throughout the year.</li>
<li>Facebook status updates on our fan page and twitter accounts shouldn&#8217;t just be “come to this event” messages. This is where we can engage with other clubs and groups (comment on what they&#8217;re doing), encourage our students to be involved in the wider campus community, and communicate who we are to the lost, not yet involved students, university staff, etc.</li>
</ol>
<p>I&#8217;m particularly interested in your comments on ideas 3, 4 and 5 above, as well as other ideas you have. How can we better engage with those who matter to our local campus movements using SM tools?</p>
]]></content:encoded>
			<wfw:commentRss>http://digitalfishbowl.net/how-do-we-better-engage-using-social-media/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Hello Again</title>
		<link>http://digitalfishbowl.net/hello-again/</link>
		<comments>http://digitalfishbowl.net/hello-again/#comments</comments>
		<pubDate>Sun, 29 Jan 2012 05:17:15 +0000</pubDate>
		<dc:creator>joefish</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://digitalfishbowl.net/?p=8</guid>
		<description><![CDATA[I&#8217;ve decided to use this site as a blog for posts that don&#8217;t necessarily fit on josephgibbs.com. This includes ministry related posts that are better aimed at my fellow staff workers. I look forward to sharing some of my thoughts &#8230; <a href="http://digitalfishbowl.net/hello-again/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve decided to use this site as a blog for posts that don&#8217;t necessarily fit on <a href="http://www.josephgibbs.com">josephgibbs.com</a>. This includes ministry related posts that are better aimed at my fellow staff workers. I look forward to sharing some of my thoughts and discussing ideas with you.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitalfishbowl.net/hello-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

