There is a conversation that happens fairly regularly in my work, usually after something has already gone sideways. A VP calls. A board member reaches out. An operations lead is quietly frustrated. The story is the same: a major infrastructure or workspace project is launched with everyone aligned on the outcome, but no one is clearly aligned on who is accountable for which decisions, at which stages, and through which channels.
That gap between intent and structured authority is where infrastructure projects quietly collapse. Not from a lack of effort, and rarely from a lack of budget. From a lack of governance.
Why Governance Fails Before Projects Do
Most project governance fails at the design stage, meaning it was never really designed at all. What gets built instead is a loose understanding of roles. Leadership assumes the project manager is accountable. The project manager assumes leadership and makes the calls. The vendors are filling the vacuum.
I’ve seen this pattern across real estate portfolios, multi-site workplace transitions, and complex IT infrastructure rollouts. The organizational alignment problem isn’t about people; it’s structural. When decision authority is undefined, people default to what’s comfortable: their domain, their relationship with the vendor, or the path of least resistance.
The result? Scope creep was accepted without authorization. Change orders approved informally. Decisions made below the appropriate level that cascade into budget overruns no one saw coming. And when it surfaces, it surfaces late.
Governance isn’t bureaucracy. It’s the architecture of accountability. When done well, it actually speeds up projects because everyone knows who can say yes, who needs to be informed, and who needs to escalate.
Read this to get a better insight into governance: Governance Structures for Complex Projects.
The Three Layers of Decision Authority Worth Getting Right
1. Strategic Authority
Strategic authority belongs to ownership or executive leadership. This is the layer that defines success, not just project completion but business continuity, brand alignment, cost discipline, and long-term operational performance. What I’ve observed is that this layer often delegates too early, handing the reins to internal operations or directly to a vendor relationship without retaining meaningful oversight.
Retaining strategic authority doesn’t mean micromanaging. It means staying in the information flow at the right altitude. It means insisting on structured reporting that isn’t just vendor-generated. It means having an independent advisor whose job is to protect the owner’s interests, not just manage deliverables.
2. Operational Authority
Operational authority is where project management lives. This layer should have clear decision rights over execution, scheduling, vendor coordination, issue escalation, and day-to-day scope management. The problem is that operational authority without proper boundaries becomes a de facto decision layer for things that should go upward.
A strong governance structure defines what decisions can be made at this level, what requires escalation, and what triggers a formal review. This isn’t about limiting authority; it’s about protecting the person at this level from being put in an impossible position when something significant comes up.
3. Provider Authority
This is where most owner-side governance breaks down. Vendors, even highly competent, well-intentioned ones, are optimizing for their own deliverables, timelines, and contractual protections. That’s their job. The owner’s job is to maintain authority over decisions that affect scope, cost, and long-term fit.
A well-structured engagement explicitly defines provider authority: what they control, what they recommend, and what requires owner sign-off. Without that structure, vendors inadvertently or occasionally deliberately fill the authority vacuum.
Read this for preventing misalignment between owners and vendors.
Organizational Alignment Isn’t a One-Time Meeting
One of the most common misunderstandings I encounter is treating alignment as an event rather than a discipline. Leadership aligns in the kickoff. Then, 90 days into execution, the project manager is fielding questions from a vendor that require strategic input, but there’s no clear path to get it, so a decision is made by default.
Organizational Alignment During Growth and Infrastructure Change requires a communication structure that is active throughout the project lifecycle. Who gets what reports? At what cadence? What format? Who is the decision authority for change orders under a certain threshold versus over it? What’s the escalation path when a vendor pushes back?
These aren’t complicated questions, but they need to be answered before the project starts, documented, and revisited at structured intervals. When I work through Lightwater’s Strategic Needs Assessment with an owner, establishing this communication architecture is one of the first things we build. Not because it’s procedurally satisfying, but because it determines whether everything downstream will actually be manageable.
The Lightwater Approach: From Assessment to Oversight
The framework I’ve developed over more than two decades of infrastructure leadership and advisory work is built around three phases, not because a framework sounds credible, but because the sequence actually matters.
The Strategic Needs Assessment comes first because the most expensive mistakes in infrastructure happen when solutions are selected before the problem is fully understood. This phase isn’t about gathering requirements in a spreadsheet. It’s about understanding the organizational dynamics, the hidden constraints, the risk profile, and, critically, what governance structure the owner is actually capable of sustaining.
Curated Provider Alignment follows. The right vendor is not the vendor with the best pitch. It’s the vendor whose capabilities, culture, and contractual structure fit the owner’s actual situation. I’ve seen organizations sign with impressive firms and struggle because the provider’s model required a level of internal bandwidth the owner didn’t have. Provider alignment means matching not just on capabilities; it means matching on communication style, risk tolerance, and accountability norms.
Here’s How Vendors Structure Contracts to Protect Themselves.
Structured Engagement & Oversight is where governance lives day-to-day. This phase includes establishing communication rhythms, reporting structures, and decision-escalation pathways that maintain owner authority throughout delivery. It’s also the phase that most organizations skip, moving directly from selection to execution without building the oversight architecture. That’s where control erodes.
Communication Structure as a Governance Tool
If you want to know whether a project is going to stay on track, look at the communication structure before you look at the schedule. The vendor manages the schedule. The communication structure is what the owner controls.
A functional communication structure typically includes:
- Weekly operational status updates with a defined format, not narrative emails from the vendor.
- A documented change order authority matrix, who approves what, at what threshold.
- A risk register is reviewed at regular intervals, not just when something breaks.
- Clear escalation triggers, conditions that automatically require executive involvement.
Communication structure isn’t administrative overhead. It’s how owners stay in control without being in every room. Also read Contract Clauses Owners Should Understand.
Continuity After Implementation
When a major initiative closes, the governance structure typically dissolves with the project team. Then, six to eighteen months later, problems emerge that nobody owns.
Continuity planning should be part of the engagement from the start, including who holds the vendor relationships, who has the institutional knowledge, and what post-implementation reviews are scheduled. The investment in a well-executed project is quickly eroded without a handoff structure.
“Rich’s attention to detail, ability to communicate with all levels of the corporate ladder, and ability to create timelines and execute accordingly are a package of attributes not found in many people. Over approximately ten years, his capacity to help people improve — and to do so consistently — made a lasting difference.”
Mark Shapiro | EVP Logistics, Workspace
Where to Start
If you’re heading into a significant infrastructure initiative or if you’re mid-project and feeling like something is structurally off, the place to start is an honest assessment of how decision authority is currently structured. Not as it was intended to be, but as it actually functions day-to-day.
That assessment usually reveals more than the project plan does. And it tends to surface the risks that are hardest to see from inside the engagement.
Ready to assess your current governance structure? Request a Private Strategy Call →