Great idea! I dumped the scenarios above into this doc. Anyone can edit it so feel free to add to it or make changes!
@betatim That’s really interesting. I’ll bring this up with the team. For this test specifically though, some of the pages we want them to find are already non-existent, so it might be a bit too confusing to not use names in the tasks. However, we might be able to use this method when we do usability tests on our redesign later on in June/July. At that point, hopefully, the information architecture will be more aligned with how users naturally explore the site so then the tasks could be more creative.
@lresende You’re right, Project Jupyter has so many components, we couldn’t dive deep into all the different parts of the site even in the 1-on-1 interviews. It’s incredible.
I will say though, that we are looking at influential sites to see what works well for them just like you suggested, but unfortunately, our timeline for this project is rather short for a thorough research-driven website design. Given the mandate that we received from the steering council: The site should guide and inform individuals, organizations, contributors, and sponsors about Project Jupyter’s core values, technology, and community; we only have a limited amount of time to try to provide a website and components to meet this goal. These use-case tasks will give us an idea of how users begin to explore the site, and I’d imagine that when we hand over our redesign & research data to the community, that this project will continue on and improve, especially with broader strategies like you suggested.