When project disaster strikes, we probably aren’t overly prepared for it. And the question then becomes what to do about it. What follows is one expert’s best guidance about what to do when disaster strikes—and how to appropriately manage in the face of impending challenge.
It’s a very strange thing, but we don’t really like success. We don’t embrace it. We often forget to celebrate it. We very frequently look upon the idea of rejoicing in success as an unproductive and unnecessary frivolity. But it doesn’t have to be this way…
We know we are supposed to learn from our projects. While we know this, acknowledge it and theoretically agree with it, for the most part we don’t do it. Lessons aren’t learned so much as they are observed. Can we change?
Do we recognize as project managers the kind of service we are describing? What service actually matters as a project manager? And how do we know that we are delivering it?
There’s been an increasing intersection between business analysis and project management. All of this can leave people scratching their heads and wondering what it all means. Where are the overlaps? Where are the boundaries? What does it mean to be a business analyst relative to what it means to being a project manager?
Some studies have suggested that risk management is more critical than every other project management tool and approach combined. It should be at the top of everyone’s mind. And yet, while many of us pay it lip service, it isn’t.