MSPOT Generator

What is MSPOT?

One-page strategic clarity (from HubSpot):

• Mission: Why we exist (rarely changes)
• Strategy: How we'll win this period
• Projects: The 3-5 big bets
• Omissions: What we're explicitly NOT doing
• Tracking: How we'll measure success

Why It Works

1. Forces Omissions: Saying NO is harder and more valuable
2. Limits Projects: 3-5 max prevents spreading thin
3. One Page: If it doesn't fit, it's not clear
4. Trackable: Decision-useful metrics only

Output Format

═══════════════════════════════════════════════
MSPOT: [Name]
Period: [Timeframe] | Owner: [Person]
═══════════════════════════════════════════════

MISSION: [One sentence: Why this exists]

STRATEGY: [2-3 sentences: How we'll win]

PROJECTS (3-5 max):
1. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]
2. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]
3. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]

OMISSIONS:
✗ NOT [X] - Because: [reason]
✗ NOT [Y] - Because: [reason]

TRACKING:
Lead: [Activity] → Target: [X]
Lag: [Result] → Target: [Y] by [date]
═══════════════════════════════════════════════

Key Questions

Integration

Compounds with:

• pre-mortem-analyst → Pre-mortem each Project before committing
• inversion-strategist → Invert to find Omissions
• artem-decision-journal → Log major MSPOT decisions

See references/examples.md for TeddySnaps/TISA/GolfTab MSPOTs