by Nick Norman
The Relational Infrastructure Framework for Complex Projects
Version 1.1
Complex projects create more friction as they grow and scale. This framework helps teams see how that friction affects participation, trust, collaboration, and momentum.
In this context, what is a complex project?
For this framework, a complex project is one that is ambitious or innovative, crosses institutional or geographic boundaries, involves multiple teams, organizations, or communities, and grows beyond the ability of any one person or group to coordinate alone.
It could be a healthcare transformation, a technology deployment, movement building, or institutional change—where coordination, collaboration, and momentum matter.
Eight Pillars
Each pillar identifies a critical point where relational conditions present in a project can mean the difference between gaining momentum and losing it
Select any pillar below to explore it.
Identifying Strategic Momentum is the stage where early sources of relational and social energy begin to surface before anything formally begins or is built. That energy may show up through early conversations, thoughtful emails, early social interest, partner outreach, or people who keep returning to the idea. This pillar does not treat those moments as random. It treats them as early signals of relational and social energy that may be useful to the project if they are noticed and applied with intention.
The value of this stage is learning how to read those signals and use them with intention. When those sources of relational and social energy are noticed early, they can be mapped, carried forward, and applied at the points where momentum tends to slow, decisions become harder, or the work needs support to keep moving.
This stage remains active throughout the life of a project and can be revisited whenever new people, conditions, or sources of momentum emerge.
Defining the Shared Perspective is the early sense-making stage where people begin to level set around what they are doing, what may be forming, and what they could be building toward together.
This stage also helps reset expectations. When people come together around something new, there can be pressure to overcommit early, especially when only a few people are involved and the work still feels fragile.
The purpose of this pillar is to create room for people to engage without turning every conversation into an obligation. By reducing early pressure, this pillar aims to create room for people to stay connected to the work in ways that feel natural and appropriate to their role, interest, or capacity.
Flexible Strategic Direction is the stage where strategy begins to form without forcing the work into a rigid plan too early. The work needs enough direction for people to understand where it may be going, while still leaving room for the strategy to adjust as new insight, context, and participation emerge.
This pillar creates a way for others to step in, review the direction, and contribute perspective without having to fully commit to the project.
If a shared direction does not emerge here, that is useful information about who is at the table and what may still be missing, rather than a failure of the stage itself.
Parallel Incubation and Testing is the protected background space where people can explore ideas, build early versions, and test pieces of the work without bringing everything into full view too soon.
This pillar can continue throughout the life of the project. It gives people a way to develop ideas behind the scenes, learn from what they are building, and carry useful insight forward before new work reaches the wider organization or community.
This stage often begins informally and naturally through a call, a message thread, or a simple shared space. It does not require a separate formal decision before useful testing can begin.
Community Space & Active Contributors is the stage where the work begins to establish a dedicated home for collaboration, building, and shared participation. This may take the form of a Slack workspace, shared project hub, working group, digital community, or internal collaboration space.
A key value of this stage is that organizational leaders, department heads, and stakeholders can help identify where the project may overlap with other teams, institutions, regions, or areas of responsibility.
Integration and Organizational Alignment is the stage where the collaborative infrastructure connects more formally into the wider organization, while the primary output is still coming into focus.
By this point, the people who may eventually operate or carry the primary output forward should begin entering the collaboration space. They need visibility into the flows, processes, decisions, and social pathways they may inherit.
Operational Handoff is the stage where the project begins moving from infrastructure building and relational setup into day-to-day operation. Responsibility starts shifting from the people who built the collaboration infrastructure to the people who will operate or carry the primary output forward.
This stage connects back to Parallel Incubation and Testing. Some parts of the primary output or supporting infrastructure may still need to be tested, refined, or held back before moving fully into view.
Community Migration is an optional stage for projects that already have a relationship with an outside audience or community, often through conversational spaces like social media, newsletters, public forums, or online groups.
The goal of this stage is to build a bridge between the existing community and the space where the collaborative infrastructure has been built. Building an effective bridge requires identifying the right people within the existing community who have already shown signs of wanting to contribute more actively.
Who this is for
The environments where this framework applies
For institutional leaders, the framework is a derisking tool. It helps identify whether the relational and social conditions are in place for a grantee or initiative to sustain momentum beyond the initial funding period. Rather than discovering those gaps after a grant is deployed, the framework surfaces them early when there is still time to act.
For CSR leaders, the framework is an activation tool. It helps design programs where partners, employees, and community members do not just receive but actively participate and contribute. The framework identifies what conditions need to be in place for engagement to go beyond a one-time event and become something people return to.
For accelerators, the framework is a scaling tool. It helps early stage concepts identify the relational infrastructure they need to build before they try to grow. Many initiatives scale the work before they scale the conditions that make the work possible. This framework helps teams see that gap before it becomes a problem.
For stewards of digital and physical commons, the framework is a participation design tool. It helps build contributor ecosystems that distribute ownership and do not collapse when a single person or team steps back. The framework identifies where participation pathways are missing or fragile before the project depends on them.
For practitioners moving from direct service toward community-led models, the framework is a transition tool. It helps identify what relational conditions need to be built before responsibility can shift from staff to community. That shift rarely fails because of bad intentions. It fails because the infrastructure for shared ownership was never built.
For founders in the pre-scale phase, the framework is a design tool. It helps build collaborative systems from day one so trust, participation, and momentum are part of the infrastructure rather than something you try to add later. The relational conditions that allow a project to scale are much easier to build at the start than to retrofit after growth has already created complexity.
Why This Framework Exists
The data confirms what the field proves
Industry data has long tracked this reality. Studies ranging from the classic CHAOS Report to the Project Management Institute's Pulse of the Profession consistently show that project failure is rarely caused by technical limitations alone. The primary vulnerabilities are almost always human and organizational.
Wayne Baker's 2019 research explains exactly why relational energy is a core component of this framework. Energy is actively generated or depleted between people. In complex projects, this dynamic is critical because systemic trust, participation, and coordination dictate whether momentum builds across teams or gets lost during major handoffs.
This framework gives teams a way to account for these conditions before they turn into friction.
Built in social impact, applied to complex projects
This framework was originally built for global social impact work, where momentum often depends on shared vision, trust, participation, and coordination across different groups. Over time, it became clear that the same relational conditions show up in many kinds of complex projects, including healthcare programs, regional technology deployments, institutional change efforts, partner ecosystems, and movement-building work.
From The Friction Point
See how Nick thinks through complex projects
The Friction Point is where Nick writes about what building trust, participation, and momentum looks like in practice — the strategy, the lessons, and the questions people ask him most.
About Nick
Nick Norman has spent more than fifteen years working across nonprofits, healthcare, digital ecosystems, libraries, universities, and distributed teams with global reach. That experience helped him develop an ability to see how relational conditions shift at critical stages of a project, and the Relational Infrastructure Framework was built from that insight.
Connect With Nick