A steering team that nobody listens to is a calendar expense. One whose decisions hold is one of the most valuable governance assets an asset-management program can have, and one of the rarest. In my experience the difference comes down to one thing: whether anyone has the patience to stand the team up properly and mentor it through the first uncomfortable year.
There are three stages to building a steering team that earns its keep: chartering it, standing it up, and mentoring it past the awkward early period while it builds credibility. None of it is glamorous. Each stage builds on the last.
Why steering teams matter (and why they fail)
The case for a steering team is simple. Asset-management programs cut across silos: operations, maintenance, capital planning, finance, IT, and executive leadership. Decisions that have to hold across those silos can’t belong to any one of them. Somebody has to put the trade-offs on the table, write down the reasons, and remember why decisions were made after the people who made them are gone.
That’s the steering team’s job. Most of them fail at it, and I’ve seen it happen one of three ways:
- The team has no authority. It can recommend, but every recommendation has to be re-litigated by whoever controls the budget or the workflow. Members stop attending.
- The team has authority but no scope. Every meeting becomes a dumping ground for every adjacent issue. Members can’t tell what they’re supposed to decide.
- The team has both authority and scope but no facilitation. The senior person in the room dominates, the junior members go quiet, and decisions get made the same way they would have without a steering team in the first place.
You can fix all three. The fix is in the charter, the launch, and the mentoring, in that order.
Stage 1: Chartering the team
The charter is the document the steering team agrees to before its first meeting. Keep it short. The good ones run two to three pages. What’s in it matters more than how long it is.
Membership and roles
Name the seats, not just the levels. The seat is the function the steering team needs represented (operations, maintenance, capital planning, finance, IT, executive sponsor). The person filling the seat is who’s currently in that role. When they leave, the seat persists, and a successor steps in. Here’s why it matters: the steering teams that survive leadership change are built around seats. The ones built around personalities fall apart when those people leave.
Pick the chair carefully. Don’t hand it to the most senior person by default; that’s often the wrong choice. The chair’s job is to run the meeting, surface the harder questions, and make sure the quieter members get heard. That’s a different skill than being the most senior executive.
Authority and decision rights
State explicitly what the team can decide and what it can only recommend. The cleanest charters distinguish three tiers:
- Decide and act. Decisions the team can make and implement without further approval, usually within an agreed budget or risk envelope.
- Recommend with authority. Decisions that go to a higher level (board, executive committee) with the steering team’s formal recommendation, where overruling is allowed but uncommon.
- Advise. Issues where the team provides input but the decision lives elsewhere. Be honest when this is the case. This is where most steering teams slide into being advisory-only without anyone deciding it.
Cadence and scope
Monthly is usually right. Quarterly is too far apart to keep momentum. Go weekly and your senior members stop coming. Whatever cadence you pick, protect it. A meeting that keeps getting rescheduled has no credibility left within six months.
Scope means writing down what the steering team owns and, equally important, what it doesn’t. The exclusion list is the part most teams skip, and it’s the part that saves you later when somebody tries to drag in an unrelated fight.
The exclusion clause in a steering team charter is more useful than the inclusion clause. The first time someone tries to expand the agenda inappropriately, you have a written reason to push back.
Stage 2: Standing the team up
The first six to eight weeks decide how this goes. The habits you form in those early meetings are the habits you’ll have for the next two years. Three things matter most.
The first meeting
The first meeting should not try to make any real decisions. It should walk through the charter, agree on it, and discuss one or two illustrative scenarios the team will likely face. The goal is to align on how the team will operate before there’s a contentious decision in front of it. Put a hard call in front of them at the first meeting and they won’t have the muscle yet to handle it.
Early decisions that build credibility
The second and third meetings should put a handful of medium-stakes decisions in front of the team: decisions where the steering team’s involvement clearly adds value but where the consequences of getting it slightly wrong are bounded. These early decisions are how the team builds trust with itself and with the organization watching it. Jumping straight to the highest-stakes decision in meeting two is a common mistake. You don’t want the team learning how to disagree when getting it wrong is expensive.
Common early failure modes
Three patterns to watch for and head off:
- Status-meeting drift. The team starts spending more time hearing updates than making decisions. The fix is a standing agenda template that allocates most of the time to decisions, with updates strictly time-boxed.
- Senior-member dominance. One member, usually the most senior or the loudest, dominates the discussion. The chair has to break this pattern early, before it becomes the team’s default. Direct invitations to the quieter members work better than general “does anyone else have thoughts” appeals.
- Decision avoidance. The team consistently kicks decisions to “next month with more data.” This is often a sign the charter’s authority section isn’t clear, or that members don’t feel they have permission to commit. Call it out in the room. It won’t fix itself.
Stage 3: Mentoring through the first year
Mentoring decides whether this becomes a real governance asset or one more standing meeting on everybody’s calendar. The maturity curve usually has four stages, each lasting roughly two to four months.
Months 1–3: Norms and pattern-setting
The team is learning how to disagree, how to surface concerns, and how to commit. The chair is doing most of the heavy lifting, decisions are smaller, and trust is being built. This stage is normal; don’t try to rush it.
Months 4–6: First hard calls
The team starts making real decisions with real consequences. This is where the charter’s authority section gets tested. If decisions stick (that is, if the organization respects the team’s calls even when somebody senior would prefer otherwise), the team’s credibility solidifies. If not, the charter needs revisiting.
Months 7–9: Operating rhythm
By this point, the team has a working pattern. Decisions are made within reasonable timeframes. Members trust each other to surface dissent constructively. The chair is doing less facilitation work because the team has internalized the norms. This is the stage where most external facilitation can step back.
Months 10–12: Membership refresh and continuity
By the end of the first year, the team should be thinking about succession. Who will replace the current chair? How do new members get onboarded? What’s the institutional knowledge that has to transfer? The teams that survive their second and third years are the ones that build these transitions into their normal operating rhythm instead of scrambling when someone leaves.
What good looks like
A steering team that’s doing its job is often invisible. Decisions get made, trade-offs get documented, and capital plans get defended. The team doesn’t generate dramatic moments because the drama happens inside the room and stays there.
The signs of a healthy steering team:
- Decisions reliably hold: what the team decides on Monday is still the answer on Friday.
- Quieter members are heard. The chair has institutionalized the practice of explicitly bringing them in.
- The team can revisit and change a prior decision without losing face. New information changes the answer, and that’s a feature.
- Membership transitions are managed, not improvised.
- The exclusion clause gets cited at least twice a year. Somebody has tried to drag in an adjacent issue and the team has politely pushed back.
None of this happens in a single engagement. Steering teams get stronger over years, and the work you put into the charter, the launch, and the early mentoring is what makes them last. Skip those stages and you better plan on rebuilding the team in three years, after spending the years in between putting on governance theater. Does your steering team decide anything, or does it just hear updates? When did one of its decisions last hold up against somebody senior who wanted a different answer?
