Mixed methods · 12 participants · 4 weeks

Evaluating Novel Speech Input for Smart Glasses

Impact

De-risked a new technology investment by establishing that the input is physically feasible and serves unique use cases.

Role
UX Researcher, end-to-end ownership
Team
Research directors, PMs, SWEs, linguists
Duration
4 weeks
Methods
In-lab task (NASA-TLX, SEQ), semi-structured interviews
Person wearing sensors on the neck during a speech study
Example of novel speech input method.*Details generalized under NDA
1
The stakes

An investment in a new speech input was moving ahead on internal viewpoints, without user evidence

The organization was envisioning a novel speech input for smart glasses. There was no primary data on whether people could physically produce it, or how it differed from the speech types users already rely on.

My ownership

Strategy

Set the study goals and aligned research directors, PMs, SWEs and linguists on them

Execution

Designed the study and ran AI-enabled analysis

Impact

Delivered the report and roadmap next steps

2
The question

To keep investing, two things had to be true: people can physically produce it, and they’d choose it over other voice inputs

I framed the study around those two conditions. Feasibility: can users produce novel speech with sufficient comfort and physical ease? Desirability: what use cases does it serve that existing voice input doesn't? Five research questions broke them down.

Research questions
01

Physical feasibility

How easy or difficult is it to physically mouth novel speech compared to other speech types?

02

Effort & performance

How effortful is it, and how accurate does pronunciation feel?

03

Learning curve

Is there a learning curve? Does it change over time?

04

Value driver

What scenarios would this be helpful in?

05

Social acceptability

How socially acceptable is it, and how is discomfort mitigated?

3
The approach

Task-based lab study with surveys to measure effort and ease; interviews to explain it

Effort and ease had to be measured, not just described, so a structured task with standard surveys measured feasibility against other speech types. Value and social acceptability needed the why, so interviews followed the task.

Person speaking to a phone, representing a voice UI user

Participant profile

  • 12 internal employees
  • Voice UI users
  • Early technology adopters
  • No knowledge of the workstream
  • Available for an in-person study
  • Sized for thematic saturation and statistical trend
Participant at a computer in a lab with a researcher

Methodology

Repeated for each sentence
1
ReadSentences counterbalanced for length, reading complexity and speech style
2
RateNASA-TLX for mental workload and effort; SEQ for overall difficulty
3
InterviewOnce, at the endProduction experience, use cases, social acceptability, technology expectations
Affinity diagram with sticky notes

Analysis

Quant

Google Sheets → RStudio sanity check → ggplot plots per speech type

Qual

Transcription → codebook → first-cycle coding → affinity mapping → synthesis → report with quotes

Tools: Gemini, NotebookLM, Google Sheets

Designing around constraints
4-week turnaround

Interviews ran right after the task; AI tooling for the test-bed and analysis

Limited SWE support

Built the on-screen test-bed with lovable.ai

No external participants

Recruited employees with no knowledge of the workstream; flagged social acceptability for external follow-up

Sample of 12

Sized for thematic saturation and statistical trend; findings positioned as directional

4
The findings

It's feasible and wanted in specific situations, but effortful at first, with social barriers to solve

01Experience & effort

It's feasible, but effortful until people get used to it

Novel speech production is physically and experientially distinct. It feels effortful and cognitively demanding at first, then improves with familiarity.

“The first few sentences took real concentration. By the end, I wasn’t thinking about it nearly as much.”

Participant · illustrative quote
What I recommended
  • Quantify the difference (dB levels, mouth and facial movements) with research scientists to train AI models.
  • Map production experience and compensatory mechanisms to reduce cognitive demand.
02Use cases & adoption

People choose it over voice input in specific situations

Unique contextual factors and specific use cases motivate users to choose novel speech over traditional voice inputs.

“There are times I’d never talk out loud to my glasses. That’s exactly when I’d use this.”

Participant · illustrative quote
What I recommended
  • Identify top use cases and contextual factors so AI models cater to key needs.
03Social acceptability

Social discomfort is a barrier, but users named clear ways around it

While social discomfort presents adoption barriers, users identified clear and actionable mitigation techniques.

“It felt a little awkward with people around at first, but I could see ways to make it work.”

Participant · illustrative quote
What I recommended
  • Expand social acceptability questions to external participants.
  • Map mitigation techniques to different scenarios.
5
The impact

The program moved forward on evidence, and engineering got a direction for model training

  • Replaced opinion with evidenceEstablished user feasibility of novel speech production, instead of indexing on subjective points of view.
  • Reinforced the investment planReinforced the program's investment plan by establishing desirability through value drivers and unique use cases.
  • Guided AI model trainingGave engineering direction for AI model training to improve performance with novel speech.
6
Reflection

Next time, I'd flag small-sample limits up front and track learning per repetition

What worked

  • Rapid execution for directional insights
  • AI tooling to build the test-bed

What I'd do differently

  • State the interpretability limits of a small sample up front.
  • Visualize SEQ and NASA-TLX per repetition to answer the learning-curve question.

*Illustrative visuals and quotes. Study data under NDA.