How We Work

Planning and Sprints

The planning sheet is the single source of truth. Goals cascade into weekly work

The planning sheet is the single source of truth. Everything traces back to it.

Goal cascade

Yearly goals → Quarterly plans (Q1, Q2, Q3, Q4) → Monthly targets → Weekly sprints.

Each sprint has specific deliverables tied to GitHub issues. Action items are derived by tracing from goals down, not invented in meetings.

Weekly and monthly target metrics sit alongside actuals — progress is always visible. The sheet contains evidence and reasoning, so anyone can trace why a task exists without investigating on their own.

Leading indicators are broken out by function (product, marketing, etc.).

Stable vs nightly

Stable — Polished, user-facing. Each release should make the app genuinely stickier — a real improvement, not just a version bump.

Nightly — Internal testing, rapid iteration. Break things here so stable stays solid.

Principles

  • One core feature per stable — Anchor each release with one significant improvement
  • Habit loop focus — Make Char indispensable before expanding scope
  • Ship and iterate — Good and shipped beats waiting for perfect
  • Trace, don't invent — Every task should connect to a goal. If it doesn't, question it.