<?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>Acuity Solutions &#187; schedule</title>
	<atom:link href="http://acuitynv.com/tag/schedule/feed/" rel="self" type="application/rss+xml" />
	<link>http://acuitynv.com</link>
	<description>Sage Business Partner in Las Vegas, Nevada (Sage 100, Sage CRM, Sage HRMS, and Sage Fixed Assets)</description>
	<lastBuildDate>Sat, 18 May 2013 21:26:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Do You Publish Your Calendar?</title>
		<link>http://acuitynv.com/2012/04/18/do-you-publish-your-calendar/</link>
		<comments>http://acuitynv.com/2012/04/18/do-you-publish-your-calendar/#comments</comments>
		<pubDate>Thu, 19 Apr 2012 01:28:10 +0000</pubDate>
		<dc:creator>Brian Rice</dc:creator>
				<category><![CDATA[Make Your Business Better]]></category>
		<category><![CDATA[calendar]]></category>
		<category><![CDATA[meeting]]></category>
		<category><![CDATA[schedule]]></category>

		<guid isPermaLink="false">http://acuitynv.com/?p=2066</guid>
		<description><![CDATA[<p>Let&#8217;s put aside the argument for or against meetings for a moment. We may be closer to eliminating unnecessary meetings but we all still have schedules to manage. Because I want to eliminate questions of my availability and the associated email threads and phone tags, I choose to publish my calendar. I can use my [...]</p><p>The post <a href="http://acuitynv.com/2012/04/18/do-you-publish-your-calendar/">Do You Publish Your Calendar?</a> appeared first on <a href="http://acuitynv.com">Acuity Solutions</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Let&#8217;s put aside the argument for or against meetings for a moment. We may be closer to eliminating unnecessary meetings but we all still have schedules to manage.</p>
<p>Because I want to eliminate questions of my availability and the associated email threads and phone tags, I choose to <a title="Brian Rice Calendar" href="http://tungle.me/BrianRice" target="_blank">publish my calendar</a>. I can use my calendar to suggest available times for those that I want to meet with and those that want to meet with me know when I may or may not be available. Some users may be more transparent that I am &#8211; I only share regular business hours and only available times rather than a 24x7x365 view with all of my meeting details. Some might think that this is over-exposure and enables people that want to take advantage of your time by scheduling meetings at inopportune times of with little (or no) notice but one of the benefits of <a title="Tungle.me" href="http://tungle.me" target="_blank">this particular service</a> is that meetings are requested rather than posted directly &#8211; I maintain the ability to accept or decline any proposed meeting.</p>
<p>I find <a title="Comic for April 10, 2012" href="http://dilbert.com/strips/comic/2012-04-10" target="_blank">this strip</a> an argument for publishing my calendar. You may find it an argument against.</p>
<p><a href="http://dilbert.com/strips/comic/2012-04-10"><img class="alignleft" title="Comic for April 10, 2012" src="http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/100000/50000/7000/100/157161/157161.strip.gif" alt="Comic for April 10, 2012" width="640" height="199" /></a></p>
<p>The post <a href="http://acuitynv.com/2012/04/18/do-you-publish-your-calendar/">Do You Publish Your Calendar?</a> appeared first on <a href="http://acuitynv.com">Acuity Solutions</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://acuitynv.com/2012/04/18/do-you-publish-your-calendar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
