Helm Founder Cadence

---
name: helm-founder-cadence
description: "The founder says \"my weeks just disappear,\" \"I never have time for the real work,\" or \"I'm always reactive.\" Load for personal-rhythm questions, weekly-review design, or deep-work installation. If they ask for a company operating rhythm, route to Ops — that's the team layer."
metadata:
  author: wayland
  version: "1.0.0"
  category: "helm"
---

# Founder cadence

## When to load this mode

The founder says "my weeks just disappear," "I never have time for the real work," or "I'm always reactive." Load for personal-rhythm questions, weekly-review design, or deep-work installation. If they ask for a company operating rhythm, route to Ops — that's the team layer.

## What a cadence is for

Founders default to reactive mode — the inbox sets the agenda, every fire fought personally. A cadence protects time for the work only the founder can do.

The point isn't productivity. The point is making sure the avoided consequential work gets done before the inbox eats Friday.

## The three rituals

**Weekly review — 45 minutes, same time, same day.** Three questions. (1) What did I do this week only I could do? If "nothing," next week's calendar gets rebuilt. (2) What did I avoid? Name it. Schedule a slot for it next week. (3) What's the one thing that, if it shipped, would make the next 12 weeks easier? That gets a slot before Tuesday.

**Daily anchor — 90 minutes, first block of the day, no exceptions.** One task. Not a list — one. Whatever moves the avoided consequential thing forward. Email closed. Phone elsewhere. The anchor protects the work that compounds.

**Quarterly walk — half day, off-calendar.** No laptop, no agenda, walking outside. Three questions only. What is the business actually for? What am I tolerating that I shouldn't be? What would I do differently starting today? Not a planning ritual; a clearing ritual. Decisions surface, get written down, run through `decision-frames.md` in a separate session.

## Procedure to install

1. **Find the broken layer.** Ask what the founder did last week only they could do. If they can't name one thing, the daily anchor is missing. If they can name daily work but can't say what shifted over the quarter, the quarterly walk is missing. Most founders are missing two of three.

2. **Install one layer at a time.** Daily anchor if firefighting; weekly review if losing weeks. Don't install all three at once — the cadence dies in week two if it's too heavy.

3. **Protect the anchor block on the calendar.** Recurring, name it boring ("Strategy block"), no one else owns it. If the founder accepts a meeting in the block, that's data: either the block isn't real or the meeting wasn't a priority. Surface next session.

4. **Score the cadence after four weeks.** Did the avoided thing get done? Did the anchor survive? If not, cut something — usually a recurring meeting producing no decisions. Don't add discipline; cut load.

5. **Stamp the cadence in `TEAM_MEMORY.md`.** Which rituals, what times. So Ops knows not to schedule the company weekly during the founder's daily anchor.

## Decision rules

- **Three priorities maximum at any time.** A fourth is a not-a-priority. Founders default to ten; cut to three first.
- **The daily anchor is non-negotiable for 21 days before it counts.** Below that, you don't know if it works or they just had a calm month.
- **Schedule the avoided thing first.** Whatever "what did I avoid" surfaced gets the first slot of next week. Not the easiest slot — the first one.
- **One ritual per layer. Never two.** Two weekly reviews is no weekly review.
- **Calendar audit before any new ritual.** If the calendar is 80% meetings, no cadence fixes it. Cut meetings first.

## Anti-patterns

- **Productivity-system tourism.** GTD this month, time-blocking next, second brain after. The system isn't the problem; the avoided work is. Pick one, run 90 days, judge.
- **Optimizing inbox triage instead of protecting the anchor.** A faster inbox makes the inbox bigger. Protect the deep block first.
- **Treating the weekly review as planning.** Review is backward-looking. If they spend it building next week's task list, they've skipped the avoidance question.
- **A quarterly walk with a deck.** No slides. No agenda. If there's a deck, it's a board meeting in costume.
- **Adding rituals to fix a broken ritual.** Don't add a "pre-weekly." Cut the weekly's question list from five to three.

## Before / after

**Before:**

> Founder: "I do a weekly review every Sunday. Two hours. I list everything I did, plan the next week, journal. By Tuesday the plan's irrelevant."

Diagnosis: review is doing the planner's job. The plan dies on contact with the week because no slot was protected for the founder-only work.

**After:**

> Install: 45-minute Friday review, three questions. The "what did I avoid" answer (a cofounder-equity conversation) gets the first slot of Monday's anchor. By month two: the conversation happened, the equity resolved, the Friday review stopped feeling like homework. The plan didn't get tighter; the avoided work got named.