Your supplier says the prototype will take twelve weeks. Your brand team says you have eight. One of them is wrong — but probably not the one you think.
Every product development program contains a negotiation about time. The brand needs the product faster. The supplier quotes a timeline that feels too long. The project manager splits the difference. And the resulting schedule — a political compromise between urgency and caution — is almost certainly both too long in some places and too short in others.
The problem is not that people are bad at estimating timelines. The problem is that most development schedules do not distinguish between the two fundamentally different kinds of time that make up every project: compressible time and floor time.
Floor Time vs. Compressible Time
Floor time is physics. It is the irreducible minimum duration of a process step that cannot be shortened by working harder, adding people, or running processes in parallel. When a material supplier receives your specification and begins producing trial samples, the polymer extrusion process takes the time it takes. The curing reaction runs at the speed chemistry dictates. The logistics carrier crosses the ocean at the speed the ship travels.
Compressible time is everything else. It is the organizational overhead that surrounds the floor-time processes: review cycles, approval queues, meeting schedules, email response times, document formatting, internal alignment discussions, holiday calendars, and the dead time between when one step finishes and the next step’s responsible person notices and begins.
In every product development timeline we have analyzed, compressible time accounts for roughly half of the total. This is not waste in the pejorative sense — some of it is necessary quality assurance, stakeholder alignment, and risk management. But it means that a twelve-week timeline contains only five to seven weeks of floor time. The remaining five to seven weeks are, at least in principle, compressible.
The reason most timelines feel simultaneously too long and too tight is that they compress in the wrong places. The brand pressures the supplier to shorten floor-time processes (“can you do the trial run in one week instead of two?”) while leaving compressible-time processes untouched (“we’ll review the samples at next Thursday’s product meeting”). The floor-time compression fails because physics does not negotiate. The compressible-time bloat persists because nobody identified it as the actual source of schedule fat.
The Floor-Time Calculation
To build a compressed timeline that is aggressive but achievable, you start by calculating the theoretical floor — the absolute minimum duration if every process step began the instant its predecessor completed, with zero organizational overhead.
For a typical hygiene product prototype development cycle involving material sourcing, sample production, and performance validation, the floor-time components stack roughly as follows:
Material specification and supplier identification is not floor time — it is preparatory work that should be completed before the clock starts. If you are starting material sourcing on Day 1 of the prototype timeline, you have already lost.
Material procurement — the supplier receiving your order, scheduling production, and shipping samples — is the first genuine floor-time block. For specialty nonwoven materials, this typically ranges from seven to fifteen working days depending on whether the material is a standard catalogue item or a custom specification.
Sample production — the converting partner receiving materials, setting up the production line, and producing trial units — is the second floor-time block. For hand-made prototypes, this can be as short as two to three days. For machine-produced trial runs, five to eight working days is typical, including line setup and teardown.
Performance testing — the laboratory receiving samples and completing the test protocol — is the third floor-time block. A basic performance characterization (absorption speed, rewet, capacity) takes one to two days. A comprehensive protocol including dynamic simulation, cumulative insult testing, and overnight simulation takes three to five days.
Logistics between steps — shipping materials to the converter, shipping samples to the laboratory, shipping validated prototypes to the brand — adds floor time that is geography-dependent. Domestic logistics within a manufacturing cluster might add one to two days per transfer. International shipping adds five to ten days per transfer — or one day if you use express courier, at a significant cost premium.
Sum the floor-time components and you get a theoretical minimum of three to five weeks. Compare this to the twelve-week timeline that most programs operate on, and the compression opportunity becomes visible.
Where the Compression Actually Lives
The gap between three-to-five-week floor time and twelve-week typical timeline is filled with compressible activities that accumulate in predictable patterns.
Sequential approval chains. A material sample arrives. It sits in a queue until the product manager reviews it. The product manager requests input from the quality team. The quality team adds it to their next weekly review cycle. The review produces a conditional approval that requires a follow-up question to the supplier. The question sits in an outbox until the next scheduled supplier call. Total time consumed: two to three weeks. Floor time consumed: zero.
Batch scheduling. The converting partner schedules trial runs in weekly or biweekly production windows. Your prototype request arrives on Tuesday; the next available window is the following Monday. You have lost five days to scheduling granularity, not to production physics.
Holiday and calendar gaps. Manufacturing regions have holiday calendars that differ from the brand’s calendar. A prototype timeline that spans a major holiday period — and most do, because product development programs always seem to coincide with holidays — can lose one to two weeks to calendar gaps that were not accounted for in the original schedule.
Specification iteration loops. The first sample does not meet the target specification. A revision is needed. But instead of specifying the revision immediately and sending it the same day, the team schedules a meeting to discuss the revision, produces a revised specification document, routes it for approval, and then sends it to the supplier — consuming one to two weeks of compressible time for a change that could have been communicated in a thirty-minute phone call.
Each of these compression opportunities, individually, saves three to five days. Stacked across a typical development program, they account for the entire gap between floor time and actual elapsed time.
The Parallel Processing Unlock
The most powerful compression technique is not doing things faster — it is doing them simultaneously.
In a default sequential timeline, material procurement finishes before sample production begins, which finishes before testing begins. Each step waits for the previous step to fully complete before starting.
But not every dependency is truly sequential. You can begin supplier qualification for your secondary material options while your primary material is being produced. You can ship the first batch of prototypes for testing while the second batch is still in production. You can conduct preliminary performance testing on pre-production material samples while the final production samples are in transit.
The key is mapping which dependencies are real (you cannot test a product that has not been produced) and which are organizational (you do not test until the full production batch arrives, because that is how the process has always been structured). Real dependencies are floor time. Organizational dependencies are compression opportunities.
The Decompression Trap
A counterintuitive risk in compressed timelines is what happens when the compression succeeds. The prototype arrives ahead of schedule. The testing is completed faster than expected. The team now has buffer time — and the almost universal response is to use that buffer for additional iteration, additional testing, additional review.
This is not wrong in principle. More iteration generally produces better products. But it means that the compressed timeline did not actually compress the total program duration — it compressed the floor-time phases and then re-expanded the compressible-time phases to fill the recovered space. The project finishes on the original twelve-week schedule, not the compressed eight-week schedule, because Parkinson’s Law operates at the organizational level just as reliably as it does at the individual level.
The discipline required to actually realize the schedule compression — to lock the end date based on the compressed plan and not allow recovered buffer to be consumed by additional process — is a management challenge, not an engineering challenge. And it is the reason that compressed timelines require explicit program management rather than informal acceleration of individual steps.
Building Your Floor-Time Map
The practical starting point is straightforward: for every step in your current development timeline, ask one question. “If I could start this step the instant the previous step finished, with zero waiting, and complete it as fast as physics allows, how many working days would it take?”
The sum of those answers is your floor time. Everything above that sum is compressible time — not all of which can be eliminated, but all of which should be visible, named, and subjected to the question: “Is this delay serving a purpose, or is it serving a habit?”
The brands that consistently bring products to market faster are not the ones who pressure suppliers to violate physics. They are the ones who have mapped their floor time, identified their compressible time, and made deliberate decisions about which organizational processes to preserve and which to streamline. Speed is not urgency. Speed is architecture.
Simon Gong | Founder & CEO, Corio Hygiene Innovation Team
