Why Projects are Hard
February 17th, 2004 by HalThis sidebar to Frank Patrick's series on Promises and Prescriptions attempts to show why it is we find projects hard. I found it hard to understand the sidebar! (Just kidding Frank.)
Projects are hard due to the interaction of uncertainty and variability. Our efforts to minimize uncertainty, for instance by deciding early, serve to limit the actions available to performers as the future unfolds. At the same time, we introduce variability by being unreliable with our project commitments. "Hard" is an understatement.
For those of you subscribing to Reforming Project Management via Bloglet, you can add a subscription to Frank's Focussed Performance Business Blog and have our postings delivered together automagically in the same email message. (You'll find Frank's subscription box at the top of the right-hand column.) Try it out for awhile.
Related Posts
- Bringing New People to Your Project Needn’t Be Hard As project performers come and go you'll need a strategy for them to be successful. Johanna is ready to help. Read h...
- Taking a Lean Approach is Hard Work Seth Godin writes A Brief History of Hard Work, Adjusted for Risk in Fast Company. Check out Seth's Blog for more of hi...
- Seth’s “The Dip” Makes the NY Times Best Sellers This is quite funny. While The Dip made the hard-to-break NYT Best Sellers list, one of the editors shared how much mus...
- Call for Book Proposals We need your help. Listeners were so happy with the first conversation with David Schmaltz that Greg Howell and I have...
- Habits Die Hard This is a continuation of my series of postings on the theme Variation as an Enabler that started on Sept 12th. It's ob...
February 18th, 2004 at 5:38 pm
Your Bloglet subscription has worked just fine! (Although it’s worth checking every once in a while.)