GitHub user zyratlo added a comment to the discussion: Making Texera easier for 
researchers to get started with

I've spent the last couple of months helping a biology researcher on dkNET, so 
this comes from that.

Our development process was like this: they would tell me what analysis they 
needed migrated to dkNET, I would make it, and then they would use it and give 
me feedback for what they want changed. They never built a workflow from 
scratch, they ran one that I prepared for them. So from their use case, all 
they do is find the workflow I shared, upload a gene list, select it in the 
workflow, run, look at the results and export. This is a related but slightly 
different user experience than a domain researcher who creates their workflows 
from scratch.

A lot of the questions they asked were related to using the platform instead of 
developing a workflow. Here are a few problems they ran into to give you an 
idea of where they got stuck:

- The shared workflow wasn't where they looked. They opened the Hub instead of 
"Your Work".
- After picking their dataset, the Select button stayed grayed out until they 
clicked the file name inside it.
- It's possible to create a dataset with no file in it. They did this while 
testing and got a run with no results and no explanation.
- After running, they saw a row count but didn't know where the results were, 
and the result panel didn't open on its own.
- Export failed once because an input dataset wasn't marked downloadable, and 
another time it just did nothing until they cleared their browser cache.

The technical jargon was a barrier as well, not only the number of buttons. 
When they reviewed my tutorial guide (for context, a guide I am writing to help 
new users get started and clone a workflow, upload a dataset, and run an 
analysis), they flagged "cloning", "operator", "version control", "computing 
unit" and "execution" as things that could put people off, so I rewrote it 
without them. I don't think we should completely remove technical words since 
users still have to learn some of them, but it is something we do need to keep 
in mind.

Hiding advanced options by default like in point 1 helps with not overwhelming 
the user, and #9151 from point 2 would also have saved them a step in the 
tutorial.

+1 to @xuang7 on error messages. The worst moments were silent ones, like an 
empty result with nothing saying why. They asked a lot of questions about when 
something went wrong without an explanation of why (like no error message, or a 
wrong result). To help with this, in our workflow I changed the analysis to 
stop with a message saying what to fix in the gene list.

Most of their questions were "how do I do X in the UI", and even with a guide 
they sometimes asked something it already covered, because the answer wasn't on 
screen when they needed it. The YouTube videos help, but they mean leaving the 
platform. So I'd support the in-workspace onboarding in point 2 and the 
assistant in point 3, and it would be even better if they also cover datasets, 
running, and results, not just building a workflow.

The result panel was where they spent most of their time, and their feedback on 
it is in #9123.


GitHub link: 
https://github.com/apache/texera/discussions/9246#discussioncomment-19362831

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to