state-check

State Check

Run a structured Operational State Check for a function or the full company.

Variables

function: sales | product | partnerships | tribe | research | company-wide context: [Brief situational context — what's happening that prompted this check?]

---

Instructions

Before running, read:

• outputs/operations/workspace/31c-operational-state-model.md — Core operational states for each function
• reference/state-check-guide.md — State Check format and four questions
• context/current-data.md — Current metrics and active workstreams
• context/pipeline.md — Active pipeline context

Run a structured State Check using the four questions from the State Check Guide:

1. Sea State (2 min) What external conditions have changed since last check? What's the environment doing?

2. Current State (3 min) What operational state is [function] actually in right now? Not what we want — what's true? Evidence: [list observable signals]

3. Heading Check (2 min) Are we on heading? Have we drifted? Assessment: [on heading / slight drift / significant drift]

4. Course Corrections (3 min) If drift detected: what specific, behavioral adjustments restore the state? Course corrections are behaviors, not goals. "Do X daily" not "achieve Y."

Output format:

---

Function: [name]

Current State: [one sentence assessment]

On Heading: Yes / Slight drift / Significant drift

Sea State Summary: [2-3 sentences]

Course Corrections: [bulleted list, max 3]

Next State Check: [recommended timing]

---

Total output: 1 page max. The point is clarity, not comprehensiveness.