GPS Goals 2026-27 [DRAFT]

Goal 1: Communication: Build a Sustained Writing & Publishing Practice

What (one year from now): I produce a written piece every month. After a year, I’ve written twelve pieces (any length), and I pulled four of them out to external venues such as an article, or a blog post.

How (operationalized): I block the first Wednesday of every month before the rest of the week fills. Each piece leads with strategy and uses technical work as the evidence.

Why: I had over ten strategic consultations in 2025-26 and the learnings and work doesn’t get shared unless I write things down and share it.

Buckets

• Direct control: Holding the time on my calendar, writing, submitting.
• Indirect (resources align): Outside circulation, editorial timelines.
• Out of my control: Whether anything gets accepted, cited, or referenced.

Goal 2: Capacity Building: Documented Studio Offerings Catalog

What (one year from now): I’ve documented the Studio’s seed-grant support model as a catalog, organized the way we already deliver it: across the grantee lifecycle (Spark → Build → Sharpen → Scale) and the three C’s (Critical Boost, Capacity Building, Cross-Pollination). I’ve written up at least 4 offerings, prioritizing the ones still marked “proposed” (Meet the Toolkit, Privacy by Design, IRB Demystified, Prototype to Pilot, User Testing Jam) and turning them into ready-to-run sessions, alongside documenting the ones that already ran (Legal 101, Scaling Sustainably, PM of One).

How (operationalized): I document one offering per quarter,working across the lifecycle so the catalog fills in rather than clustering in one stage. I test each entry by running it with grantees and seeing what works and what doesn’t work. At each quarterly GPS check, I drop what didn’t work and keep what did.

Why: Our team would like to develop “repeatable Studio service offerings.” We’re a small team, and right now the support model lives in my head and a handful of slide decks. Writing it down as a catalog mapped to the lifecycle we already use is how we get the work distributed without our availability being the bottleneck. When a grantee hits the Build stage or a partner asks “what does the Studio do,” we have a documented offering to hand them instead of starting from scratch.

Buckets

• Direct control: Writing each entry, building out the proposed offerings, testing them by running them with grantees.
• Indirect (resources align): Whether the Studio adopts the catalog and runs offerings from it; depends on the entries being good enough to use.
• Out of my control: Whether catalog entries get picked up externally or by other GSE programs.

Goal 3: Reach: Scale the AI Flash Lab Train-the-Trainer to 5,000 Learners

What (one year from now): ISTE has signed the partnership and the first cohort is live. I’ve trained around 25 facilitators through the AI Flash Lab TTT; together they’ve run ~100 workshops for ~5,000 educators across the year. The TTT itself is mature: the playbook, the participant kit, the phased independence cadence, and the quality controls all run from documentation that someone else could pick up. Each new partner that lands (Latvia, future partners, etc.) plugs into the same pipeline without me rebuilding it.

How (operationalized): Run the TTT through its four phases for every new facilitator: experience the Flash Lab as a participant, co-facilitate, run solo with support, run independent. Train in cohorts when I can so facilitators absorb support load from each other. Build the quality controls into the pipeline so I don’t have to inspect every workshop myself: the written standard, the Phase 4 competence check, async signal review on recordings. Keep the partnership-side work moving: developing new partnerships; recruiting facilitators, training cadence, and post-workshop signal.

Why: We are building “public goods” that need to be able to scale without our direct on-going involvement. The TTT is how we get the Flash Lab in front of a lot more learners without growing the team to match. We are proving the model with ISTE, Latvia (potentially), and will take the learnings from those experiences to expand even more. the model proves out with ISTE, it should plug into Latvia, and beyond with minor adjustments.

Buckets

• Direct control: The TTT pipeline itself — playbook, kit, training cadence, quality controls, recruitment of facilitators from the existing pool (ASUGSV, SXSW EDU).
• Indirect (resources align): Number of facilitators trained, number of workshops delivered, ISTE-side cadence, Josh’s bandwidth for partnership work.
• Out of my control: Whether ISTE signs, whether 5,000 educators show up, whether other partners emerge this year.

Goal 4: Wellness: Keep the Sustainable Leadership Practice Going

What (one year from now): I’ve kept the routines that keep me steady through a heavier year (ISTE, the catalog, more travel) instead of letting them slide when work piles up. That’s the weekly review, a capacity check-in when I’m deciding what to take on, and a physical-health habit. I’ve also gotten better at protecting focus time so the blocks for Goals 1 and 2 don’t get eaten.

How (operationalized): Hold the weekly personal review. Run a capacity check-in each quarter, or when a big new ask lands, using the Personal Logic Model. Keep the physical-health habit. Once a quarter, look at the calendar and protect the writing block (Goal 1) and the catalog work (Goal 2) before the rest fills in.

Why: Last year I built a few sustainable routines and they kep them consistently. This year is about keeping them through a heavier travel and delivery load, not adding more. These routines are important because they will be what make the other three goals possible!

Buckets

Direct control: Holding the routines, protecting the focus blocks.
Indirect (resources align): —
Out of my control: This one is pretty much up to me!