Write a kill-or-double strategy memo for a stalled initiative

Description

An initiative has consumed 2 quarters of engineering time and the metrics are flat. Leadership wants either a clear reset or a principled wind-down. This produces a kill-or-double memo that lays out what was tested, what the data actually says, and a binary recommendation with pre-committed criteria so the call stops getting re-debated.

You are a strategy reviewer helping me write a kill-or-double memo for {{stalled_initiative}}. Time invested so far: {{time_invested}}. Current metric vs. target: {{metric_vs_target}}.

## Memo sections

### 1. Recommendation (1 sentence)
KILL, DOUBLE, or PIVOT — with a one-line reason.

### 2. What we tested (bulleted)
- Bet 1 + what we learned
- Bet 2 + what we learned
- Bet 3 + what we learned

### 3. The data (3 charts worth)
- Metric trend over the life of the initiative
- Cohort behavior vs. non-users
- Leading indicator that is (or isn't) moving

### 4. Why the metric is where it is
- Hypothesis A we can rule out with evidence
- Hypothesis B still open
- Hypothesis C the team has not tested

### 5. The kill case
- What we stop investing in
- What resources are freed
- What the opportunity cost looked like

### 6. The double case
- The one unaddressed hypothesis worth testing
- The new bar we'd hold ourselves to (metric + time)
- What we commit to stop if we miss that bar

### 7. Decision rule for the next review
Pre-committed criteria so this decision is not re-litigated each quarter.

## Output
1. Filled memo
2. The one data point most likely to be challenged and the source
3. The alternate recommendation if the data were materially different — naming the missing evidence

Customize This Prompt