Huge's Living PRDs: A global agency's ProductOS for winning time, trust & $10M

Explore

Huge's Living PRDs: A global agency's ProductOS for winning time, trust & $10M

Huge's Living PRDs: A global agency's ProductOS for winning time, trust & $10M

Epics

Epic Requirements Template

Starter template for a new epic

Background

The circumstances surrounding the creation of this creative brief:

Business context

Product system context

Other dependencies

Objective

The purpose of this creative brief (1-2 sentences)

Problems

Add bullet points here to lay out the core problems product design needs to solve for, including both use cases for the feature and accompanying difficulties that might come with traditional solutions.

Traditional behavioral framing can be helpful here:

[Persona] needs to [action] in order to [result].

Example:

Prospective clients need to see a digestible menu of all solutions TimeTable provides in order to scan for one that matches their needs.

Requirements

Bullet out the business, product, or technical constraints here. This section should include far fewer bullets than the Problems section above and should be limited to hard limitations.

Example:

Autocompletion of search terms won’t be available until two characters are entered.

Filter the table below to the Epic entry that matches the focus of this brief, then adjust components as needed.

[Components in this Epic]

[Components in this Epic]

Component

Component type

Design Sprint

Stage

🔗

Dev Sprint

Notes

Accordion block

Content

Design Sprint 1

Development

Huge Design System - Document

Dev Sprint 1

Text + media

Content

Design Sprint 1

Development

Huge Design System - Document

Dev Sprint 2

Rich media

Content

Design Sprint 1

Development

Huge Design System - Document

Dev Sprint 1

Rich text block

Content

Design Sprint 2

Development

Huge Design System - Document

Dev Sprint 2

Share pop out menu

CTA

Design Sprint 3

Designing

Huge Design System - Document

Dev Sprint 5

Prototypes & Whiteboarding

Embed whiteboards here, to show the rough approach that has been discussed across design, product, and tech so far.

Sample Data

Provide the design team with text, numbers, or other information they might need to create a reasonable mock-up of key states within the scope of this brief.

References and Beacons

Add inspirational images that the design team can refer to here. These can be screenshots, pieces of UX, links, or even visual ideas. This is a collaborative section across the ticket writer and design.