# Content Lifecycle

The content lifecycle covers planning, creation, publication, maintenance, reuse, and retirement of content over time.

- Type: framework
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/content-lifecycle/>)

## What it means

The content lifecycle describes the stages through which material is managed from an identified need to eventual withdrawal or archival. It includes recurring review and reuse rather than ending at publication. Content design shapes usefulness; lifecycle management assigns the transitions, responsibilities, and triggers that keep that usefulness current.

## Why it matters

Accurate launch content can become misleading after product or policy changes. Treating maintenance and retirement as planned work prevents obsolete guidance from continuing to shape customer decisions.

## When to use it

Use lifecycle management for help centers, product documentation, onboarding, and service guidance. Scale review effort to change frequency and consequences of error. A fixed review date is useful but should not replace event-based updates when the product changes.

## How it works

1. Connect proposed content to a user need and assign an accountable owner.
2. Define review, approval, publication, and versioning responsibilities.
3. Set maintenance triggers based on product changes, feedback, and review dates.
4. Track reused copies and translations so updates propagate deliberately.
5. Retire or archive material with appropriate notices, redirects, and record handling.

## A practical example

A product team publishes a setup guide with an owner and a review trigger tied to authentication changes. When login behavior changes, the guide and translated help are updated together. The old guide is retired with a route to current instructions.

## Where it breaks

A lifecycle diagram is ineffective without capacity and decision rights. Distributed copies may drift, and public removal is different from records deletion. Processes that demand the same approvals for every edit can delay useful corrections.

## Common mistakes

- Considering publication the end of the work.
- Assigning review dates without an accountable owner.
- Retiring a page while leaving dependent links and translated copies live.

## Sources

1. [Web information and data lifecycle](<https://www.digital.govt.nz/standards-and-guidance/governance/managing-online-channels/web-information-and-data-lifecycle?rf=1>) — New Zealand Digital Government · Government guidance
2. [Manage existing GOV.UK content](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/plan-manage-content/manage-existing-govuk-content/>) — Government Digital Service · Government guidance

## Related topics

- [Content Design](<https://wiki.soroush.uk/topic/content-design/>)
- [Product Sunsetting](<https://wiki.soroush.uk/topic/product-sunsetting/>)
- [Responsible Product Management](<https://wiki.soroush.uk/topic/responsible-product-management/>)
