Back to Proof

Two-Round Progressive Testing

6 configurations. 3 progressive rounds. 4 independent test methods. N=5 formal replication. A 72-cell data matrix compressed into one clear conclusion.

Growth-Stage Brand
Mar 26, 2026
72

6 configurations × 3 rounds × 4 test methods — a 72-cell data matrix driving a single conclusion

Engineering Story

Testing all possible material combinations exhaustively would require hundreds of samples and weeks of time. We designed a progressive validation protocol to extract maximum decision information from minimum resources.


Progressive Testing Matrix: 6 configurations × 3 rounds × 4 test methods = 72 unique data cells — each round narrows the field through progressive elimination


Phase 1 (Round 1): N=1 rapid screening of 6 cross-swap configurations, identifying trend directions within 48 hours. Phase 2 (Round 2): N=2 confirmatory testing on the strongest-trending configurations, eliminating single-test flukes. Phase 3 (Round 3): N=5 formal validation, simultaneously deploying four independent test methods — triple-pressurization protocol, national standard absorption speed, total capacity and retention rate, and 12-hour overnight simulation — cross-verifying the robustness of conclusions.


Cross-round CV (coefficient of variation) analysis confirmed data reproducibility: key metrics maintained consistent trend directions between Round 2 and Round 3, though absolute values showed expected variation from topsheet conditions and sample assembly tolerances.


Ultimately, the 72-cell data matrix compressed to one clear conclusion: Core E consistently outperformed Core C across all test methods and all topsheet conditions — not a method-specific fluke, but a structural advantage.


Why Only CORIO

We do not conduct “one-shot definitive” testing. Every conclusion must be confirmed under at least two independent test methods, with cross-round CV demonstrating reproducibility, before it is adopted as an engineering decision basis. If two methods produce contradictory conclusions, we add more tests — not pick the one that looks better.

Client Voice
“After reviewing the Round 3 data, the client’s technical gatekeeper began directly referencing our test numbering system in his own files — he no longer needed us to translate the data; he was using our framework directly.”
Ready to engineer your result?

Send us your challenge and our engineers will show you how this applies to your product.

Send an Inquiry