1,000 Drops From 6 Feet: How REEKON Validated a Digital Tape Measure

REEKON Tools validated its digital tape measure through 1,000 drops from 3 and 6 feet and 10,000 cycles on a test rig, numbers that frame a broader engineering argument: reinventing a mature instrument is harder than building a new one, because every added feature must survive the same jobsite abuse the original absorbed for decades. The account comes from Christian Reed, Founder and CEO of the Boston-based company, writing for Machine Design.

Reed's team started from a workflow observation rather than a component failure. The tape itself was not the problem. The failure point came after the reading, when a tradesperson scribbles the number on scrap wood or paper and forgets it minutes later. He notes that tradespeople may use a tape measure 50 or more times a day on a jobsite, and that errors in the recording handoff were historically blamed on the user, not the tool, because the workflow had worked well enough for decades.

What survives unchanged in a redesign?

Reed treats the characteristics users already depend on as non-negotiable requirements. Users expect the blade to hold up, the hook to work, the housing to survive the environment, and the measurement to be accurate. Adding digital functionality only raises those expectations. He points to the engineering embedded in a standard tape's metal, heat treating, and end hook, refined over decades: "We couldn't have a good digital tape measure until it was a remarkable normal tape measure first."

The principle extends past measuring tools. When engineers add sensors, connectivity, displays, or software to an established mechanical product, Reed argues the technology must not become an excuse to compromise the underlying product. Electronics consume space, new components shift weight and balance, a different housing can change how the tool is held or assembled, and new interfaces introduce fresh points of failure.

How much better is enough to change a workflow?

Reed is blunt on adoption thresholds: "We don't try to make something 10 or 20% better, because that isn't enough reason for someone to change a workflow they already know." A tradesperson asked to trust a new tool for a task performed daily across an entire career needs an improvement obvious enough to justify the disruption.

His method maps the workflow around the product rather than the product alone: what happens immediately before use, what happens after, where users write down or re-enter information, which steps exist only because of the tool's limitations, and which redundant steps technology could eliminate.

Where does simulation pay for itself?

REEKON used SOLIDWORKS design and simulation throughout development to model the product, evaluate design decisions, and flag potential failure points before physical iteration. The economics are concrete: an injection-molded iteration took roughly four weeks and cost several thousand dollars, so simulation directed where that time and money went. The model could point to a feature that might pop out under load, marking an area to examine or reinforce.

Reed is careful to separate simulation from validation. The team compared simulation results against urethane-cast parts and later hardware to check how well the model reflected real behavior. Simulation never replaced physical testing; it focused it.

Why is a prototype not a product?

Reed, previously a mechanical engineer and program manager at Formlabs, draws a hard line between the questions a prototype answers, whether the concept works, and the questions production raises: whether the design can be built repeatedly, calibrated consistently, tested efficiently, and held at the required quality level. REEKON built product-specific calibration jigs, factory fixtures, and test software in-house, so the process for calibrating and checking each unit was designed alongside the tool itself. In his view, a product is not finished when the CAD model is finished, or even when the first prototype works; manufacturing and validation are part of the engineering system.

He closes with a discipline warning. The instinct in a redesign is to change everything, and the instinct is usually wrong. The engineering effort should target the handful of things that are actually broken, leaving untouched the parts that already work well, because users trust what they know. The question the development leaves open for buyers: will trades adopt a digitized measurement chain in numbers that justify the factory infrastructure behind it, or does the recording handoff stay on scrap wood for another decade?