Moving fast in hardware: lessons from lab to $100M ARR
This article, penned by ClearMotion's co-founder, champions Colin Chapman's "simplify, then add lightness" philosophy for accelerated hardware development, citing examples from Apollo to SpaceX. However, Hacker News commentators quickly questioned the narrative, pointing out potential survivorship bias and the author's company's lengthy, capital-intensive journey. This critical reception highlights HN's penchant for scrutinizing entrepreneurial success stories and exposing the often-unseen complexities behind "moving fast" in hard tech.
The Lowdown
Zack Anderson, co-founder of ClearMotion, presents a strategic framework for rapid hardware development, echoing Colin Chapman's famous maxim, "simplify, then add lightness." He argues that true speed in hardware innovation comes not from heroic efforts but from systematically reducing the "mass of the learning loop" across the entire development process.
Key lessons and examples presented in the article include:
- Relentless Requirement Subtraction: The fastest teams rigorously question and eliminate unnecessary requirements. Examples include ClearMotion's focus on actual driving profiles to simplify active suspension, Apollo's lunar-orbit rendezvous to avoid landing an entire spacecraft, and SpaceX's use of commercial components with software redundancy over expensive space-grade parts. The Gossamer Condor's disposable design prioritized rapid iteration over initial structural durability.
- Sequential Risk Retirement: New hard technologies should be developed through a sequence of experiments, each designed to retire the next most significant risk. Boom Supersonic's XB-1 demonstrator validated specific technical unknowns before committing to the full-scale Overture. Tesla's master plan sequentially addressed market risks from desirability to high-volume manufacturing. Conversely, Lilliputian Systems failed by trying to solve too many complex problems simultaneously.
- Insource Uncertainty, Outsource Commodity: Companies should bring core, uncertain manufacturing processes in-house to accelerate learning, while outsourcing mature, well-characterized components. ClearMotion learned this by building its first production line internally. The Sidewinder missile's success was attributed to keeping design, fabrication, and testing tightly co-located, fostering innovation from the shop floor.
- Software-Defined Hardware: Shifting performance and control from physical complexity into software can dramatically accelerate iteration. ClearMotion solved complex fluid system problems with advanced control strategies. Google's DeepMind optimized data center cooling with AI without new hardware. Tesla used over-the-air updates to adjust car ride height for safety. The Mars Curiosity Rover extended its life with a software-defined traction control algorithm.
- Aggressively Compress Physical Learning Loops: Minimize the physical and organizational distance between engineers and the product's physical reality (build, test, production). Toyota's production system emphasizes direct observation, and Elon Musk's presence on the Model 3 production line reflected this. ClearMotion brought machining capabilities in-house for same-day iteration, echoing China's manufacturing density advantage.
- Organizational Lightness: Small teams reduce communication overhead and foster shared context, as exemplified by Lockheed Martin's Skunk Works. The author notes that ClearMotion's productivity dipped as the team grew beyond 30, and cautions against hiring those who don't believe in alternative, lighter ways of working.
In conclusion, the article argues that speed in hardware is achieved by strategically shedding
The Gossip
Survivorship Bias Scrutiny
Many commentators critically questioned the article's narrative as a classic case of "survivorship bias" or "post hoc revisionist marketing." They highlighted ClearMotion's long journey (17 years), substantial funding ($370M), and recent successes, suggesting that the company's path contradicts the implied "move fast" premise. The discussion centered on whether the presented lessons are universally applicable or merely a favorable interpretation of a particularly arduous, capital-intensive grind, arguing that the context of past innovations doesn't always translate to current constraints.
Defining 'Fast' in Hardware
Commenters debated the meaning of "moving fast" in hardware development, especially when contrasted with software. They noted the inherent long timelines and high costs of physical products, contrasting ClearMotion's multi-decade path to the article's implied rapid iteration. Questions also arose about the financial realities, such as how much of a hardware company's "ARR" (Annual Recurring Revenue) is truly recurring, given the typical sales cycles in industries like automotive.
Engineering Discipline and Documentation Dilemmas
A significant thread focused on the foundational elements of successful engineering, emphasizing good communication, robust documentation, and realistic, accountable milestones as critical for any project, hardware or software. Commenters pointed out that documentation often gets deprioritized when teams attempt to move quickly, leading to technical and organizational debt, and arguing that true discipline must be fostered from the top down.
Clarity and Credibility Critiques
Several comments criticized the article's writing style and perceived lack of clarity and transparency. Some found the narrative scattered, overly anecdotal, and verbose, struggling to understand the author's core message or even what his company (ClearMotion) specifically does. The use of rhetorical flourishes and perceived marketing-speak detracted from its credibility for some readers.