“Our entire engineering team operating off the same shared context.”

What a product lead at a global bank asked for

Brief is how product teams get there.

JiraPCK-208

Add a pickup window picker to checkout

Let customers choose a pickup window. See design.

Not on the ticket

Which decision this follows
Why it works this way
Who it is for
What is still open

/onboard PCK-208returns the why, from Brief

Decision: Pickup reuses the account sign-in. No guest tokens.D-187
Why: Counter staff can’t verify guest orders.
User: A shift manager at the counter, reading the screen from arm’s length.
Code: checkout/pickup/, reusing auth/session.ts
Still open: Returns at pickup. No owner yet, so leave it out.Open

JIRA TO BRIEF The same Jira ticket, as written and as the engineer’s agent gets it after /onboard. Example data throughout.

Your loop works. The why leaks out of it twice.

Decisions get made all along the loop, in chat, in meetings, on whiteboards. Jira carries what and when. Brief carries why, so it survives every handoff.

Listen
1. The reasoning rarely gets captured
“Decisions get made in chat, in meetings, on whiteboards. That scattering is the problem.”
Consolidate
Split
Shape
Build
2. The why is out of reach at the keyboard
“A month later, oh well, we have to go and rebuild this.”
Lock scope
Validate
Demo
Release

Jira holds what and when

Brief holds why, from the first conversation to release

next cycle

Listen
1. The reasoning rarely gets captured
“Decisions get made in chat, in meetings, on whiteboards. That scattering is the problem.”
Consolidate
Split
Shape
Build
2. The why is out of reach at the keyboard
“A month later, oh well, we have to go and rebuild this.”
Lock scope
Validate
Demo
Release

next cycle

Jira holds what and when
Brief holds why, from the first conversation to release

THEIR LOOP A bank’s AI product team described its own loop, and the two places it breaks. Quotes are theirs.

“I walk over there like 10 times in a day to bother them with whatever thought I had in my head.”

A VP of AI product at a global bank, on walking the why over to engineering

Nobody should be
the transport layer

Today the PM carries the why from desk to desk and rewrites it for every audience. Brief does the carrying, so the PM keeps the judgment and gets the day back.

Time	What the PM walked over to say	How it reaches the team now
09:12	D-193Windows are two hours, not one.	/onboard on PCK-208
09:40	D-187Pickup needs the account sign-in.	Claude Code, before the auth change
10:25	D-195Stores set their own pickup hours.	/onboard on PCK-211
11:05	D-196Counter staff want the order ten minutes out.	The store session themes
13:30	D-197Build from Figma v3. v2 is retired.	Linked on every pickup ticket
16:20	OpenHold off on returns. It isn’t decided.	Flagged wherever it comes up

TimeWhat the PM walked over to say

How it reaches the team now

09:12
D-193Windows are two hours, not one.
/onboard on PCK-208
09:40
D-187Pickup needs the account sign-in.
Claude Code, before the auth change
10:25
D-195Stores set their own pickup hours.
/onboard on PCK-211
11:05
D-196Counter staff want the order ten minutes out.
The store session themes
13:30
D-197Build from Figma v3. v2 is retired.
Linked on every pickup ticket
16:20
OpenHold off on returns. It isn’t decided.
Flagged wherever it comes up

ONE PM, ONE DAY Six of the day’s desk visits, and where each answer reaches the team now.

Your digestTue, 5:30 PM

While you were in planning, the team made three calls on pickup.

Followed: Jamie built the window picker to D-193.
Followed: Cursor skipped a new animation library, per D-162.
Needs you: Returns at pickup came up twice. Still no owner.

DIGEST Judgment calls made while the PM was out.

Capture the why where it’s decided

Drop in the whiteboard photo and the session transcript. Brief pulls out the themes in your customers’ words and records what you decided, before anyone writes a ticket.

BriefSession record · Store pickup

Pickup session, Sep 9. Three themes from six customer quotes, and two decisions.

From whiteboard-sep9.jpg Session transcript, 48 min

1
See the order before the customer arrives
“If I can see it ten minutes out, the bag is on the counter.” Counter lead, store 112
2
Windows follow staffing, not opening hours
“Mornings we have one person. Don’t promise a 9am rush.” Shift manager, store 87
3
One ready message, not five
“Just tell me once that it’s ready.” Pickup customer, Austin

Recorded

D-193Two-hour pickup windows
D-195Stores set their own pickup hours

CUSTOMER SESSION A biweekly customer session, turned into themes and decisions in Brief.

Deliver it at the keyboard

When an agent is about to build against something the team decided, it reads the decision and changes course. Nobody has to sacrifice an engineer to keep the markdown files happy.

CursorBrief MCP · kestrel-web

> Add a confetti burst when a pickup order is ready

brief_ask “celebration animation, pickup ready screen”

D-162 · confirmed Aug 4 by Design · celebrations use the Kestrel motion kit, no new animation libraries

Skipping canvas-confetti. Using motion-kit/celebrate on the ready screen.

CURSOR An agent finds a design decision before it adds a dependency.

“The more time we spend taking engineers’ hands off keyboards to spend time in a focus group with us, it’s just time not building.”

A head of AI and digital product at a global bank

The user travels with the ticket

Your best engineers build well because they know the persona. Brief attaches the user, the quotes, and the reason to every ticket, so the rest of the team gets there without leaving the keyboard.

What have we agreed on?
What is still open?

Two questions a telco’s product leads ask after every team reshuffle. Whoever joins mid-launch asks Brief where they already work and gets both answers, with who decided and when.

#pickup-squadSlack

Priya Shah9:04 AM

@Brief first day on pickup. What did we agree on, and what’s still open?

Brief9:04 AM