Tailoring & Effectiveness

Good governance gives people enough direction and oversight to make sound decisions, without adding reviews or reports that do not help. The right approach depends on the project's size, uncertainty, risks, rules, and stakeholders.

Tailor Governance to the Project

Consider these factors when deciding how much governance a project needs:

Factor What it can mean in practice
Project size A small internal improvement may need a sponsor and a short status check. A large investment may need several approval levels and regular reporting.
Complexity A project with many teams, suppliers, or technical dependencies needs clearer decision owners and ways to resolve conflicts.
Risk and uncertainty If costs, safety, or outcomes are uncertain, decision-makers may need more frequent forecasts, clearer limits, and independent checks.
Regulation Laws or policies may require specific approvals, records, independent reviews, or retention of evidence.
Organization Existing policies, portfolio reviews, and leadership roles affect who can approve work and how decisions are made.
Stakeholders When customers, regulators, teams, or business units have competing needs, make decision rights and escalation routes explicit.

Tailoring explains the general idea. For governance, tailoring means choosing who does each review, what information they need, how often reviews happen, and which decisions must be referred to a higher authority.

For example, a small project might let its sponsor approve routine changes in a brief monthly check-in. A regulated project might require a documented review by an independent group before a major phase can begin. Neither approach is automatically better: it should fit the decisions and risks involved.

Lightweight governance More formal governance
Sponsor and project manager make most decisions A steering group or several authorities share decisions
Simple limits define what the team can approve Approval roles and decisions reserved for senior leaders are documented
Reviews happen when a decision or issue comes up Reviews follow a schedule or occur at formal phase gates
Changes are recorded simply Changes have formal records and may receive independent review
People communicate directly Status, decisions, and escalations follow agreed reporting routes

Lightweight does not mean unclear, and formal does not automatically mean effective. In either case, people should know who decides, what evidence is needed, and how to raise an issue.

Adapt Governance to the Development Approach

The project's development approach affects when decisions are made and what gets reviewed:

Approach How governance often works Example
Predictive Review progress at planned phases, compare forecasts with approved plans, and use agreed limits for changes. Before moving from design to construction, leaders review cost, schedule, risks, and readiness.
Adaptive Review results frequently. Teams can make day-to-day product choices, while leaders set boundaries for funding, risk, and release. A product team demonstrates a working update every few weeks; the sponsor checks whether it is delivering useful outcomes.
Hybrid Be clear about which decisions the team can make quickly and which affect longer-term commitments. The team can reorder short-term work, but a change to the release date or total funding needs sponsor approval.

Predictive Governance Considerations

Predictive projects may need extra controls when decisions sit with senior leaders or funding is released in stages. Use them when the project's decision structure or exposure calls for them, not just because the project is predictive.

  • Escalation: Agree how the team raises a problem when it cannot resolve it within its authority. In a hierarchical organization, a senior leader may be able to settle a conflict, remove a persistent obstacle, or provide resources the team cannot access. Define what triggers escalation, who receives it, and how quickly a response is expected. See the Governance Model for more on escalation.

    Example: If two departments cannot agree on access to a test facility, the project manager escalates the conflict to the sponsor, who can set the priority.

  • Investment control: When an organization must formally oversee project funding, set review points before major commitments or later funding releases. At each point, decision-makers check spending to date, expected returns, risks, and whether the Business Case still supports investing. They can continue, change, pause, or stop the work.

    Example: A lender financing a construction project may review the design and forecast costs before releasing funds for the build phase. If costs or risks have changed enough to undermine the expected return, the lender can reconsider the next investment.

Set SMART Performance Objectives

Use SMART criteria to make project objectives clear, attainable, and trackable. SMART stands for specific, measurable, achievable, realistic, and time-bound:

  • Specific: State the outcome or change sought, and who or what it applies to.
  • Measurable: Define evidence that will show progress or completion.
  • Achievable: Set an objective that can be accomplished with the authority and resources available.
  • Realistic: Check that the objective fits the project's constraints, context, and risk.
  • Time-bound: Set a target date or period for achievement.

For example, replace “improve delivery performance” with “reduce late customer deliveries from 12% to 6% by the end of Q4.” The second objective names the result, a measurable baseline and target, and a deadline. Confirm that the target is achievable and realistic for the project before approving it.

Metrics and Mechanisms for Effective Governance

Whatever the governance style, decision-makers need three things:

  1. Measures that show whether the project is achieving important outcomes. Choose measures that connect project results to the organization's goals. For example, if a project is meant to reduce delivery delays, track delivery performance—not just how busy the team is.
  2. Signals that show when action may be needed. A leading indicator is a measure or observable condition that provides an early warning about likely future performance, such as a rising number of unresolved design issues or disengaged stakeholders. A lagging indicator measures an outcome or event after it has occurred, such as completed deliverables, schedule or cost variance, or resources consumed. Leading indicators can give the team time to prevent a problem; lagging indicators confirm what happened and help assess results. When a leading indicator trends unfavorably, investigate its cause and take corrective action before performance exceeds agreed tolerances where possible. Use lagging results to understand past performance and look for relevant correlations that may reveal root causes.
  3. Feedback that helps improve decisions. After a decision, check what happened. Did the change protect the outcome? Did a funding decision rely on assumptions that proved wrong? Use what you learn to make future decisions better.

Useful governance measures focus on outcomes, or on a reasonable proxy for them:

Governance question Example measure
Are we choosing projects that are worth the investment? Compare expected and realized benefits or return on investment (ROI) with the assumptions used to prioritize the work.
Are decisions helping us meet dates we committed to? Track the share of committed milestones met. Read this alongside scope changes and how accurate earlier forecasts were.
Is the approved plan still the best option for delivering value? Compare the current scope, schedule, cost, and risks with available alternatives. Check whether the chosen plan still offers the strongest value for the intended outcomes.

Measures such as resource utilization, compliance with standards, or training completion can help explain how work is going. On their own, however, they do not show whether the project is delivering valuable outcomes. Use them alongside outcome measures.

Process Measures

Process measures help show whether governance itself is working. Use them to spot delays, weak handoffs, or decisions that are not being acted on:

Question Example signals
Are decisions made in time? How long decisions wait, how long approval takes, or how often a request is returned because information is missing.
Do decisions lead to action? Whether agreed actions are completed on time, or whether decisions have to be reversed or redone.
Does escalation work? How long issues take to resolve, whether they reach the right decision-maker, or whether the same issue keeps returning.
Are changes controlled? How long changes wait for a decision, whether approved changes are implemented, or whether plans are updated afterward.
Does oversight provide early warning? Whether forecasts are reliable and exceptions are spotted before they exceed agreed limits.
Does governance protect value? Whether expected benefits remain achievable and leaders act when key assumptions no longer hold.

A quick approval is not automatically a good approval. Consider whether the decision was sound, put into practice, and helpful to the intended outcome—not just how fast it was made.

Review Governance Effectiveness

Periodically discuss questions like these with the people involved in governance:

  1. Which decisions changed what the project did or protected its intended value?
  2. Did anyone lack the authority to act, causing delay or duplicate work?
  3. Did decision-makers get useful information in time? Was it trustworthy?
  4. Did any approval limit create unnecessary escalations—or fail to flag a real problem?
  5. What review, report, or approval could be simplified, delegated, automated, or removed?

Do not judge governance by a metric alone: people can optimize a number while missing the real outcome. Look at the trend, ask what caused it, and decide what action it calls for. If a report does not help anyone make or improve a decision, reconsider whether it is needed.