← 홈 / 주제
주제

connaissance-notes

에세이 20편
최신순
2026-10-28

산출물은 결론을 남기고 이유를 잃는다

한 고객에게 통했던 권고가 다음 고객에게는 틀린 답이 될 수 있지만, 보고서는 그 이유를 말해 주지 않습니다. 각 결정을 대안, 근거, 조건과 함께 남기고, 여기서 고객 데이터가 빠진 노트를 끌어내면, 컨설팅 회사는 누구의 신뢰도 저버리지 않고 배운 것을 다시 쓸 수 있습니다. 좋은 답이 더 이상 성립하지 않는 순간도 첫날부터 알아볼 수 있습니다.

2026-10-28

처음부터 다시 할 것인가, 복사할 것인가: 아는 것을 잃는 두 가지 방법

같은 보안 질문서에 열 번째 답할 때, 모든 것을 다시 하지도 않고 틀린 답변을 복사하지도 않는 방법이 있습니다. 사실을 주제별로 정리하고 출처, 날짜, 한계를 함께 남기면, 115개 질문짜리 질문서도 10분 만에 80~90%가 준비됩니다. 그리고 빠진 부분은 담당 팀에 보내는 구체적인 질문이 됩니다.

2026-10-14

AI 없는 Graphify: 위키를 토큰 0개로 탐색 가능한 그래프로 바꾸기

서로 링크된 노트가 천 개나 있어도 전체 모습은 보이지 않습니다. 어떤 아이디어가 중심이고 어떤 것이 고립되어 있는지, 멀리 떨어진 두 개념이 어떻게 이어지는지 알 수 없습니다. 위키의 링크마다 이미 설명이 적혀 있다면, 160줄짜리 Python 스크립트만으로 완전한 그래프를 뽑아낼 수 있습니다. 탐색은 Graphify가 맡고, 걸리는 시간은 0.2초, 쓰는 토큰은 하나도 없습니다.

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

최신 글