Skip to content Feature Vertex Hub

Briefings

The meeting is for the decision, not for a first look at the table.

A Feature Vertex Hub briefing lasts seventy-five minutes. The memo is sent at least a day before. People who have not read it are asked to use the first minutes in silence rather than to be talked through every chart.

Colleagues seated along a conference table during a briefing
In Johor Bahru we use a quiet table. By video we still keep the same clock.

Who should be there

  • The product manager who owns the flag
  • One engineer who can speak to assignment and known bugs
  • Someone with authority to refuse a ship — often a design lead or a group product manager
  • The analyst who pulled the table, if that person is not already in the room as one of the above

More than eight people turns the briefing into a town hall. Extra attendees can receive the memo and the decision slip without sitting in.

Where

In person at Bang Mara,Johor Bahru,Johor,80000,Malaysia, or by video. We do not brief from a noisy open floor if we can help it; if your office cannot offer a room, video is kinder to the original question.

What to send five days before

  • The hypothesis in the wording used at launch
  • Variant descriptions, including screenshots
  • Assignment rule, start and stop dates, sample sizes
  • Primary metric and guardrail definitions
  • Results table for that window
  • A note on peeking, campaigns, outages, or bugs

If that pack is thin, we postpone rather than invent. Read how to pack an experiment folder.

Clock

Seventy-five minutes

0:00–0:10
Silence for anyone who has not finished the memo. The hypothesis is read aloud in the original words.
0:10–0:25
Who qualified, who was excluded, and whether assignment still means what the brief said.
0:25–0:45
Primary result with size, then guardrails. Peeking and festive or campaign weeks sit here, not in a footnote.
0:45–0:60
Declared segments only. Undeclared slices are parked as questions.
0:60–0:75
Ship, iterate, or stop is written on the decision slip, with an owner for the next step. New hypotheses go to a later design, not onto this slip.

What we will not reopen

Once the slip is signed, we do not reopen the same experiment because a later chart looked friendlier. A new window, a repaired assignment, or a different hypothesis is a new engagement. The flagship readout includes this briefing. Workshops use a shorter clock per experiment; see squad readout workshop.

Hold a date

Send the experiment name and a window the product manager can attend. We confirm after the pack is readable. Fees are on the rates page.

Request a briefing date