THE RELATIONAL INFRASTRUCTURE FRAMEWORK FOR COMPLEX PROJECTS V1.0

Projects fail for human reasons


Complex projects are affected by relational conditions most teams never account for. Nick Norman built this framework to help teams see them early.

Built from 15+ years of field experience | CC BY-NC 4.0

What we mean by complex projects

For this framework, a complex project is one that's ambitious or innovative, crossing (or aiming to cross) institutional and geographic boundaries, involving multiple teams or regions, and operating across ecosystems. It could be a healthcare initiative, a technology deployment, movement building, or institutional change — anywhere coordination and momentum matter.

This framework is organized around eight pillars, each identifying a critical point in a project's development where attention to relational conditions can mean the difference between gaining momentum and losing it. Select any pillar below to explore it.

1. Identifying Strategic Momentum

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.

2. Defining the Shared Perspective

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. At this point, the work may not need a rigid plan yet; it needs enough shared understanding for people to stay oriented as the idea develops.

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. That means allowing people to contribute thoughts, questions, perspective, or encouragement without immediately adding meetings, timelines, assignments, or ongoing responsibility.

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. It also helps build a softer bridge into the next stage, where others may be invited to contribute to direction and strategy without feeling obligated to take on more than they are ready or able to carry.

3. Flexible Strategic Direction

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. That matters because many complex efforts need input from people who may have valuable insight, but limited time, capacity, or readiness to take on an ongoing role.

The value of this stage is that it gives people enough direction to understand what is forming, while leaving enough room for their insight to help guide where the project goes next.

4. Parallel Incubation and Testing

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. It gives the project a place for experimentation while the larger direction is still developing.

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.

The value of this stage is that it protects work while it is still forming. Not everything needs to be visible, final, or ready for integration right away. By giving people space to try things, make adjustments, and learn in parallel, the project can avoid putting too much weight on ideas before they have been worked through.

5. Community Space & Active Contributors

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. While some ideas may still be developing through parallel incubation (the prior pillar), this pillar gives contributors a clearer place to enter the work and understand how they can take part.

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. Their role is not always to join the day-to-day work. Often, their contribution is to provide context on where collaboration may be needed, how different parts of the organization may connect, and what social pathways may need to be built as the project becomes more formalized.

6. Integration & Organizational Alignment

Integration and Organizational Alignment is the stage where two primary things are happening in parallel. The collaborative infrastructure is connecting more formally into the wider organization, while the primary output, whether that is a product, program, or solution, is still coming into focus. As the collaborative infrastructure plugs into the broader system or structure around it, social channels and pathways have to be built so that people can flow through them and contribute to the main build.

By this point, the people who may eventually operate, manage, 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, including why certain choices were made and how those pathways are meant to connect across departments, teams, or partner environments. Having that visibility enables them to improve or optimize the collaborative infrastructure through the lens of execution.

The value of this stage is that the transition begins before the handoff happens. As operators are introduced gradually into the collaboration infrastructure and the broader organization around the project, trust has more time to build and the transition can feel more natural. This helps the primary output and the infrastructure around it become more aligned with the organization while preparing for a smoother handoff later.

7. Operational Handoff

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, manage, or carry the primary output forward.

By this point, the collaboration infrastructure has begun connecting into the wider organization. Operators are now working through the systems, processes, relationships, and social pathways that were put in place. As they begin using that infrastructure, they can see what works as expected, where friction appears, and what needs to be adjusted

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. Not everything has to become public or operational at the same time.

The value of this stage is that operational responsibility begins shifting gradually instead of all at once. Operators are not simply handed a finished product, program, or solution. They begin stepping into the communication channels, decision flows, working relationships, and processes that were built around the primary output, so day-to-day responsibility can transfer with less disruption.

8. Community Migration

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.

Those spaces are usually built for conversation, reaction, and low-commitment engagement. The challenge is moving people from that environment into a space where participation often requires collaborating or taking ownership of certain aspects of the project.

The goal of this stage is to build a bridge between the existing community and the space where the collaborative infrastructure has been built, where the primary output is being developed and maintained. That bridge makes the transition easier for everyone who will eventually move over.

Building an effective bridge requires identifying the right people within the existing community. The focus is on those who have already shown signs of wanting to contribute more actively. Pillar 1 can be useful here because it helps teams recognize early signals of relational and social energy, including who may be ready to help ease the transition for others.

WHY THIS FRAMEWORK EXISTS

The research already points in this direction

The 1994 CHAOS Report and the Project Management Institute's 2023 Pulse of the Profession both point to the same pattern: project failure is often tied not to technical problems, but to human and organizational ones.

"Projects with limited funding could still gain traction when the relational conditions were strong. Heavily funded projects could still fail when those conditions were overlooked." — Nick Norman

Wayne Baker's 2019 research offers useful context for why energy appears in this framework. He points out that energy is not only something individuals carry. It can also be generated between people. In projects, that matters because trust, participation, and coordination can affect whether energy builds, carries forward, or gets lost across teams and critical stages of the work.

This framework gives teams a way to examine those conditions before they become problems — not by relying on good people skills, but by designing the infrastructure of a project intentionally.

Meet the creator of this framework 

The Assessment

The assessment gives teams a practical way to read the relational conditions around their project using the framework. It surfaces where those conditions are likely to create friction, slow momentum, or introduce misalignment before they do.

Originally developed for social impact, the assessment is now being applied across fields where collaboration, coordination, and momentum matter. A no-cost cohort is currently available for healthcare innovation teams.

15+ years of field observation behind v1.0

Nick Norman

Nick has spent more than fifteen years working across complex projects spanning nonprofits, healthcare, digital ecosystems, libraries, and universities — including distributed teams with global reach. He developed the ability to anticipate how relational conditions would be impacted at critical stages, and built this framework around that insight.

The Relational Infrastructure Framework for Complex Projects is one part of a broader body of original work — including more sophisticated standalone frameworks and plug-in models not yet in public view. For a private first look at what is in development, reach out using the form below.

Inquire About the Framework

This framework is licensed for personal and non-commercial use under CC BY-NC 4.0. For questions about organizational implementation, staff training, commercial use, custom licensing, or proprietary assessments, please reach out through the contact form below.
Name E-mail
Tell us what you're interested in?
I want to bring this framework to my team as a workshop
I’m interested in advisory support for a project
I'd like to invite Nick to speak or join a panel
Commercial Use or Custom Licensing Inquiry
Other (explore partnership, collaboration or general question)
Share any details or context (optional) Submit