Teklens logo
DEEN
Back to the Playbook
DefinePlanningDE-08

Review architecture impact

Identify the architectural consequences, blast radius and key technical decisions of a change before implementation begins, including security and compliance questions.

Product statusAvailable now

Context in4 required inputsPRD or story · Codebase · Architecture context
TransformationArchitect + Architecture AgentCode Analysis · Local Files · Atlassian
OutcomeArchitecture impact assessment with blast radius and recommended decisions.Artifact: Architecture Decision Record

Owner

Architect

Human + Agent

Participants · Agents

EngineerProduct ManagerArchitecture Agent

Trigger

Event-drivenA feature touches shared architecture, the data model, integrations, security-relevant or high-risk code.

Required context

JiraPRD or storyCodeCodebaseArchitectureArchitecture contextArchitectureAffected systems and data flows

Optional context

ArchitectureExisting ADRsFilesNon-functional requirementsFilesCompliance and data-protection rules

Skills

Code AnalysisLocal FilesAtlassian

Methods used inside this Activity: Blast-radius analysis · Architecture Decision Records · Shift-left security and compliance questions

Activity steps

  1. 1Map affected components, APIs and tests: the blast radius.
  2. 2Identify constraints, dependencies and data flows.
  3. 3Surface design choices, risks and compliance questions.
  4. 4Recommend decisions or spikes and record durable decisions.

Output

Architecture impact assessment with blast radius and recommended decisions.

Artifacts

Creates: Architecture Decision Record

Updates: Architecture context

What good looks like

  • Grounded in current code.
  • Alternatives and trade-offs are visible.
  • Security and data-protection questions are raised before build.
  • Consequential decisions are recorded as ADRs.

Quality gate

Architect or engineering lead approves consequential decisions.

Destination

ConfluenceJiraProduct 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