Brian's Order of Operations

Re-checked Oct 9, 2026 against live GitHub, the Q4 rocks, this week's PM syncs and every circle tracker. Ordered by what moves the Trust Layer SMART first: 1 rider follows someone for every 7 who create a route, in December (Dec 2025 was 20:1; stretch 5:1). A suggested order, not a committed plan.

The verdict

KEEPProfile first, social on top

Still right. Every follow surface lands on the profile, and Will's rollout gate (cohort + survey) is the only thing left before everyone gets it.

WATCHKelly is the bottleneck

Mobile profile is her #1 (Brian, Oct 12). Search design and the mobile follow-back card come after it; badging and cover pages wait until after December.

The big picture

1 · NOW (OCT)Close the follow loop

Kelly on the mobile profile first. Ship the web cards, follow emails and mobile privacy; roll the web profile out past admins; start search design.

3 · LATER (AFTER DEC)Deepen and recognize

"Rode with" matching, rider badging, partner cover pages, profile follow-up, and 3D once the Dec 1 read is in.

The projects

Click any project to see what it needs first, what it unlocks, and its sub-issues. Top to bottom within each lane.

Now

October

Later

After the December read

Context

Open a section for details.

Your open moves (6)
  • Follow emails: get ridewithgps#23983 on Jean's sprint. The new-follower email isn't sending today; that fix can ship alone.
  • Profile rollout gate: upload the v2 cohort (4,126 riders) to Iterable, review the survey, enroll the cohort (management#290).
  • Recommended riders: pick the ship order (route makers first is the pick here), confirm Henry on the pairs table (Macon leads #89), approve the breakdown on management#89.
  • Pin privacy PR: ask William why ridewithgps#23972 is on HOLD.
  • Android search: keep or clear your assignment on RWGPS-Android#9219.
  • Follow metric: attempts or successful follows, by Nov 30 (reminder Nov 16). Also decides whether org follows count toward 7:1.
Timeline to December
Oct 9 · todayMatt reviewing the two web follow PRs
Oct 12Zack and Cullen assign engineers
Oct 14All-hands
~Oct 21Q4 roadmap presentation
Mid-NovLast ship date that still moves December
Nov 30Follow metric defined
DecSMART measured; 3D read Dec 1
What changed since the Sep 28 version
  • Q3 profile target slipped. Web profile is on prod for admins only; full rollout waits on the feedback cohort (Will, Oct 6).
  • Follows privacy shipped on web Oct 6 (management#257). Mobile is in PRs; phase 3 is dropped.
  • Recommended riders' backend is not "mostly built." Route scores exist; ride matching (the pairs table) doesn't exist anywhere. Dev cost likely L, not M.
  • Search moved into code repos, 9 issues under management#209. Kelly picked up the design Oct 8.
  • Designers set for every rock item; Kelly added on Follow orgs (#177) and search design (#24197).
  • Trust Layer SMART written: 7:1, stretch 5:1, counter-metric blocks + reports at or under 20 per 1,000 new follows.
  • 3D is off the table until the Dec 1 read (upsells still edging down). Google 3D button shipped Oct 8.
  • Oct 8 decision: followers of private profiles stay out of search and recommendations.
Other people's work this touches
  • Home page (management#252, Carl): where recommended riders and people search land. Requirements with Kelly and Macon.
  • Receiving users (management#240, Will): "follow whoever sent it" also adds follows toward your 7:1.
  • Privacy code leaks (ridewithgps#24063, Jean): side track, keep an eye on it.
Parked (not in this plan)