a16zTesla and SpaceX Alumni on Elon Musk, Decision Velocity, and the Future of Hard Tech | a16z
CHAPTERS
From SpaceX/Tesla to startups: Galadyne missile propulsion and Mariana minerals
Erin Price-Wright introduces Chandler Luzsicza (ex-SpaceX Starship propulsion) and Turner Caldwell (ex-Tesla battery/minerals). They share the origin stories behind their new companies and the industry gaps they’re targeting in defense propulsion and critical minerals infrastructure.
- •Galadyne’s thesis: missiles are too expensive, too slow to build, and produced in insufficient quantity
- •Mariana’s thesis: minerals/refining/mining are software-deficient with shrinking talent pools
- •Applying autonomy and orchestration software to heavy industry operations
- •Why both founders saw old, conservative incumbents as an opening for new entrants
The core transferable lesson: flat orgs + fast, high-conviction decisions
They argue that the “flat org” myth is really about maximizing information flow and collaboration. Decision velocity—making informed bets quickly, then iterating—is described as the practical edge that lets hardware teams move faster without paralyzing junior engineers.
- •Flat orgs work when they democratize access to decision-makers and context
- •Decision velocity reduces hesitation and de-risks execution for junior engineers
- •You can’t wait for perfect information; you learn whether decisions were right after acting
- •Speed + execution excellence as the operating mantra
Avoiding silos at scale: building a shared data backbone for execution
Turner explains that coordination across large groups is often harder than the technical problems themselves. Mariana is built around eliminating data silos by making engineering and project context broadly accessible, with decision history tracked and queryable.
- •Misalignment and churn appear as teams grow past ~100 people
- •Default behavior creates data silos even when leadership discourages them
- •Web-hosted systems with minimal internal access controls to democratize context
- •Track “why” behind decisions; use LLMs to navigate institutional knowledge
Critical path as a daily discipline (and the ‘second-grade soccer’ trap)
Chandler emphasizes “chasing critical path” as the schedule-driving habit learned at SpaceX. They discuss how to swarm on the blocker without accidentally starving the next set of work, using focused owners and parallel “SWAT teams.”
- •Critical path = the task/procurement item driving schedule to the next milestone
- •Early-stage startups may have a single dominant critical path, but it evolves quickly
- •Avoid everyone swarming the hottest fire (“second-grade soccer”)
- •Use small, independent teams to attack blockers in parallel while keeping other work moving
Execution rhythms that scale: high-signal email updates, passdowns, and drumbeats
Both founders advocate for written, high-cadence updates as a forcing function for clarity and accountability. Turner extends this into “shift passdowns” and company-wide cadence (“drumbeat”) to keep flat orgs aligned over long hardware timelines.
- •High-signal, low-noise email updates especially for critical-path work
- •Writing clarifies thinking and reveals whether real progress happened
- •Manufacturing-style ‘passdowns’: planned vs done vs why not done
- •Set a company cadence to align teams and celebrate intermediate wins in 12–18 month cycles
Aggressive milestones (‘Elon time’) as a forcing function to find what matters
They describe setting ambitious timelines not as performative pressure, but as a tool to surface priorities. Unrealistic timelines force teams to identify the true non-compressible constraints—then either attack or delete them.
- •Set ambitious schedules, then negotiate feasibility early with the doers
- •Aggressive targets expose the subset of tasks that truly can’t fit the timeframe
- •Prioritization includes deletion: cut requirements/features that don’t serve the goal
- •Technical credibility in leadership helps set ‘hard but achievable’ milestones
All-nighters without burnout: mission alignment, progress, and eliminating churn
They reframe intensity as sustainable when people are aligned to the mission and feel momentum. Burnout is attributed less to hours and more to churn—politics, erratic priorities, and ‘hoarding Legos’—which drains energy and slows progress.
- •Strong mission alignment makes hard pushes feel meaningful rather than punishing
- •Burnout driver #1: churn and lack of visible progress
- •Burnout driver #2: politics, silos, and resource hoarding
- •Goals must be aggressive but within technical reach to motivate instead of demoralize
Factory mindset in practice: simplifying requirements to speed iteration (Starship example)
Chandler explains how Starship iteration balanced complexity and production by aggressively questioning requirements. By removing “stupid” requirements and reusing existing hardware, teams reduced bespoke design and accelerated manufacturing readiness.
- •Factory mindset starts upstream: simplify requirements to enable simple designs
- •Simple designs are faster, cheaper, and easier to produce
- •Example: reusing Booster hardware on Ship by quickly testing a valve/liquid concern
- •Information access across teams enables reuse and avoids redundant design cycles
Treating refineries and construction like products: takt time, modularization, and measurement
Turner describes applying manufacturing discipline to infrastructure projects like refineries and mines. The key is breaking work into modular, measurable steps, capturing site data, and managing labor/material/equipment allocation algorithmically.
- •Design refineries/projects as modular systems that can be fabricated offsite
- •Use takt time analysis to quantify discrete steps across labs, construction, and operations
- •Construction often lacks quantified short-interval control compared to manufacturing
- •Automated progress capture (e.g., 3D scans/robot surveys) enables dashboard-driven execution
Vertical integration, demystified: when it’s strategic vs naive
They argue vertical integration should be a strategic response to existential constraints, not an identity. The decision hinges on whether the company can exist without integrating a component, factoring in risk transfer and upstream supply-chain complexity.
- •Avoid ‘vertical integration for its own sake’; it’s expensive and operationally hard
- •Integrate the bottlenecks that block schedule/scale (e.g., key weldments for Galadyne)
- •Binary test: does the company exist if we don’t integrate this?
- •Vertical integration shifts supplier risk onto you and expands upstream dependencies
Why Tesla/SpaceX produce elite talent: deep technical screening + internships as trials
They explain that hiring quality comes from rigorous technical evaluation and multiple engineering interviews. Chandler highlights internships as a powerful conversion funnel—a real-world, months-long audition that reliably identifies high performers.
- •Multiple technical interviews and tests validate real problem-solving ability
- •Rigorous hiring is a feature: it signals talent density and filters for motivated candidates
- •Intern programs act as extended trials; many critical contributors are intern conversions
- •Early-stage startups replicate rigor while balancing candidate experience without a big brand
Advice to young engineers: get reps end-to-end, then take the founder leap
They recommend staying long enough in a high-talent environment to see multiple projects through full lifecycle execution. The goal is to build deep technical credibility before layering on fundraising, hiring, and company-building—skills you’ll inevitably learn on the job.
- •Optimize early career for learning rate and exposure to exceptional teams
- •See projects end-to-end multiple times to build execution intuition
- •Credibility helps attract talent and set realistic-but-aggressive targets as a founder
- •You’ll never feel fully ready—so over-index on technical foundation first
