First Principles

Full Markdown demo

# First Principles: Classic Generation Example

## Input Summary
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Classic Case Context
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Skill Used
- First Principles
- Strip a problem down to facts and constraints, then rebuild.
- Best for: Cost reduction, new business models, architecture redesign, and innovation.
- Can generate: Facts, assumptions, hard constraints, and redesigned options.

## Situation Judgment
This is a classic situation for First Principles: the input contains a goal, constraints, stakeholder judgments, and a need for action.

## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use First Principles to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.

## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through First Principles | Create shared language |
| Action | Owner, time, metric | Drive execution |

## Reusable Diagram
This is a Markdown-only output. Switch to diagram or PDF-ready output to generate Mermaid.

## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.

## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.

## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.

Full Markdown demo

# First Principles: Classic Generation Example

## Input Summary
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Classic Case Context
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Skill Used
- First Principles
- Strip a problem down to facts and constraints, then rebuild.
- Best for: Cost reduction, new business models, architecture redesign, and innovation.
- Can generate: Facts, assumptions, hard constraints, and redesigned options.

## Situation Judgment
This is a classic situation for First Principles: the input contains a goal, constraints, stakeholder judgments, and a need for action.

## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use First Principles to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.

## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through First Principles | Create shared language |
| Action | Owner, time, metric | Drive execution |

## Reusable Diagram
```mermaid
mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions
```

## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.

## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.

## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.

Mermaid demo

mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions

Full Markdown demo

# First Principles: Classic Generation Example

## Input Summary
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Classic Case Context
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Skill Used
- First Principles
- Strip a problem down to facts and constraints, then rebuild.
- Best for: Cost reduction, new business models, architecture redesign, and innovation.
- Can generate: Facts, assumptions, hard constraints, and redesigned options.

## Situation Judgment
This is a classic situation for First Principles: the input contains a goal, constraints, stakeholder judgments, and a need for action.

## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use First Principles to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.

## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through First Principles | Create shared language |
| Action | Owner, time, metric | Drive execution |

## Reusable Diagram
```mermaid
mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions
```

## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.

## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.

## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.

Mermaid demo

mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions

PDF-ready HTML demo

<!doctype html>
<html>
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>First Principles: Classic Generation Example</title>
  <style>
    body { font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; margin: 48px; color: #161a1d; line-height: 1.6; background: #fbfcf8; }
    h1 { font-size: 34px; line-height: 1.1; margin: 0 0 18px; }
    h2 { font-size: 20px; margin-top: 28px; }
    pre { white-space: pre-wrap; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 18px; overflow-wrap: anywhere; }
    .meta { color: #2563eb; font-size: 12px; text-transform: uppercase; font-weight: 800; letter-spacing: .08em; }
    .sheet { max-width: 940px; margin: 0 auto; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 32px; }
    @media print { body { margin: 18px; background: #fff; } .sheet { max-width: none; border: 0; padding: 0; } }
  </style>
</head>
<body>
  <main class="sheet">
    <p class="meta">ThinkOps AI PDF-ready output</p>
    <h1>First Principles: Classic Generation Example</h1>
    <pre># First Principles: Classic Generation Example

## Input Summary
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Classic Case Context
Our support cost grows 18% every quarter. The obvious suggestions are more outsourcing or a FAQ bot, but both have limited impact. The real drivers may be unclear product copy, a complex permissions model, weak implementation training, and confusing invoices. Use first principles to separate facts, assumptions, redesignable constraints, and new low-cost solution combinations.

## Skill Used
- First Principles
- Strip a problem down to facts and constraints, then rebuild.
- Best for: Cost reduction, new business models, architecture redesign, and innovation.
- Can generate: Facts, assumptions, hard constraints, and redesigned options.

## Situation Judgment
This is a classic situation for First Principles: the input contains a goal, constraints, stakeholder judgments, and a need for action.

## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use First Principles to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.

## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through First Principles | Create shared language |
| Action | Owner, time, metric | Drive execution |

## Reusable Diagram
```mermaid
mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions
```

## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.

## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.

## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.
</pre>
    <h2>Mermaid diagram source</h2><pre>mindmap
  root((First Principles))
    Facts
      Evidence
      Signals
    Assumptions
      Unknowns
      Tests
    Options
      Preferred path
      Alternatives
    Delivery
      Report
      Diagram
      Actions</pre>
  </main>
</body>
</html>