Making Relational Infrastructure Visible to Leaders

A sixty-minute keynote that names the often-invisible structures behind effective collaboration, including how decisions are made, how feedback moves, how conflict is addressed, and how people remain connected under pressure.

At a Glance

Client: State of Michigan

Sector: Cross-sector

Format: Keynote and practice framework

Audience: Michigan interest holders

What we noticed

Organizations can have capable people, a clear strategy, and strong commitment and still struggle to accomplish what they set out to do.

Roles become unclear. Decisions are made inconsistently. Feedback does not move. Conflict goes unaddressed. Transitions depend on informal knowledge. Trust begins to decline.

When those relational conditions are left to chance, strain tends to follow a predictable path: coordination weakens, issues remain unresolved, people leave, knowledge is lost, and impact suffers.

The intervention

We developed and delivered Relational Infrastructure, a sixty-minute keynote for Michigan interest holders.

The keynote defined relational infrastructure as the designed system of shared norms, clear structures, and named practices that shapes how an organization functions, particularly under pressure.

It broke the concept into specific components, including:

  • Role clarity
  • Shared purpose
  • Psychological safety
  • Feedback norms
  • Repair practices
  • Communication structures
  • Decision clarity
  • Transition protocols

The keynote also demonstrated the concept through practical before-and-after examples. An ordinary set of one-on-one questions was redesigned to surface more useful information, and a standard coalition agenda was rebuilt to produce clearer decisions, ownership, and follow-through.

Why we designed it this way

We designed the keynote to make an invisible condition visible. Leaders cannot intentionally build or repair something they do not have language for.

Rather than simply arguing that relationships matter, the keynote defined relational infrastructure as a set of concrete, buildable parts. This gave leaders something they could examine and act on rather than only a principle they could agree with.

We also included before-and-after demonstrations because showing a familiar meeting, agenda, or check-in redesigned makes the concept easier to understand and apply.

Questions for Consideration

If the conditions that turn effort into impact are relational, what changes when organizations treat them as infrastructure rather than as culture?

Why do organizations invest readily in strategy, talent, and technology while leaving the relational conditions that determine their value largely to chance?

When a system’s most important functions are often invisible until they fail, how should leaders decide when and how to invest in them?

SELECTED ARTIFACTS