<?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>Alberto Ferrer Blog &#187; Management</title>
	<atom:link href="http://albertoferrer.com/blog/tag/management/feed/" rel="self" type="application/rss+xml" />
	<link>http://albertoferrer.com/blog</link>
	<description>Things I think about</description>
	<lastBuildDate>Tue, 16 Feb 2010 15:33:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Leading a Company in Tough Times</title>
		<link>http://albertoferrer.com/blog/2009/08/03/leading-a-company-in-tough-times/</link>
		<comments>http://albertoferrer.com/blog/2009/08/03/leading-a-company-in-tough-times/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 15:42:22 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Managing]]></category>
		<category><![CDATA[Brand]]></category>
		<category><![CDATA[Leader]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Organization]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=147</guid>
		<description><![CDATA[I recently read an article from the July 2009 issue of the McKinsey Quarterly called &#8220;Leadership lessons for hard times&#8221; (registration required) as part of their &#8220;managing in the new normal&#8221; series. The article is a collection of tips gathered from interviews with 14 CEOs of large (mostly multinational) companies. A few of the companies [...]]]></description>
			<content:encoded><![CDATA[<p>I recently read an article from the July 2009 issue of the <a title="McKinsey Quarterly Site" href="http://www.mckinseyquarterly.com/" target="_blank">McKinsey Quarterly</a> called &#8220;<a title="McKinsey Quarterly Article &quot;Leadership lessons for hard times&quot;" href="http://www.mckinseyquarterly.com/Leadership_lessons_for_hard_times_2413" target="_blank">Leadership lessons for hard times</a>&#8221; (registration required) as part of their &#8220;managing in the new normal&#8221; series. The article is a collection of tips gathered from interviews with 14 CEOs of large (mostly multinational) companies. A few of the companies represented are <a title="Procter &amp; Gamble site" href="http://www.pg.com" target="_blank">Procter &amp; Gamble</a>, <a title="3M site" href="http://www.3m.com" target="_blank">3M</a>, <a title="Travelers site" href="http://www.travelers.com" target="_blank">Travelers</a>, <a title="Pepsi Bottling Group site" href="http://www.pbg.com" target="_blank">Pepsi Bottling Group</a>, <a title="AutoNation site" href="http://www.autonation.com" target="_blank">AutoNation</a>, and <a title="Macy's site" href="http://www.macys.com" target="_blank">Macy&#8217;s</a>.</p>
<p>As stated in the article, this is an interesting take on the current economic situation. Much has been written about the mistakes that have been made, about how we got to where we are now, etc. Little has been made of the learning from those mistakes or how to best lead an organization in less-than-rosy times. Here are the lessons:</p>
<p><strong>Confront Reality</strong> <em>Always question whether the &#8220;halo effect&#8221; of a business or business situation is blinding you to what lies on the horizon. </em>—Herbert Henkel, chairman and CEO of Ingersoll Rand</p>
<p><strong>At Board Meetings, Put Strategy Center Stage</strong> <em>The board has been heavily involved in strategy formulation with me, and we have a better strategy because if it. </em>—Bill Nuti, chairman and CEO of NCR</p>
<p><strong>Be Transparent With Employees</strong> <em>The only way to address uncertainty is to communicate and communicate. And when you think you&#8217;ve just about got to everybody, then communicate some more. </em>—Terry Lundgren, chairman, president, and CEO of Macy&#8217;s</p>
<p><strong>Be Transparent With Investors</strong> <em>Our policy is: &#8220;If in doubt, communicate.&#8221; We always want to conduct our business with integrity and forthrightness. </em>—Ron Sugar, chairman and CEO of Northrop Grumman</p>
<p><strong>Build And Protect The Culture</strong> <em>Stay focused on culture, people, and values: it&#8217;s the area most likely to get compromised in this environment.</em> —Eric Foss, chairman and CEO of Pepsi Bottling Group</p>
<p><strong>Keep Faith With The Future</strong> <em>If you don&#8217;t invest in the future and don&#8217;t plan for the future, there won&#8217;t be one.</em> —George Buckley, chairman, president, and CEO of 3M</p>
<p>While there is much to be learned from each of these lessons or principles, a subset of them resonated the most with me. First is the notion of transparency and communication. Especially in touch times (but at all times, really) there is ample opportunity for rumor and innuendo to take over. Communication (even over-communication) with stakeholders is critical to pushing forth an agenda and keeping the team with their eye firmly on the ball. Yes, it&#8217;s difficult to remain focused on the task at hand if I&#8217;m worried about losing my job. But communications from leadership of the organization about what&#8217;s going on can go a long way towards making me comfortable about the situation and about the folks who are leading the company through the challenging environment.</p>
<p>Another favorite is the confronting of reality. Addressing head-on the challenges of the day, whatever they may be, is not only more efficient but also more effective. I&#8217;ve been in corporate situations where the reality of the day (the forest) has been ignored (or perhaps set aside) while management focuses on something else (the trees) and the results have been more painful than needed. Especially in tough times, leaders need to take a good hard look at what&#8217;s in front of them and confront that reality however different, unexpected, or chaotic it may be. Only then can the organization truly begin charting its course through the situation.</p>
<p>Last is the point about the culture. In difficult economic times, it can be easy to throw out elements of company culture, reject company values, and lose sight of the people as you seek to swiftly control costs, for example. These short-term-focused actions, however, will have a profound effect on the company long term. A company is not just its balance sheet and income statement. In fact, a company is its people, the values that bind them together, and the culture in which they thrive. Short-changing that in difficult times will do much harm and impede the very recovery that management is trying to effect.</p>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2009/08/03/leading-a-company-in-tough-times/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Taking a Look at Poor Leadership</title>
		<link>http://albertoferrer.com/blog/2009/06/01/taking-a-look-at-poor-leadership/</link>
		<comments>http://albertoferrer.com/blog/2009/06/01/taking-a-look-at-poor-leadership/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 22:06:28 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Leader]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Team]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=130</guid>
		<description><![CDATA[In a short article in the June 2009 issue of Harvard Business Review, authors Jack Zenger and Joseph Folkman (from leadership consulting company Zenger/Folkman and authors (with Scott Edinger) of The Inspiring Leader: Unlocking the Secrets of How Extraordinary Leaders Motivate) take a very different look at leadership.
Instead of talking about how good leaders lead, [...]]]></description>
			<content:encoded><![CDATA[<p>In a short article in the June 2009 issue of <a title="Harvard Business Review" href="http://hbr.org" target="_blank"><em>Harvard Business Review</em></a>, authors Jack Zenger and Joseph Folkman (from leadership consulting company <a title="Zenger Folkman" href="http://www.zengerfolkman.com/" target="_blank">Zenger/Folkman</a> and authors (with Scott Edinger) of <em>The Inspiring Leader: Unlocking the Secrets of How Extraordinary Leaders Motivate</em>) take a very different look at leadership.</p>
<p>Instead of talking about how good leaders lead, or focusing on what makes great leaders, or anything like that, they looked at the opposite. Based on two research studies on executives and leaders, they examined those who failed and developed a list of the ten things most commonly missing in bad leaders. As they write, &#8220;every bad leader had at least one, and most had several.&#8221;</p>
<p>According to their work, the worst leaders:</p>
<ul>
<li>Lack energy and enthusiasm</li>
<li>Accept their own mediocre performance</li>
<li>Lack clear vision and direction</li>
<li>Have poor judgment</li>
<li>Don&#8217;t collaborate</li>
<li>Don&#8217;t walk the talk</li>
<li>Resist new ideas</li>
<li>Don&#8217;t learn from mistakes</li>
<li>Lack interpersonal skills</li>
<li>Fail to develop others</li>
</ul>
<p>The authors further note that the bad leaders they studies often were unaware of these behaviors.</p>
<p>This is interesting because the vast majority of the literature on leadership has been focused on the positive traits and behaviors of good leaders. This look at the flip side of the coin provides fresh perspective (even though some of the factors outlined above might seem somewhat obvious).</p>
<p>Being a good leader might be as much about exhibiting the good traits and behaviors as it is about not displaying the bad ones. Read <a title="Then Fatal Flaws That Derail Leaders" href="http://hbr.harvardbusiness.org/2009/06/ten-fatal-flaws-that-derail-leaders/ar/1" target="_blank">the full article</a> for the details.</p>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2009/06/01/taking-a-look-at-poor-leadership/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Account Management or Client Service</title>
		<link>http://albertoferrer.com/blog/2007/08/01/account-management-or-client-service/</link>
		<comments>http://albertoferrer.com/blog/2007/08/01/account-management-or-client-service/#comments</comments>
		<pubDate>Wed, 01 Aug 2007 23:04:58 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Agency Business]]></category>
		<category><![CDATA[Account]]></category>
		<category><![CDATA[Agency]]></category>
		<category><![CDATA[Client]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Service]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=6</guid>
		<description><![CDATA[

You say “toh-MAY-toh” and I say “toh-MAH-toh,” the song exclaims, suggesting that it’s the same thing simply pronounced a little differently in each instance. Does a similar dynamic apply in the ongoing debate of Account Management versus Client Service? As I understand it, this is not a matter of simple semantics. It is a deeper [...]]]></description>
			<content:encoded><![CDATA[<div class="entry-content">
<div class="entry-body">
<p>You say “toh-MAY-toh” and I say “toh-MAH-toh,” the song exclaims, suggesting that it’s the same thing simply pronounced a little differently in each instance. Does a similar dynamic apply in the ongoing debate of Account Management versus Client Service? As I understand it, this is not a matter of simple semantics. It is a deeper discussion about what we do as agency folks.</p>
<p>Client Service is the older of the two terms and has been used for generations. I was part of the Client Service department when I started in the agency business many years ago. The term is easy to understand (“it’s the people who work with the clients”) and tried and true. It focuses on the client.</p>
<p>At the same time, there are those who see a more negative meaning here. They feel that the term connotes subservience (the “service” part of the term makes many an account person bristle) and a “jump!” “how high?” mentality that is not the reality in business today. They believe that today account managers lead client businesses and thus they need a term that more accurately reflects that: Account Management.</p>
<p>Account Management is a newer term that focuses on the account versus the client. It drives home the point that account people manage the client business rather than servicing anyone or anything. It’s perhaps a stronger term.</p>
<p>However, some people believe the term suggests that it’s taking the people out of the equation and that account managers are all about the business and not about the softer side. They feel the term connotes an arrogance about the account manager (we know what’s important, the account) versus giving clients their due.</p>
<p>And of course there’s the hybrid Account Service term, which perhaps means that we provide service to an account. Not loving that one.</p>
<p>To me, it really isn’t about the name. It’s about what’s behind it. In my opinion, we need a little account management and a little client service. My view, and what I tell my teams, is that we need to do both.</p>
<p>We need to do Account Management. That is, we need to manage the client’s business. We need to manage their account, get the work done, lead the process, etc. That’s the nuts and bolts part.</p>
<p>We also need to do Client Service. At the end of the day, agencies are in the service business where clients pay the bills. And by clients I mean human beings. These are the folks with whom we interact every day, the folks who approve (or not) our briefs, our work, and our fees. We need to provide service to them, to be a resource to them, to be nice and engaging to them, to be accommodating and sympathetic. You get the point.</p>
<p>Clients hire and fire agencies both for the quality of the work and for the human element of the relationship (among other factors). Therefore, having a strong relationship with both the account (the business) and the client (the people) is critical.</p>
<p>The best work done by arrogant jerks will get you fired just as crappy work done by the nicest most accommodating people in the world will. The challenge is balancing both in a way that the client feels listened to, understood, and valued as a person and contributing member of the team, while managing the business as passionately as if it were your own.</p></div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2007/08/01/account-management-or-client-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Teams Are Impacted by Leaders’ Moods</title>
		<link>http://albertoferrer.com/blog/2007/07/30/teams-are-impacted-by-leaders%e2%80%99-moods/</link>
		<comments>http://albertoferrer.com/blog/2007/07/30/teams-are-impacted-by-leaders%e2%80%99-moods/#comments</comments>
		<pubDate>Tue, 31 Jul 2007 00:07:38 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Leader]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Team]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=13</guid>
		<description><![CDATA[A paper recently published in the Journal of Applied Psychology describes the results of a study seeking to link the moods of leaders with their teams. I read an excerpt of the paper as published in Rotman, the magazine of the Rotman School of Management at the University of Toronto.


Authored by Stéphane Côté from the [...]]]></description>
			<content:encoded><![CDATA[<p>A paper recently published in the <em><a href="http://www.apa.org/journals/apl/">Journal of Applied Psychology</a></em> describes the results of a study seeking to link the moods of leaders with their teams. I read an excerpt of the paper as published in <em>Rotman</em>, the magazine of the Rotman School of Management at the University of Toronto.</p>
<div class="entry-content">
<div class="entry-body">
<p>Authored by Stéphane Côté from the Rotman School, Thomas Sy from California State University, and Richard Saavedra from the University of New Hampshire, the study showed causal links between the mood in which a leader is and the performance of his or her team. Below are some key points.</p>
<p><strong><span style="text-decoration: underline;">Findings</span></strong></p>
<p><strong><span style="text-decoration: underline;">Leaders’ moods are transferred to group members</span>.</strong> This is probably no surprise to most, but the study produced evidence that individuals with a leader in a good mood were in a good mood mode than in a bad mood and those with a leader in a bad mood experienced the opposite. This “transfer of mood” was also observed at the group level, where the leader’s mood affected the moods of the group as a whole.</p>
<p><strong><span style="text-decoration: underline;">Leaders’ moods impact group processes</span>.</strong> The two processes that were studies were “effort” and “coordination.” In terms of effort, the authors found that groups with leaders in a bad mood tend to exert more effort on the task at hand than groups with leaders in a good mood.</p>
<p>This is believed to be because when the leader is in a good mood, the group takes that cue to mean that the work is satisfactory and thus they can relax. When the leader’s mood is bad, however, the group interprets that to mean that they’re not measuring up and so they redouble their efforts.</p>
<p>In terms of cooperation, the findings are more consistent with common belief. Groups with leaders in a positive mood exhibited more cooperation than those with leaders in a foul mood.</p>
<p>The authors presume this to be related to the effort findings above. Groups with a leader in a good mood, while relaxing their efforts, also feel more secure and thus behave in a more agreeable and cooperative fashion. Those with leaders in a bad mood, on the other hand, exhibit the opposite behavior.</p>
<p><strong><span style="text-decoration: underline;">Implications</span></strong></p>
<ol>
<li><strong>Leaders must understand the role of moods to be successful.</strong> To be effective, leaders need to understand how their moods impact their teams so that they can manage those moods accordingly.<strong>
<p></strong></li>
<li><strong>Leaders must efficiently regulate their teams’ moods.</strong> This means not just focusing on the mood of individuals but rather on the overall group mood (the so called “group affective tone”) to be effective.</li>
<li><strong>Leaders can influence their groups by regulating their mood displays.</strong> The display of the leader’s mood to subordinates can be managed to attain the desired outcome from the team.</li>
</ol>
</div>
<div class="entry-body"></div>
<div class="entry-body">
<p>It used to be that emotions in the workplace were seen as unprofessional or otherwise negative. More and more, emotions are being seen as a non-trivial part of organizational performance.</p></div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2007/07/30/teams-are-impacted-by-leaders%e2%80%99-moods/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building Leaders vs. Building Leadership</title>
		<link>http://albertoferrer.com/blog/2007/07/10/building-leaders-vs-building-leadership/</link>
		<comments>http://albertoferrer.com/blog/2007/07/10/building-leaders-vs-building-leadership/#comments</comments>
		<pubDate>Tue, 10 Jul 2007 15:56:25 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Leader]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=58</guid>
		<description><![CDATA[I recently read at article by Dave Ulrich and Norm Smallwood in the July-August 2007 issue of Harvard Business Review that advocates companies focus on leadership instead of leaders. The authors are partners and co-founders of RBL Group, a leadership development and human resource education consultancy.
The authors submit that some companies produce a steady supply [...]]]></description>
			<content:encoded><![CDATA[<p>I recently read at article by Dave Ulrich and Norm Smallwood in the July-August 2007 issue of <a href="http://www.hbr.org"><em>Harvard Business Review</em></a> that advocates companies focus on leadership instead of leaders. The authors are partners and co-founders of RBL Group, a leadership development and human resource education consultancy.</p>
<p>The authors submit that some companies produce a steady supply of strong managers because instead of focusing on building up the strengths of individual people, they concentrate on developing a “broad organizational leadership capability.” That’s what they call a <em>Leadership Brand</em>.</p>
<p>Firms that have leadership brands use an “outside-in” approach to develop their executives. That is, they look outside at what they want to be known for by clients and customers and then link that with required management skills for their executives. For example, Lexus takes it “The pursuit of perfection” tagline and translates it into an expectation that its leaders excel at managing quality processes. The outside-in approach helps companies develop a reputation for high-quality leaders whom clients can trust to deliver on the company&#8217;s promises.</p>
<p>The authors looked at 150 companies with reputations for strong leadership and found that those organizations follow five strategies. Those strategies are:</p>
<ul>
<li>Ensure managers master the basics of leadership—for example, setting strategy and developing talent.</li>
<li>Ensure that leaders internalize the&#8217; high expectations of clients.</li>
<li>Incorporate client feedback into evaluations of executives.</li>
<li>Invest in programs that help managers hone the right skills by tapping clients to participate in them.</li>
<li>Track the success of efforts to build leadership bench strength over the long term.</li>
</ul>
<p>What results, the authors conclude, is “outstanding management” that persists even when individual executives leave the company. In fact, companies with the strongest leadership brands often become “leader feeders” and generate executives who go on to head other companies. Examples of these firms are GE, PepsiCo, P&amp;G, Disney, Toyota, and Kraft, among others.</p>
<p>The authors actually provide a list of companies that they consider leadership brand companies and their P/E ratio compared to their category (they used the past ten years’ worth of data). The chart below shows that consistently a leadership brand is correlated with higher P/E ratios versus the category.</p>
<p><img class="aligncenter size-full wp-image-64" title="leadership_brand_31" src="http://albertoferrer.com/blog/wp-content/uploads/2007/07/leadership_brand_31.gif" alt="leadership_brand_31" width="390" height="810" /></p>
<p>How do you rate? The following graphic shows a short assessment test that will help leaders determine their company’s leadership branding capability.</p>
<p><img class="aligncenter size-full wp-image-66" title="leadership_brand" src="http://albertoferrer.com/blog/wp-content/uploads/2007/07/leadership_brand.gif" alt="leadership_brand" width="390" height="795" /></p>
<p><em>24 or less: Start working on the fundamentals of leadership. 25 to 34: Select one or two dimensions where you’re not yet strong and focus on improving them. 35 to 44: You are well on your way to becoming a leadership brand company. 45 or higher: You’re sitting pretty, pat yourself on the back.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2007/07/10/building-leaders-vs-building-leadership/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prioritizing Tasks at Hand: GTD</title>
		<link>http://albertoferrer.com/blog/2007/06/17/prioritizing-tasks-at-hand-gtd/</link>
		<comments>http://albertoferrer.com/blog/2007/06/17/prioritizing-tasks-at-hand-gtd/#comments</comments>
		<pubDate>Sun, 17 Jun 2007 16:08:27 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Managing]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Organization]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=73</guid>
		<description><![CDATA[Sometimes we have more tasks on our to-do lists than we have time or resources in which to do them. Perhaps most of the time. How to prioritize? A common (yet erroneous) approach is to prioritize by due date. Start with what’s due first, continue with the task that is due right after the first [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes we have more tasks on our to-do lists than we have time or resources in which to do them. Perhaps most of the time. How to prioritize? A common (yet erroneous) approach is to prioritize by due date. Start with what’s due first, continue with the task that is due right after the first one, and so on.</p>
<p>If you know <a href="http://www.davidco.com/">Getting Things Done</a>, you’re familiar with the Four Criteria Model for choosing tasks. It’s where the rubber meets the road in GTD, because it’s the way you decide, in the moment, how those tasks get done.</p>
<p>As common sense as it seems to GTD’ers, this model is one of the more controversial aspects of Getting Things Done for a simple reason: it posits that priority is not the only factor in deciding what to do at a given time. It’s just one of four factors:</p>
<p><span style="text-decoration: underline;"><strong>Context</strong></span> &#8211; Where are you? What tools are available? What are the limits and possibilities unique to this moment?</p>
<p><span style="text-decoration: underline;"><strong>Time Available</strong></span> &#8211; Do you have, for example, 30 seconds, 30 minutes, or 30 hours available to you right now? What tasks could you accomplish given the time you have?</p>
<p><strong><span style="text-decoration: underline;">Energy Available</span></strong> &#8211; Are you full of energy, are you dragging, or are you somewhere in between? Which of the tasks on your list could you finish, given that energy level?</p>
<p><strong><span style="text-decoration: underline;">Priority</span></strong> &#8211; If you had access to all the tools, opportunities, time, and energy you needed, what’s the most important or time-sensitive thing you could do right now?</p>
<p>Most of us have been conditioned to think that Priority trumps everything, all the time. But is it true, reasonable, or even physically possible to always work this way? Can you will yourself into doing only your identified high-priority items anytime, all the time?</p>
<p>Probably not, so maybe you ought to give this approach a try</p>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2007/06/17/prioritizing-tasks-at-hand-gtd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information Freedom</title>
		<link>http://albertoferrer.com/blog/2007/05/18/information-freedom/</link>
		<comments>http://albertoferrer.com/blog/2007/05/18/information-freedom/#comments</comments>
		<pubDate>Fri, 18 May 2007 23:43:24 +0000</pubDate>
		<dc:creator>Alberto Ferrer</dc:creator>
				<category><![CDATA[Managing]]></category>
		<category><![CDATA[Account]]></category>
		<category><![CDATA[Agency]]></category>
		<category><![CDATA[Client]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Service]]></category>
		<category><![CDATA[Team]]></category>

		<guid isPermaLink="false">http://albertoferrer.com/blog/?p=76</guid>
		<description><![CDATA[When I was working at Leo Burnett as an AAE, I thought quite highly of myself. There I was, making $16,000 per year, working on the prestigious Procter &#38; Gamble business. I had my very own cubicle, my very own key to come in and out of the office (no access cards back then), and [...]]]></description>
			<content:encoded><![CDATA[<p>When I was working at <a href="http://www.leoburnett.com">Leo Burnett</a> as an AAE, I thought quite highly of myself. There I was, making $16,000 per year, working on the prestigious Procter &amp; Gamble business. I had my very own cubicle, my very own key to come in and out of the office (no access cards back then), and my own extension (no direct lines back then). I even had use of the three IBM PCs that were available to the Client Service department. I thought I had it made. I also thought I knew everything.</p>
<p>It got to the point that I thought I knew more than my boss, the Account Supervisor on the business. I ran my projects well, with not a ton of supervision, and usually with no issues. I even had some minor client contact and did not embarrass myself or the agency. I thought that I was indispensable. And that&#8217;s when it started.</p>
<p>I began to keep my boss just a little less informed than normal, and give her information just a little later than before. I started sharing less, less often, and later. I was the keeper of the information. I had the knowledge. She didn&#8217;t. Knowledge is power, they say, so I was powerful. I continued like that for a while, almost walking on air intoxicated by my perception of power. I was like the squirrel stashing away nuts for the winter, storing away information so that I could sound smart or knowledgeable (more up to speed or up to date than my boss, even) if anyone asked anything.</p>
<div>
<div id="attachment_77" class="wp-caption aligncenter" style="width: 310px"><img class="size-medium wp-image-77" title="hoarding_squirrel" src="http://albertoferrer.com/blog/wp-content/uploads/2009/02/hoarding_squirrel-300x227.jpg" alt="Hoarding makes your cheeks floppy" width="300" height="227" /><p class="wp-caption-text">Hoarding makes your cheeks floppy</p></div>
</div>
<p>Then it happened. We had a problem. A big problem. A big client problem. It was traced back to part of my work, to things that I managed. Things that I had been managing myself without sharing as much with my supervisor. All of a sudden, all eyes were upon me. Lots of questions were asked <span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">“</span>how could this happen?<!--[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="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]--><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">” </span>was a popular one), all the way up to the Director of Client Services. I was freaked out and afraid I&#8217;d lose my job (which made sense considering that my not sharing information had kept the agency in the dark about something that seemed insignificant to me then but to the trained eye of my managers would have meant something).</p>
<p>In the end, no one was fired and things were cleared up. My Account Supervisor heroically covered for me and taught me a huge lesson in the process. From then on, I was the most prolific sharer of information out there. I learned that having the information itself does not really give any power. It&#8217;s knowing what to do with it that does. It&#8217;s not about having the information and keeping it to yourself (where&#8217;s the power in that?). It&#8217;s about the power of sharing it and letting those around you know that you have it (that&#8217;s power).</p>
<p>I learned that the more I shared with my Account Supervisor, the more she saw how I was understanding things, managing things, and being proactive. That helped her assess my performance and it allowed me to grow. It also made my boss look good. And there I learned that making my boss look good makes me look good. It all trickles down.</p>
<p>Information about the client business, about a project&#8217;s status, about what someone said in a creative presentation related to our work, all wants to be free. Sharing it often with your supervisors lets them stay abreast of what&#8217;s going on (which is part of your job) and helps them help you do yours (which is part of their job).</p>
<p>Keep your boss informed of things so that he or she is not surprised (in any business, surprises are not exactly welcome) by any development. Keep your team abreast of what&#8217;s going on so that everyone benefits from your information and you benefit from theirs. And don&#8217;t hoard. It makes your cheeks floppy.</p>
]]></content:encoded>
			<wfw:commentRss>http://albertoferrer.com/blog/2007/05/18/information-freedom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
