Teams often default to 90-day timelines because it fits the quarterly business calendar, not because it's the actual time required. By simply asking 'How is it that every problem can be solved in exactly 90 days?', leaders can force more first-principles thinking about project scoping.

CEO Dylan Field combats organizational slowness by interrogating project timelines. He seeks to understand the underlying assumptions and separate actual work from "well-intentionally added" padding. This forces teams to reason from first principles and justify the true time required, preventing unnecessary delays.

When a team presents a timeline that feels instinctively too long, trust that gut feeling. It likely signals an over-engineered solution. Complex systems never become simple; they only breed more complexity, causing timelines to expand endlessly. It's better to reset the team or the approach early on.

In a competitive market, prioritizing speed forces a team to be resourceful and figure out how to maintain quality under pressure. This mindset prevents the design team from becoming a bottleneck and keeps the company's momentum high.

Jensen's "Speed of Light" principle sets the only benchmark for project speed as the absolute theoretical maximum, constrained only by physics. Teams are judged against this ideal, not against their own past performance or competitors, forcing them to eliminate all delays and downtime.

Jensen Huang demands to know the absolute fastest possible production timeline, the "speed of light," irrespective of the initial astronomical cost. This forces suppliers to reveal their true physical limits, providing a powerful strategic baseline for decision-making beyond conventional quotes.

Returning founder Jamie Siminoff cut an 18-month hardware development cycle to under 7 months. He did this by challenging the "why" behind every process step and eliminating generous time buffers, arguing that excess time guarantees that delays will fill it.

The "SOL" framework at NVIDIA isn't just a top-down executive command to "get the bullshit out." It's a cultural tool used by frontline engineers to challenge assumptions and push for a root-cause, physics-based understanding of timelines and constraints on any project.

Instead of relying solely on internal timelines, create public-facing product events. This establishes an unmissable, external deadline that serves as a powerful forcing function, ensuring teams are aligned and deliver high-quality work on time.