# TNN Recommendations Package — Spec **Built from the Thursday-morning build list** **Drafted June 18, 2026** > Purpose: turn what the room asked for into a small, buildable set of deliverables. Source is Movement 4 of the consolidated Thursday synthesis. The asset-and-commitment survey referenced in Deliverable 2 is a separate file: `tnn-asset-commitment-survey.md`. --- ## Design principles These come straight from the room and from George's closing framing. They constrain every deliverable below. 1. **Orientation, not overwhelm.** No single large report. George's own test: someone emails a big document and it never gets opened. Each deliverable is short and does one job. 2. **Role-specific, not monolithic.** Build around the seats people hold. A funder reads a different cut than a practitioner or a newcomer. 3. **Commitment, not just capability.** Any asset inventory captures what a member is committed to give, concretely, alongside what they have. This is the difference between a declared system and a functional one. 4. **Co-created, not delivered.** The neighborhood-work drafts exist to be reacted to, by the room, by TNN folks who weren't present, and by a few people from each member's context. The artifact is a prompt for voice, not a finished statement. 5. **Protect the sticky part.** The package itself should reduce the administrative load on community time, not add to it. --- ## The deliverables The eight build-list items collapse into five deliverables. Each maps back to the items it covers. ### D1 — TNN One-Pager *Covers build-list item 3.* - **What it is:** a single page defining what TNN is and what it is after, with the seven components named. - **Primary audience:** the cohort first, outsiders second. - **Purpose:** a re-centering reminder and a clean hand-off to anyone who asks "what is this." - **Format:** one page, plain language, the seven components as the spine. - **Effort:** low. Draftable now from existing retreat material. - **Priority:** 1. Fastest path to "orientation, not overwhelm," and the thing the room most wanted to be able to hand over. ### D2 — Asset and Commitment Map *Covers build-list items 1, 2, and 7.* - **What it is:** a directory of each org's capabilities, offerings to the network, bench, and concrete commitments. Populated by the survey. - **Primary audience:** the cohort, for routing and collaboration. A redacted cut can go to funders. - **Purpose:** let any member see who does what, who can offer what to whose people, and what each member is actually committed to give. - **Format:** survey to populate, then a browsable directory. Static table or simple searchable page to start. Could later sit alongside the existing C4C asset work. - **Effort:** medium. Survey design is done (see survey file). Build is gated on responses. - **Priority:** 2. Highest-value structural artifact, but it needs the survey to run first. - **Note:** the commitment fields are not optional. An asset map without them recreates the catalog-then-cannot-access failure. ### D3 — Neighborhood Work Brief (two cuts) *Covers build-list items 4 and 5, and absorbs item 8.* - **What it is:** a working draft systematizing the neighborhood work. One source document, two audience cuts. - **Cut A, funder-facing:** for Duke, Lilly, judicatory leaders, the foundation CEO. What we mean by the work, the challenges, the opportunities, why neighborhoods. - **Cut B, community-facing:** for TNN folks who weren't in the room and for about five people from each member's context, to react and ground-truth. - **Absorbs item 8:** the economic-security reframe (free time and economic security as preconditions for co-creation, not the goal) belongs inside this brief as a core framing, not as a standalone note. - **Primary audience:** funders and institutional leaders (Cut A); the wider TNN community and constituencies (Cut B). - **Purpose:** make the case to outside funders, and bring absent voices into the co-creation. - **Format:** short brief, two to four pages, explicitly marked as a working draft for reaction. - **Effort:** medium to high. Needs a first draft the group can react to, then a revision pass. - **Priority:** 3. This is the funding-case artifact the report-backs asked for. Feeds the August Lilly report directly. ### D4 — Facilitator Field Notes *Covers build-list item 6.* - **What it is:** the meta-reflections from George, David, and other non-facilitating observers. What was noticed over the weekend. - **Primary audience:** the cohort. - **Purpose:** the outside-eye read the room explicitly asked for. Names patterns the group cannot see from inside. - **Format:** a short reflective note, prose, in the C4C writing voice. Observation before assertion. This is the one deliverable that is an essay, not a reference document. - **Effort:** low to medium. Largely written already in the synthesis work. - **Priority:** 2. Fast, and uniquely yours to provide. ### D5 — Operating Model Recommendation *Not a hand-off artifact. A recommendation in the package.* - **What it is:** a short recommendation on how the network works, drawn from Movement 3. Covers cadence, who holds what, how administrative work gets pulled off community time, a structured hot seat, intentional celebration, and a break-glass brain trust. - **Primary audience:** the cohort and its conveners. - **Purpose:** answer "protect the sticky part" and "who holds what" with a concrete proposal, and surface the growth-versus-depth question for a decision rather than leaving it open. - **Format:** one to two pages of recommendations, framed as options where the room has not yet decided (especially on growth). - **Effort:** medium. - **Priority:** 3. --- ## Sequencing **Now (low effort, no dependencies):** D1 One-Pager, D4 Field Notes. These can ship while the rest is in motion and deliver the "orientation, not overwhelm" promise quickly. **Next (gated on the survey):** field the asset-and-commitment survey, then build D2. The sooner the survey goes out, the sooner D2 exists. **Then (needs drafting and group reaction):** D3 Neighborhood Brief and D5 Operating Model. D3 in particular should be drafted, reacted to by the room, revised, then taken to the two audiences. --- ## Tie to known deadlines - **August Lilly report:** D3 Cut A (funder-facing neighborhood brief) and the "what the network provides" material are the natural core. The case-for-the-work pain from the report-backs feeds straight into this. - **November convening:** D2 Asset and Commitment Map and D5 Operating Model are the pieces that make the convening about decisions rather than re-discovery. Aim to have the survey fielded and D2 in at least draft form before then. --- ## Open decision the package should force The growth-versus-depth question will not resolve itself. D5 should present it as a real choice with options (hold, grow slowly with an intentional onboarding into the community, or split into linked formations), rather than leaving it as an open thread the network keeps re-opening. Pace is the agreed value. The package should name what pace looks like in practice. --- *v1.0 — June 18, 2026. First spec, derived from the Thursday build list. Deliverable count and sequencing to be confirmed with Sarah and the conveners.*