← ホーム / テーマ
テーマ

connaissance-notes

エッセイ 20 本
新着順
2026-10-28

成果物は結論を残し、「なぜ」を失う

ある顧客で成功した提言も、次の顧客では誤りになりえます。しかし報告書はその理由を語りません。決定を代替案・理由・条件とともに残し、そこから顧客データを含まないノートを引き出せば、ファームは誰も裏切ることなく学んだことを再利用でき、正しかった答えが通用しなくなる瞬間を初日から見抜けます。

2026-10-28

ゼロからやり直すか、コピーするか:知っていることを失う2つの方法

10回目の同じセキュリティ質問票に、すべてをやり直すことなく、誤った回答をコピーすることもなく答える。事実をテーマごとに整理し、出どころ、日付、限界を添えて残しておけば、115問の質問票も10分で80〜90%まで準備できます。欠けている情報は、担当チームに向けた具体的な質問に変わります。

2026-10-14

AIなしのGraphify:Wikiをトークンゼロで探索できるグラフに変える

1,000枚のノートが互いにリンクされているのに、全体像が見えません。どのアイデアが中心にあり、どれが孤立しているのか、離れた2つの概念がどうつながるのかがわかりません。wikiのリンクがノートの中ですでに説明されているなら、160行のPythonスクリプトで完全なグラフを取り出せます。Graphifyで探索でき、計算は0.2秒、トークンは1つも使いません。

2026-10-04

Stateful Corpus Research Loop:ソースの収集をやめる

次に何を探すべきか、そして何よりいつ止めるべきかを知るための方法です。30件や50件といったソース数を最初に決めるのではなく、厳選された小さなコーパスから始め、そこから構造化された知識を取り出します。そのうえで、コーパスが知っていること、まだ知らないことに次の検索を選ばせます。重複が減り、死角が見えるようになり、検証できる停止基準が手に入ります。

2026-09-21

「Contexte」で自分が本当に発明したものは何だったのか、調べてみました

何か月もかけてつくった方法が、別の名前ですでにどこかに存在していないかを確かめるにはどうすればよいのでしょうか。手順はいくつかに絞れます。アイデアを仕組みに分解する。用語ではなく機能で探す。自分の分野と英語の外に出る。そして、新しい発見が何を変えれば意味があるのかを、あらかじめ決めておくことです。

2026-09-20

柱カード:考え続けるために記憶を手入れする

AIで速く生産するほど、考える時間がその生産に置き換わっていきます。この記事では、その時間を守るための具体的な仕組みを紹介します。数を絞ったカードの中核を間隔反復で手入れし、テーブルに並べて新しい考えを自分の信念と突き合わせるというものです。カードに加える基準、見直しの間隔、そして始め方まで説明します。

2026-09-04

The deliverable is no longer the asset

Every new format feels like starting over: you reopen the last document, copy, rephrase, and two versions slowly drift apart. The cause isn't a missing tool, it's treating a deliverable as your source of truth. How to install a reusable layer between your sources and your documents, and what AI gains from it.

2026-09-07

How I write my articles by talking to my phone

Your best article ideas die between the moment they turn up and the moment you sit down to write. Here is the setup that catches them while they are still warm: the voice to empty your head without putting anything in order, a session source to keep the raw material raw, AI to surface the gaps in ten seconds rather than in two days.

2026-08-11

I wrote a product's ontology. Three times, I thought I was done.

Your team rebuilds the same product model for every question, every bug, every tender. Here is how to write it down once: several dozen objects, a few hundred rules, under six hours. And above all how to know you have finished — the three stopping criteria that look like proof of completeness and prove nothing, plus the one that holds.

2026-07-20

Session sources: what your documents miss

Your documents never say everything. The fine-grained understanding of what happens on the ground stays in the PM's head. Session sources open a channel for pouring that informal knowledge into an AI Context — a hallway remark, a nuance picked up from a customer, a tension just starting to show — and turn dozens of micro-signals into notes, assumptions and better-framed decisions.

2026-06-16

What Is a Thematic Note?

A thematic note is the link between a note system and writing. It doesn't pile up everything that touches a subject — it picks an angle and brings several atomic notes together to make a pattern, a tension or a line of argument visible. Not a folder, not an encyclopedia: a temporarily stable view onto a network of thought.

2026-06-16

What is an atomic note?

"One idea per note" is the formula everyone knows, and it sends most people in the wrong direction. An atomic note is not a short note. It is a note with a single conceptual centre of gravity. Once you see that difference, it changes how you capture, rephrase, title and link. And in the end, how you write.

2026-06-16

What is a glossary entry?

The same words travel between product, marketing, sales and leadership, and nobody gives them quite the same meaning. A glossary isn't a collection of textbook definitions: it's a tool for collective precision. It pins down the terms that carry decisions, protects the links between notes, and cuts the cost of conversations where everyone defends a different idea with the same vocabulary.

2026-06-16

The art of capture

We pile up tabs, links and quick notes — and never read them again. The problem isn't the amount of information, it's that nothing is ever decided about what it becomes. This article separates capturing from building capital, and offers a simple rhythm for turning your captures into knowledge without drowning in them.

2026-06-16

Flash Card

An excellent note base isn't enough if the ideas never get absorbed. A flash card isn't a small atomic note: it's a personal pillar of thought, recognised in the heat of the moment by its resonance, tested over time by experience and by new sources. Rare by definition, it holds up what you really want to carry in you.

2026-06-08

The PM as Architect of Context

Most organisations know how to produce documents. They don't know how to bank the reasoning behind them. On every decision they start again almost from scratch. The PM as Context architect turns scattered customer knowledge — transcripts, objections, past calls, weak signals — into a reusable asset. The result: faster, sturdier decisions, and an advantage competitors cannot copy overnight.

2026-05-25

AI Wiki: why I built a knowledge base maintained by an AI

Classic RAG starts from scratch with every question. By building an AI Wiki — a persistent wiki maintained by an LLM — you capitalize on domain knowledge once and for all. Atomic notes, links between concepts, contradiction detection: knowledge is compiled, not rediscovered. Lessons learned from 950 notes extracted from industrial maintenance sources, with calibration insights and concrete use cases.

2026-05-03

The second brain is a dead end for product management

Managing product opportunities inside a borderless network of notes means losing control: errors propagate silently, the AI context window blows up, and contradictions and decisions become impossible to find. The bounded context — borrowed from DDD — offers a better approach: each opportunity in its own bounded, auditable space, with a structured memory.

2026-04-24

One file, a few directives, and Claude does the rest — how I structured 500 emails effortlessly

Drowning in email and losing track of the threads in flight? By handing the structuring over to Claude — one file, a few directives, then a gradual split — I turned 500 building-management emails into a queryable knowledge base. Seven steps, from the vague directive to a multi-file system, without ever needing a complex framework.

2026-04-21

From the Single File to a System of Contexts: Why an LLM's Memory Won't Fit in One Document

最新の記事