by Nick Norman
The Relational Infrastructure Framework for Complex Projects
Version 2.0
Framework Overview
What is the Relational Infrastructure Framework?
Developed by Nick, the framework helps teams identify and anticipate friction that may emerge as complex projects grow. It focuses on trust, relationships, participation, coordination, and influence, relational dynamics that timelines, budgets, and technical plans may not fully capture.
What is a complex project?
A complex project, within the context of the Relational Infrastructure Framework, is a project where people, teams, organizations, institutions, disciplines, or communities must coordinate across boundaries and depend on one another to move the project forward.
These boundaries can include differences between departments, professions, regions, institutions, or organizations that have their own structures, responsibilities, and ways of working.
Why Relational Infrastructure
The Case for Relational Infrastructure
Complex projects increasingly depend on people and organizations working across organizational, technological, geographic, and institutional boundaries. As those connections grow, so can the potential for friction around trust, participation, coordination, influence, and continuity. The Relational Infrastructure Framework provides a way to examine those conditions as part of the project itself.
The Six Relational Conditions
Earlier versions of the framework were organized around eight pillars. Version 1.1 began moving away from treating those pillars as a sequence or lifecycle. As Version 2.0 has developed, the framework has shifted toward six relational conditions that can coexist and interact across a complex project.
Relational conditions are like weather conditions for a project. They help describe what different parts of the project's relational environment are like at a given time. Understanding those conditions can help you see where friction may be coming from and where attention may be needed as the project grows or changes.
The six relational conditions in Version 2.0 are listed below. Each can take different forms, change over time, and be experienced differently across the same project.
Shared Perspective
Mutual understandingDefinition. Shared Perspective looks at whether people involved in a project understand its goals, their roles, how their roles and responsibilities relate to one another, and the circumstances or differences that may affect how they work together.
What to know. Shared Perspective is not the same as agreement. People can have different priorities or perspectives and still understand each other well enough to work together.
Relational Environment
Project experienceDefinition. The Relational Environment is the overall relational climate of a project. It includes what working with others is like day to day in different parts of the project.
What to know. The relational environment is not uniform. Different teams or groups within the same project can experience it very differently.
Participation Pathway
Ways to participateDefinition. Participation Pathways are the ways people and organizations can become involved in and contribute to a project.
What to know. A participation pathway may exist but still be difficult to find, access, or use.
Boundary Integration
Working across groupsDefinition. Boundary Integration is the state in which work functions across the separations or divisions between organizations, teams, or other groups involved in the same project.
What to know. Boundary Integration does not mean organizations merge or stop being separate. Their work can function across the boundaries between them while they remain separate.
Continuity of Capability
Capability through changeDefinition. Continuity of Capability examines whether access to project capability that depends on relationships, distributed expertise, tacit knowledge, network connections, or relational history remains accessible, transferable, or reconstitutable through change.
What to know. Continuity of Capability is not about keeping the same people or relationships in place. It concerns whether the project can still access what those relationships made possible when people, roles, or organizations change.
Influence Alignment
Where influence meetsDefinition. Influence Alignment examines whether formal authority, informal influence, decision responsibility, relevant knowledge, and project dependencies operate visibly and compatibly around consequential decisions and action.
What to know. Unequal influence is not automatically a problem. A regulator or technical expert may reasonably carry more influence within their area. What matters is whether different sources of influence support or interfere with project decisions.
Who this is for
The environments where this framework applies
For institutional leaders, the framework helps examine whether relational conditions around a grantee or project may place trust, participation, coordination, or continuity under pressure as the work grows. It can surface those questions while there is still time to investigate them.
For CSR leaders, the framework helps examine how partners, employees, and community members are able to participate, contribute, and influence the work. It can reveal where the relational environment or participation pathways may be limiting involvement.
For accelerators, the framework helps early-stage projects examine relational conditions before growth adds new partners, responsibilities, and dependencies. It provides a way to see where scaling may create friction around participation, coordination, continuity, or influence.
For stewards of digital and physical commons, the framework helps examine how people enter, contribute, stay connected, and carry knowledge or relationships forward. It can reveal fragile participation pathways or continuity risks before the project depends heavily on them.
For nonprofits, NGOs, and community leaders, the framework helps examine relational conditions as responsibility, participation, or decision-making begins to shift. It can help teams see where trust, influence, continuity, or boundary relationships may need closer attention.
For founders and entrepreneurs, the framework helps examine the relational infrastructure around a growing project before new partners, teams, or communities increase its complexity. It can help identify where growth may create friction that is not visible in the project plan alone.
Research Behind Version 2.0
The six conditions were challenged, not simply carried forward
Version 2.0 compared each developing condition with established research related to shared understanding, psychological safety, participation, boundary spanning, continuity, influence, decision-making, and other relational dynamics. The full Development & Evidence Record documents the research, cases, corrections, and decisions that informed that process.
Published cases from outside the creator’s own experience were also used to test whether the framework could interpret relational problems it had not been built around. Cases involving primarily technical, financial, regulatory, staffing, or other non-relational problems were used to test the framework’s boundaries.
That work supports the framework’s developmental rationale and research grounding. It does not establish that Version 2.0 predicts project success, improves outcomes, or functions as a validated measurement instrument.
Built in social impact, now examined as a framework for complex projects
The framework began with recurring patterns observed across social impact, community, digital, and institutional work where progress often depended on relationships across different groups.
Version 2.0 reorganizes those observations into six project-level relational conditions that can be examined across complex projects in different sectors and settings.
Review, Use & Licensing
Version 2.0 is open for public, noncommercial use and ongoing review.
Use the framework
Apply the six conditions to a project that is new, underway, changing, or completed.
Participate in review
Work with Nick to apply Version 2.0 and help identify where the framework is useful, unclear, or incomplete. With permission, feedback may inform continued development.
Contact Nick about participating in a reviewCommercial use
Noncommercial use is permitted under the framework’s Creative Commons license with attribution to Nick Norman. Commercial use requires separate permission.
Contact Nick about commercial usePutting the Framework to Use
Explore the framework
Apply the six conditions on your own.
Work with Nick
Use the framework in a review, workshop, team discussion, or project setting.
Contact NickTry the diagnostic
Use a real project or scenario to explore how the framework surfaces relational friction.
Try the diagnostic
About Nick
Nick Norman has spent more than 15 years working across organizations and complex projects involving distributed teams, communities, and hybrid ecosystems, with a reach that extends globally. His work focuses on the relational side of complex projects, especially what happens as projects grow across organizational, geographic, and community boundaries.
He is the creator of the Relational Infrastructure Framework. His work involves building communities, programs, and engagement around complex projects while helping teams account for the relational challenges that can emerge as those projects grow.
Nick also writes about growth, friction, trust, participation, and complex projects in The Friction Point.
See his services Read The Friction Point