The Open
Adaptive District
A quick guide to the SHIP cycle — six weeks of work, two weeks to plan, repeated.
The Open Adaptive District is Peninsula's operating model for keeping pace with a technology landscape — particularly AI — that changes faster than traditional district planning cycles. SHIP is the working cadence inside it: six weeks of active work, two weeks of planning, repeated.
§ I · Why it existsThe pace problem
AI capability is doubling on a roughly six-month curve. District change cycles run two to five years. Without an adaptive operating model, every new wave creates fresh paralysis — and vendors, not districts, end up deciding what AI in education looks like. The Open Adaptive District closes that gap.
§ II · The cycleSHIP
Sense
What changed in the AI landscape since the last cycle? What district problem are we trying to solve in this cycle? End state: a one-paragraph framing.
Hypothesize
If we do X, we expect Y — and here's how we'll know. End state: a written hypothesis with success criteria.
Implement
Run the bet inside the cycle. Stay close to it. Adjust as evidence comes in.
Publish
Public debrief at the end of the cycle. What worked, what didn't, what we adopt district-wide, what we kill. Method and lesson go to psd401.ai; specifics are redacted where privacy or legal requires.
§ III · Who runs themTeams in motion
| Phase | Teams |
|---|---|
| At launch · Aug 2026 | Cabinet department teams — HR, Finance, Teaching & Learning, Operations, Tech, Communications, Special Education. Principal teams by grade band — elementary, middle, high. |
| Fall · after cycles 1–2 | Teacher teams (in-building or cross-district), Tech, Employee Support Services, Business Office, and any other staff group ready to run a cycle. A SHIP team can be anyone in the district with a problem worth running through a cycle — title is not the criterion. |
Each team takes one bet per cycle. Cross-team formations are allowed when a bet crosses boundaries.
§ IV · The leadership moveQuarterly intent
the superintendent issues a 3-sentence quarterly intent before each cycle window:
- What we're after this quarter
- Why now
- What we won't compromise
Teams choose their bets inside that intent. The intent sets the what and the why; teams own the how. This is directed-opportunism doctrine (Bungay): replace plan-and-implement with do-and-adapt.
§ V · How teams stay connectedShared consciousness
PSD's meeting culture isn't built to carry cross-silo coordination. So the operating model runs on async by design:
- Every SHIP team works in a shared space with weekly written check-ins — what we tried, what we learned, where we're stuck, what we need.
- An AI agent reads across team spaces and produces a weekly cross-team digest, surfacing themes, blockers, and accountability flags.
- the superintendent reviews the digest weekly without holding a meeting.
§ VI · A feature, not a failureKilling bets
Not every hypothesis works. Publish can mean "we tried this, here's what we learned, we're decommissioning it." Education culture punishes this; the Open Adaptive District treats public decommissioning as evidence the system is honest. Bets that quietly disappear are the failure mode — not bets that are publicly killed.
§ VII · A literacyComplex & complicated
Most AI questions are not "complicated" problems that an expert or vendor can solve. They are "complex" problems where no one knows the answer yet, and the only honest response is a small, safe-to-fail experiment. SHIP is built for complex problems. When something genuinely is complicated, we solve it the normal way and don't waste a cycle on it.
§ VIII · Intellectual groundingThe doctrine stack
Five frameworks anchor the operating model. Most teams won't need to learn these names. They're for the publication, and for leaders who want intellectual grounding.
Peter Senge's Fifth Discipline argued that organizations fail to change not because people resist, but because systems are wired for stability. The Open Adaptive District targets Senge's leverage points — shifting mental models, opening cross-silo information flows, and building reinforcing feedback loops cycle over cycle. It is the foundation beneath everything else.
Stephen Bungay drew his model from Prussian Auftragstaktik — mission command — where commanders set intent and subordinates make their own tactical decisions. He translated it for enterprise as do-and-adapt replacing plan-and-implement when the ground is moving faster than plans can hold. The quarterly intent is the practical application: the superintendent sets purpose; teams own method.
General Stanley McChrystal redesigned Joint Special Operations Command from a hierarchy of expert silos into a network of interdependent teams. The two key shifts: shared consciousness, so everyone sees what everyone else is learning, and empowered execution, so decisions get made at the edge rather than waiting for approval. The Logbook is how Peninsula puts shared consciousness into practice; SHIP teams are the empowered edges.
Dave Snowden's Cynefin framework separates complicated problems (expert-solvable, known unknowns) from complex ones (no one knows the answer yet; you have to probe). Most AI adoption questions are complex, not complicated — and the wrong response is to expert-solve them. The SHIP cycle is the Cynefin-correct response: small, safe-to-fail experiments rather than expert pronouncements.
David Teece's framework for firms that thrive in turbulent environments is sense → seize → transform. Sense the change, seize the opportunity through rapid mobilization, transform the organization's structure to support what was learned. SHIP is sense-seize-transform on a six-week clock. This is the citable academic backbone for the Year-One publication.
§ IX · A pair of declarationsWhat this is, what it isn't
It is
- An operating system for the district
- A repeatable adaptive cadence
- A publishable, forkable model
- The capacity to absorb new AI in weeks
It is not
- A strategic plan goal
- An AI policy
- A tech rollout
- A directive to vendors
§ X · The doctrine, in one sentence
A public school district can be redesigned to absorb new technology at the pace technology actually moves — through cross-silo teams operating on short, shared cycles under common intent, with the learning published as it happens.