HUGO JERIA STRAUSS
Menu
← All writing

NOTE 03 · Knowledge Management · 5 min read

Building Knowledge Systems for Food Expertise

Most of what a professional cook knows never gets written down. Turning that into something reusable is a documentation problem before it's an AI problem.

A surprising amount of culinary expertise is tacit — held in hands and habits rather than written anywhere. A cook who's made a sauce a thousand times knows what it should look like a minute before it's ready in a way that's genuinely difficult to put into words. That's fine in a working kitchen, where the knowledge is transmitted by watching and doing. It's a real problem the moment you need that knowledge to be usable outside the person who holds it — for training new staff, for documentation, or for any system that needs a defensible, explicit version of what an expert knows.

Turning tacit knowledge into explicit knowledge is a discipline in its own right. It means breaking a technique down into the specific, checkable cues an expert is actually using — not just 'cook until done,' but the visual, textural, and timing signals that define 'done' for that specific method and ingredient. It means building a shared vocabulary so the same term means the same thing every time it's used. And it means organizing that material so it can be found and reused, rather than living as scattered notes that only make sense to the person who wrote them.

The result, done well, looks less like a recipe collection and more like a reference system: technique documented separately from any single dish, ingredient behavior documented separately from technique, sensory vocabulary defined once and reused consistently. That structure is what makes the knowledge portable — usable by a new cook, a documentation team, or a dataset labeling guideline, without needing the original expert in the room to interpret it.

This is also, not coincidentally, the same structure that makes domain knowledge usable for AI work. A well-organized culinary reference system and a well-organized dataset guideline are solving the same underlying problem: making expert judgment explicit, consistent, and checkable by someone who isn't the expert. Good knowledge management in a kitchen and good knowledge management for AI training data turn out to be closer disciplines than they first appear.