Study first
Review the ideas behind the questions
Check who the research might miss before you write the plan. Recruit the right participants and ask what support they need. Report only what the findings can prove.
Include Customers With Support Needs
Inclusive research starts by asking which customers may struggle to take part or use the service. Those people need to be included early enough for the team to learn from them.
- Research should actively include disabled users and people who need support to use a service.
- People may need help because of trust, confidence, access, digital skills, or motivation barriers.
- Support-needs research should include people with low skills and people with high skills, because both groups may need help for different reasons.
In Practice
Do Not Recruit Only Easy Users
A customer panel made only of confident online users can miss barriers that shape conversion, onboarding, support, and trust.
Support Needs Are Not One Profile
A customer can be confident online and still need help if the service feels complex, risky, or hard to trust.
Common mistakes
Treating current confident users as proof that no one needs help.
Research the people who may avoid, struggle with, or need support for the service before making that claim.
Q&A
Who should inclusive customer research make room for?
Include customers who may face access, confidence, trust, skill, disability, language, or support barriers, not only the easiest customers to schedule.
Can a high-skill customer still need support?
Yes. A confident online customer may still need help if the service is complex or hard to trust.
Plan The Session Around The Participant
Ask about access before the session is booked. Confirm the contact method and materials. Then check location, device setup, timing and support budget.
- Disabled participants may need contact preferences, communication support, assistive technology, different consent formats, travel help, or a specific location.
- If a participant needs assistive technology, it is usually better for them to use their own setup or for the researcher to visit them.
- Extra expenses may be needed so disabled participants can take part, such as a helper, taxi, or communication support.
In Practice
Ask Before Choosing The Format
The session plan should fit the person. A remote call, office visit, home visit, printed form, or interpreter can change whether the participant can take part well.
Personal Settings Matter
A lab laptop may not recreate the way a customer actually uses a screen reader, speech tool, browser setting, or input device.
Common mistakes
Choosing the cheapest venue before checking access needs.
Check what support, location, equipment, and travel the participant needs before locking the session plan.
Q&A
Why should participants use their own assistive technology when possible?
Their own setup is more likely to reflect how they really work, and personal settings can be hard to recreate on another device.
Keep Claims Within The Evidence
Inclusive research can reduce blind spots by showing which users were included and where they struggled. Report who was studied and which barriers affected them. Keep the next change within what the evidence supports.
- Researchers should talk directly to users and specifically address their support needs, not only test the screen.
- People often misjudge their own digital skill, so support-needs research should not rely only on self-rating.
- When reporting inclusive research, name the barriers found and the users studied instead of turning the sample into an all-customer claim.
In Practice
Watch The Customer Try It
A support-needs session should show what help the customer needs in context, not just whether they describe themselves as confident or unconfident.
Report Who Was Included
A useful research readout says whether the finding came from disabled participants, low-confidence users, third-party helpers, or another group with a specific support need.
Common mistakes
Reporting one access-needs session as proof that every customer has the same barrier.
Report the barrier, the participant context, and the next design or research action without making an all-customer claim.
Q&A
What should the team do before saying no customers need support?
It should have research and testing evidence that explains why no support need exists for the service.