Teklens logo
DEEN
Back to the Playbook
OperateLearningOP-07

Improve Product Playbook

Turn repeated learnings about how the team works into an approved change to an Activity, a Skill or a rule, so the Playbook itself learns.

Product statusAssisted workflowActivities and Skills are configured together with Teklens during onboarding; the change is applied by the Teklens team.

Context in3 required inputsCurrent Activity or Skill definition · Evidence of the repeated issue · Examples of desired behaviour
TransformationProduct Ops + Product AgentLocal Files · Atlassian
OutcomeApproved Playbook change.Artifact: Playbook Activity

Why it matters

The Playbook is not a static process diagram. Retro findings and accepted agent suggestions become versioned changes to the Activities and Skills the team runs.

Owner

Product Ops

Human-led

Participants · Agents

Head of ProductEngineerProduct Agent

Trigger

Agent-suggestedA repeated retro finding, a recurring correction, a strong accepted agent suggestion, or a process change.

Required context

Product BrainCurrent Activity or Skill definitionJiraEvidence of the repeated issueFilesExamples of desired behaviour

Optional context

FilesAgent run historyFilesAccepted and rejected draftsFilesTeam feedback

Skills

Local FilesAtlassian

Activity steps

  1. 1Identify the repeated pattern.
  2. 2Propose the change to the Activity, Skill or check.
  3. 3Test it against real examples.
  4. 4Review and publish the new version.

Output

Approved Playbook change.

Artifacts

Updates: Playbook Activity

What good looks like

  • Based on repeat evidence, not one anecdote.
  • The change is specific and testable.
  • An owner is defined.
  • The old version stays traceable.

Quality gate

The Playbook owner approves the change.

Destination

Teklens onlyProduct Brain

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.

Deep dives from the AI PM Lab

Articles that explain the thinking behind this Activity.

Show us exactly how product work happens today.

Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.

Book a demoBack to the Playbook