The levels of governance should generally be minimised, while ensuring there is sufficient separation to avoid conflicts of interest between those doing the work and those governing, and to facilitate escalation paths. Too many layers of governance dilute accountability and can slow down decision-making [1-SRO], (1).
In general, membership of the board should be limited to those who have ongoing ownership for the solution and those that will be most impacted by the operation, maintenance, benefits and risk. Similarly, risk and benefit ownership should be assigned to the individuals whose roles are best placed to control risk, and with ongoing ownership of benefits. For example, ownership of benefits should not reside with the delivery manager [3-DTA].
Involve users throughout the Service Design and Delivery Process to make sure their perspectives, needs and feedback are incorporated into the final service. Encourage shared ownership by co-designing accompanying artifacts, such as tutorials and guides, using language that is meaningful for all.
Tailor your digital service to meet the specific needs of users to promote inclusion and make sure support is provided at the appropriate level. Consider how you will apply the following cohort specific requirements when designing and delivering digital services.
Off
It is important that members of the board are not conflicted in decision-making, for example, an external vendor on a board that makes decisions on the vendor’s scope or payment. To avoid a conflict of interest, external supplier interests could be represented in a separate advisory committee, or represented by internal procurement management, as appropriate to the needs of the project.
Corporate boards have moved away from an emphasis on stakeholder representation to skills-based composition. Project boards should also look past stakeholder representation to consider the skills and capabilities that members contribute. Board members should include external members, and be chosen for their authority, expertise, experience, status and connection (11), focusing on people who:
Project boards rarely have the time or luxury to be able to develop complete knowledge of all aspects of any project. Some literacies can readily be taught, helping board members know what to look for and the questions to ask. Project board training can help rapidly develop core literacies (11, 21). Other board member capabilities are developed through years of experience. We differentiate between SROs’ and board members’ digital project literacies (Table 4), the collective experience the board should contain (Table 5), and the culture, attitude and behaviours that needs to be established for a digital project board to be effective (Table 6).
| Capability | Description |
|---|---|
| Benefits and outcomes | Understanding of benefits management processes, and the relationship between outputs and outcomes, benefits and value (23, 40) |
| Communication in the context of change | Understanding the importance of a project narrative, creating a culture of transparency, stakeholder identification, constructive conflict and feedback loops (20) |
| Project management foundations | Understanding of key project management concepts, giving the board the ability to question aspects of the project lifecycle, critical path, earned value, burn rate and baselines (5, 15, 23) |
The expertise needed on the Board should be guided by key areas of risk, both enterprise and project delivery.
| Skills | Description |
|---|---|
| Business expertise | Understanding of the business, impacts and change required for end users, allowing the board to maintain sight of the business logic of the project (5, 15, 23) |
| Operations expertise | Understanding of the operational environment to ensure the solution is integrated, maintainable and sustainable within the existing IT applications portfolio (29) |
| Digital project management expertise | Understanding of digital projects, their lifecycle, risks, ideally with experience in a similar type of project (e.g. AI, SAAS, risk tier) |
| Interpersonal skills and social capital | Strong networks and relationships that support negotiation, decision-making, issue resolution, stakeholder management, effective communication and resourcing (5, 28) |
| Digital, data and cyber expertise | Depending on the project type and stage, deep technical expertise may be required |
| Legal and policy | Depending on the project type and stage, regulatory and policy expertise may be required |
| Procurement and contract management | Depending on the project type and stage, expertise in procurement and contract management may be necessary |
| Independence | Balancing the need for vested interests, ensuring there is someone who can view the project and its progress objectively and independently |
| Supplier expertise | Depending on the project, experience and knowledge of the product, implementation approach and supply chain |
| Interdependencies | Knowledge of areas the project has interdependencies with, for example, resourcing, systems integration |
| Employee/customer experience | Expertise in ensuring a solution is well suited to the needs of the users of project deliverables |
| Change management expertise | Experts in communicating and designing organisational change, reducing resistance and increasing uptake of change |
| Financial expertise | Depending on the complexity, size, risk and procurement strategy of the project |
| Culture | Description |
|---|---|
| Skin in the game | Members should have a genuine interest, commitment and ownership of the project's success (28) |
| Psychological safety | Boards need to foster a no-blame environment where people feel safe with constructive conflict, raising ideas and escalating issues (23, 41) |
| "Can do" agency | Board membership is not a passive role. Members should take action to ensure they have the right information to support decisions and proactively identify strategies that enhance project success (23) |
| Time commitment | Board members often underestimate the time involved. Members must ensure they are suitably informed, attending meetings and prepared to support decision-making (11, 23, 42) |
| Courage | Courage to stop a project, escalate risks or reset the project if the project does not have sufficient business justification and/or delivery confidence is low (1, 25) |
| Attendance | Continuity in core board membership facilitates historically informed decision-making. Use of deputies or proxies should be avoided as it signals a lack of commitment, dilutes accountability and can delay decision-making (11). Members should not attend just to report to others (28) |
| Decision expediency | Boards need to make decisions escalated to them in a timely manner, possibly despite incomplete information. Decisions should be clear and prioritise action (23, 43) |
| Value-focused | Boards should suspend self-interest and operate from a position of what is best for the organisation and project, optimising value from the project investment |
| Empowering | The project board can make the decisions it needs to so that the project is empowered to deliver |
| Humility | Openness to learning and adaptation – seeking robust advice from independent advisors and project assurance, seeking out lessons learned from similar projects, listening to user and reference groups, acting on recommendations (1, 44) |