We’ve been doing some thinking at work recently about how to improve the project management processes. The processes aren’t terrible, but it’s good to review them every so often to see how the rest of the business has changed and how we should keep up.
However, project management outcomes are more important than processes. Processes should facilitate outcomes, but often we spend so much time looking at process maps that we forget what the processes are even there for.
Project teams should be geared around delivering outcomes. Processes can help you get there in a repeatable way. Processes add structure, which is good for new starters and for making sure things are done almost automatically. But don’t design your team around how the processes work: design it around what you want the projects to do.
Project management outcomes are the results – the outputs from any process. This is what counts. Processes are how you get there. That makes processes relevant and important. But when you design project management processes you should focus on the end result: the outcome. If the process doesn’t help you get there then it isn’t a very good process.
Do any of your processes hinder, rather than help, you achieve your objectives? If so, what are you going to do about it?