APAC Launch

Committed Mar 31, 2027

APAC Launch run by Maya Chen owned by D. Okafor

Committed decisions

what everyone carries forward

Pipeline readiness

owned by R. Delgado · Sales

“Pipeline is ready for a Mar 12 start — sequencing, quota, and the two enterprise holdouts are all handled.”

Committed Mar 12

Partner motion

owned by J. Kaur · Sales

Committed Mar 14

Platform v2 dependency

owned by Priya T. · Engineering · carries the condition below

Committed Apr 2

Open condition

on the record, in their words

Condition · Data migration

“Migration can't start until Platform v2 lands. If that's the 31st, this is April.”

Set by G. Tan · Engineering — one condition, bound to every place it touches. One check-in and one answer reach all of them.

Bound to

Committed decision 03 · Platform v2 dependency

The Apr 2 committed date for Data migration

The Q1 review check-in (below)

Shown here because it lands on this record — nothing about it is pending on you, and it will not change unless someone opens a new round.

Accepted risks

named, and taken on with eyes open

Platform v2 slip pushes APAC to April

named by G. Tan in the framing round · accepted into the plan by D. Okafor

Accepted

Coming up

the scheduled revisit — a date, not a deadline

Q1 review — scheduled Jun 30, 2027.

The plan is revisited on its own schedule. If anything is decided before then, it opens a new round — this record stays exactly as it is.

How this got decided

No loops. One bottleneck — Platform v2 — carried into the condition above rather than left unowned. The map is the residue of how this actually got decided.

Open the map →

Changes are new rounds — everyone carries forward. This record is committed and won't change. To adjust anything, open a new round — everyone carries forward with it, and it stays connected to this record.