<?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>Prialto</title>
	<atom:link href="http://blog.prialto.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.prialto.com</link>
	<description>Personal Outsourcing</description>
	<lastBuildDate>Thu, 02 Feb 2012 18:07:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Scheduling with Success</title>
		<link>http://blog.prialto.com/2012/02/02/schedulingwithsuccess/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=schedulingwithsuccess</link>
		<comments>http://blog.prialto.com/2012/02/02/schedulingwithsuccess/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 17:55:10 +0000</pubDate>
		<dc:creator>rkaldani</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[calendar management]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[Personal Assistant]]></category>
		<category><![CDATA[personal productivity]]></category>
		<category><![CDATA[Productivity tools]]></category>
		<category><![CDATA[Remote Personal Assistant]]></category>
		<category><![CDATA[Sales Productivity]]></category>
		<category><![CDATA[Time Management]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=687</guid>
		<description><![CDATA[TweetHaving a human scheduling appointments on your behalf sets you apart from the crowd more than ever in a world of web-published calendars and do-it-all mobile devices Technology-powered tools now available for scheduling are amazing: Web apps like Tungle.me and timebridge provide slick functionality for publishing your calendar to the world of people who’d like [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton687" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2012%2F02%2F02%2Fschedulingwithsuccess%2F&amp;via=Rkaldani&amp;text=Scheduling%20with%20Success&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2012%2F02%2F02%2Fschedulingwithsuccess%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p><strong>Having a human scheduling appointments on your behalf sets you apart from the crowd more than ever in a world of web-published calendars and do-it-all mobile devices</strong></p>
<p>Technology-powered tools now available for scheduling are amazing:</p>
<ul>
<li>Web apps like <a href="http://www.tungle.me/Home/">Tungle</a><a href="tungle.me">.me</a> and <a href="http://timebridge.com/">timebridge</a> provide slick functionality for publishing your calendar to the world of people who’d like to select a time to meet with you</li>
<li>Apple’s <a href="http://www.apple.com/iphone/features/siri.html">Siri</a> takes key scheduling steps on your voice command without you even having to click or swipe</li>
</ul>
<p>But simply saying “I’ll have my smart phone call your smart phone,” has some key limitations.</p>
<p>Relying entirely on these tools naively implies a business environment in which all parties have an equal interest in meeting.  Your most important contacts will appreciate a more personal touch, and human input is critical to navigating the art in that the back-and-forth of “scheduling Ping-Pong,”</p>
<p>So how do you empower your remote admin in the complex and subtle game of business etiquette that starts when two busy people decide to meet and then need to lock down place and time?</p>
<p><strong>It&#8217;s not “just” scheduling</strong></p>
<p>Prospective Prialto members will sometimes say they “<em>only</em>” need help with scheduling, as if to imply this is a simple, commodity task.</p>
<p>They are right when the playing field is even and the parties looking to meet have plenty of time. Then it really is simply a matter of finding the next open spot on the calendar. The algorithm is indeed simple, and technology alone may get it done.</p>
<p>Those experienced in leveraging a professional scheduler will more often understand how much time gets consumed. They also know that there is an art to navigating through the complexity of how to time reminders, decide on where to meet and at what time.</p>
<p><strong>Three tactics for getting it right</strong></p>
<p>So how does one best leverage their assistant to track down targets and get you the right meetings in the right place and at the right time?</p>
<p><strong>1) </strong><strong>Start slow in the beginning to go fast later: </strong></p>
<p>Many tech equipped, near autonomous knowledge workers have forgotten this basic management need, but there is always a tradeoff between the ease of getting something done yourself today verses taking the time to enable someone else to take it off your hands later.  One should never offload key tasks to a new employee without great care. True, you might as well do a task yourself if you will always have to micro mange and explain it to your helper with painful specificity. But micro managing your new scheduler in the beginning is totally appropriate. Take the time to:</p>
<ul>
<li>Explain the etiquette of your business and client base</li>
<li>Download the places you like to meet for which kinds of meetings</li>
<li>Download the names of your VIPs, the key clients and/or personal contacts that get the highest priority</li>
<li>Sensitize your assistant on how to discern in your email exchanges the importance of a contact and how that should translate into how a meeting is scheduled</li>
</ul>
<p>To do all this, you ought to initially watch every email your assistant sends out and then set times to go over and give feedback on how they can be improved. Doing this for just a few days, will quickly yield great time savings and peace-of-mind.</p>
<p><strong>2) </strong><strong>Surface key information to the top of long email threads. </strong></p>
<p>A good assistant may successfully disentangle long and complex email threads to decipher what you want done on an email, even if you simply copy him in with no instruction. But it may require a lot of unnecessary energy and time.</p>
<p><strong>A couple of simple specifics as you CC your assistant will save lots of time and energy.</strong></p>
<p>&nbsp;</p>
<p><strong>Here’s an email that works well:</strong></p>
<p><strong><a href="http://blog.prialto.com/wp-content/uploads/2012/02/Screen-Shot-2012-02-01-at-5.37.14-PM.png"><img class="alignnone size-full wp-image-710" title="Screen Shot 2012-02-01 at 5.37.14 PM" src="http://blog.prialto.com/wp-content/uploads/2012/02/Screen-Shot-2012-02-01-at-5.37.14-PM.png" alt="" width="625" height="522" /></a><br />
</strong></p>
<p><strong>Here is an e-mail that does NOT work well:</strong></p>
<p><a href="http://blog.prialto.com/wp-content/uploads/2012/02/Screen-Shot-2012-02-01-at-5.41.30-PM.png"><img class="alignnone size-full wp-image-711" title="Screen Shot 2012-02-01 at 5.41.30 PM" src="http://blog.prialto.com/wp-content/uploads/2012/02/Screen-Shot-2012-02-01-at-5.41.30-PM.png" alt="" width="574" height="641" /></a></p>
<p><strong>Develop a scheduling vernacular with your PA</strong></p>
<p>Maintaining positive client relationships with a PA in the middle requires sensitivity. You can’t meet with everyone all the time. You have to prioritize and, while most everyone understands this need, you want to avoid inadvertently insulting even a lower priority contact.</p>
<p><strong>Develop special words that you can place in the kind of email copy above to help your PA prioritize on your behalf.</strong></p>
<p><strong>For example:</strong></p>
<ul>
<li>To indicate that you indeed want to meet while tactfully letting your assistant know that this meeting is not the highest priority, say things like “please schedule a coffee” or “please schedule for this month” <strong> </strong></li>
<li>To indicate that a contact, Charlie, is a high priority client who you want to defer to, say something like “please schedule at place and time that works well for Charlie <strong> </strong></li>
</ul>
<p><strong>Oh, and one more thing</strong></p>
<p><a href="http://blog.prialto.com/2011/12/04/the-1-sales-mistake-turning-your-sales-stars-into-data-clerks/">See Andy Mowat’s article on how to leverage your assistant to do CRM right.</a> If you are looking to have an assistant help you schedule, you probably are tracking lots of contacts. A CRM and a good CRM process can be amazing tools with which to collaborate with your assistant and track key interactions. But if you’re a relationship person, you probably don’t want to spend too much time meticulously inputting data. Configure your CRM to work with your assistant.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><strong><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2012/02/02/schedulingwithsuccess/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scientific proof you can’t handle more SaaS/Mobile applications</title>
		<link>http://blog.prialto.com/2012/01/22/scientificproof/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=scientificproof</link>
		<comments>http://blog.prialto.com/2012/01/22/scientificproof/#comments</comments>
		<pubDate>Sun, 22 Jan 2012 19:48:17 +0000</pubDate>
		<dc:creator>amowat</dc:creator>
				<category><![CDATA[Productivity tools]]></category>
		<category><![CDATA[Applications]]></category>
		<category><![CDATA[Dunbar's Number]]></category>
		<category><![CDATA[Pinch Media]]></category>
		<category><![CDATA[Producitivty]]></category>
		<category><![CDATA[SaaS]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=674</guid>
		<description><![CDATA[TweetLove new tools but don’t have the time? If you are like me, every time a friend suggests a new cool online tool (SaaS software, web application, or mobile app), you quickly write it down to research later.  But, inevitably, after taking a quick peek at the website, that interest quickly fades. I used to [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton674" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F22%2Fscientificproof%2F&amp;text=Scientific%20proof%20you%20can%E2%80%99t%20handle%20more%20SaaS%2FMobile%20applications&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F22%2Fscientificproof%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p><strong>Love new tools but don’t have the time?</strong></p>
<p>If you are like me, every time a friend suggests a new cool online tool (SaaS software, web application, or mobile app), you quickly write it down to research later.  But, inevitably, after taking a quick peek at the website, that interest quickly fades.</p>
<p>I used to kick myself for not adopting every new tool I heard about.  I constantly asked myself, “Bob found this tool useful and he appears more productive that I am, why can’t I adopt it?”</p>
<p><strong>There is a scientific reason</strong></p>
<p>The simple scientific fact is that, like social relationships, there are only so many SaaS applications you can effectively manage on a regular basis.  In 1992, British anthropologist <a href="http://en.wikipedia.org/wiki/Dunbar%27s_number">Robin Dunbar</a>, studied social networks and found that a human can maintain ~150 stable relationships.</p>
<p><a href="http://www.plosone.org/article/fetchObjectAttachment.action;jsessionid=0995028AD922252DF7CEE86B1C4841BF.ambra02?uri=info%3Adoi%2F10.1371%2Fjournal.pone.0022656&amp;representation=PDF">Further studies</a> have shown that Dunbar’s Number remains consistent, even with the advent of social networks.  As another data point, <a href="http://techcrunch.com/2009/02/19/pinch-media-data-shows-the-average-shelf-life-of-an-iphone-app-is-less-than-30-days/">Pinch Media</a>, which tracks iPhone app usage, has shown that 30-days after an app is purchased, less than 5 percent of buyers continue to use it.</p>
<p><strong>Want the power of these applications without the effort?</strong></p>
<p>Through our team’s 100,000+ hours supporting Prialto members, we have observed the practices of senior executives and sales teams.   We estimate that a busy executive can manage 6 to 8 applications on a consistent basis.   However, there is a second tier of apps that executives need functionality from but can’t spare the time to use (i.e. expense management, CRM, social media monitoring..)</p>
<p>If you are like us and enjoy learning about new applications but fear adding another one to your processes, please take a minute to share:</p>
<ul>
<li>The top apps you use regularly</li>
<li>Apps you would like to get value out of without using/learning</li>
</ul>
<p style="text-align: center;"><strong><a href="https://www.surveymonkey.com/s/prialtocorollary">Productivity Applications 1-Minute Survey</a></strong></p>
<p><strong>About Prialto</strong></p>
<p>Helping executives manage web-based applications is at the core of Prialto’s mission to deliver a turnkey productivity solution.   Prialto has built a database of applications and best practices for executive productivity.  If you would like to learn how you and your team can leverage global assistants to increase productivity, contact us at <a href="http://www.prialto.com/">www.prialto.com</a> or 866.910.8440</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2012/01/22/scientificproof/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Which Edition of Salesforce Should I Get?</title>
		<link>http://blog.prialto.com/2012/01/18/whichsalesforceedition/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=whichsalesforceedition</link>
		<comments>http://blog.prialto.com/2012/01/18/whichsalesforceedition/#comments</comments>
		<pubDate>Thu, 19 Jan 2012 00:26:45 +0000</pubDate>
		<dc:creator>amowat</dc:creator>
				<category><![CDATA[Sales Strategies]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[Salesforce]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=610</guid>
		<description><![CDATA[TweetA great post from our friends at StarrForce: Which Edition of Salesforce Should I Get? You’d like to get the edition that best meets your needs without buying more than you need. You’re looking for the proper balance between price and requirements. Want a simple explanation of which Salesforce Edition to get? Here you go: [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton610" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F18%2Fwhichsalesforceedition%2F&amp;text=Which%20Edition%20of%20Salesforce%20Should%20I%20Get%3F&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F18%2Fwhichsalesforceedition%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><h2><em><strong>A great post from our friends at <a href="http://starrforce.com/">StarrForce</a>:</strong></em></h2>
<h3><strong><a rel="attachment wp-att-5366" href="http://blog.prialto.com/?attachment_id=5366"><img class="aligncenter" title="Which Edition of Salesforce Should I Get" src="http://starrforce.com/wp-content/uploads/2011/09/Fotolia_17692026_XS.jpg" alt="Which Edition of Salesforce Should I Get" width="326" height="217" /></a></strong></h3>
<p><strong>Which Edition of Salesforce Should I Get?</strong></p>
<p>You’d like to get the edition that best meets your needs without buying more than you need.</p>
<p>You’re looking for the proper balance between price and requirements.</p>
<p><em>Want a simple explanation of which Salesforce Edition to get? Here you go:</em></p>
<p><strong>Why purchase Salesforce Professional Edition rather than Salesforce Group Edition?</strong></p>
<p>Salesforce Professional Edition does everything Group Edition does plus:<br />
1. Can support more than 10 users<br />
2. Offers mass email ability<br />
3. Supports customizable dashboards<br />
4. Has better support for AppExchange apps<br />
5. Supports role hierarchy/sharing model (translation: in Group Edition there is no security among users, everyone sees all records)<br />
6. Supports products, marketing campaigns, and offline edition<br />
7. Supports the Mobile client</p>
<p>So if you don’t need one or more of these additional capabilities you’ll be fine with Group Edition.</p>
<p>If you haven’t already tried Salesforce you can get a free trial by <a href="http://starrforce.com/salesforce-implementation/salesforce-free-trial/?svpage=signupform&amp;sid=3d79dea9183caa5e16df88446efdfa85" target="_blank">clicking here.</a></p>
<p><strong>Why purchase Salesforce Enterprise Edition rather than Salesforce Professional Edition?</strong></p>
<p>Salesforce Enterprise Edition does everything Professional Edition plus has:<br />
1. Profiles (the ability to support multiple departments)<br />
2. API integration<br />
3. Partner Portal support<br />
4. Custom workflow, including assignment rules and auto escalation rules<br />
5. Team selling<br />
6. Record types<br />
7. Customer portal support<br />
8. APEX code</p>
<p>So if you don’t need one or more of these additional capabilities you’ll be fine with Professional Edition.</p>
<p><strong>Note that its easy to upgrade your edition of Salesforce but not to downgrade:</strong><br />
1. Salesforce will allow you to upgrade your license type at any time.<br />
2. But you can only downgrade a license type when your contract expires.</p>
<p>Want to know more about Salesforce Editions and licensing? Check out this post from the StarrForce blog <a href="http://starrforce.com/2010/12/comparsion-of-salesforce-and-force-com-editions/" target="_blank">Salesforce license types.</a></p>
<p><strong>Need hep implementing Salesforce? Check out  <a href="http://starrforce.com/services/quick-start-packages-3/" target="_blank">Quick Start packages</a> from StarrForce for more information.</strong></p>
<p>Have a Salesforce question? Get free support: Twitter @starrforce</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2012/01/18/whichsalesforceedition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Be interested in others so they can be interested in you</title>
		<link>http://blog.prialto.com/2012/01/10/be-interested-others-so-they-can-be-interested-in-you/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=be-interested-others-so-they-can-be-interested-in-you</link>
		<comments>http://blog.prialto.com/2012/01/10/be-interested-others-so-they-can-be-interested-in-you/#comments</comments>
		<pubDate>Tue, 10 Jan 2012 14:39:45 +0000</pubDate>
		<dc:creator>Eric Taussig</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=603</guid>
		<description><![CDATA[TweetThe professional services challenge If you are a management consultant, venture capitalist, lawyer, accountant, IT firm, executive coach or any other service professional, you face the same challenge: How do you balance execution and client acquisition? And, if you’re good at what you do, you in all likelihood are a better practitioner than salesperson. It’s [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton603" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F10%2Fbe-interested-others-so-they-can-be-interested-in-you%2F&amp;text=Be%20interested%20in%20others%20so%20they%20can%20be%20interested%20in%20you&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F10%2Fbe-interested-others-so-they-can-be-interested-in-you%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p><strong>The professional services challenge</strong></p>
<p>If you are a management consultant, venture capitalist, lawyer, accountant, IT firm, executive coach or any other service professional, you face the same challenge: How do you balance execution and client acquisition?</p>
<p>And, if you’re good at what you do, you in all likelihood are a better practitioner than salesperson. It’s the love of your craft that got you into the business, not your love for sales.  How are you supposed to build a relationship business with cold-calling techniques?  There has to be a better way!</p>
<p><strong>The initial dead end </strong></p>
<p>We recently worked with an executive coach who was having challenges in scaling his practice. His clients love him, but direct referrals alone couldn’t grow his business quickly enough.</p>
<p>The coach – I’ll call him Jim – spoke with Prialto about having us call target lists he was generating from his professional networks, but we advised him that the approach he’d outlined would not work. Three months later Jim came back to us: “Eric,” he said, I have a very professional productivity assistant (“PA”). She’s great. But I’ve NOT gotten one meeting arranged by her in three months. This is not working for me, and I need to change something.”</p>
<p>The problem wasn’t that cold calls don’t work, but that the premise for the calls was wrong. Jim’s PA was essentially making “cold calls” to strangers, and asking them to meet and talk with Jim about his practice. While nicely worded, it was clear to these strangers that Jim would be coming to talk about himself and to pitch work.</p>
<p>Unsurprisingly, they had no interest.  To cap it off, Jim himself didn’t enjoy direct selling.</p>
<p><strong>From a chore to a passionate calling</strong></p>
<p>We advised Jim to find something that he enjoyed in his work and focus his meetings and outreach around this instead. Jim had a passion for the problems that executives face and the more he learned about them the more valuable he became to his larger customer base.</p>
<p>Jim started a simple blog about these issues. His first postings were based on his, current clients. With their permission, he took a few thorny subjects he had helped clients on, scrubbed the personal information, and wrote about them in a clean direct format.</p>
<p>His PA then began calling the same list that had been ignoring Jim’s meeting requests and asking if Jim could interview them for his blog. Jim, the PA explained, wanted to hear about one key challenge and what they’d done to overcome them.</p>
<p><strong>A constant flow of meetings</strong></p>
<p>Literally within days of this tactical change, Jim was getting receptive meetings with people in his target market. Most importantly, the meetings were enjoyable for both parties. Jim got to learn about a subject he found intrinsically interesting, up –close executive issues. The people he met with got to talk about almost everyone’s favorite subject: Themselves.</p>
<p>These first couple of meetings, turned into a constant and predictable flow of appointments. Over several months, several of the executives that Jim interviewed asked more about what he did when he was not interviewing for and writing his blog. And a few of these curious executives became clients.</p>
<p>What’s critical is that this was no ruse. Jim was not pretending to want to interview these folks. Jim truly enjoyed the subject. He was passionate about it and this came through.</p>
<p>By being genuinely interested in these executives, they became interested in working with him.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2012/01/10/be-interested-others-so-they-can-be-interested-in-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>9 Simple Tactics to Optimize Your CRM</title>
		<link>http://blog.prialto.com/2012/01/02/ninesimplecrmtactics/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ninesimplecrmtactics</link>
		<comments>http://blog.prialto.com/2012/01/02/ninesimplecrmtactics/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 17:01:15 +0000</pubDate>
		<dc:creator>amowat</dc:creator>
				<category><![CDATA[Sales Strategies]]></category>
		<category><![CDATA[Adoption]]></category>
		<category><![CDATA[CRM]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=595</guid>
		<description><![CDATA[TweetPrialto works closely with sales teams to offload valuable recurring tasks and allow them to better focus on their clients. Our focus on making executive more productive within their current systems has allowed us to see what works universally well across organizations. When prialto starts working with a new client, we often find that a [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton595" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F02%2Fninesimplecrmtactics%2F&amp;text=9%20Simple%20Tactics%20to%20Optimize%20Your%20CRM&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2012%2F01%2F02%2Fninesimplecrmtactics%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p>Prialto works closely with sales teams to offload valuable recurring tasks and allow them to better focus on their clients. Our focus on making executive more productive within their current systems has allowed us to see what works universally well across organizations.</p>
<p>When prialto starts working with a new client, we often find that a company’s CRM design itself is a barrier to adoption.   Just like Microsoft Word, CRM systems have incredible functionality, most of which goes unused.  We recommend making a system as simple as possible and putting thought into each field tracked.  Below are a few best practices we have observed through our team’s 100,000+ hours supporting prialto members.</p>
<ol>
<li><strong>Turn off unused tabs: </strong> There are a number of tabs your team likely isn’t using (chatter, files, getting started…) which can be turned off to reduce complexity.</li>
<li><strong>Clean up page layouts: </strong> Most companies use standard page layouts with little customization.  Your team is likely not using many of these fields (i.e. fax #, address, home phone, birthday&#8230;) which should be removed.</li>
<li><strong>Leverage structured data:</strong> Most standard CRM fields are text-based.  The value of data increases dramatically with structured fields using pick-lists (i.e. client status, industry…)</li>
<li><strong>Add strategic custom fields: </strong> Here are a several custom fields we find quite useful:  <em><span style="text-decoration: underline;">Next contact date</span></em><strong>:</strong> Typically this is the most valuable field in our members CRMs.  Every follow-up is driven off of this field.  <span style="text-decoration: underline;"><em>Referral source</em><strong>:</strong></span> Rather than just tracking lead source, we also suggest linking the record to the contact who provided the referral.   <span style="text-decoration: underline;"><em>Value</em></span><strong>:</strong> Many of our members rank each company and contact in their CRM to allow for quick prioritization.</li>
<li><strong>Focus on relevant data:</strong> A number of lists throughout your CRM system can be customized to allow your team to focus on key data to your business.</li>
<li><strong>Optimize views: </strong>Each module can have customized views to allow your team to leverage your data and quickly prioritize accounts.</li>
<li><strong>De-duplicate data:</strong> As companies grow, data duplication becomes a serious issue.  Setup your system early to flag and eliminate duplicates.</li>
<li><strong>Copy all communication to your CRM: </strong>To improve communication across teams, most CRMs allow you to easily add emails to the system by BCC’ing a specific address.</li>
<li><strong>Integrate a support team:</strong> Requiring your sales team to enter data themselves, diverts their attention from clients.  Prialto works with sales teams to offload tasks such as data entry and prospect research.   To optimize collaboration, we suggest adding additional fields to track status and priority.</li>
</ol>
<p>If you are exploring how to optimize your CRM, we would be happy to provide referrals to CRM consultants we know and trust.  And, if you want to optimize your sales team itself, visit <a href="http://www.prialto.com/">www.prialto.com</a> to learn more or call us at 866.910.8440.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2012/01/02/ninesimplecrmtactics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting to the first million dollars in sales</title>
		<link>http://blog.prialto.com/2011/12/26/gettingtothefirstmillion/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=gettingtothefirstmillion</link>
		<comments>http://blog.prialto.com/2011/12/26/gettingtothefirstmillion/#comments</comments>
		<pubDate>Tue, 27 Dec 2011 02:00:43 +0000</pubDate>
		<dc:creator>amowat</dc:creator>
				<category><![CDATA[Sales Strategies]]></category>
		<category><![CDATA[sales tactics]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=569</guid>
		<description><![CDATA[TweetUnless you are one of the few companies with an inherent viral model, building a sales team takes a lot of work.  We have seen founders and CEOs make two consistent mistakes (in previous careers we were guilty of these ourselves): Trying to hire a sales team before you prove your model yourself Creating a [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton569" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2011%2F12%2F26%2Fgettingtothefirstmillion%2F&amp;text=Getting%20to%20the%20first%20million%20dollars%20in%20sales&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2011%2F12%2F26%2Fgettingtothefirstmillion%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p>Unless you are one of the few companies with an inherent viral model, building a sales team takes a lot of work.  We have seen founders and CEOs make two consistent mistakes (in previous careers we were guilty of these ourselves):</p>
<ul>
<li>Trying to hire a sales team before you prove your model yourself</li>
<li>Creating a commission plan before a sales model</li>
</ul>
<p>As you build your sales team, here are a few simple tips to maximize your chance of success:</p>
<ul>
<li><strong>Do-it-yourself:</strong> “Good sales people don’t go to companies with un-proven sales models”.  We all think our product / service is the best and should sell itself.  But until you know the pitch, objections, pricing strategy… you shouldn’t turn this over to a salesperson who lacks the authority necessary to fix issues uncovered in the sales process.  Even if you could attract a sales rock-star at this stage, they likely would fail.  So roll-up your sleeves and start selling.</li>
<li><strong>Hire a Closer First:</strong> Once you have begun to figure out the sales model, don’t immediately turn it over to someone else.  Start building your sales team by bringing in people to close the leads you generate.</li>
<li><strong>Pay Bonuses, Not Commissions: </strong>Resist the urge to pay people on a commission basis until the sales model is refined.  You need to know your team can hit targets consistently before tying them into a commission model.  If you adopt a commission model too soon, you are apt to spend your time managing compensation expectations rather than improving the sales model.  Instead, focus on discretionary bonuses for the time being.</li>
<li><strong>Build Your Marketing Funnel:</strong> Before your sales model is finished, you need to develop a clear lead generation model.  This doesn’t require cold-calling and there are a number of great guides out there (i.e. a <a href="http://www.amazon.com/Predictable-Revenue-Business-Practices-Salesforce-com/dp/0984380213">recent book by our friend Aaron Ross</a>)</li>
<li><strong>Create a Simple Commission Plan: </strong> Now, finally you are ready for a commission plan.  But, make it simple – you should be able to track it on the back of a napkin, not a whiteboard.</li>
</ul>
<p>We wish you success as you grow your company.  Getting to the first million dollars in sales is the first challenge and we encourage you to focus on sales rather than sales compensation.  As you scale, sales productivity will become a challenge and opportunity.  For more information on how prialto helps sales teams become more productive, visit <a href="http://www.prialto.com/">www.prialto.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2011/12/26/gettingtothefirstmillion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Top Sales Mistake:  Turning Your Sales Stars Into Data Clerks</title>
		<link>http://blog.prialto.com/2011/12/04/topsalesmistake/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=topsalesmistake</link>
		<comments>http://blog.prialto.com/2011/12/04/topsalesmistake/#comments</comments>
		<pubDate>Mon, 05 Dec 2011 05:47:43 +0000</pubDate>
		<dc:creator>amowat</dc:creator>
				<category><![CDATA[Sales Productivity]]></category>
		<category><![CDATA[Adoption]]></category>
		<category><![CDATA[CRM]]></category>
		<category><![CDATA[Salesforce]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=560</guid>
		<description><![CDATA[TweetOver the past ten years, I have rolled out CRM systems at four different companies and have personally witnessed the power of CRM to: Improve management of customer and prospect relationships Provide better sales visibility Improve communication across a sales team However, I also know full-well the statistics on CRM.  Gartner estimates that over 60% [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton560" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2011%2F12%2F04%2Ftopsalesmistake%2F&amp;text=The%20Top%20Sales%20Mistake%3A%20%20Turning%20Your%20Sales%20Stars%20Into%20Data%20Clerks&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2011%2F12%2F04%2Ftopsalesmistake%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p>Over the past ten years, I have rolled out CRM systems at four different companies and have personally witnessed the power of CRM to:</p>
<ul>
<li>Improve management of customer and prospect relationships</li>
<li>Provide better sales visibility</li>
<li>Improve communication across a sales team</li>
</ul>
<p>However, I also know full-well the statistics on CRM.  Gartner estimates that over 60% of CRM implementations fail after the go-live date.    I recently spent an evening talking about sales productivity with a leading sales rep for a Bain Capital portfolio company.  What I heard shouldn’t surprise anybody but hopefully it is a wakeup call.</p>
<ul>
<li><strong>Hunters aren’t built to enter data: </strong>We all know successful salespeople are wired differently.  But, in a quest to fulfill the promise of new systems, we try to turn our team into desk-jockeys.  This sales rep shared with me that his entire team feels like “… well paid clerks.” and that he “… didn’t get into sales to do admin.”</li>
<li><strong>Sales teams don’t see the promise of CRM: </strong>Star sales people see sales as an art and CRM as ‘big brother’.  Like the sales rep I talked to they believe, “I hit my numbers and don’t see the reason to document in Salesforce just so they can monitor me.”</li>
<li><strong>Sales training isn’t working: </strong>Despite the investment in systems, stars prefer to be lone wolfs.  With few established processes, sales teams end up with a few rock stars and a ton of new sales reps struggling to figure out the ropes.   This sales rep shared with me, “Our company is a total mess.  There is a huge learning curve for new reps and we lose many of them quickly”</li>
</ul>
<p>No wonder that according to Forrester the average VP of sales lasts 18 months.  With a sales team that sees no value in the systems, the worst thing you can do is add more process.  So how can we stop this cycle and improve our sales productivity?  Here are two, not-so-revolutionary, ideas:</p>
<ul>
<li>Stop having your sales people enter data they don’t see as valuable</li>
<li>Free your salespeople up to focus on what they do best</li>
</ul>
<p>While these ideas sound simple, they take some effort to implement.  Here are a few basic steps you can take to get started:</p>
<ul>
<li><strong>Review your sales administration processes:</strong> Analyze each process to understand a) the level of specialized knowledge and b) the priority for your business</li>
<li><strong>Focus first on those processes easy to standardize: </strong>Processes such as CRM data entry, appointment setting, prospect research, lead and contact management, travel, expenses, and reporting are great places to start.</li>
<li><strong>Create a true sales support function:</strong> Inside sales and lead gen are not focused on increasing the productivity of your sales team.  They are measured by their own metrics.  To solve your sales challenges, you need to provide your sales reps with a support system.  We find the best way to achieve this is to integrate assistants into your sales team’s processes and track the impact on your reps productivity.</li>
<li><strong>Commit your organization to success: </strong> The benefits of freeing up your sales team to focus on sales can be powerful.  A study by McKinsey of a global manufacturer showed an average gain of 15% more time for selling and decreased cycle time for internal sales processes of 20%.    But, to realize the potential, an on-going commitment, technology platform, and training are required.</li>
</ul>
<p>Prialto (<a href="http://www.prialto.com/">www.prialto.com</a>) works with growing companies to focus their sales reps on key client interactions.  By integrating assistants with sales teams, Prialto helps improve sales productivity while, at the same time, providing better visibility into sales pipelines.  To discuss how we can help you re-engineer your sales team, contact us at <strong>866.910.8440</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2011/12/04/topsalesmistake/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One phone rule will save us all time</title>
		<link>http://blog.prialto.com/2011/11/22/one-phone-rule-will-save-us-all-time/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=one-phone-rule-will-save-us-all-time</link>
		<comments>http://blog.prialto.com/2011/11/22/one-phone-rule-will-save-us-all-time/#comments</comments>
		<pubDate>Tue, 22 Nov 2011 16:56:33 +0000</pubDate>
		<dc:creator>Eric Taussig</dc:creator>
				<category><![CDATA[Doing everything right]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=493</guid>
		<description><![CDATA[Tweet One simple cell phone etiquette rule will save us all many hours. You will recognize the context: Say you are driving north down Highway 101 from Palo Alto to San Francisco at about 3:00 PM on Friday afternoon. You dial your friend in New York and reach him as he is heading home to [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton493" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F22%2Fone-phone-rule-will-save-us-all-time%2F&amp;text=One%20phone%20rule%20will%20save%20us%20all%20time&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F22%2Fone-phone-rule-will-save-us-all-time%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]><br />
<mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --></p>
<p><!--[endif]--></p>
<p><!--[endif]--></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">One simple cell phone etiquette rule will save us all many hours.</span></p>
<p class="MsoNormal" style="line-height: normal;"><strong><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You will recognize the context: </span></strong></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">Say you are driving north down Highway 101 from Palo Alto to San Francisco at about 3:00 PM on Friday afternoon. You dial your friend in New York and reach him as he is heading home to rest before going out to dinner. He’s on the E Train.</span></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You are in the midst of an important discussion. And, then, just before he heads into Brooklyn Heights, he says “If I lose you going under the water, I’ll . . .” You hear silence, and, then, silence. . Gone! Lost connection, and who knows exactly what the last words were your friend heard?</span></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You wait for about how long you know it takes for the E Train to resurface on the other side of the East River. Here, then, is the sequence of events that follow:</span></p>
<ol>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You redial</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You hear a busy signal, and hang up</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You see a message waiting on your cell phone screen</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You are near certain it is from the friend you were just speaking with saying “tag, I&#8217;m trying to call you back,&#8221; so you redial again</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You think you are about to connect, but you hear the call waiting signal. You check your screen for the incoming number. Sure enough, it’s your friend calling you back again. You try to click over, but he’s already gone back to voice mail.</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You hit the red button several times to terminate any call left connected</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You wait for your friend to dial again, but nothing happens because now your friend is also waiting</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">You are both probably frustrated by now. You hit the green button again to dial, but now all the cells on Highway 101 are clogged with people planning their Friday evenings. Your call takes several minutes to get through and now you can hear that your friend is on the line with someone else.</span></li>
<li><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">“Forget it,” you think, “I’ll catch him tomorrow.”</span></li>
</ol>
<p class="MsoNormal" style="line-height: normal;"><strong><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">Who should call back and who should hold off?</span></strong></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">Here’s the etiquette:</span></p>
<p class="MsoNormal" style="line-height: normal;"><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">Don’t spend time guessing or presuming whose phone or location was responsible for the lost connection. That’s impossible for either party to know.</span></p>
<p class="MsoNormal" style="line-height: normal;"><em><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;">Whoever initiates the call should dial back, regardless.</span></em><span style="font-size: 12pt; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;"> It’s simple and straightforward. You’ll both always know who that is and you will avoid a lot of confusion and wasted dialing and waiting.</span></p>
<p class="MsoNormal">
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2011/11/22/one-phone-rule-will-save-us-all-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Taking emotion out of corporate email</title>
		<link>http://blog.prialto.com/2011/11/16/taking-emotion-out-of-corporate-email/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=taking-emotion-out-of-corporate-email</link>
		<comments>http://blog.prialto.com/2011/11/16/taking-emotion-out-of-corporate-email/#comments</comments>
		<pubDate>Wed, 16 Nov 2011 13:28:46 +0000</pubDate>
		<dc:creator>Eric Taussig</dc:creator>
				<category><![CDATA[Doing everything right]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=487</guid>
		<description><![CDATA[Tweet How about a corporate policy mandating against emotional communication in email? Michael Keck recently informed me that this is the rule for internal communications over at Algentis. Michael and team want to stay focused on serving their clients. They DO NOT want to waste time parsing email sentences to decipher any hidden meaning behind [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton487" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F16%2Ftaking-emotion-out-of-corporate-email%2F&amp;text=Taking%20emotion%20out%20of%20corporate%20email&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F16%2Ftaking-emotion-out-of-corporate-email%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--> <!--[if gte mso 10]><br />
<mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --></p>
<p><!--[endif]--><br />
How about a corporate policy mandating against emotional communication in email? <a href="http://www.linkedin.com/in/michaelkeck">Michael Keck</a> recently informed me that this is the rule for internal communications over at <a href="http://algentis.com/Default.asp">Algentis</a>.</p>
<p>Michael and team want to stay focused on serving their clients. They DO NOT want to waste time parsing email sentences to decipher any hidden meaning behind the written words.</p>
<p><strong>The no subtext rule</strong></p>
<p>Their solution is a no-subtext rule: Don’t write with emotion and don’t waste time looking for it. If a manager wants to know when he will receive an overdue deliverable, he will write, “when will you send that deliverable?” He will not spend time crafting a more tactful, but easily over analyzed, sentence like, “I just wanted to check in on when you’ll be able to get that deliverable to me, as I was under the impression you would send it to me yesterday.”</p>
<p>The policy probably won’t work with customers, and, even internally, it requires colleagues to adhere to the same principles that make a marriage work well: Assumption of goodwill, complete forgiveness for past disputes, etc.</p>
<p><strong>Don&#8217;t read between the lines<br />
</strong><br />
If a manager writes to a colleague “when will you be arriving today?” the receiver of the message must avoid reading any innuendo into the simple question. The point is for the reader not to waste time thinking “I wonder if he thinks I’m late a lot.” The Algentis policy says such nuanced discussion will be left out of email and transmitted only in verbal communication, a form far less prone to misunderstanding.</p>
<p><strong>Higher personal productivity is the benefit</strong></p>
<p>I’m not sure if the tip is a good one for all teams. Operating among diverse groups may require a commitment to extra communication. But adherence to the no-subtext rule is probably helpful to any individual reaching for higher personal productivity. Imagine unilaterally telling coworkers that you’ll no longer spend time deciphering emails with emotion: The information only, please!</p>
<p>You may miss a bit of the meaning and connection. But spending less time reading between the lines may save enough mental energy to make it worth the tradeoff.<br />
<!--[if !supportLineBreakNewLine]--><br />
<!--[endif]--></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2011/11/16/taking-emotion-out-of-corporate-email/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finally a way to connect your laptop to the web via your BlackBerry</title>
		<link>http://blog.prialto.com/2011/11/10/finally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=finally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry</link>
		<comments>http://blog.prialto.com/2011/11/10/finally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry/#comments</comments>
		<pubDate>Thu, 10 Nov 2011 16:13:58 +0000</pubDate>
		<dc:creator>Scott Plamondon</dc:creator>
				<category><![CDATA[Doing everything right]]></category>
		<category><![CDATA[Productivity tools]]></category>
		<category><![CDATA[BlackBerry]]></category>
		<category><![CDATA[Tether]]></category>

		<guid isPermaLink="false">http://blog.prialto.com/?p=483</guid>
		<description><![CDATA[TweetFor two years I had a Verizon PC card to give me web access for my HP laptop. The card was free, but the service cost me about $60 per month—a big monthly cost. The connection was fast and the ability to connect from client locations was an important benefit. But the $60 per month [...]]]></description>
			<content:encoded><![CDATA[<div id="tweetbutton483" class="tw_button" style=""><a href="http://twitter.com/share?url=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F10%2Ffinally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry%2F&amp;text=Finally%20a%20way%20to%20connect%20your%20laptop%20to%20the%20web%20via%20your%20BlackBerry&amp;related=&amp;lang=en&amp;count=vertical&amp;counturl=http%3A%2F%2Fblog.prialto.com%2F2011%2F11%2F10%2Ffinally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry%2F" class="twitter-share-button"  style="width:55px;height:22px;background:transparent url('http://blog.prialto.com/wp-content/plugins/wp-tweet-button/tweetn.png') no-repeat  0 0;text-align:left;text-indent:-9999px;display:block;">Tweet</a></div><p>For two years I had a Verizon PC card to give me web access for my HP laptop. The card was free, but the service cost me about $60 per month—a big monthly cost. The connection was fast and the ability to connect from client locations was an important benefit. But the $60 per month ($720 per year) really irked me, so I ended up dropping the service. </p>
<p>Now I finally found a way to get the mobile web connection I want on my laptop without the high monthly fee. I recently download the <a href="http://tether.com/">Tether app for BlackBerry</a>. For a one-time fee of $49.99 I can connect my BlackBerry to my HP laptop via a USB cable and get the web and email from almost anywhere. There is no additional fee beyond the BlackBerry data plan I already have from Verizon.</p>
<p>Not only do I save a bundle, but also I score a victory for competition with the big carriers.</p>
<p>What: Tether app for BlackBerry<br />
Where: <a href="http://tether.com/">http://tether.com/</a><br />
Price: Free trial available, full version is $49.95 one-time fee</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.prialto.com/2011/11/10/finally-a-way-to-connect-your-laptop-to-the-web-via-your-blackberry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

