The short answer: Technical buyers do fine with a big product portfolio if they can start with what they already know, like torque, speed, voltage, size, application, or the part they’re replacing, and narrow down from there.
In our research, the manufacturer’s site asked them to pick a product family first. That’s where they stalled.
The behavior data shows it clearly. Visitors kept clicking into a category, looking around, and going right back. On the main Products page, the behavioral audit counted 42 of these U-turns within a 30-day period. The Motors page had 32, and Servo Motors, one level deeper, had 13. You’d expect the pattern to fade as people got closer to a decision. It didn’t. It showed up at every layer.
The interviews told the same story. One participant described what the site was asking of him: “You’re not searching by the characteristics… you’re searching for the family.” Another said, “I think you have to be very familiar with their products already to know which one to click on.”
They know what they need. They don’t know what you call it.
About the research
This series comes from a Voice of Customer study we ran for an industrial motion-control manufacturer. It had three parts: 12 moderated interviews with live website walkthroughs (engineers and technical decisionmakers in the US and Europe), an unmoderated study where 38 qualified participants completed tasks and 46 gave open-ended responses, and a behavioral audit of key pages on the manufacturer’s site.
The majority of the participants were new to the manufacturer. In the unmoderated group, 47% had never heard of it. So these findings describe motion-control engineers looking at one manufacturer’s site. We haven’t tested them against every technical buyer, and we wouldn’t assume they carry over unchanged.
What did buyers actually bring to their search?
Requirements. In the unmoderated study, application requirements were the most common starting point, followed by budget and existing motor specifications. When we asked what they’d search for, more than a quarter said they’d include technical specs like voltage, torque, speed, or encoder type. Others started with a broad term like “motion control system” and refined from there.
The surprise was where the friction began. Buyers were fine with broad categories. “Servo motor” made sense to them. The trouble started one level down, where product families had names that meant something inside the manufacturer and not much outside it.
In the interviews, 6 of 12 participants looked visibly confused by the manufacturer’s naming. The difference between two similar-looking series read as labels rather than differences that could help them choose.
What do manufacturers commonly get wrong?
Most assume confused buyers need simpler information. Our participants said the opposite.
Once they reached a product page, they liked the technical depth. Getting to the right page was the problem. So we wouldn’t simplify the content. We’d change how it’s organized.
Your internal teams know why one product sits in one category and another sits somewhere else. They know the acronyms. Buyers show up with a different mental model: a job to do, with numbers attached.
What does navigating by buyer requirements look like?
Here’s an example, based on how one participant described their own search: a machine builder looking for a servo motor and drive combination for a 400 to 750 watt, EtherCAT application.
| Today (family-first) | Requirement-led |
| Products, then Motors, then Servo Motors, then a list of family names | Start at a “help me choose” path, an application, or spec filters (torque, speed, voltage, dimensions, IP rating) |
| Family names carry the differences, so the buyer opens several pages to compare | Each product card says what it’s best for and shows key differentiators before the click |
| Buyer has to already know which family fits | Matching products appear, with the family name as a label, not the starting point |
| Compatible drives live somewhere else | Compatible drives and cables show up on the motor page, and the reverse |
The product families stay. Experienced buyers who know exactly where they’re headed can still use them. Requirement-led discovery just adds more ways in for everyone else.
What should you change first?
Start with the cards. Add plain-language “best for” lines and a small set of spec filters at the category level, right where buyers were backing out. In our recommendations, this was the top priority. It doesn’t mean rebuilding the site, and it gives you a before-and-after you can measure in friction points.
Here’s a quick test you can run this month. Give five engineers from outside your company one real requirement and no help. Watch where they click, and where they go back.
If you want to find out where your buyers are getting stuck, reach out and let’s talk.


