Monitor arm tilt mechanism: saving a $500K sale in three months
A 55% failure rate, 20 suspects, 3 root causes and a customer who needed an answer in a quarter.
- When
- 2022
- My role
- Design Engineer II, lead investigator
The situation
A newly released ultra-wide curved monitor was paired with our heavy-duty monitor arm, and the field started sending it back. The tilt would not hold. One customer had more than 1,200 arms installed and a new office opening. They needed a fix inside three months. The standard path through quality and operations was six months or more.
tilt-hero.jpgWhat I did
- Built a test jig and measured the monitor's moment arm. It was twice that of a flat monitor of the same weight, but still inside the mechanism's rated range. The spec was not the problem.
- Tested units and found a 55% failure rate with two distinct failure modes, pointing at both the friction washer clutch and the one-way bearing.
- Modeled the theoretical torque versus clamp force curve by hand and in Excel, then compared it to actual units. That gap had been flagged before and set aside because nobody was complaining yet.
- Listed 20 possible sources of error, ranked them by risk, and tested each one in isolation until three were confirmed: friction pad placement drifting 2 to 3 mm during assembly, one-way bearing quality varying performance by up to 50%, and supplier-applied grease cutting friction.
- Negotiated expedited material from a new bearing supplier by offering future business across all of our tilt mechanisms if they were selected.
- Ran accelerated life and use/abuse testing to qualify the fix before it shipped.
How it came out
The fix landed in three months. It avoided more than $500K in returns, replacements and restocking, and it made Humanscale one of only two monitor arm manufacturers able to support that monitor.
The follow-on: a new offering
That request also triggered the first special order request on the tilt mechanism, for a higher load. The design that came out of it worked for about 90% of configurations and went into production as a standard offering. I worked with product managers to build the configuration matrix: what they needed to know, and what they could use for stock and SKU planning. Leadership had first said the existing mechanism was not a problem. The investigation and documentation turned it into a capability most competitors did not have.
What I took from it
Passing tests and a quiet complaint log had hidden the problem. Writing down what the performance curve should look like before anyone asked meant we could move quickly the day leadership started paying attention.
tilt-curve.pngtilt-rootcause.png