Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

“DATE”: “Feature Name”

Participants

Document Status

DRAFT IN REVIEWREVIEWED

Deadline

Document Owner(s)

Reviewers

  •  
  •  
  •  
  •  

Table of Contents


🔍 Context

  • IREQ: [INSERT LINK]

  • FIGMA: [INSERT LINK]

  • Design plan document: [INSERT LINK]

  • Opportunity analysis document: [INSERT LINK]

🎯 Problem Statement

  • What is the problem that we are trying to solve?

  • Why is this a problem? (if possible include metrics and research findings)

  • Who is being impacted by this problem? (Ex: customers, users, etc)

❔ Expected Outcome

  • What is the overall goal of this feature?

  • Detail the changes on experience / flow

(blue star) Decision

  • Detail the different technical solutions that were considered

    • Option 1: details

      • Pros

      • Cons

    • Option 2: details

      • Pros

      • Cons

  • Detail the final chosen solution

Details to be included in each option:

  • Which app/ tool / product (s) is it affecting (ex: Whitelabel, Sanity, Admin/support tool, DOP, etc)

  • Will we use launch darkly flags?

    • Temporary/ Permanent

Option 1

Pros

(plus)

(plus)

Cons

(minus)

(minus)

Option 2

Pros

(plus)

(plus)

Cons

(minus)

(minus)

✅ Solution: Final decision

Consequences

  • Detail the pros & cons for the chosen decision.

  • Detail the potential impacts on other teams / products

(plus)

(plus)

(minus)

(minus)

  • No labels