© 2026 licensed under CC BY-NC 4.0

The Relational Infrastructure Framework for Social Impact™ 

v1.0 Built by Nick Norman

The Relational Infrastructure Framework for Social Impact is a framework for understanding and accounting for the relational and social dynamics that affect how projects get off the ground, sustain themselves, and scale.

Those dynamics include how people relate, communicate, coordinate, and make decisions. They are present before a project begins and continue through every stage as the work moves forward. If they are not considered or accounted for, they can create friction, slow progress, cause a loss of momentum, or cause things to break down entirely. This is where the Relational Infrastructure Framework for Social Impact comes in. 

Explore the full framework below 

How It Works

Like an architect who studies the soil before construction begins, this framework maps key turning points in a project's development where relational and social conditions can be significantly affected. These are the conditions that often determine whether a project gets off the ground, sustains itself, and scales.

To do that, the framework is organized around eight core pillars. Each pillar represents a specific stage in the development of a project where those conditions can be affected. If they are not accounted for, teams can become strained, projects lose momentum and traction, or in many cases the work fails to move forward.

Below is a summary of each pillar and the stage it represents:

  1. Identifying Strategic Momentum

Momentum is one of the most critical parts of getting a project off the ground, and it often begins with identifying early sources of relational or social energy before anything is formally built.

Part of the work is knowing where to look for that energy so it can be used at the right points across the life of the project. It might show up in a few strong conversations, thoughtful emails, early social interest, or outreach from potential partners. These aren’t just random events. They’re signals.

The value is being able to interpret those signals and use that energy with intention. You’re not using it all at once. You’re pulling from different pieces and applying it in the right places, especially where momentum tends to slow as the project moves through different stages.

That energy becomes fuel. It helps carry the work forward and can be turned into something tangible that supports the project.

2. Defining the Shared Perspective

Defining the Shared Perspective is the early conversation stage where people begin level setting around what they are doing, what may be unfolding, and what they could be building toward together.

What’s also happening here is you’re resetting expectations. When people come together around something new, there’s often a tendency to overcommit early, to feel like they have to take on a lot because there are only a few people involved.

This stage is meant to counter that. You’re creating space for people to engage without pressure. No required meetings, no response timelines, no added expectations. Just conversation as random or often as you choose.

When that pressure is removed, it can make it easier for people to contribute in ways that feel natural to them. It also prepares them for what’s needed in the next stage (Pillar 3), where that same mindset has to extend to others who come in to contribute to direction and strategy without feeling constrained.

3. Flexible Strategic Direction

Flexible Strategic Direction is the stage where strategy begins to take shape without locking the work into a rigid plan too early. It creates an easier way for others to step in, look at the strategy, and contribute to how the work might move forward, especially as new insights begin to surface.

The goal is to give the project enough direction to gather input and early buy-in, while keeping the structure open enough for the strategy to gel, adjust, and continue developing as more people come into it.

The value here is that it makes it easy for high-level thinkers to contribute without feeling tied down. People can step in, add something meaningful, and step back. This is where a lot of projects struggle -- it's hard for others to contribute unless they fully commit.

When people can contribute without being tied down, they’re more likely to stay connected to the work. And that makes it more likely they come back later or support it in a bigger way.

4. Parallel Incubation and Testing

Parallel Incubation and Testing is the protected background space where people can explore ideas, build early versions (prototyping), and work collaboratively without bringing everything to the surface too soon. It serves as a sandbox for explorations and testing in parallel, which also helps reveal what kind of community space, tools, and working environment the project will eventually need.

This stage can continue throughout the life of the project, giving people a place to develop ideas behind the scenes, learn from what they are building, and pass valuable insight forward before new work reaches the wider organization.

The value here is that it protects the work while it's still forming. Not everything needs to be visible or finalized early, and this space allows people to try things, make adjustments, and learn without pressure.

It also helps prevent the main project from taking on too much risk too early. Instead of pushing untested ideas into the open, you are allowing them to be worked through first, so what moves forward is stronger, clearer, and more ready to be integrated.

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. It creates the social lanes that allow internal teams, partners, volunteers, and other contributors to enter the work with more clarity about where they fit and how they can take part.

The consistency and participation built in the prior stage often act as the early buy-in for this one. It shows that there is enough real activity to support a more defined space for building together.

This stage also creates an entry point for organizational leadership, stakeholders, and department leads. They are often busy, but more importantly, they are meant to provide early input on how their department may connect to the work over time.

The goal is to make stakeholder contribution easy and clear. They can step in, provide what’s needed, and step back out without being pulled into ongoing activity.

6. Integration & Organizational Alignment

