Blog

Notes on how companies remember.

Long-form thinking on decision records, context graphs and the quiet cost of institutional forgetting.

The half-life of a decision

When the reason behind a decision is scattered across tools, teams can lose the context needed to revisit it. The examples below illustrate that problem; they are not a customer study.

Why knowledge bases keep dying

Documentation needs maintenance. Connecting permitted source evidence with decisions helps teams keep the reasoning close to the work.

Designing a graph people actually read

Node-link diagrams are usually decoration. We rebuilt ours around influence weighting so that the layout itself carries information.

Investor updates as a byproduct

A completed Report can provide a starting snapshot for an Investor Update. The team still reviews, edits and publishes the final narrative.

01

The half-life of a decision

A decision can outlast the conversation that explained it. This hypothetical chart illustrates why preserving evidence matters; it does not measure customer behavior or predict an outcome.

  • Record the decision and its rationale
  • Attach the supporting evidence
  • Revisit current state when the context changes

Illustrative data only. No customer study is represented.

Recall of a decision's reasoning

Hypothetical percentage, by week.

W018% recallW14
Illustrative scenario
02

Why knowledge bases keep dying

Maintaining documentation takes work while new context continues to arrive in company tools. These sample series illustrate the gap a team might investigate.

  • Review where your team records decisions
  • Check whether evidence is still accessible
  • Make uncertainty visible before relying on context

Wiki edits per week

Illustrative editing activity.

W1W3W5W7W9W11

Context produced elsewhere

Illustrative connections over the same period.

1248
Connections

Topics to explore

Questions behind shared company state.

Illustrative notes on decisions, evidence and reporting.

Research

The half-life of a decision

How a decision can lose the evidence behind it.

Illustrative product note

Essay

Why knowledge bases keep dying

Connecting evidence alongside maintained documentation.

Illustrative product note

Design

Designing a graph people actually read

Influence weighting turns decoration into information.

Illustrative product note

Playbook

Investor updates as a byproduct

Preparing a reviewed narrative from a completed Report.

Illustrative product note

Illustrative signals

The charts behind the essays.

The following charts use sample data to illustrate investigation topics; they are not live company metrics.

Documentation coverage is falling behind

Coverage drops long before anyone notices.

48

Engineering velocity improved

What happens once context stops going missing.

61

Support load is shifting to billing

An illustrative change a team could investigate.

31

Everything here was written inside Loreflow.

Bring evidence and drafts into one workspace, then review the narrative before sharing an Investor Update.

FAQ

About these notes.

Ideas and illustrative examples.

Open the live demo

Company memory, decision history, evidence and reporting workflows.

No. Charts on this page are illustrative sample data, not measured customer results or product performance.

Contact the team with the workflow you want to understand.