# Weekly Cadence — Captain's Template

> Drop this into `~/command/cadence/weekly/template.md` in your Command Kit.

## 🚢 Captain's call (with the team)

Standing agenda — Max + Tati + Ellen, ~30 minutes:

- [ ] **Information / content** — what can we ship this week?
- [ ] **Products** — what can we ship this week?
- [ ] **What's intriguing us** — the lateral thinking pulling on us
- [ ] **System improvements** — where is our own machine creaking?

If a topic doesn't fit one of these, it's probably an async Linear comment, not a meeting topic.

## 🎬 Content cadence (3 pieces minimum)

Each week, three pieces ship across our channels. In practice that means:

- [ ] Take a video → turn it into 2-3 shorts
- [ ] Take an essay → turn it into a LinkedIn carousel
- [ ] Take a Field Report → adapt to a Twitter thread + IG post
- [ ] Friday filming → following week's distribution

There are many idea-to-output paths. We have flexibility right now and we'll double down on what the analytics show us is working.

## 🔁 The rolling pipeline

Always rolling, always adding to the main content database (the blog / `/log`):

- Friday's videos must be finished + scheduled by following Wednesday
- Raw insights from the week → captured as Field Report material
- Blog content → converted to YouTube + social
- Watch what's being read, who's reading it, how often

## 📊 Weekly review (solo, end of week)

Five questions, written down:

1. **What shipped?** — list the actual artifacts (PRs, posts, customers)
2. **What didn't?** — and why
3. **What's blocked?** — what needs unblocking next week
4. **What surprised us?** — the unexpected signal worth tracking
5. **What rolls up to next week?** — concrete carryovers

## What rolls up

Weekly outputs feed monthly review. Four weekly answers stack into pattern. Three months stacks into a quarterly. Without weekly, monthly has nothing real to compound on.

---

Maintained at `/log/cadence/weekly` on max-ship.com.