<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://rss.projectconnections.com/~d/styles/itemcontent.css"?><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
    <channel>
        <title>ProjectConnections Articles</title>
        <description>Ten most recent articles published on ProjectConnections.com</description>
        <link>http://www.projectconnections.com/articles/index.html</link>
        <copyright>2009</copyright>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs>
        <language>en-us</language>
        <lastBuildDate>Tue, 16 Mar 2010 09:20:01 -0700</lastBuildDate>
        <managingEditor>deanna@projectconnections.com</managingEditor>
        <pubDate>Tue, 16 Mar 2010 09:20:01 -0700</pubDate>
        <webMaster>erik@projectconnections.com</webMaster>
        <generator>FeedForAll Mac v2.1 (2.1.0.1); http://www.FeedForAll.com/</generator>
        <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://rss.projectconnections.com/rss/pc_columns" /><feedburner:info uri="rss/pc_columns" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
            <title>Hawaii Uh-Oh by Kent McDonald</title>
            <description>There is an inherent danger in writing about your job on a regular basis&amp;mdash;you begin dissecting everything that happens in your life and try to apply it to a lessons learned in that particular field. Experiences on trips seem to be an exceptionally easy target for these lessons learned stories. I mention this downside because I am about to use my recent vacation to Hawaii to discuss risk management, and managing scope and schedule changes when things go bad... well, let's say, when things stray from the plan.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/ToctC3HRc2s" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/ToctC3HRc2s/hawaii-uhoh.html</link>
            <guid isPermaLink="false">9572D588-93BE-419F-A4D5-8080C319A283-26843-0001AF794E5FA669-FFA</guid>
            <pubDate>Tue, 16 Mar 2010 09:20:01 -0700</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/kent_mcdonald/2010/03/hawaii-uhoh.html</feedburner:origLink></item>

        <item>
            <title>Checklist? Check! by Geof Lory</title>
            <description>When it comes to simplifying a process, more often than not I have found that a simple checklist will fulfill 80% of the process governance requirements with a fraction of the effort and frustration. Checklists define the undone and done states through a simple binary process. It is either done, or not done. It tracks the process through examination of empirical evidence that something exists and can be visually verified. It can be checked off. You can't get much simpler than that.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/iMgcWNAEKJQ" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/iMgcWNAEKJQ/checklist-check.html</link>
            <guid isPermaLink="false">22928B56-1218-43BB-8CA2-FA003B8BD768-34444-000026B74A4A8F15-FFA</guid>
            <pubDate>Wed, 03 Mar 2010 12:02:30 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/geof_lory/2010/03/checklist-check.html</feedburner:origLink></item>

        <item>
            <title>Catalytic Events – Effortless Ways to Change Behavior for the Better by Kimberly Wiefling</title>
            <description>A catalytic mechanism is a device, process, policy or structure that encourages, evokes, or even forces, a desired behavior. A simple example is an entrance gate at a parking garage. The gate won't let you drive into the garage until you take the parking ticket. What if we could create catalytic mechanisms that automatically, permanently, and effortlessly eliminated some or all of our recurring project problems? Suddenly the lives of project managers everywhere would brighten and a chorus of "hallelujah" would ascend from their collective voices around the world. Certainly worth a shot!&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/HGJDrH2jD-w" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/HGJDrH2jD-w/catalytic-events.html</link>
            <guid isPermaLink="false">7B516EFF-42A6-4915-8901-3BC9F1DDD604-78622-00005D0AC0901DBA-FFA</guid>
            <pubDate>Thu, 18 Feb 2010 10:14:07 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/kimberly_wiefling/2010/02/catalytic-events.html</feedburner:origLink></item>

        <item>
            <title>Falling in Love with GREAT Communications by Carl Pritchard</title>
            <description>We all acknowledge that a significant amount of our success or failure is rooted in our abilities to communicate. And yet we don't invest a lot of time thinking about how to turn our mundane communications into opportunities for others to fall in love with us and our message. I raised this specter in a recent class and got an interesting array of responses from my students. Rather than simply share my insights, I offer theirs here with a simple suggestion. Pick two. Steel yourself to try them &lt;i&gt;consistently&lt;/i&gt;. Make them a personal mission. You'll be surprised by the shift.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/kNi_SsqMxp8" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/kNi_SsqMxp8/falling-in-love-with-great-communications.html</link>
            <guid isPermaLink="false">9F799F0E-3F7B-41BA-AF23-1662F142B773-70045-00013CE1F1AB3CB1-FFA</guid>
            <pubDate>Wed, 20 Jan 2010 10:25:01 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/carl_pritchard/2010/01/falling-in-love-with-great-communications.html</feedburner:origLink></item>

        <item>
            <title>New Year's Resolutions for Your Project by Kent McDonald</title>
            <description>It's that time of year where we all participate in the seemingly futile ritual of committing to improve ourselves by creating a list of self-betterment activities we refer to as resolutions. It may be worth a quick aside to ponder why we call them "resolutions" and not "commitments" or "promises." Perhaps it has something to do with our subconscious realization that we have no intent whatsoever to actually hold ourselves to them. If we associated some measure of success and a time frame with them instead of just stating we will do more of a certain activity, maybe, just maybe, they would have more staying power.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/MAgixFpJcSo" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/MAgixFpJcSo/new-years-resolutions-for-your-project.html</link>
            <guid isPermaLink="false">DBC6B7A6-D27A-4B41-BB59-1008BC2E7AF9-61479-000048CDF0E1E743-FFA</guid>
            <pubDate>Wed, 06 Jan 2010 11:42:47 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/kent_mcdonald/2010/01/new-years-resolutions-for-your-project.html</feedburner:origLink></item>

        <item>
            <title>Lego My Schedule by Geof Lory</title>
            <description>On a recent project, we were having numerous discussions regarding the complex scheduling of incrementally adding functionality to a new system. So like all good project managers we went to our tool of choice (Microsoft Project, right?) and built a beautiful representation of the proposed rollout and product development to communicate the plan. While this was a valuable exercise to understand dependencies and forecasted resource demands, the look on our stakeholders' eyes as they glanced at the Gantt chart said they needed something else: Legos.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/RuSfkNXIxsY" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/RuSfkNXIxsY/lego-my-schedule.html</link>
            <guid isPermaLink="false">195759CF-5335-4E7B-AEB3-AFCD367E8AB5-94974-000202D4C5C183D0-FFA</guid>
            <pubDate>Thu, 17 Dec 2009 15:13:57 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/geof_lory/2009/12/lego-my-schedule.html</feedburner:origLink></item>

        <item>
            <title>Kollaboration Is Killing Me</title>
            <description>Alas, after a year of what I'm now calling "the collective consciousness conspiracy experiment," I can honestly say, "Kollaboration is killing me!" If you are struggling to harness the hydra of the group genius in your project team, I'm sure you'll be able to relate to some of what I've experienced with these three wiki experiments. It's just a tad painful, but press on if you're curious.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/tmAx7dlvt_Y" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/tmAx7dlvt_Y/kollaboration-is-killing-me.html</link>
            <guid isPermaLink="false">F1C8C029-8ECA-431F-A0A3-6B4F494005AF-19270-00012F4902D94A2F-FFA</guid>
            <pubDate>Tue, 08 Dec 2009 09:38:24 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/kimberly_wiefling/2009/12/kollaboration-is-killing-me.html</feedburner:origLink></item>

        <item>
            <title>Context in Communication by Carl Pritchard</title>
            <description>What's compelling is that I have shared that story so many times, that I begin to believe that everyone has heard it. They haven't. But I often use the term "deer" in my conversations with others about risk to refer to some risk we have "hit" in our careers. I know what I mean. Those who have been in my classes or keynotes know what I mean. But the term "deer" is far from synonymous with "things that you have hit one time in your whole life, but which loom so large that you continually cite them as significant, even though it's a remote chance you will ever hit them again."&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/4BjhSuranfg" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/4BjhSuranfg/context-in-communication.html</link>
            <guid isPermaLink="false">B2740B39-AD1D-474A-8C66-015C1253B104-72910-00007C7447BDE03C-FFA</guid>
            <pubDate>Wed, 25 Nov 2009 09:59:51 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/carl_pritchard/2009/11/context-in-communication.html</feedburner:origLink></item>

        <item>
            <title>Fix It Fast vs. Fix It Right by Alan S. Koch</title>
            <description>"Root Cause Analysis (RCA) will be our first Quality Improvement initiative." Carl told me. "It fits your definition of 'low-hanging fruit' (within reach and oh-so sweet). Besides, everyone agrees that we would really benefit from doing it right!"&lt;br /&gt;
