When examining why projects have failed, many observers blame poor project ‘Governance’. Poor, in this case, can mean a lack of governance, badly designed governance, but it is most often caused by overly complicated governance.
So what is project Governance, and why is it so important to the success of a project?
Let’s start by defining Governance: Roles and Responsibilities, and the structures and validation points to ensure those responsibilities are carried out.
Whoever you are in the program or project, you should clearly understand your role (such as Sponsor). It is just as important that you understand the responsibilities that go with the role (such as reading and challenging status reports, attending regular progress meetings, making decisions etc.). Once you take on those Responsibilities you must devote the time to discharge them. In a healthy project, stakeholders don’t ignore or delegate their responsibilities, as they understand the importance that their role plays in overall project success.
Think about almost any organised team sport in the world. Players have positions (Roles) and use tactics to outplay the opposition (Responsibilities). In this analogy it would not be acceptable for players comprehensively beaten to say “I didn’t know what to do”, or “I wasn’t told”. Imagine a football goalie saying “I didn’t know I had to stop a goal being scored”! That excuse would never fly. This is why training and reinforcement play such a critical role in the team members’ understanding of their responsibilities.
Governance may have been set up, but sometimes team members haven’t understood their own roles and responsibilities. Maybe the Governance Framework documentation was well written, but unless teams are made aware of, and trained in the Governance framework (and the part they play) – what’s the point? This is particularly important for new team members – it is not a one-off exercise and should be regularly revisited with the whole team. A good example of specific responsibilities might be the role of software developer. Without clear, measurable responsibilities (KPIs) they can (and might do) whatever they like. For this role, specific responsibilities might be:
- Attendance at mandatory meetings,
- Focus on quality as measured by defect rates,
- Document to team quality standards,
- Alert the team to poor practices/ call out better ways of working.
Sometimes in the event that roles and responsibilities are not properly documented, people will confuse their responsibilities with others, which can lead to a number of negative outcomes:
- Duplication of effort (ringing any bells?),
- Tasks not being done (“it’s not my responsibility”)
- Contradictory/ misleading reporting
- Turf wars
- And just a lot of wasted time, effort – and money!
To sum up …
The word ‘regular’ is used a lot in this article. Governance isn’t a set-and-forget thing. It is an evolving practice which has a critical impact on project performance. Getting into the cycle of review/update doesn’t have to be a burden, and the benefits which can be gained can make a significant and enduring impact on your organisation and the people who make projects succeed.
Creating overly complicated and detailed governance frameworks can make the situation worse. Keep it simple, just make sure people know their roles and responsibilities – and follow through!