The structure keeps drawing itself underneath us. We can refuse to write it down, but the team still behaves as though it exists — so we may as well make it explicit and argue about the real version.
Idea pool
The @orgdevkit/kit-idea-pool durable idea archive — capture in seven kinds, a five-dimension filter and search, a theme treemap, drag or multi-select to combine, compose with the joins under your control, and six syntheses made from what the pool holds. Over synthetic fixtures; the assistive seams play scripted answers with no live model.
The pool — click through it
Type a thought and press Enter to keep it (a leading /quote, /seed or /read-later picks the kind). Hold ⌘ or Ctrl and click two cards to select them, then Compose to arrange them and write the joins, or Combine to merge them straight away. Clusters swaps the stream for a treemap of its themes. The verbs at the foot make something from the whole pool — each answer arrives a piece at a time and cites the notes it stands on.
Every recurring meeting we run is answering a question nobody has written down. Write the question at the top of the agenda and half of them end.
Nobody describes themselves as our target segment. They describe a Tuesday afternoon that went badly.
“We do not have a strategy. We have a series of arguments we keep losing.”
A circle lead, planning session
“Good tools are mostly a list of things they refuse to do on your behalf.”
A workshop participant, craft session
A useful frame for the messy middle of our pricing tiers — worth re-reading before the next quarterly.
Long piece on why interfaces that explain themselves beat interfaces that are merely simple. Relevant to the reveal question.
I keep adding surfaces because building one is more comfortable than deciding which of them we actually need. The decision is the work; the building is the avoidance.
unsettled, 2026-05-30
The week went better when I named the one outcome on Monday instead of ranking twelve tasks. Ranking felt like progress and produced none.
2026-05-12
“They said the handover is the part that hurts — not the work, the handover. Three people each assume one of the others is holding it.”
“Asked what would make them switch: "somewhere I can see who decided what, without asking anyone."”
“They had built the same thing twice in a spreadsheet and did not think of it as a tool. That is the whole opportunity in one sentence.”
A one-page "who decided what" trail per circle, generated from the records we already keep. No new inputs.
Quarterly re-read ritual: everything captured older than a month, ten minutes, keep or retire. The archive earns its keep or it is a graveyard.
Works best with the decision already framed as two options. Open-ended asks come back as more questions.
About Finance role, budget rounds