playbooks

home / skills / coowoolf / insighthunt-skills / historian-decision-model

historian-decision-model skill

/decision-thinking/historian-decision-model

This skill helps teams learn from past decisions by excavating history, contextualizing constraints, and forming data-informed strategies.

npx playbooks add skill coowoolf/insighthunt-skills --skill historian-decision-model

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.3 KB
---
name: historian-decision-model
description: Use when joining a new company, taking over legacy products, or proposing strategies that were previously attempted to avoid repeating past mistakes
---

# The Historian Decision-Making Model

## Overview

A process for improving decision quality by **excavating and analyzing organization history** to understand the context of past failures before charting a new path.

**Core principle:** Learn from mistakes you didn't personally live through.

## The Process

```
┌─────────────────────────────────────────────────────────────────┐
│  1. EXCAVATE                                                    │
│     Research past decisions and outcomes                        │
│     Talk to long-tenured employees                              │
├─────────────────────────────────────────────────────────────────┤
│  2. CONTEXTUALIZE                                               │
│     Analyze "Why" decisions were made at that time              │
│     What was the environment/constraints?                       │
├─────────────────────────────────────────────────────────────────┤
│  3. IDENTIFY BAGGAGE                                            │
│     Map internal resistance and emotional blockers              │
│     "We tried that before" = baggage signal                     │
├─────────────────────────────────────────────────────────────────┤
│  4. FORMULATE HYPOTHESIS                                        │
│     Create strategy informed by historical context              │
│     Address what was different then vs. now                     │
├─────────────────────────────────────────────────────────────────┤
│  5. DECIDE & ITERATE                                            │
│     Commit to direction without needing 100% certainty          │
│     Learn from results                                          │
└─────────────────────────────────────────────────────────────────┘
```

## Key Principles

| Principle | Description |
|-----------|-------------|
| **Excavate actively** | Don't assume you know the past |
| **Context matters** | Same idea can fail or succeed based on timing |
| **Baggage is real** | Emotional weight blocks rational evaluation |
| **Commit anyway** | History informs but doesn't dictate |

## Common Mistakes

- Ignoring "baggage" associated with old ideas
- Making decisions without understanding historical context
- Assuming "we tried that" means it can never work

---

*Source: Anneka Gupta (Rubrik CPO) via Lenny's Podcast*

Overview

This skill teaches a historian decision-making model that improves choices by excavating and analyzing an organization’s history. It helps product leaders and new team members avoid repeating past mistakes by understanding why prior efforts succeeded or failed. The approach balances learning from the past with committing to forward movement.

How this skill works

First, excavate: gather records, interview long-tenured staff, and compile a timeline of past decisions and outcomes. Next, contextualize those decisions by reconstructing the constraints, incentives, and information available at the time. Identify baggage—emotional resistance and institutional stories—and surface hypotheses about what would change the outcome today. Finally, decide with an iteration plan that tests the hypothesis while acknowledging historical insights.

When to use it

  • Joining a new company and onboarding into legacy products or projects
  • Taking over ownership of long-running features or initiatives
  • Proposing revival of a previously attempted strategy or product
  • Designing a roadmap where skeptical stakeholders keep saying “we tried that”
  • Post-mortems and strategic reviews to avoid repeating systemic errors

Best practices

  • Prioritize primary sources: meeting notes, metrics, and interviews over anecdotes
  • Reconstruct the historical context: incentives, resource constraints, and market conditions
  • Treat “we tried that” as a research signal, not a veto
  • Map emotional and political baggage explicitly before proposing change
  • Formulate testable hypotheses that address why prior attempts failed

Example use cases

  • A new PM inherits a legacy product and needs to decide whether to iterate, rebuild, or sunset it
  • A team considers reintroducing a previously canceled feature and must surface why it failed before
  • A leader crafts a strategy pitch to skeptical stakeholders who recall past failures
  • Conducting a retrospective to identify systemic process gaps that caused repeated issues

FAQ

How long should the excavation phase take?

It depends on scope; for a single product, aim for 2–4 weeks of focused archival review and stakeholder interviews to form an initial narrative.

What if historical records are incomplete or biased?

Triangulate across multiple sources: metrics, timelines, interviews from different levels, and customer data. Treat gaps as hypotheses to test, not obstacles.