Capture work in‑flow, not doc sprints
Some teams are building knowledge bases by integrating weekly activities directly into operational systems instead of relying on separate documentation sprints, so learnings are captured as part of routine work. That approach treats documentation as a by‑product of tasks—pulling ownership, steps and decisions into the same tools people already use. (x.com)
More teams are trying to kill the separate “documentation sprint” and record decisions inside the work itself — in tickets, pull requests, project docs, and workflow steps. (x.com) The idea is simple: the same system that assigns work also stores who owned it, what changed, and why. Atlassian says Jira tracks work through statuses and transitions, while Confluence can embed that task context in the same flow. (atlassian.com 1) (atlassian.com 2) GitHub markets the same pattern from a developer angle. Its docs say teams can track ideas, bugs, and tasks in Issues, discuss them in issues and pull requests, and enforce ownership in pull requests with CODEOWNERS and branch rules. (docs.github.com 1) (docs.github.com 2) (docs.github.com 3) The shift comes after years of teams treating documentation as a cleanup job at the end of a sprint or quarter. Microsoft’s Azure Boards guide still describes sprints as time-boxed planning units, but the newer tooling market increasingly ties notes and decisions to the work item instead of a later recap. (learn.microsoft.com) (linear.app) That changes what a knowledge base is supposed to do. Instead of a separate wiki that goes stale, vendors now pitch a running record built from active tasks, linked documents, comments, and automations inside one workspace. (notion.com) (notion.so) (linear.app) Slack frames the problem in operational terms: without centralized process documentation, workers repeat tasks, interrupt colleagues for answers, and recreate work that already exists. Its workflow documentation guide says teams now want process steps, owners, and updates available inside the workflow itself. (slack.com 1) (slack.com 2) Some products are going further by capturing the steps automatically. Tango says it can turn a user’s workflow into a formatted step-by-step guide, reducing the need for someone to stop and write instructions from scratch after the fact. (tango.ai) The tradeoff is that “captured in flow” only works if teams are disciplined about structure. GitHub’s planning docs stress labels, repositories, and issue organization, while Linear’s docs emphasize custom statuses, issue relations, and project-linked documents so the record stays searchable instead of turning into chat debris. (docs.github.com) (linear.app) (linear.app) That leaves the same old management question in a new place: not whether people should document work, but whether the system makes documentation the default output of doing the work. The teams pushing this model are betting that if the record is created during the task, there is no sprint left to postpone. (x.com)
