Skip to main content
Peninsula School District · Gig Harbor, WashingtonOpen source · free to run
Peninsula AI
Four groups of staff around a looping track, planning at a table with sticky notes, building at a laptop and whiteboard, studying a bar chart, and pinning a finished page to a board

What We’re Learning

Every build ends with a wrap-up, and every wrap-up is published here: the builds we kept, the ones we stopped, and the ones we are running again.

Teams write their wrap-ups in about twenty minutes at the end of week 6. We publish them as the teams wrote them, with student and staff details removed.


Cycle 1: fall 2026

The first teams include executive cabinet, principals, and district office departments such as athletics, student services, teaching and learning, and career and technical education. Each team starts when it is ready, so wrap-ups are published here as each team finishes its sixth week.

Team The build The call
— Published as each team finishes —

The current focus

Each quarter, Superintendent Krestin Bahr sets the focus in three sentences. For this cycle:

This cycle is about exploration and innovation: learn what the AI tools we already have can do, and use them to improve one process or practice that serves your team’s goals. The tools are changing faster than any training plan can keep up with, and the quickest way to learn them is to use them on real work. Whatever you build, student data privacy and the relationships our schools are built on come first.

How the sharing works

  • Kept builds become tools. A kept build usually becomes a skill in the PSD AI Agent or a tool in AI Studio, and its wrap-up links to it, so you can use it as well as read about it.
  • Inside Peninsula. Full wrap-ups are open to all staff. Every Monday, cabinet gets a five-point summary of what is moving, what is stuck, and where teams are working on the same thing. At the end of each quarter, a longer write-up covers the whole cycle.
  • Outside Peninsula. Public versions of the wrap-ups, with student and staff details removed, are published on this page. Other districts are welcome to use anything here, including what didn’t work.

Why we publish stopped builds

Most organizations quietly drop what doesn’t work, and what they learned goes with it. We publish stopped builds in the same detail as the ones we keep, so other teams don’t repeat them. If this page only ever shows successes, something is wrong, and we want to hear about it.

Open the printable version