top of page
CLINICALKEY FOR PHYSICIANS
Iterative Testing and Design
Workspaces Formative Usability Testing — Q1-Q3 2026
Testing Framework
Each round scores two dimensions, then feeds into the next round until the solution is confirmed.
💡
Assumption
☐
UX/UI
Round 1
Round 2
Round 3
✓
Confirmed
Share Button
Slam Dunk:
Validated by 9/9 users after a round
Share icon is unfamiliar
Some don't notice the share button
Physicians recognize the paper-airplane icon as the way to share
Round 2
Round 3
References in Right Rail;
Collated Citations
Workspaces is the 3rd iteration of CKAI
References are located beneath each answer
Citations in a range are not collated
No hover cards
References in Right Rail; Collated Citations
Physicians intuitively look for references below the response, but appreciate the side panel view
Physicians prefer collated sidebar citations over individual inline citation interactions
Preferred AI User
It's not what you always think, the finding is more nuanced when you dig deeper.
Physicians who already use AI may prefer asking AI over keyword search.
Preferred AI User
It's not what you always think, the finding is more nuanced when you dig deeper.
The keyboard opening over the home screen hides the bottom navigation from physicians
Personalization
Some assumptions and findings keep coming back,and keep getting confirmed!
Patient Age Range: Physicians default to typing patient age into the search bar instead of using Population Focus
Population Focus automatically registers in settings and display with keyboard input
Personalization
Physicians read "Settings Conflict" as their own error and prefer "Settings Updated" — being told the setting was already updated
Physicians question whether the Population Focus filter is needed when their question already states the population
Agile Iterative Rounds
→
→
→
Currently going from Round 3 to Round 4...
→
→
After Release we will pick up the agile iterative cycle again!
→
→
→
Starting a New Conversation
Physicians think the bottom text box for query responses is only for follow-up actions.
IMPLEMENTATION
Remove "New pill CTA" inside input bar. Three pathways not needed.
"New Conversation" CTA in Left Rail is the primary pathway users tend to use.
Ask AI needs more visibility as secondary pathway to always go home and start a new conversation.
Naming Conventions
Physicians cannot tell which CK Workspace search or AI features to use (Ask AI, Search, Tools, in-article Ask, AI Reading Assistant).
Updated Search to Content. Not a similar verb naming as Ask.
Displayed blue pill within input box to specify question about the article (Reading Assistant).
Created upfront onboarding.
AI Query vs Keyword Search
Physicians default to "Ask AI" for drug monographs because Content search is harder to find, not because they prefer AI
The change from "Search" to "Content" has reduced confusion between this section and Ask AI, but "Ask AI" was still the most-used route to finding drug monographs.
Participants do not appear to be doing this because of a preference to use AI — it just seems that Ask AI is easier to find and "Content" is not intuitive.
7/9
participants chose "Ask AI" on their first attempt (Scenario 3 or 4, depending on assignment)
Next Steps
Naming Conventions
Revisit naming conventions. CKN team and physician users have brought up they prefer "References." This would apply to navigation but also sourced content for answers or assets (videos, images). Make sure it makes sense and is consistent for all places/use cases wording appears. Test various naming options with Nursing, Physician, and Research personas.
Update upfront onboarding to be more effective (UXF 1769). Add in contextual onboarding at the user journey touchpoint.
Upfront and Contextual Onboarding
Make sure there is a focus on content on the Home page in the bottom display, not just AI query features. Bottom navigation focus over AI keyboard focus will bring visibility to the content side of the product (UXF 1781).
Content Focus on Homepage
Navigation vs. Sourced Content for Answers/Assets
bottom of page