development methodologies – How does Lean both “decide as late as possible” and “deliver as fast as possible”?


I’m learning about various software development methodologies, and reading about Lean hasn’t clarified what sounds like two contradictory principles:

  • Decide as late as possible
  • Deliver as fast as possible

The first one:

As software development is always associated with some uncertainty, better results should be achieved with a set-based or options-based approach, delaying decisions as much as possible until they can be made based on facts and not on uncertain assumptions and predictions. The more complex a system is, the more capacity for change should be built into it, thus enabling the delay of important and crucial commitments.

The second one:

In the era of rapid technology evolution, it is not the biggest that survives, but the fastest. The sooner the end product is delivered without major defects, the sooner feedback can be received, and incorporated into the next iteration. The shorter the iterations, the better the learning and communication within the team. With speed, decisions can be delayed. Speed assures the fulfilling of the customer’s present needs and not what they required yesterday. This gives them the opportunity to delay making up their minds about what they really require until they gain better knowledge. Customers value rapid delivery of a quality product.

From Wikipedia

How does an industry practising lean methods prioritise both deferring decisions until the full set of facts are established, and simultaneously rapidly delivering software?