&lt;br /&gt;
A few months earlier, when I did their Quality Appraisal, RCA stood out as a big opportunity. They were already doing something (this put them light years ahead of most places), but for a number of reasons, they were failing to get any real benefit from it. This was our opportunity! Take an RCA process that was limping along, and turn it into a quality improvement powerhouse.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/1kevQiaqqao" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/1kevQiaqqao/fix-it-fast-vs-fix-it-right.html</link>
            <guid isPermaLink="false">5A1B221F-22A5-442E-93CD-4BB05C5772A0-7193-00005E9EF7B9994B-FFA</guid>
            <pubDate>Tue, 10 Nov 2009 09:46:18 -0800</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/alan_koch/2009/11/fix-it-fast-vs-fix-it-right.html</feedburner:origLink></item>

        <item>
            <title>Titles and Accountabilities</title>
            <description>At the risk of sounding like Inigo Montoya, accountability may not mean what you think it means. Accountability and responsibility mean two different things in the famous RACI chart, but it's not clear what Accountability adds other than a handy vowel. In fact, there is no clear agreement on the definition of accountability, or the distinction between accountability and responsibility, and several people seem to use them interchangeably. This does no one any good, especially since the distinction between accountable and responsible is quite important when talking about leading people through influence rather than through authority.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/doqE0OFK2OA" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/doqE0OFK2OA/titles-and-accountabilities.html</link>
            <guid isPermaLink="false">3E53E081-3445-45B0-9B8C-1781B9B61F9F-16501-0001BB6DBA134F06-FFA</guid>
            <pubDate>Wed, 28 Oct 2009 09:33:00 -0700</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/kent_mcdonald/2009/10/titles-and-accountabilities.html</feedburner:origLink></item>

        <item>
            <title>Packaged for Consumption by Geof Lory</title>
            <description>Anyone who has every tried to explain or teach a complex subject they understand very well to someone who doesn't have their level of experience knows what I'm talking about. The student is looking for the recipe, but you know they need to understand all the variables and nuances because there is no recipe. To you, it really isn't that difficult once you understand how all the pieces fit together. But the reality is the student can't grasp the totality of the varying parameters or the nuances of their interaction, because they have little context in which to frame these new ideas. What they need and want are some basic rules to provide a framework for learning the skill.&lt;img src="http://feeds.feedburner.com/~r/rss/pc_columns/~4/dTG48VxXAvc" height="1" width="1"/&gt;</description>
            <link>http://rss.projectconnections.com/~r/rss/pc_columns/~3/dTG48VxXAvc/packaged-for-consumption.html</link>
            <guid isPermaLink="false">C7628765-4D32-4CA0-A014-3534D9667730</guid>
            <pubDate>Wed, 14 Oct 2009 11:09:06 -0700</pubDate>
        <feedburner:origLink>http://blog.projectconnections.com/geof_lory/2009/10/packaged-for-consumption.html</feedburner:origLink></item>

    </channel>
</rss>
