When Governance Becomes the Work

Good governance helps leaders manage complexity without burying teams under process.

“You’re gonna need a bigger boat.”

In Jaws, the line works because Chief Brody sees the shark and realizes the structure around him is not equal to the problem in front of him.

Complex programs can create a similar reaction. The work starts to feel larger, riskier, or harder to control, and the natural response is to add more governance. Another forum. A more detailed dashboard. A heavier reporting cycle.

The question is whether the bigger boat helps the team move, or simply gives everyone more room to keep discussing the same unresolved decisions.

In complex programs, governance usually begins as a reasonable response to uncertainty.

Leaders need a steadier view of the work as it stretches across functions, and teams need a way to raise issues before hallway escalation becomes the operating model. Good governance gives complex work enough structure to hold together when pressure increases.

The problem begins when the structure keeps expanding while the decision system underneath it remains weak. Another forum appears. The dashboard gets more detailed. The reporting cycle takes more time. The effort receives more attention, but the critical decisions stay open and familiar blockers keep returning.

After a while, the team starts preparing for the next governance discussion instead of resolving the issue the forum was meant to address. Governance begins to bury the work it was created to support.

In my experience, governance creates value only when the meeting changes the next step. If the team leaves with the decision still unresolved, the owner still unclear, and the blocker merely better described, the process has produced visibility without movement. The program may look better managed while becoming harder to move.

How governance gets heavier

Governance rarely becomes heavy in one obvious moment. It usually accumulates through reasonable requests.

A sponsor asks for more visibility because the effort feels uncertain. A leader asks for a separate review before the steering committee because the topic is sensitive. A workstream prepares a special update because one audience needs more context. None of these moves is necessarily wrong. Over time, though, the program develops a second layer of activity around the actual delivery.

The team still has to deliver, while translating the same story for a growing set of review routines.

At first, this can feel productive. More people are paying attention. The artifacts look cleaner. The status story becomes more polished. Leaders can point to a stronger governance routine and feel that the program is under tighter control.

That control only matters when an issue leaves the room closer to a decision.

Useful governance helps the team move. The right forum gets the decision maker into the conversation. The right dashboard provides enough evidence to support a tradeoff. The right escalation path helps an issue move from concern to resolution.

Governance creates drag when it mainly adds preparation. The team spends more time translating the same story while the underlying issue remains unresolved. When that starts happening, the governance rhythm deserves the same scrutiny as the delivery plan.

Where the decision system breaks

Governance often starts to fail where a decision has to cross organizational boundaries.

The issue may be visible. The risk may be documented. The dependency may be understood. The team may even agree that a decision is needed. What remains unclear is who has the authority to make the call and what would allow the decision to stick.

The drag shows up in the waiting. Product is not ready to commit without technical confidence. Technology wants clearer risk boundaries. Finance needs enough confidence in the value case. Operations is thinking about readiness. Each group has a valid concern, and the decision keeps slipping because the governance path has not forced those concerns into a single recommendation.

This is where weak governance becomes expensive. The issue has appeared in the deck, the notes, the risk log, and the meeting discussion. The organization can see the problem, but the governance routine has not created a path to resolve it.

The program keeps circling the issue. People refine the language. The update becomes more careful. The explanation becomes more complete. The decision remains exactly where it was.

The decisions no one wants to own

There is another version of this pattern that is harder to name.

Sometimes everyone knows a decision is needed, and no one wants visible accountability for the call. The decision may disappoint a stakeholder, reduce scope, expose a missed assumption, or force a conversation leaders would rather avoid.

When that happens, the decision can become politically orphaned. Everyone stays engaged with the topic, but no one fully owns the call. The governance forum keeps returning to the issue, and the status remains carefully worded. The organization continues to discuss options while the decision remains exposed and unresolved.

This is one of the places where governance has to be more than a reporting routine. It has to make avoidance harder to hide. A useful governance rhythm names the decision, clarifies who owns the recommendation, and makes the cost of delay visible enough that leaders can act.

The governance routine should at least prevent continued discussion from passing as progress.

This matters in transformation, data, AI, risk, and operating model work because decisions often cut across traditional boundaries. A decision may look straightforward until the organization realizes how many groups have a legitimate stake in the answer. When governance does not account for that complexity, decisions sit open while teams keep preparing updates.

That is how process starts to bury the work it was supposed to support.

What useful governance changes

The test of governance is what changes after the meeting.

A useful governance routine does not need to capture every detail of the program. It needs to help leaders understand where attention is needed and what should happen next.

A governance forum should have a clear reason to exist. People should understand what belongs there and what should be handled elsewhere. The right people need to be present, especially when the topic requires a decision instead of another round of discussion.