Integration and Organizational Alignment is the stage where what has been built begins to connect more directly into the wider organization, its departments, and the environment where the work is meant to live.

This stage often overlaps with the prior phase, but the focus now shifts from creating a space for building to weaving that work into the larger structure or organization around it. By this point, the people who will operate and run the work are already in the picture. 

Operators need to be able to step into the infrastructure, flows, and processes they are inheriting and understand how the work is set up. That includes why certain decisions were made and how the work was integrated into the organization. 

Their presence is introduced gradually over time, which helps build trust across the organization and makes the handoff feel more natural rather than sudden.

7. Operational Handoff

Operational Handoff is the stage where the project gradually moves from infrastructure building and relational setup into the work being carried forward day to day. The work begins shifting from the people who built the conditions for the project to exist into the people who will run it.

By this point, the work is already connected into the organization. Operators begin working across departments, using the systems, processes, and relationships that have been put in place.

This stage overlaps directly with Pillar 4: Parallel Incubation and Testing. As operators begin using what has been built, they are also testing it in practice. This is where they can see what works as expected, where there is friction, and what needs to be adjusted or improved.

Not everything at this stage needs to move forward publicly. Some of the work may stay within incubation, but it still carries value. As trust builds through the earlier stages, it often becomes easier for teams and departments to engage and contribute, even at this point.

8. Community Migration

Community Migration is a bonus stage for projects that already have a connection to an outside group of people, often from conversational spaces like social media.

The key is that those environments are built for conversation, not building. People are used to reacting, commenting, and low-commitment engagement. So when you bring them into a space where the expectation is to contribute, collaborate, or help build something, that’s a different mode of participation.

If you make that shift abruptly, things break down. People disengage because the environment is asking more of them than they’re used to giving.

So the work here is to bridge that gap. From the existing community, you identify the ones who already lean toward building. Those are your ambassadors.

They go into the new space early with an exploration mindset, and they start moving through the pillars where needed. They’re the ones figuring out how things actually work in practice.

They’re either helping establish that collaborative foundation in the new space, or they’re stepping into one that’s already in place, depending on when this happens in the project. Everybody isn’t coming. The goal is getting the right people there first.

© 2026 licensed under CC BY-NC 4.0

The Case for Relational Infrastructure

v1.0 Built by Nick Norman

Many conversations about projects focus on the visible and technical elements, such as tools, funding, timelines, and mission. But decades of research suggest that human and social dynamics are just as important to whether a project succeeds.

Research on projects has been pointing in this direction for years. Both the 1994 CHAOS Report and the Project Management Institute's 2023 Pulse of the Profession brought wider attention to the fact that project failure is often tied not only to technical problems, but to human and organizational ones as well.

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.

These are just a few examples from a larger body of research pointing in the same direction. The relational and social conditions around a project, when not accounted for, affect how people work together and ultimately how the project turns out.

Meet the creator of this framework 

Nick Norman

The Thinking Behind This Framework

Nick has spent more than fifteen years working on complex projects across a wide range of environments, from hospitality and retail to nonprofit outreach, large digital ecosystems, libraries, and major institutions and universities. Across that work, one thing became clear... the projects that succeeded were not always the best funded or the most technically sophisticated. They were the ones where the relational and social conditions were right.

As Nick worked across more projects, he developed a pattern recognition for what made projects thrive. He noticed projects with limited resources often succeeded when leaders valued relational and social dynamics. Yet projects with strong teams, funding, and time investment frequently broke down when those dynamics were overlooked.

Once those patterns became clear, Nick began gravitating toward organizations and projects where leaders valued the relational and social side just as much as the technical side. Those tended to be the projects that attracted strong talent, sustained participation over longer periods, and created conditions for broader reach and lasting impact.

The Relational Infrastructure Framework for Social Impact™ is not meant to prescribe what is right or wrong. It's meant to create a moment of pause for teams to ask... "Have we accounted for how people, relationships, and social dynamics will affect our work as it grows or scales from one stage to the next?"

This framework is licensed for personal and non-commercial use (CC BY-NC 4.0). If you would like to implement this logic within your organization, use it for staff training, or integrate it into a commercial project, please reach out to Nick using the contact form below.

The Relational Infrastructure Framework™ > Licensed under CC BY-NC 4.0. For commercial licensing or proprietary diagnostic assessments, please contact Nick Norman.

Required attribution here > The Relational Infrastructure Framework for Social Impact (v1.0) by Nick Norman, available at workwithnick.us, is licensed under CC BY-NC 4.0

Inquire About This Framework

If this framework connects with your work, feel free to use the form below to explore workshops, advisory support, speaking, or other ways to collaborate.
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