HRG INC / Software comprehension research
We study how people understand interface language, find their way through software, and anticipate the consequences of an action.
Explore the questions ↓READ.CHOOSE.ACT.
Specific research questions.
For product owners, design teams, and organizations revising operational software.
The purpose of an investigation
What did the person
think would happen?
A completed click does not explain the belief behind it. We scope research around the words, routes, and decisions that shape how a person uses a product.
Define a study with a clear boundary ↗Reading / Methods / Investigations
FOLLOW
THE QUESTION.
14 pages shown
Company
Company
Investigations
Interface Language
Investigations
Navigation Trials
Investigations
Decision Flow Reviews
Study design
Task Observation
Study design
Comparing Alternatives
Study design
Participant Fit
Study design
Interpreting Findings
Reading notes
Labels & Meaning
Reading notes
Action Consequences
Reading notes
Empty & Error States
Reading notes
Reading Under Pressure
Working agreement
Study Scope
Working agreement
Research Outputs
A research distinction
“CLEAR”
TO WHOM?
A phrase can be familiar to the product team and still mean something different to the reader. Research needs a task, an audience, and a record of what the person understood.
We keep observations separate from interpretations and proposed changes. That makes the resulting recommendation easier to examine and use.
Read how a finding becomes assessable ↗What the work can leave with your team
A decision map.
A terminology review.
A traceable findings record.
The project agreement selects the useful artifacts. The handover connects the material examined, the observations, their limits, and a practical next step.
Understand the possible outputs ↗