---
title: "Knowledge consumption, retrieval and retention call for different structures of information"
author: "Stan Voo"
url: https://www.99rabbits.com/blog/knowledge-consumption-retrieval-and-retention-call-for-different-structures-of-information
published: 2024-12-02
summary: "Learning needs information in sequence, retrieval needs a network, retention needs both. What that means for building a company knowledge base."
---

# Knowledge consumption, retrieval and retention call for different structures of information

**Key idea:** we might need to transform information between different structures at different stages of learning:

- Present it sequentially for initial learning.
- Store it in a network structure for flexible retrieval.
- Support both patterns and sequences for long-term retention.

---

When we build a corporate knowledge base, we usually think of it as a book or a collection of instructions. That way, we may unknowingly put reading it for the first time ahead of using it for reference later.

Here's how employees actually interact with information.

**Consumption (learning).** Sequential structures work better at first, because they align with our cognitive limits and our natural learning process. Humans naturally understand and recall information in a sequential, chronological or cause-and-effect order. Sequentially structured information is also easier to transmit. Reading is decompressing a narrative into a concept network, and that decompression is part of how we first consume and process information.

![](https://www.99rabbits.com/blog/knowledge-consumption-retrieval-and-retention-call-for-different-structures-of-information-information-transmission.webp)

*Writing compresses a concept network into a narrative; reading decompresses it*

**Retrieval.** Network structures are superior here, because they allow multiple access points and pathways to the same information: a networked narrative. A network makes information easy to reach, which is crucial for PKM, while ease of transmission doesn't matter in this context. This aligns with how our brains actually store information — in interconnected semantic networks, not linear sequences. Multiple pathways mean we can retrieve information even if we forget the exact "route" by which we originally learned it.

![](https://www.99rabbits.com/blog/knowledge-consumption-retrieval-and-retention-call-for-different-structures-of-information-reading-a-paper.webp)

*From Ilya Shabanov’s [The 10 Commandments of Academic Note-Taking](https://thestrugglingscientists.com/10-commandments-of-note-taking/)*

**Retention.** A hybrid approach seems most effective. While we might learn sequentially, retention works best when information is integrated into a broader network of understanding. Pattern recognition (network-based) and sequence recognition (linear) serve different but complementary purposes in retention.

We should build knowledge management tools with these processes in mind.

## A corporate knowledge base that respects both structures

**Entry points.** Create multiple "front doors" for different use cases: task-based pathways ("I need to do X"), concept-based navigation ("I want to understand Y"), role-based guides ("I'm a new sales rep") and problem-based access ("I'm trying to solve Z").

**Sequential learning paths.** Design structured learning sequences for first-time exposure. Break complex topics into digestible modules, provide clear progression paths, and include checkpoints and practical exercises. *Example:* onboarding guides that follow a "day 1 → week 1 → month 1" structure.

**Network connections.** Implement rich hyperlinking between related concepts, create concept maps that show relationships, use consistent tagging for cross-referencing, and build "see also" sections that show related content. *Example:* each procedure links to related procedures, the concepts beneath it and common troubleshooting.

**Retrieval features.** Strong search that handles task-based queries, quick reference guides and checklists, context-sensitive help inside tools, and visual navigation maps. *Example:* search that understands both "how to process refund" and "refund policy".

**Retention support.** Practice scenarios and examples, real-world case studies, decision trees for complex processes, and interactive elements for active engagement. *Example:* troubleshooting guides that combine step-by-step processes with an understanding of the underlying systems.

**Integration.** Link sequential guides to network-based reference material, provide both quick-start guides and deep dives, create multiple paths to the same information, and build bridges between theoretical and practical content. *Example:* a procedure guide that links to both "next steps" and related concepts.