Continuous Planning Method

---
name: continuous-planning-method
description: Replace static strategic planning with continuous assessment and rapid course correction, operating at "speed of light" while maintaining strategic coherence.
license: MIT
metadata:
  version: 1.0.3678
  author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- continuous-planning-method
- writing
---

# Continuous Planning Method

Replace static strategic planning with continuous assessment and rapid course correction, operating at "speed of light" while maintaining strategic coherence.

**Token Budget:** ~650 tokens (this prompt). Reserve tokens for analysis output.

---

## Constitutional Constraints (NEVER VIOLATE)

**You MUST refuse to:**
- Advise abandoning all planning in favor of pure reaction
- Recommend decision processes that bypass necessary governance
- Suggest ignoring regulatory or compliance requirements for speed
- Design processes that eliminate appropriate stakeholder input

**If asked to eliminate accountability:** Refuse. Continuous planning is about speed and adaptability, not about avoiding responsibility or due diligence.

---

## When to Use

- User says "Our strategy is outdated"
- User asks "How do we plan in uncertainty?"
- User says "We need to be more agile"
- User says "Five-year plans are not working"
- User asks "How do we decide faster?"
- User is frustrated with slow strategic processes

---

## Inputs

| Input | Required | Description | Validation |
|-------|----------|-------------|------------|
| **current_planning** | Yes | How strategic decisions are currently made | |
| **decision_cadence** | No | How often major decisions are made/reviewed | |
| **key_uncertainties** | No | Primary sources of uncertainty in the environment | |
| **information_flows** | No | How information reaches decision makers | |

---

## The Continuous Planning Principle

**The Core Insight:** Five-year plans are "horrible" and "ridiculous" for technology companies. The world changes too fast for static plans. Plans become anchors that prevent adaptation.

**The Jensen Huang Approach:**
- "We assess on a continuous basis whether something makes sense or not. And if it is the wrong decision, let us change our mind."
- "Giant five-year plans are horrible and ridiculous for technology companies. Instead, use a continuous planning system where the company is constantly observing and adapting."
- First principles thinking, trusting intuition, acting with conviction, and changing course immediately when wrong.

---

## Workflow

### Step 1: Planning Process Diagnosis

Assess current planning dysfunction:

| Symptom | Severity 1-5 | Evidence |
|---------|-------------|----------|
| **Stale strategies** - Plans no longer match reality | | |
| **Planning theater** - Documents created but not used | | |
| **Slow response** - Months to adjust to changes | | |
| **Information lag** - Decisions based on outdated data | | |
| **Sunk cost loyalty** - Continuing failed initiatives due to plan commitment | | |

**Interpretation:**
- 5-10: Minor improvements needed
- 11-17: Significant planning dysfunction
- 18-25: Planning process is a competitive disadvantage

### Step 2: Information Flow Design

Create real-time strategic intelligence:

**The "Top 5 Emails" Model:**
- All employees send their five most important observations weekly
- Leadership reads a sampling of these directly (not filtered through hierarchy)
- Topics include: what they are working on, market signals, competitor actions, customer feedback
- Creates hundreds of data points daily for strategic adjustment

| Information Type | Source | Frequency | Who Receives |
|-----------------|--------|-----------|--------------|
| Market signals | | | |
| Competitive intelligence | | | |
| Customer feedback | | | |
| Team observations | | | |
| Risk indicators | | | |

**Key Requirement:** Information must flow unfiltered. Hierarchy sanitizes information until it becomes useless.

### Step 3: First Principles Decision Framework

Replace plan-following with principle-following:

1. **Identify first principles** for your domain
   - What is fundamentally true regardless of market conditions?
   - What physics, economics, or human nature dictates?

2. **Apply to each decision**
   - Does this follow from first principles?
   - What does first principles reasoning say about this situation?
   - Are we following consensus or fundamentals?

3. **Maintain conviction until wrong**
   - Act decisively based on first principles analysis
   - Do not second-guess without new information
   - When proven wrong, admit it immediately

### Step 4: Continuous Assessment Cadence

Design rapid review cycles:

| Review Type | Frequency | Participants | Scope |
|-------------|-----------|--------------|-------|
| **Tactical check** | Daily/Weekly | Team leads | Execution |
| **Strategic pulse** | Weekly | Leadership | Direction validity |
| **Assumption audit** | Monthly | Cross-functional | First principles still valid? |
| **Full reassessment** | Quarterly | All stakeholders | Major pivots if needed |

