🛸 Hitchhiker's Guide — Phase 12: Collaboration, EBOM & Staff Leadership
Read this if: you can build the systems but the "Staff" parts — EBOM, specs, ADRs, runbooks, mentoring a distributed team — feel fuzzy. Compressed map of the artifacts that are the job.
0. The 30-second mental model
In a distributed, multi-site, ODM-partnered program, your artifacts (EBOM, interface specs, ADRs, runbooks) and your writing ARE the engineering — they create the shared understanding that lets two continents build one thing. Staff = leverage over output: multiply the team through standards, reviews, docs, decisions, and mentorship, while staying hands-on and execution-focused.
1. Software EBOM (the ODM contract)
versioned inventory of what runs on a node/rack + interfaces: firmware baselines (P08), software + compat matrix (P11), Redfish/IPMI/SNMP interfaces + OEM deltas (P03), config baselines (secure boot/ VLAN — P09), provenance. Commissioning reconciles discovered vs EBOM (P01); drift = a defect.
2. Interface spec (build-to-it-without-you)
name the standard + deltas (resources, OEM ext, sensor names/units, AllowableValues) · specify behavior (state machines, error semantics, idempotency, timing) · make it testable with a conformance suite (P11 — tests don't drift, prose does) · version it · owner + defect loop + upstream (OpenBMC, P04).
3. Design review + ADR
Review on: feasibility · performance · reliability · maintainability (+ security P02/09, operability P07). Ask: how does it fail? testable without HW (the seam, P11)? blast radius (P01)? rollback (P11)? Separate must-fix from opinion; critique the design, bring alternatives. ADR = context · decision · alternatives · consequences (incl. accepted downsides).
4. Runbook
trigger (alert/symptom, P07) → goal → precise checklist (commands + expected output + "if X then Y") → risk bounds (pre-checks, blast radius, dry-run/confirm P04, rollback P11) → links (dashboard/ADR/ escalation). Source = RCAs (P10). Progression: manual → runbook → automated → self-healing (P06).
5. Distributed-team comms (async-first)
lead with the decision/ask → context · decision + consequence + honest limit · self-contained (understandable without the meeting) · durable decisions in docs/ADRs not chat · respect timezones, minimize synchronous, rotate the painful hour.
6. Senior → Staff
scope: features → outcomes across an area · leverage > personal commits · drive implementation of a defined design (break down, sequence, de-risk seams P03/04, keep the distributed team aligned, own the debugging P10) · mentor deliberately · influence without authority (reasoning + data + prototypes) · know the role: ambitious execution, collaborative on direction.
7. STAR (behavioral)
Situation · Task · Action (you, specific) · Result (quantified + learning). Prep 5–6: hardest bug/RCA (P10), cross-team/ODM delivery, an incident prevented from recurring, mentoring, a review disagreement, a tradeoff under constraints. Avoid vague "we" and unquantified results.
8. The "done this before" tells
"Is that in the EBOM?" · "Is the spec testable — where's the conformance suite?" · "Is there an ADR for that?" · "Where's the runbook?" · "Did you write the decision down or was it just a call?" · "How are you growing the juniors?"
9. How this phase pays off later
It IS the Staff bar the interview probes (interview-prep/05). EBOM/specs gate Phases 01/03/08;
ADRs document the whole curriculum's decisions; runbooks come from Phase 10; the capstone (Phase 13)
ships with a design doc + runbook + retro produced exactly this way.