Skip to content

Kanban board · reads note

Research board

Findings by status.

Cards in columns, one column per stage.

Keeping "one comment" labelled as raw is what stops it becoming a strategy by Tuesday.

Concluded

Wholesale buyers want 30-day terms

Corroborated

Subscriptions churn after month 4

Raw

People find the grinder overpriced

Cafés would white-label

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Columns are confidence, not progress. Moving a card right means the evidence got stronger.

Keeps hunches visibly separate from things you know, which is what stops one comment becoming a strategy.

Sources are recorded per finding, so a claim can be traced.

How it works

  1. 1

    Findings enter as Raw with whatever source they came from.

  2. 2

    Moving one right means the evidence got stronger, not that somebody worked on it.

  3. 3

    The source is required, so a claim can always be traced back.

  4. 4

    A finding that stays Raw for weeks is visible, and usually should be dropped.

Best for

Anything that moves through stages: leads, orders, applications.

Not the right choice for

Data with no natural stages — you get one very long column.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
FindingrequiredtextWhat you think you have learned, stated as a claim.
ConfidencerequiredchoiceRaw, Corroborated or Concluded. The column is confidence, not progress.
SourcerequiredtextWhat it rests on. Required, because an unsourced finding is a hunch with a promotion.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • Confidence is three levels. Anything finer is a judgement pretending to be a measurement.
  • No weighting or aggregation across findings.
  • Nothing prevents a Concluded finding being wrong; it only records that somebody decided.
  • No link between a finding and the decision it informed unless you write one.

Before it works

What you have to provide, if anything.

  • Nothing.
  • Pair with Decision log, so a conclusion and the choice it drove sit next to each other.

In practice

A team doing customer research before building.

Somebody at the market said cafés would white-label.
What was said to the agent

What the agent built

A finding in the raw column, sourced to one overheard remark.

What changed

It stayed raw for six weeks and was never corroborated. The feature it would have justified was not built.

Questions

What data does the Research board page use?

It reads note records the agent has collected. Findings by status. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a kanban board the wrong choice?

Data with no natural stages — you get one very long column. It is best for: anything that moves through stages: leads, orders, applications.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