Teklens logo
DEEN
Back to the Playbook
DiscoverOpportunityDI-01

Explore a product idea

Turn a vague idea or request into a clear problem, target user and discovery question, checked against what already exists in Jira and the code.

Product statusAvailable now

Context in4 required inputsThe original idea or request · Product objectives · Existing tickets and epics
TransformationProduct Manager + Product AgentStory Discovery · Atlassian · Code Analysis · Local Files
OutcomeStructured opportunity statement with a reuse-or-build recommendation and open questions.Artifact: Opportunity

Why it matters

Before another feature becomes another project: does something similar exist already, half-built, or decided against? The answer comes from tickets, decisions and the actual code, not from memory.

Owner

Product Manager

Human + Agent

Participants · Agents

Head of ProductProduct Agent

Trigger

ManualA new idea, a customer request or a vague feature concept.

Required context

FilesThe original idea or requestProduct BrainProduct objectivesJiraExisting tickets and epicsCodeRelated code and components

Optional context

Customer evidenceCustomer evidenceProduct BrainPrevious decisionsFilesCompetitor examples

Skills

Story DiscoveryAtlassianCode AnalysisLocal Files

Methods used inside this Activity: Opportunity framing (problem, user, evidence) · Reuse, extend, merge or build new

Activity steps

  1. 1Clarify the problem and the user behind the request.
  2. 2Check existing tickets, decisions and code: reuse, extend, merge or build new.
  3. 3Test the fit with the product objectives.
  4. 4Surface assumptions and define what must be learned next.

Output

Structured opportunity statement with a reuse-or-build recommendation and open questions.

Artifacts

Creates: Opportunity

What good looks like

  • The problem is separated from the solution.
  • The target user is explicit.
  • Existing functionality and duplicates are named, with the affected components.
  • Assumptions and unknowns are visible.

Quality gate

No human gate before the result is promoted. It stays an Activity result in Teklens until a person decides to use it.

Destination

Teklens onlyProduct BrainJira

Usually next

Method references: Torres, Continuous Discovery Habits · SVPG, Discovery – Delivery

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