Teklens logo
DEEN
Back to the Playbook
Product BrainFoundationPB-06

Onboard a team member

Give a new product manager or engineer the product's real context in days: objectives, decisions, the code behind each area and the people who know it.

Product statusAvailable now

Context in4 required inputsProduct objectives and vision · Recent decisions · Codebase and component map
TransformationHead of Product + Product Agent + Architecture AgentCode Analysis · Atlassian · Local Files · Find Code Owners
OutcomeOnboarding brief per product area with decisions, code map, owners and open questions.Artifact: Documentation

Why it matters

A new product manager needs around three months until the context is there, from conversations with teams. With a current Product Brain the context already exists; this Activity turns it into a guided tour instead of twenty open tabs.

Owner

Head of Product

Agent-led

Participants · Agents

Product ManagerEngineerProduct AgentArchitecture Agent

Trigger

ManualA new product manager, engineer or agent joins the team or takes over a product area.

Required context

Product BrainProduct objectives and visionProduct BrainRecent decisionsCodeCodebase and component mapJiraActive epics and roadmap

Optional context

Customer evidenceCustomer evidenceArchitectureArchitecture notesFilesTeam map and ownersProduct BrainProduct terminology

Skills

Code AnalysisAtlassianLocal FilesFind Code Owners

Activity steps

  1. 1Assemble the product overview: objectives, areas and terminology.
  2. 2Map each area to its code, its open epics and its owners.
  3. 3Summarise the decisions of the last months with their rationale.
  4. 4Answer the newcomer's questions from the Product Brain and record what was missing.

Output

Onboarding brief per product area with decisions, code map, owners and open questions.

Artifacts

Creates: Documentation

Updates: Product Brain

What good looks like

  • Every statement links to a source in Jira, the code or a decision.
  • Owners are named per area.
  • Terminology matches the product glossary.
  • Gaps found during onboarding flow back into the Product Brain.

Quality gate

The responsible lead reviews the brief before it is handed over.

Destination

Product BrainConfluenceTeklens only

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.

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