<?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>Windward</title>
	<atom:link href="http://windward.ws/feed/" rel="self" type="application/rss+xml" />
	<link>http://windward.ws</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Tue, 14 Feb 2012 20:59:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Ignorance is Not Bliss</title>
		<link>http://windward.ws/ignorance-is-not-bliss/</link>
		<comments>http://windward.ws/ignorance-is-not-bliss/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 20:59:25 +0000</pubDate>
		<dc:creator>annerein54@gmail.com</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://windward.ws/?p=369</guid>
		<description><![CDATA[I decided last fall to run for the board of my local energy coop, Cobb Electric Membership Corporation (Cobb EMC). After reading a series of stories in the local newspaper about the coop’s plan—misguided in my opinion—to join with other coops in Georgia to build a coal-fired energy generation plant in the central part of<span>... </span><a href="http://windward.ws/ignorance-is-not-bliss/">Read on</a>]]></description>
			<content:encoded><![CDATA[<p>I decided last fall to run for the board of my local energy coop, Cobb Electric Membership Corporation (Cobb EMC). After reading a series of stories in the local newspaper about the coop’s plan—misguided in my opinion—to join with other coops in Georgia to build a coal-fired energy generation plant in the central part of the state, I became concerned that the organization had drifted away from its core purpose—distributing energy to its members at the lowest possible price—and needed at least one board member with industry experience to help get it back on track. I am pleased to say that I won the election easily, and I am enjoying my role in public service. One of the first actions taken by the new board was to withdraw from plans to build this plant.</p>
<p>Our decision was celebrated immediately by environmental groups who had opposed the plant from the beginning. I am not opposed to power generation using coal, but I would rather see new, highly efficient plants with updated emissions controls in place while closing the older, more polluting ones. If a new plant were to be built, natural gas—which is cleaner and cheaper—would probably be a better choice.</p>
<p>Of even greater concern to me was that building a plant which wasn’t actually needed could bankrupt the utility. When I asked for the business case which should have been developed to support the planned construction, I was met with blank stares. <em>Pro Forma</em> financials analyzing revenues &amp; expenses over the life of the financing? Nope. A cost estimate for construction? Not that either. Yet the coop had awarded a no-bid project development contract, and the developer (who had no experience in developing this type of project) had started the process of obtaining permits.</p>
<p>It became apparent to me and the other new Directors that the previous Board had decided to venture into the new business of energy generation—which operates on a completely different business model—without understanding the risks involved. The Board didn’t know what it didn’t know. A thorough business case, for example, would have revealed whether there was a market for the surplus energy the plant would produce. Without buyers for its surplus energy, the plant could have bankrupted the coop.</p>
<p>How the Board devolved into the state of dysfunction in which it was flying blind is a story that is still surfacing. Much of it has been told in the local media over the past 18 months. Some of it will emerge in criminal court proceedings. When all is said and done, the story will be a great business school case study about corporate governance and fiduciary responsibility.</p>
<p>As far-fetched as it sounds, something like this could happen again. To make a modest contribution toward the prevention of future scandals, I offer these suggestions for nonprofit Boards and individual Directors:</p>
<p>• Consider setting limits on the number of terms a Director may serve. Some of the Cobb EMC Directors had served for 25 or 30 years. A continual influx of new Directors asking probing questions helps to keep the organization on track. Long-term service leads to Board complacency.</p>
<p>• Know the organization’s bylaws and squawk when one is violated.</p>
<p>• When presented with a proposal for a major initiative or a significant change in direction, ask questions, beginning with “Why?” “Why do we need this?” “What’s driving this change?”</p>
<p>• Take a stand. Vigorous debate about important issues is crucial to the health of any organization. When you’re advocating for your constituency, try to persuade your fellow Directors to come around to your perspective. All votes on important issues will appear in the Board minutes—along with which Directors voted “for” or “against” the motion. These minutes should be shared with the membership so the true “owners” of the COOP are fully informed.</p>
<p>• Most importantly, if you’re concerned that illegal activity is taking place, report it immediately to your local district attorney.</p>
<p>In the next couple of weeks I’ll be writing a series of posts about national energy policy. Thanks for reading.</p>
]]></content:encoded>
			<wfw:commentRss>http://windward.ws/ignorance-is-not-bliss/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing the Project Lifecycle</title>
		<link>http://windward.ws/managing-the-project-lifecycle/</link>
		<comments>http://windward.ws/managing-the-project-lifecycle/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 18:34:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://windward.ws/?p=292</guid>
		<description><![CDATA[The chart shown below is an eagle-eye view of project management. I use it to explain how to prevent problems which may occur during implementation by devoting some extra attention to the first three phases of the project lifecycle. Too many times I’ve heard the statement, “I’ve got the concept, let’s go.” This approach is<span>... </span><a href="http://windward.ws/managing-the-project-lifecycle/">Read on</a>]]></description>
			<content:encoded><![CDATA[<p>The chart shown below is an eagle-eye view of project management. I use it to explain how to prevent problems which may occur during implementation by devoting some extra attention to the first three phases of the project lifecycle. Too many times I’ve heard the statement, “I’ve got the concept, let’s go.” This approach is the fastest route to failure.</p>
<p>Today I am addressing <strong>senior business executives</strong> in the role of <strong>project sponsors</strong>. You hold an eagle-eye perspective, and you’re in the best position to ask the tough questions which will steer a project away from danger. The project manager—even if s/he is an executive—is focused on producing short-term results and will not be able to see the big picture at the same time. It’s up to senior executives to bridge the “perspective gap.”</p>
<p><img class="alignright size-full wp-image-293" title="lifecycle" src="http://windward.ws/wp-content/uploads/2011/04/lifecycle.png" alt="" width="322" height="243" />Depending on what industry you’re in and the maturity of your company, what I call the “Normal Project Lifecycle” may resemble your own project lifecycle, appear very simplistic compared to your more rigorous process, or represent an ideal you’re striving for.</p>
<h2><strong>Business Case</strong></h2>
<p>Most projects begin with a business case. The most important outcome of this phase is clear, measurable <strong>objectives</strong>. Projects can drift toward opportunities and away from impediments. One of the most important things an executive sponsor does is hold the project manager accountable for meeting the <strong>original objectives</strong>.  Note that projects always have more than one objective.</p>
<p>To test the worthiness of a business case, these are some of the questions you might ask:</p>
<ul>
<li>“Is there a market for this product or service?”</li>
<li>“What is the expected ROI?”</li>
<li>“What are the risks?”</li>
<li>“Are there better or more strategic investments we might make instead of this one?”</li>
<li>“Do we have the right resources?</li>
<li>“Are our competitors in a position to do the same thing better/faster/cheaper?”</li>
</ul>
<p>If you give the go ahead, this is the point at which a budget is established and planning begins.</p>
<h2><strong>Plan</strong></h2>
<p>Planners work out the details that were probably glossed over during the development of the business case. (After all, salespeople will say almost anything to get a deal.) Planners identify all the tasks, establish a schedule, and determine whether resources are available in-house or must be outsourced.</p>
<p>When presented with a plan, the first question to ask is “What haven’t we thought about?” This is the time to perform a formal risk assessment. Changes to market conditions, shifts in the competitive landscape, emerging technologies, labor disruptions—all of these should be surveyed again—especially if the planning required more than a month or two.</p>
<h2><strong>Design</strong></h2>
<p>By the end of the design phase, the technical team should have verified that the task list is complete and identified who is doing what. They should also have established relationships with suppliers and know what equipment is needed and what the lead times are.</p>
<p>At this point, it’s important to ask whether the project can meet the original objectives on time and within budget. If not, a new business case should be made or the project scrapped. It’s also important to perform another risk review. Have market conditions changed? Are we trailing the competition rather than leading?  Has the projected ROI changed? What is still unknown? Open the gate to implementation only when the answers to all these questions point to success.</p>
<h2><strong>Implementation</strong></h2>
<p>I call the implementation phase the danger zone because this is where any glossed-over details will rear their ugly little heads. Problems arising during implementation— whether it’s called construction, fabrication, development, or something else—are very expensive to fix and can have disastrous consequences for the profitability of the project.</p>
<p>Projects get cancelled all the time during implementation because of cost overruns, schedule delays, or the loss of market opportunity. Many of the projects I’m asked to review could have been implemented profitably if risk analyses had been more thorough. Others should have been scrapped before they got to the drawing board. In both cases, better planning would have prevented irrecoverable losses.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://windward.ws/managing-the-project-lifecycle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome</title>
		<link>http://windward.ws/welcome/</link>
		<comments>http://windward.ws/welcome/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 12:26:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://windward.ws/?p=287</guid>
		<description><![CDATA[Hello, and welcome to my new blog and updated website. I invite you to take a few minutes to browse the site and let me know what you think of it. You’re my guest, and I want my site to be useful and informative to you. I’ll be adding new content regularly, and I’m eager<span>... </span><a href="http://windward.ws/welcome/">Read on</a>]]></description>
			<content:encoded><![CDATA[<p>Hello, and welcome to my new blog and updated website. I invite you to take a few minutes to browse the site and let me know what you think of it. You’re my guest, and I want my site to be useful and informative to you. I’ll be adding new content regularly, and I’m eager to hear what particular topics you want to hear more about.</p>
<p>In my consulting practice I apply project management discipline to all kinds of business problems. In my blog, I’ll be writing for an audience that includes <strong>business executives</strong>, <strong>engineers</strong>, <strong>project managers</strong>, and anyone interested in the topic <strong>“Energy and Our Future.”</strong> This year I am especially interested in helping business executives become more effective project sponsors. My very next blog post will feature a management tool that I give away to help project sponsors spot the early warning signs of projects entering the “Danger Zone.”</p>
<p>Next week, May 2, I’ll be giving a talk called “Leadership in Crisis Situations” to participants at the New Jersey PMI conference.  My talk is based on the lessons learned in one of the <a title="$100 Million Recovery" href="http://windward.ws/case-studies/100-million-recovery/">case studies</a> on this site. I’ll be giving the same talk to the North Carolina chapter of PMI on June 16. If you attend either of these sessions, please introduce yourself. If you do, and you mention this blog post, I’ll give you a free consultation on one of your current projects. I look forward to meeting you.</p>
<p style="text-align: right;"><em>David</em></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://windward.ws/welcome/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

