What problem does this system address?
Organizations that need cross-project coordination but cannot justify a formal PMO often default to ad hoc coordination, which produces dependency collisions, resource conflicts, and duplicated effort.
I assessed program management needs at a 150-person technology organization running 8-12 concurrent projects. They had no PMO and no dedicated program managers. Cross-team coordination happened through direct communication between project leads, which worked until it did not. I identified 23 dependency conflicts in a single quarter: instances where Team A’s project required a deliverable from Team B, but Team B had not planned for it or had scheduled it for a different date. Each conflict consumed an average of 18 person-hours to resolve (meetings, replanning, and emergency work). Total quarterly cost of ad hoc coordination: approximately 414 person-hours, or 2.6 FTEs worth of productive time consumed by coordination failures.
How is the system structured?
The system distributes PMO functions across 3 lightweight mechanisms: a dependency board, a monthly portfolio review, and a resource allocation protocol.
Step 1: Dependency board
A shared board (I used a simple Notion database) listing every cross-team dependency with 4 fields: providing team, consuming team, deliverable description, and agreed date. Updated weekly by project leads (5 minutes per lead per week). Reviewed in a 15-minute weekly dependency standup attended by all project leads. This single artifact eliminated 78% of dependency surprises by making them visible before they became conflicts. The key is that dependencies are tracked as commitments between teams, not as notes in individual project plans. According to program management methodology, dependency management is the primary function that distinguishes program management from project management.
Step 2: Monthly portfolio review
A 90-minute monthly meeting where all project leads present a 3-slide update: project health (green/yellow/red with one-sentence rationale), resource needs for the coming month, and risks that could affect other projects. This meeting replaces the informal “hallway conversations” that ad hoc coordination relies on. The structured format ensures that resource conflicts and risk cascades are surfaced systematically. I found that 4 of the 23 dependency conflicts from the pre-system quarter would have been prevented by this meeting alone, because the resource conflicts were visible 3-4 weeks before they caused problems.
Step 3: Resource allocation protocol
When 2 projects need the same person or team during the same period, the protocol defines how to resolve the conflict: compare project priority (set by leadership quarterly), compare deadline flexibility, and if both are equal, the project that requested first has priority. This protocol eliminates the “loudest voice wins” dynamic that characterizes ad hoc resource allocation. It also makes the cost of overcommitting the organization visible: if 3 projects need the database team simultaneously, the protocol forces a conversation about sequencing rather than pretending all 3 can happen in parallel. This connects to the reality of limited capacity that organizations often prefer to ignore.
How do you validate it works?
Track dependency delay frequency, multi-project delivery predictability, and coordination overhead hours per quarter.
After 2 quarters: cross-team dependency delays dropped from 23 to 11 per quarter (54% reduction). Multi-project delivery predictability (percentage of projects completing within the committed timeline) increased from 41% to 73%. Coordination overhead decreased from 414 person-hours to 180 person-hours per quarter. Total time investment in the 3 mechanisms: approximately 40 person-hours per month (dependency standup, portfolio review, and protocol facilitation). Net time saved: approximately 78 person-hours per month. The system provides systems-level visibility without systems-level bureaucracy.