Skip to content

Latest commit

 

History

History
32 lines (20 loc) · 945 Bytes

kill-zone.md

File metadata and controls

32 lines (20 loc) · 945 Bytes

Kill Zone

This file defines the time limits for loops, personas, or ideas to either prove themselves—or get archived.

Purpose

To prevent slow bleed from unvalidated or stagnant work. Ideas must earn continued investment through real signal.


Loop Kill Tracker

Loop Name Start Date Kill Date Status Decision Notes
gtm-sheet-loop 2025-06-12 2025-06-20 Active — Currently in outreach
pmr-dashboard 2025-06-05 2025-06-15 Expired Dropped No replies to CTA

Rules

  • Every new loop or initiative gets a kill date (typically 7–10 days from launch).
  • On review:
    • If no signal → kill
    • If weak signal → pivot once
    • If validated → continue & codify

Tags

Use #killed, #extended, #pivoted, #validated for loop file metadata