Steering Committees Might Be Too Late

One of the most common governance mistakes I see is expecting steering committees to operate at the same level of detail as the project team. They shouldn't.

In fact, if a steering committee is spending its time discussing individual requirements, task assignments, defect counts, or detailed project activities, something has already gone wrong.

Steering committees exist because leaders have responsibilities that are different from those of the delivery team.

• The project team's job is to manage the work.

• The steering committee's job is to govern outcomes.

Yet many organizations unintentionally blur those lines. When that happens, governance meetings become lengthy status reviews instead of strategic decision-making forums.

Risks Are Usually Known Long Before Governance Meetings

I've participated in countless steering committee meetings where a risk is formally presented for discussion, only to discover that the project team has been aware of the issue for weeks.

• The developers knew.

• The business analysts knew.

• The project manager knew.

• Often, even the stakeholders knew.

  
  

The steering committee was simply the last group to hear about it.

That raises an important question: Why are we waiting for the steering committee to discover risks?

The purpose of governance is not risk discovery.

The purpose of governance is risk response.

The Right Level of Detail

A project team should operate in the details.

They should know:

• Which tasks are behind schedule

• Which requirements are changing

• Which defects remain unresolved

• Which resources are overloaded

• Which dependencies are creating challenges

That level of detail is necessary to manage delivery effectively.

A steering committee, however, should be focused on a different set of questions:

• Is the initiative still aligned with business objectives?

• Are we achieving the intended outcomes?

• Do we need to adjust scope, timeline, or funding?

• Are there organizational barriers that require executive action?

• What decisions cannot be made at the project level?

The steering committee does not need to know every detail.

They need to understand enough to make informed decisions.

If executives are spending their time reviewing individual project activities, they are operating too far down in the organization. If project teams are waiting for steering committee meetings to solve operational issues, they are operating too far up.

Both create delays.

Governance Should Be About Decisions, Not Updates

A useful test is this:

At the end of a steering committee meeting, what changed?

If the answer is simply that leadership received updates, the meeting probably wasn't governance.

Governance should result in decisions.

• Approvals.

• Prioritization choices.

• Resource commitments.

• Risk acceptance.

• Strategic direction.

  
  

The project team should arrive having already identified the issue, analyzed options, and developed recommendations.

The steering committee should arrive prepared to make decisions that the team cannot make on its own.

Visibility Matters More Than Reporting

The healthiest organizations create environments where risks surface continuously rather than waiting for formal governance cycles.

Team members feel comfortable raising concerns early.

Leaders encourage transparency.

Bad news travels quickly.

As a result, steering committees rarely hear surprises.

Instead, they hear well-understood issues accompanied by clear recommendations.

That's exactly how governance should work.

The project team manages the details.

The steering committee governs the outcomes.

When those roles are clear, meetings become shorter, decisions become faster, and organizations spend less time reporting and more time delivering.

How does your organization balance project-level management and executive governance? Does your steering committee focus on decisions, or does it spend most of its time reviewing project details?