Infrastructure vs. Curriculum
A clarification on what the two pathway documents are, and what they are not.
These are two different conversations. Keeping them distinct keeps the work clean.
What do we teach people, and in what order?
A curriculum defines the content, classes, resources, studies, and sequence that help someone grow in head, heart, and hands.
How do we make sure nobody gets lost along the way?
Infrastructure defines the system — who is responsible for whom, how the baton moves, where drop points appear, and how communication flows.
Both are necessary. But they are not the same conversation.
Communication Pathway
Defines the communication cascade, role clarity, baton pass mechanics, shared language, growth metrics, and the annual rhythm of leadership alignment. Staff-facing.
Discipleship Baton Pass
Defines the relational handoff mechanism — the moment a congregation member personally takes ownership of another person's next step. Member and leader-facing.
Neither document tells you what to put in a class. They tell you how the environment is organized so that classes, relationships, and community can actually produce formation. The rooms still need to be furnished — that is the curriculum conversation the team is working through together.
“These two resources aren’t about what we teach; they’re about how we make sure nobody gets lost. The staff page is the plumbing behind the walls. The baton-pass page is when the plumbing does its job. We still need to figure out what goes in the rooms.”
The infrastructure documents exist to serve the culture. The curriculum exists to serve the people. Culture is what makes both of them work. The team is building all three — and it helps to know which conversation we are having at any given moment.