Most teams ask, “When do you want it?” and then reverse-engineer hope. That is how commitments become roulette. The passage from This Is Lean reminds us that customer demand must be decomposed operationally: what we need, when we need it, and how much we need to deliver on time. In software, this means understanding dependencies, capacity, batch size, and lead-time distribution before committing to dates. Without that, teams start too late, overload the system, and call it urgency. Spoiler corporativo: urgency is not a strategy.
The Start Date Range concept gives Tech Managers a practical decision model. If you know today’s date, your lead time distribution, and the Desired Delivery Date, you can classify when work should start: super early, early, normal, late, or irresponsibly late. This is gold because it turns planning from opinion theater into probabilistic flow management. Instead of asking for heroic estimates, you ask: Based on our historical lead time, what is the last responsible moment to start while still protecting customer expectations?
Action plan: first, measure real lead time from commitment to delivery for each work type. Second, define Service Level Expectations, such as “85% of standard items complete within 10 days.” Third, classify demand by class of service: standard, fixed date, expedite, intangible. Fourth, during replenishment, compare each item’s desired delivery date with your lead-time distribution and decide whether to start now, defer, split, or reject. Fifth, expose this visually on the Kanban board: the desired date, the last responsible moment, the risk level, dependencies, and aging. No hidden magic, no Excel voodoo in the basement.
The result is a service truly tailored to the customer’s purpose. Customers get better conversations: “To hit this date with confidence, we need to start here, reduce scope, or change class of service.” Teams get less chaos, less overcommitment, and more sustainable flow. Stakeholders get transparency about trade-offs before the crisis. A Tech Manager using this model leads with evidence: manages start dates, protects flow, and delivers value when it actually matters.