Evaluation route
When expert review is needed
Used when the main need is to identify usability, accessibility, and comprehension issues in existing flows.
Request form
Tell us what you are working on
Tell us what you are trying to understand, evaluate or deliver—whether that involves UX research, usability, accessibility, a Bangladesh research workstream, or wider programme and service research. You do not need to choose a method before contacting us.
What helps most
The clearest requests explain the current product or service issue, the users affected, the decision pending, and the uncertainty your team needs to resolve.
How requests are reviewed
How we determine the right route
Requests are reviewed against the decision need, the evidence required, and the level of uncertainty around the product or service.
Testing route
When task validation is needed
Used when the main need is to observe whether target users can complete critical tasks successfully.
Research route
When deeper context is needed
Used when adoption, trust, inclusion, or behavior cannot be explained by interface assessment alone.
Advisory route
When direction is unclear
Used when teams need help determining what should happen next, what should be prioritized first, and which evidence path should guide the work.
Review principle
We do not route requests by buzzwords or method preference. We route them by the decision the team needs to make and the strongest evidence path for supporting it.
What to expect
What happens next
Every request is reviewed for strategic fit, evidence needs, and operational feasibility before a route is recommended.
Request review
We review the request against UX research, evaluation, testing, and advisory routes to determine the most appropriate fit.
Scoping discussion
If the project is a fit, we clarify the decision context, route, delivery expectations, and any required access or governance conditions.
Structured proposal
You receive a structured proposal outlining the recommended route, scope, outputs, delivery expectations, and implementation relevance.
Preparation note
Requests are easier to route when they include the product or service context, the users involved, and the top one to three questions the team needs answered.