No Intake. No Shared Rhythm. No Visibility. Nine Verticals Running Nine Different Ways.
When decisions needed to be made, they either escalated to the principals, creating a bottleneck at the top, or they stalled in the middle, waiting on someone who didn't know they were waiting. There was no third option. No system existed to route the right decisions to the right people at the right time.
Project initiation worked the same way. If a principal or department lead decided something was happening, it happened. If they didn't, it didn't, regardless of whether it should. There was no intake process, no criteria, no way to evaluate whether a new initiative was aligned with organizational priorities or whether the capacity existed to execute it properly.
Nine verticals were each running their own operating rhythm, some with regular standups, some with nothing formal at all, with no shared layer connecting any of them. Vendors were being onboarded without any vetting process. And beneath all of it: over 350 items listed as active projects, with no centralized governance and no shared visibility into how the work connected.
The most pressing operational problem was not process or methodology. It was structural. Teams could see their own work clearly. What they could not see was how their work connected to everything else, or whether it should.
Phase 1: See It Clearly Before You Touch It
The first order of business was not building systems. It was getting an honest picture of what existed.
We revived a stalled company-wide project roster, a unified visibility layer that a previous effort had attempted and abandoned. The concept was sound. What it needed was someone willing to build it properly and advocate for it organizationally.
We built the unified tracker in Airtable as a cross-organizational layer above the existing project management infrastructure. Every team logged what they considered active projects. That process surfaced the real picture.
Phase 2: Build the Operating Infrastructure
With the portfolio visible, the gaps became obvious. Five systems needed to exist that didn't.
Projects had been starting at the discretion of principals and department leads, with no formal criteria and no tracking. I designed a structured intake process: a defined path for how new work gets proposed, evaluated against organizational capacity and priorities, and approved or deferred. The process removed arbitrariness without removing authority. Principals and leads still made the calls, they just made them with better information and within a structure that created accountability.
Nine verticals were running nine different rhythms with no shared layer. Some had regular standups. Some had nothing formal at all. None of them connected. We designed and installed a cross-organizational operating cadence that gave leadership visibility into what was moving, what was blocked, and what needed a decision, without requiring everyone to be in every room. Consistency at the governance level. Autonomy at the execution level.
Work was being approved without any realistic assessment of whether the people responsible for it had capacity to do it. I designed a capacity framework and mentored project managers across the organization on how to use it, not just headcount math, but actual available hours, existing commitments, and realistic throughput. A capacity model is only as good as the judgment of the people using it. The mentoring component was as important as the system itself.
Vendors were being onboarded without any vetting process. New relationships were initiated, contracted, and activated before anyone had assessed whether the vendor was qualified, whether the terms were sound, or whether the organization was getting good value. I designed an evaluation framework that introduced criteria and process into vendor decisions without creating bureaucracy that slowed legitimate work.
Teams working on interconnected initiatives often had no idea the others existed. Effort was being duplicated. Dependencies were invisible. The organizational cost of that invisibility compounded daily. The cross-team coordination layer, built on top of the unified tracker, gave teams visibility into adjacent work that made real coordination possible for the first time.
Phase 3: The Patterns That Held
The most useful question I learned to ask was: what do we need to move this forward today? That question almost always surfaced the real constraint. And the real constraint was almost never the team doing the work.
When projects stalled, the instinct was to look at execution. In practice, the majority of delays traced back to unclear ownership, unavailable decision-makers, or misaligned priorities at the leadership level. None of those are execution problems. They are governance problems. The systems we built were designed to surface those problems early, when they are cheap to fix, rather than late, when they have already cost the organization.
On methodology: the instinct when building a PMO is to standardize on a single framework. I pushed back on this throughout. Nine verticals operating across fundamentally different work environments required different delivery approaches. What worked was a shared governance layer with methodology flexibility underneath.
Scale Exposes What Informality Hides
What we discovered when we mapped the portfolio properly was not chaos. It was the accumulated residue of years of good intentions without infrastructure. Projects approved without clear owners. Initiatives still active long after the strategic rationale had changed. Resources committed to work nobody could articulate the outcome of.
This is not unusual. This is what most organizations look like when you pull back the curtain at scale. The question is whether you find it before it costs you, or after.
The numbers here, 350 projects, nine verticals, are not the point. These patterns exist in organizations a tenth the size. They show up earlier, they're easier to absorb, and therefore easier to ignore. Until they're not.
If your team can't move without you in the room, that's a governance problem. If projects start because someone decided they should, with no intake process and no capacity check, that's a structural problem. If your vendors are being onboarded on faith, that's a risk problem.
Visibility is the foundation. You cannot prioritize what you cannot see. You cannot coordinate work you do not know exists. Building the cross-organizational view of how work fits together is the prerequisite for everything else.
The answer is rarely more tools, more headcount, or more process. It is usually clarity: about who owns what, how decisions get made, and whether your operational infrastructure is designed for where you are going.