Big technical failures rarely begin with missing talent. They begin with somebody deciding it is safer to stay quiet.
When a team cannot surface an inconvenient technical truth early, it starts borrowing against a future incident.
I have seen versions of this pattern in startups, scale-ups, and larger organizations across different countries: the flaw is visible early, but the schedule is louder. Senior people tell themselves they are being pragmatic when they swallow the concern and "keep momentum." What they are really doing is financing a later crisis with interest. The cost just hides for a while in optimism, politeness, and deadline theater. The more pressure a team is under, the more valuable plain dissent becomes.
If your team cannot say "this will break" in time, velocity is already fake.