Skip to main content

Table 5 Usability interview excerpts reflective of tool format and function

From: Development and usability testing of an online support tool to identify models and frameworks to inform implementation

“I think if you are able to help someone really clarify their aim or goal and then hold that, if you can transfer that to these next few pages to then be able to answer these [tool] questions, it can have this thought process be a little bit more succinct.” (ID3, round 1)

“I like how it looks. Visually, it has a very clean, organized and neat look and I like the simplicity of it… I think really for anyone that has a basic understanding of just implementing and sort of conducting an evaluation, I think this could be intuitive for them, especially with the ‘more information’ prompts you have available too. Because that definitely provides more guidance as to how to answer the questions.” (ID5, round 2)

“I found the questions very helpful, very lay-friendly enough that you know, I found them easy to answer. I like these little grey dropdown menus. So it doesn’t feel overwhelming when I’m looking at just a stack of things to answer. I can go step by step which I found very nice…and I do like that when you finish it and hit submit that that little results step on the top right-hand side lights up so you know where you are.” (ID7, round 3)

“I think in general it was good that there weren’t a lot of questions. Made it quite streamlined I guess that you could just click a few things and then you get the options shown to you” (ID4, round 1)

“It is super simple, easy to understand. I like that there’s not a lot of information that can confuse people. They have three main questions they have to answer and … they already have this very basic information. So that’s great to facilitate the adaptation of the tool. People can really adapt to it.” (ID8, round 3)

“That’s useful that I can sort through these by discipline or whether or not it has a figure. Things that would just help. It’s so anxiety provoking at the beginning of implementation, trying to even start thinking about theories, models and frameworks. So this is super helpful to narrow things down and give you different ways to start all of those considerations. And it’s nice to know when things have been developed and how long they’ve been in use.” (ID10, round 4)