07 / 28 / 2026 · Manufacturing

Manufacturing Stand-Up

One topic today
TQ running · Wale co-leading

Today is about one thing: manufacturing tracking & process

We've reached the stage where operational rigor is the unlock — we can't optimize clock performance until the process underneath it is clean. Two outcomes for this meeting:

  1. Agree on one system for tracking every order.
  2. Lock in how we name parts and talk to vendors.

Why now

  • Part status is scattered across email, zip files, and vendor threads — which is causing naming drift, RFQ confusion, and near-missed holds with our fab partners.
  • Clean, consistent data isn't just tidiness — it's what lets our tools (and AI) actually help us track and search this work.
Two goals: one system · clean names
1 / 4 · scroll ↓
Mesa Quantum · Manufacturing Stand-Up

Order Tracking

From email chaos → one system

Source of truth
moving up the stack

We're moving order tracking off scattered email onto one living source of truth, and stepping it up the stack. Notion is optional — we may go straight from the sheet to the web app.

Retiring
Email + zip files
Status buried in threads; part numbers re-typed by hand.
Today
Google Sheet
Procurement Tracker — one live doc, one version. (Screen-sharing it now.)
Maybe
Notion
Structured, linked records — only if we can't get to the web app fast enough.
Target · this week
Supply Chain web app
Orders linked to parts, vendors & comms — the system we built.
supplychain.mesaquantum.com
… or skip Notion → straight to the web app
It's already working: the automated #vendor-ops channel flagged TTM's on-hold order yesterday within minutes — giving us time to respond instead of finding out days later. That's the payoff of structured tracking.
One doc now → web app by Friday
2 / 4
Mesa Quantum · Manufacturing Stand-Up

Wale's asks

Part numbers & vendor comms — lock it in

Same number, everywhere
every time
  1. Every new part in the registry gets a 1–2 sentence description in Notes — so anyone not on that part can tell what it is and why it exists.
  2. RFQs use the EXACT registry format: MQ2601-11903-V00-RevA02 — not MQ2601-11903, not ..._V00_revA0.
  3. Every external vendor message — and shared file name — carries the Part Number + Alt name + the product it goes into: MQ2601-11903-V00-RevA02 (MQC-02 Physics Card).
  4. One RFQ at a time. Never combine a PCBA assembly request with a PCB fab request — it becomes impossible to track across vendors.
Copy-paste the number. Every time.
3 / 4
Mesa Quantum · Manufacturing Stand-Up

This week

Owners & actions

Who owns each
— and by when
  • Curtis — clear all outstanding items in the tracker today.
  • Team — follow up with manufacturing partners tomorrow for status on open items.
  • BOM review owner — decide today: Brian preferred (adds a review gate before the BOM goes out); Nick continues near-term if needed.
  • Part number on every order — as a field in the tracker, so orders are searchable by part.
  • PARTS DB comments — initial context comment on each part + prominent variation/version notes (why A-01 vs A-00).
  • Parts / naming SOP — write it up and share with the team.
  • Supply Chain page — first version of web-based order tracking (linked to parts + vendor comms) by end of week.
  • Docs live on the part — every document tied to a part version (RFQ, quote, PO, fab drawing) gets attached to that part in the web app; no more digging through email.