Skip to content
kflow
Knowledge Flow Studio
  • Pages
    • kflow
      Knowledge Flow Studio
      • kflow
        KFlow Chapter Notes
      • kflow
        Consider This
      • activity
        KFlow Activities
        • activity
          Build a Starting Structure
        • activity
          Create and Use a Glossary
        • activity
          Spot the Patterns
        • activity
          Explore Core Competencies
        • activity
          Experiment with Ideas
      • pattern
        KFlow Example Studio
        • pattern
          Glossary
        • pattern
          Ideas
        • pattern
          Patterns Exploration
          • pattern
            Patterns
        • pattern
          Free Writing
          • pattern
            December 25, 2026
        • pattern
          Resources

Create and Use a Glossary

The most important tool in your studio
Knowledge can’t flow when people are using the same words to describe different experiences.
If you’ve ever used the word Agile in a meeting, you know what I mean. 98% of the time, everyone has a different definition of Agile. Even common words can trip us up. When people think they are talking about the same thing, but aren’t, the discussion spirals. Not because they don’t understand each other — they are solving different problems and don’t realize it.
Sharing the same language is key to Knowledge Flow. In Domain-Driven Design, this is called “ubiquitious language”. Everyone uses the same terms in conversations, code, documentation, and experiences. This enables quicker understanding and a significant decrease in bikeshedding.
Make a list of words that matter. The ones that people must understand in order for you to make sense. As you read, practice, and build your studio — add more, whenever a word’s meaning is essential to share.

I’ve included some relevant terms. Like bikeshedding!
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.