Teklens logo
DEEN
Back to the Playbook
DefineDefinitionDE-02

Prioritise opportunities

Rank competing opportunities by strategic fit, customer value, evidence, effort and risk, with effort grounded in the real code rather than gut feeling.

Product statusAvailable now

Context in5 required inputsCandidate opportunities · Product objectives · Customer evidence
TransformationProduct Manager + Product Agent + Architecture AgentAtlassian · Estimate Feature · Code Analysis · Local Files
OutcomeRanked opportunity list with decision rationale.Artifact: Roadmap

Why it matters

RICE, ICE, MoSCoW and Kano are methods inside this Activity, not separate Activities. What Teklens adds is the effort and risk side of every score: read from the code, with the dependencies named.

Owner

Product Manager

Human-led

Participants · Agents

EngineerHead of ProductProduct AgentArchitecture Agent

Trigger

ScheduledA roadmap or planning cycle, or material new opportunities.

Required context

Product BrainCandidate opportunitiesProduct BrainProduct objectivesCustomer evidenceCustomer evidenceJiraCurrent commitmentsCodeAffected code and dependencies

Optional context

ArchitectureEffort estimatesAnalyticsRevenue and segment dataCustomer evidenceKano or JTBD evidence

Skills

AtlassianEstimate FeatureCode AnalysisLocal Files

Methods used inside this Activity: RICE · ICE · MoSCoW · Kano · Weighted scoring · Impact × feasibility matrix · Strategic objective alignment · JTBD prioritisation

Activity steps

  1. 1Filter the candidates against the objectives.
  2. 2Choose the scoring method that fits the decision.
  3. 3Score consistently, with effort and risk read from the code.
  4. 4Challenge the assumptions and rank.
  5. 5Record the rationale and update the roadmap.

Output

Ranked opportunity list with decision rationale.

Artifacts

Updates: Roadmap, Product Brain

What good looks like

  • The method fits the decision.
  • Evidence and assumptions are visible.
  • Effort comes from the code, not from memory.
  • Strategic exceptions are documented.

Quality gate

Product leadership approves roadmap commitments.

Destination

RoadmapProduct BrainJira

Usually next

Method references: Intercom, RICE · Kano model · Ulwick, Jobs-to-be-Done

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