Back to the Playbook
Strategy & DiscoveryDefine & DesignSD-12

How to write a feature brief

Answer whether the opportunity deserves exploration without prematurely prescribing requirements or implementation.

Product statusAvailable now

Input3 required inputsCustomer problem evidence and affected segment · Opportunity size and business goals · Initiative focus and approved Product Brain guidance
SkillsDraft a feature investment brief · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeFeature brief: problem and audience, opportunity and value, approach, risks and success signals, and the requested decision.Artifact: Feature brief

Owner

Product Manager

Human + Agent

Participants · Agents

Head of ProductResearcherProduct Manager Agent

Trigger

ManualA product opportunity needs investment alignment.

Required context

Customer evidenceCustomer problem evidence and affected segmentProduct BrainOpportunity size and business goalsProduct BrainInitiative focus and approved Product Brain guidance

Optional context

CodeCurrent product behaviourArchitectureConstraints and alternatives

Skills

Draft a feature investment briefPrepare task contextReview an artifact against agreed criteria

Suggested conversation arc

  1. 1Clarify the opportunityIdentify the user problem, segment and why it matters now. Separate facts from a favoured solution and clarify the investment decision needed.Skills: Prepare task context
  2. 2Draft the feature briefWrite a concise problem, opportunity, business case, high-level direction, risks and success criteria. Quantify only where evidence supports it.Skills: Draft a feature investment brief
  3. 3Challenge the case and risksTest the connection to strategy, strength of customer evidence and top assumptions; identify what could reverse the recommendation.Skills: Review an artifact against agreed criteria
  4. 4Agree the next investmentConfirm explore, proceed, revise or stop, with rationale and unresolved questions. Keep approval of a brief distinct from approval of every later requirement.

Output

Feature brief: problem and audience, opportunity and value, approach, risks and success signals, and the requested decision.

Artifacts

Creates: Feature brief

What good looks like

  • The brief explains why to invest rather than prescribing implementation.
  • Opportunity claims distinguish evidence, estimates and unknowns.
  • No invented commercial impact and no implied approval.

Quality gate

Product leadership decides: explore, proceed, revise or stop.

Destination

ConfluenceProduct 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.

Choose the path that matches your role.

Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.