Quarterly Synthesis

A Quarterly Synthesis is what the Open Adaptive District publishes at the close of each quarter. It pulls the cycle briefs published in the quarter into a coherent narrative — what we learned across teams, what shifted in our thinking, and what the next quarterly intent should be. It is the longest artifact the district publishes, and the most read by other districts.

§ I · The structureSeven sections, ~3,000 words

Quarterly Synthesis [Quarter] · [Year] · Logbook ID

[Title — what this quarter was about, in one phrase]

01 · The intent we set

Quote the quarterly intent verbatim. Two paragraphs of context: why this intent, what we expected to learn, what counted as success at the cabinet level.

02 · The bets we ran

List every SHIP team that ran a cycle this quarter, with a one-sentence summary of each bet. The reader should be able to scan the quarter's activity in 90 seconds.

03 · What we learned across teams

Four to six paragraphs. The cross-team synthesis — what showed up in multiple briefs, what surprised the cabinet, what pattern only became visible when the briefs were read together. This is the section other districts find most useful.

04 · What we decommissioned

Two to three paragraphs on the bets that did not work and why. Be specific about the failure modes. This is the section the field is least used to seeing — make it count.

05 · What we are scaling

Two to three paragraphs on the Adoption Briefs from this quarter. What is moving district-wide, what conditions made it work, what we will watch for as it scales.

06 · How the doctrine held up

One or two paragraphs. Did SHIP work? Did the Logbook do its job? Were teams able to write good Bet Briefs? What in the doctrine needs to evolve based on this quarter's experience? This is the meta-reflection — the operating model is itself under examination.

07 · The next intent

One or two paragraphs that bridge to the next quarter. What the cabinet is paying attention to. What the next quarterly intent should focus on. Quote the new intent verbatim if it has been issued.

§ II · What makes a synthesis usefulThe discipline of writing this well

Cite the briefs. Every claim in the synthesis should link back to a published cycle brief. The synthesis is not a separate report — it is a reading of the corpus. Readers should be able to drill into any claim.

Be honest about the doctrine. Section 06 is what makes the synthesis distinct from most district reports. Most reports defend the model. This one examines it. If SHIP didn't work in a particular case, say so. If the Logbook missed something important, name it.

Read the corpus, don't summarize it. The synthesis is most valuable when it surfaces patterns that no single brief revealed — themes that show up in three or four briefs from different teams. The Logbook is good at finding these; the human author keeps them honest.

Write for the next district. The primary audience is a superintendent in another district who is considering forking this model. What would they need to know? What would change their decision? Write for them.

Don't bury the decommissions. Section 04 should be at least as long as Section 05. A field-defining publication treats failed bets as equally informative — that is what separates the Open Adaptive District from most ed-tech narratives.

§ III · Cadence and authorshipHow it gets made

Cadence: Published at the close of each quarter — four times a year. Roughly January, April, July, October.
Drafted by: The Logbook produces the first draft from the quarter's brief corpus, the cabinet weekly reads, and the team Spaces. Aim for 3,000 words.
Finalized by: the CIO and the superintendent together. Section 06 in particular requires the superintendent's voice.
Published to: psd401.ai. Picked up by the field; cited by other districts; eventually accumulates into the Year-One Publication.
Length: 2,500–3,500 words. Long enough to do the synthesis work; short enough to be read in one sitting.

§ IV · Relationship to other publicationsHow the syntheses build over time

Four Quarterly Syntheses in a school year compose into the Year-One Publication — the long-form article that goes to the field via AASA, the Digital Promise League of Innovative Schools, and the GSV fellowship network. The Year-One Publication does not start from scratch. It is the four Quarterly Syntheses, integrated, with an introduction and a closing reflection. By April of each year, three of the four syntheses are already written.

A note on volume The synthesis can feel long compared to the briefs. That is intentional. Briefs are operational — they tell the next team what to do. The synthesis is strategic — it tells the next district whether to fork the model. Different audiences, different lengths.