Back to the Playbook
Operate & LearnOL-05
Plan product deprecation and retirement
Separate discouraging new use from actual removal and preserve users’ ability to complete their work through the transition.
Product statusAssisted workflowTeklens plans and reviews the transition; notices, migration and removal are separately authorised actions by your team.
Input3 required inputsUsage, dependencies and affected audiences · Replacement options and data commitments · Initiative focus and approved Product Brain guidance
SkillsPlan deprecation and retirement · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeRetirement plan: decision and impact, deprecation, migration and removal timeline, transition guidance, and the completion review.Artifact: Retirement plan
Owner
Product Manager
Human-led
Participants · Agents
EngineerSales & SupportHead of ProductProduct Manager Agent
Trigger
A capability is proposed for deprecation or retirement.
Required context
AnalyticsUsage, dependencies and affected audiencesProduct BrainReplacement options and data commitmentsProduct BrainInitiative focus and approved Product Brain guidance
Optional context
CodeDependent integrations in the codeConfluenceSupport ownership
Skills
Plan deprecation and retirementPrepare task contextReview an artifact against agreed criteriaRecord decisions and follow-up
Suggested conversation arc
- 1Agree rationale and affected usersExplain why retirement is proposed, identify user needs that remain and map dependent people/integrations; surface transition constraints.Skills: Prepare task context
- 2Draft the transition planDistinguish deprecation and removal dates; describe migration paths, communication, support and retained information ownership with unresolved dependencies visible.Skills: Plan deprecation and retirement
- 3Review transition readinessCheck actual migration evidence, unresolved dependencies and support coverage before approving removal; do not mistake a planned notice for delivered communication.Skills: Review an artifact against agreed criteria
- 4Capture authorised transition evidenceObtain evidence of separately authorised notices, migration and removal or redirects. Confirm retained information ownership; do not execute retirement solely because the Activity is running.
- 5Confirm the final lifecycle recordReview what has truly been retired, what remains supported and who owns remaining obligations. Preserve a discoverable notice and explicit outstanding matters.Skills: Record decisions and follow-up
Output
Retirement plan: decision and impact, deprecation, migration and removal timeline, transition guidance, and the completion review.
Artifacts
Creates: Retirement plan
What good looks like
- Deprecation and removal are distinct and evidence-based.
- Completion requires transition evidence, not a drafted notice.
- No deletion, access change or external notice happens inside the Activity.
Quality gate
Product leadership approves removal only after the transition readiness review.
Destination
ConfluenceRelease channel
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.