**Critical Rule:** No sacred cows. Every strategy is evaluated for current validity, not past commitment.

### Step 5: Course Correction Protocol

When change is needed:

1. **Acknowledge immediately** - "We were wrong about X"
2. **Explain the change** - What new information or analysis led to this?
3. **Redirect resources** - Move resources to new direction same day
4. **Communicate broadly** - Tell everyone at once, not in stages

**Speed is essential.** The cost of continuing a wrong strategy exceeds the cost of admitting error.

---

## Outputs

Return a Continuous Planning Assessment:

```markdown
## Continuous Planning Assessment

### Current Process Diagnosis
**Dysfunction Score:** [X/25]
**Key Problems:**
- [problem 1]
- [problem 2]

### Information Flow Design
| Stream | Current State | Recommended | Action |
|--------|--------------|-------------|--------|
| [type] | [state] | [target] | [change] |

### First Principles for Your Domain
1. [principle 1]
2. [principle 2]
3. [principle 3]

### Recommended Cadence
| Review | Frequency | Scope | Owner |
|--------|-----------|-------|-------|
| [type] | [freq] | [scope] | [who] |

### Course Correction Protocol
[Specific process for rapid strategy adjustment]

### Implementation Roadmap
**Week 1-2:** [actions]
**Week 3-4:** [actions]
**Month 2+:** [actions]

### Cultural Shift Required
[What mindset changes are needed]
```

---

## Error Handling

| Situation | Response |
|-----------|----------|
| Regulated industry requiring documentation | Design continuous planning that produces required artifacts as byproduct, not anchor |
| Leadership attached to annual planning ritual | Demonstrate cost of planning lag with specific examples; propose parallel process initially |
| Distributed decision-making culture | Continuous planning works with decentralization; emphasize information flow, not centralized decisions |
| No clear first principles | Work to establish them; without first principles, continuous planning becomes reactive thrashing |

---

## Constraints

- Do not oversimplify complex business realities
- Do not ignore resource and timeline constraints
- Acknowledge risks and uncertainties explicitly
- Honor stakeholder concerns and competing priorities
- Base recommendations on available evidence, not assumptions
- Consider second-order effects and unintended consequences

## Example

**Input:**
```
current_planning: "Annual strategic planning process with quarterly reviews"
decision_cadence: "Major decisions require 2-3 months of analysis"
key_uncertainties: "AI capabilities evolving rapidly, competitor moves unpredictable"
information_flows: "Monthly reports rolled up through management layers"
```

**Output Summary:**

> "Your planning process is a competitive liability. In a world where AI capabilities change monthly and competitors can pivot in weeks, you are making decisions with 3-month-old information and strategies set a year ago. This is not planning; this is organizational paralysis.
>
> Dysfunction score: 21/25. Your monthly reports through management layers mean leadership is making decisions based on sanitized, stale data. By the time you identify a strategic issue, analyze it, and decide, the world has moved.
>
> Here is the redesign:
>
> **Information flow:** Implement Top 5 emails immediately. Every leader sends five key observations weekly. CEO reads 100+ of these directly. No filtering. This creates real-time strategic intelligence.
>
> **Decision cadence:** Move from quarterly reviews to weekly strategic pulse checks. Every Monday, leadership asks: 'Are our current priorities still the right priorities?' This is not a full replanning - it is a validity check.
>
> **First principles anchor:** In AI infrastructure, the first principles are: (1) compute demand grows exponentially, (2) latency matters for edge applications, (3) developer ecosystems compound. Evaluate every decision against these.
>
> **Course correction speed:** When you identify a wrong strategy, change direction the same day. Not next quarter. Not after more analysis. Today.
>
> Five-year plans are horrible. The world changes too fast. You need a system that assumes the plan is wrong and continuously corrects. Build that system now."

---

## Integration

This skill originates from the Jensen Huang expert methodology. When used:
- Apply Jensen Huang voice characteristics (direct, urgent, first-principles-based)
- Emphasize speed of adaptation
- Challenge attachment to existing plans
- Frame continuous planning as survival requirement

---

## Success Criteria

Continuous Planning Method is complete when:
- [ ] Current planning dysfunction diagnosed and scored
- [ ] Information flow redesign specified
- [ ] First principles for the domain identified
- [ ] Review cadence designed
- [ ] Course correction protocol established
- [ ] Implementation roadmap provided