The Doc Landscape is built on a premise: documentation is part of a living knowledge system. Not a deliverable or a phase of development, but one layer of something larger.

So, if documentation is part of a knowledge system, what does that system actually look like? Who else is in it? Where does documentation fit and where does it fall short?

This series exists to explore these questions seriously.

What Is The Living Knowledge Systems Series?

The Living Knowledge System examines how product knowledge is created, flows, degrades, and gets used across the full lifecycle of a software product, from discovery through operation.

It looks at documentation not as a standalone discipline but as one layer within a larger knowledge architecture. Some of that architecture is intentional. Much of it isn’t. And the gap between the two is where knowledge debt accumulates, where useful context disappears, and where documentation ends up playing catch-up with a system that was never fully designed.

The series maps that system: its stages, its tiers, its audiences, and its structural failure points. It also examines where documentation engineering fits within it and where the field is still working out what its scope should be.

The Mental Model for The Living Knowledge System

The following diagram is the foundation of the series. It maps the knowledge system across five product lifecycle stages, three knowledge tiers, five audience types, and the upstream and downstream flows that connect them.

It also shows where most companies under-invest: the pipeline that should move ephemeral knowledge into durable form before it disappears, and the retirement process that almost never exists for content that has quietly stopped being true.

Each section of the series expands on what the diagram maps.

Who Is The Living Knowledge System Series Is For?

This series is for you if documentation plays a meaningful role in how your organization builds or operates software and you’ve started to suspect that the problem you’re solving is larger than any single document, tool, or workflow.

More specifically, it’s for you if:

• You document software products and have felt the gap between writing documentation and keeping knowledge usable as systems evolve
• You work on documentation structure, reuse, and lifecycle and want a clearer model of the larger system you’re operating within
• You’re a documentation engineer, or a technical writer moving in that direction, and want to understand how the field’s scope is expanding beyond content production
• You work in a role that depends on product knowledge (engineering, QA, support, or content design) and want to understand why knowledge systems break down even when individual contributors are doing their jobs well

You don’t need a background in knowledge management. You do need to care about whether knowledge stays usable over time.

How Is The Living Knowledge System Organized?

The series is organized into five sections, each corresponding to a layer of the mental model diagram above.

• The System introduces the full model in detail: what each layer means, how the pieces connect, and why companies with mature documentation pipelines can still have broken knowledge systems
• The Knowledge Tiers articles discuss ephemeral, versioned, and evergreen knowledge types — how each tier behaves, where investment goes, and where it doesn’t
• The Knowledge Flows articles examine upstream and downstream knowledge movement. Why documentation enters too late to capture the context that matters most, and why downstream signals rarely find their way back into content
• The Knowledge Audiences articles discuss each audience the knowledge system serves (product, Design/UX, engineers, QA, customer support, customer success, end users, content owners) what each needs, and where the system typically fails them
• The Knowledge Infrastructure articles cover the DDLC, the architectural layer that designs the knowledge system, the operations infrastructure that implements it, and documentation engineering as the discipline spanning both.

Articles can be read in sequence or by section. The mental model diagram is the fastest way to orient before diving in.

What This Series Does Not Cover

This series does not cover:

• Knowledge management as an enterprise discipline or organizational practice
• Specific tooling recommendations or platform comparisons

Where to Start

If you’re new to this series, start with The Knowledge System in Software Companies — the written companion to the mental model diagram. It covers the full system in prose and sets up everything that follows.

If you already have a specific question in mind, go directly to the relevant section:

• Questions about knowledge types →The Knowledge Tiers
• Questions about where knowledge gets lost → The Knowledge Flows
• Questions about who the system serves → The Knowledge Audiences
• Questions about how the system gets designed and run → The Knowledge Infrastructure

How This Series Relates to the Rest of The Doc Landscape

The Living Knowledge System is the foundational series on this platform. It maps the system that documentation operates within — the full lifecycle of product knowledge, from the moment it’s created to the moment it’s retired or lost.

The other series on this platform focus on different layers of that system. Writing craft and foundational documentation principles live in Technical Writing Best Practices. Documenting AI products and features specifically lives in Writing About AI. Writing and structuring documentation so AI search and retrieval systems can surface it reliably lives in Writing for Retrieval. Exploratory thinking, observations, and reflection on how documentation work is changing live in Reflections.