---
tags: ["synthesis", "speed", "execution", "cadence"]
articles: ["a119", "a120", "a121", "a123", "a131"]
synthesis: true
id: "cross-speed-compressed-timelines"
sources: ["tail2"]
type: "synthesis"
sourceVaultSlug: "hbr-seg-tail2"
originDay: 2
articleStem: "hbr-seg-tail2"
sourceUrl: "(unified vault: 14 sources)"
sourceTitle: "HBR — Tail Ⅱ · Founders, PE, 2025 items, industry/security/ops (#118–131)"
---
## Everyone is racing the clock

Five articles treat *speed* as a primary competitive variable and prescribe mechanisms to compress the gap between decision and execution.

- **A119:** [[concept-smart-speed]] — test the hardest element first, resolve manufacturing risks in minutes not weeks ([[framework-rapid-risk-resolution]]).
- **A120:** [[concept-strategy-under-pressure]] — in PE, 'you make a decision, and the next meeting is about how you're implementing it'; the decision-to-implementation gap is near-zero.
- **A121:** agile operating rhythms and the [[framework-visual-operating-rhythm]] institutionalize cadence and push accountability down.
- **A123:** China's rapid catch-up ([[claim-chinese-ai-caught-up]]) is itself a speed story.
- **A131:** China's trials run ~50% faster ([[claim-chinese-trials-efficiency]]); the whole AMC prescription is about matching that clinical velocity.

## The connective logic

Speed is enabled differently in each: frugal engineering (A119), the finite hold period (A120/A121 — see [[prereq-pe-hold-period]] and [[prereq-value-creation-plan]]), vertical integration (A123/A131 — see [[cross-vertical-integration-as-weapon]]). But the shared claim is that *bureaucratic slowness is the enemy* and that speed is a designed capability, not a personality trait. The corpus's counterweight is [[cross-hustle-vs-recovery-tension]] and A119's own worry ([[question-scaling-hustle-culture]]): unmanaged speed becomes fatigue-linked error — and safety-critical domains (aerospace, drugs, national-security payloads) require rigor that pure 'fail fast' can erode.