Manage feedback from several organisations testing the same wearable by giving every tester the same protocol, the same feedback template, and one shared repository. Then tag each response by site, user group, and firmware build before you compare anything. Without that structure, you cannot tell whether a complaint reflects a product flaw or a local difference.
The core difficulty is that each organisation brings its own users, environment, and vocabulary. A soldier, a physiotherapist, and a sports scientist will describe the same vibration in three different ways. The sections below cover how to standardise, centralise, reconcile, prioritise, interpret, and report back.
How can feedback be standardised across different testing organisations?
Standardise feedback by issuing every organisation the same test protocol, the same questionnaires, and the same rating scales before testing starts. Fix the build, the task list, and the data format in advance so every response can be compared directly with every other one.
Agree on these elements during a kickoff, not after the first complaints arrive:
- A single protocol: Define tasks, wear duration, usage scenarios, and how often testers should log their experience.
- Fixed rating scales: Use one scale for comfort, one for usability, and one for perceived value. Avoid free-text-only forms.
- A shared glossary: Define terms such as “strong vibration,” “slipping,” and “discomfort” so a score of 4 means the same thing in Utrecht and in Texas.
- Context fields: Record who tested, in which environment, with which firmware version, and for how long.
- A frozen hardware and firmware build: If sites test different versions, you are comparing different products.
Run a short pilot of the protocol with one organisation first. It exposes ambiguous questions cheaply, before you multiply them across every site.
What is the best way to collect and centralise tester feedback?
The best approach is one shared repository that every organisation writes into, using a common template. Collect structured scores and free-text comments together, attach timestamps and device identifiers, and add objective logged data from the wearable where possible.
Capture structured and unstructured input
Rating scales give you numbers you can compare across sites. Open comments explain the numbers. You need both. A comfort score of 2 tells you something is wrong, and the comment tells you the seam rubs under the arm during overhead movement.
Add device data to subjective feedback
Wearables can log their own behaviour: wear time, battery drain, connection drops, and actuator activations. Pairing this data with questionnaire answers separates what users felt from what the device did. If three organisations report short battery life, the logs show whether it is a firmware issue or a usage pattern.
Whatever tool you choose, whether a spreadsheet, a ticketing system, or a research platform, keep one rule: nobody sends feedback by email or chat unless someone transfers it into the repository within a day.
How do you handle conflicting feedback from different organisations?
Handle conflicting feedback by checking context before judging who is right. Compare user groups, environments, firmware builds, and tasks across the conflicting reports. Most conflicts disappear once you see that the sites tested different things. The rest point to a genuine design trade-off.
Work through the conflict in this order:
- Verify the conditions. Confirm that both sites ran the same build and protocol.
- Segment the users. A clinician may want a subtle haptic cue while a field operator in a noisy environment wants a stronger one. Both are valid for their own segment.
- Look for the underlying need. Two opposite requests often share one goal, such as “I want to notice the signal without being distracted.”
- Decide between adjustment and a variant. If needs differ by segment, consider a user-adjustable setting, such as haptic intensity, instead of a single compromise.
- Test the decision. Return to both organisations with the proposed change and confirm it resolves the issue.
Never average conflicting opinions. A midpoint that satisfies nobody is a worse outcome than a documented decision with a reason behind it.
How should wearable feedback be prioritised for the next iteration?
Prioritise wearable feedback by scoring each issue on severity, frequency across organisations, and effort to fix. Address safety and regulatory concerns first, then problems that block core use, then comfort and polish. Repeated reports from independent sites outweigh a single loud opinion.
A practical scoring approach uses three questions per issue:
- Severity: Does it endanger the wearer, break the core function, or only annoy?
- Frequency: How many users and how many independent organisations reported it?
- Cost to fix: Is it a firmware parameter, a textile change, or a hardware redesign that touches tooling?
The cost question matters most for physical products. A firmware tweak can ship in days, while an enclosure change can trigger new tooling and weeks of delay. Fix cheap, high-frequency issues immediately and batch the expensive ones for a planned hardware revision. Document what you decided not to change and why, because testers will ask.
What makes feedback on haptic wearables harder to interpret?
Feedback on haptic wearables is harder to interpret because touch is subjective and depends on body location, clothing, movement, and attention. Two people can feel the same actuator pulse differently, and users often lack words to describe it, which makes complaints vague and difficult to trace.
Several factors muddy haptic feedback specifically:
- Perception varies by body site and tissue. The same vibration feels different on the wrist, waist, and torso, and between wearers.
- Fit changes the signal. Loose contact between actuator and skin weakens the cue, so a “weak vibration” report may really be a fit problem.
- Context masks cues. Walking, vehicle vibration, or a noisy environment changes whether a cue gets noticed.
- Actuator type shapes the sensation. ERM, LRA, and piezo actuators feel distinct, and users describe them inconsistently.
- Habituation sets in. A cue that feels strong on day one may fade into the background by day five.
To counter this, ask testers to describe what they felt, where, and during which activity, not just whether they liked it. Log actuator settings with each session, and use short guided exercises where testers identify patterns, so you gather comparable perception data instead of opinions alone.
How do you close the loop with testing organisations?
Close the loop by telling every organisation what you heard, what you will change, what you will not, and why. Share a summary within a set timeframe after testing ends, and show testers the revised build so they can confirm that their feedback was understood.
A reliable closing routine includes:
- A consolidated findings report sent to all sites at once, so no organisation feels it is working from different information.
- A decision log listing each issue, its priority, the action taken, and the reasoning for anything deferred.
- A follow-up session where testers try the changes and confirm they fix the original problem.
- A clear timeline for the next iteration, so partners know when to expect the updated build.
Closing the loop protects the relationship. Organisations that see their input shape the product stay engaged in later rounds, and their feedback gets sharper each time.
How Elitac Wearables helps with multi-organisation wearable testing
Elitac Wearables runs validation rounds as part of an end-to-end development process, so feedback never gets stranded between hardware, firmware, and textile teams. Because the development process is handled under one roof, test findings go straight to the specialists who can act on them.
- Haptic specialists who interpret perception data and tune actuator selection, timing, and patterns.
- An in-house 180m² Wearables Lab for fast prototype iterations between test rounds.
- Demonstrator builds that let several organisations validate comfort, interaction, and perceived value before committing to tooling.
- Experience in medical, defence, and sports projects, including regulatory demands such as MDR.
If you are planning a multi-site pilot or struggling to make sense of conflicting results, see how to work with us or contact our team to discuss your wearable.