The team also needs a clearer trail after each meeting. Leaders should be able to tell what changed, what decision was made, who owns the next move, and what evidence is needed before the issue returns.

Without that kind of trail, the issue can return with better wording and no movement.

A good governance rhythm reduces ambiguity over time. Complex programs will always have unresolved tradeoffs, but open issues should not circulate indefinitely without an owner or a path to decision. When an issue keeps coming back with more polished language and little movement, leaders should treat that as evidence that the governance rhythm needs attention.

This is where governance and program drift connect. Drift continues when teams keep discussing the work without resolving the decisions underneath it. A stronger rhythm forces the issue toward a decision, an owner, or a deliberate escalation.

The human side of governance

Governance forums carry the organization’s history with difficult decisions.

People remember what happened the last time a hard call went badly. A team under pressure may soften status language because it does not want to create alarm. A leader may ask for more detail because the summary no longer feels trustworthy. A workstream owner may avoid committing to a date because prior commitments were undone by later decisions.

Those behaviors shape what gets said in the room. They also shape what gets softened, delayed, or avoided.

A well-run forum makes it easier for teams to say what is stuck before the story gets softened for presentation. Leaders set that tone through the questions they ask and the way they respond when the news is uncomfortable.

A practical governance conversation is usually direct. The group should be able to name the decision in front of them, who owns it, what evidence is missing, and what happens if the organization waits.

Governance has to earn the time it consumes. Teams can handle difficult conversations when the routine helps them move the program. They become frustrated when governance only creates another performance of concern.

How leaders reset the rhythm

A governance reset does not need to be dramatic. In many cases, leaders can improve the rhythm by looking closely at each forum and asking whether it still helps the program move.

A reset usually starts by stripping the forum back to its purpose. If it exists mainly because people are anxious, it will probably create more reporting than resolution. If it exists to make a decision, the decision maker needs to be present. If it exists to manage risk, the conversation should lead to action instead of another restatement of concern.

From there, leaders should look at the preparation burden. Teams should not spend more time preparing for governance than using governance to resolve the program’s hardest issues. Some reporting is necessary. Excessive reporting becomes a tax on delivery, especially when different audiences want the same story in slightly different forms.

The meeting itself should produce something the team can use. A decision, a clearer owner, a path to escalation, or specific evidence for the next conversation is enough. When a meeting produces only discussion, the forum is probably designed around observation rather than movement.

The reset usually requires simplification. Remove duplicate forums. Reduce reporting that does not support decisions. Make ownership visible. Track open decisions with the same seriousness as open risks.

The goal is governance that helps the team spend less energy maintaining the process and more energy moving the program.

When weak governance becomes part of the drag

Weak governance changes the feel of a program slowly.

At first, the impact may seem manageable. A few decisions take longer. A few meetings feel repetitive. A few updates require more explanation than they used to.

Over a few weeks, those small frictions start changing the feel of the program. Teams become more cautious. Sponsors lose confidence in the story. Leaders begin asking for more detail because the status no longer feels stable. Eventually, the team begins to feel that it is managing the process more than moving the work.

The longer weak governance remains in place, the harder it becomes to separate reporting noise from execution risk. People may start to believe the program needs more oversight when the deeper need is a cleaner decision system.

Governance is easier to reset before the process becomes part of the drag. Leaders still have room to remove duplicate forums, simplify reporting, clarify decision rights, and reset escalation paths before the extra process becomes normalized.

Governance should help leaders see the work clearly enough to act. When it only helps them observe the work, the program remains vulnerable to drift.

Governance should move the work

Governance earns its place when it reduces friction around the decisions that matter most.

When governance works, the operating cadence changes in visible ways. Meetings have sharper purpose. Status is easier to understand. Risks are tied to action before they become background noise. Teams spend less time translating status for different audiences and more time resolving the issues that matter.

That kind of governance requires discipline and restraint. Leaders need enough structure to manage complexity and enough judgment to keep the structure from becoming the work.

For complex transformation work across data, AI, technology, risk, and operating model change, governance is one of the main ways leaders keep ambition connected to execution. The right rhythm helps prevent drift by making sure visibility leads to a decision, a tradeoff, or a clear next move.

Here is where I can help

This is the work I am focused on now: helping organizations stabilize complex transformation work across data, AI, technology, risk, and operating model initiatives when the work is important, cross-functional, under pressure, or when execution is starting to slow.

I am most useful when capable teams are already working hard and the work needs a cleaner decision system, stronger delivery governance, and a more practical operating rhythm. That may mean stepping in to help reset a program, support an executive sponsor, create structure around ambiguous work, or help a team convert effort back into progress.

If this sounds familiar in a program you are leading or supporting, I would be glad to talk. This is the kind of work I do.