For right now, we want to start with one-one-one conversations that can allow us to dive deeper into certain topics and have a more free-flowing discussion. We are less interested in specific Q&As and more interested in listening and learning from anything you have to say about Jupyter. Later on, we will definitely be asking for more specific feedback through discourse as we go. We understand that everyone is spread far and wide and extremely busy, but if anyone is able to carve out 45 minutes for an interview, we would really appreciate it!
Hey everyone! We’re looking for more members of the community to do interviews with. If we’re quick, it can be done in 30 minutes. We would love your help on this.
I’d be happy to do an interview.
Also, I tweeted this out here: https://twitter.com/zrsailer/status/1118939825917181953
Hey everyone! We’re making great progressive doing interviews and understanding what jupyter.org means to every member of this community. If you don’t have time for an interview, we’d really appreciate it if you completed a brief survey for us. It’ll take 5-10 minutes of your time. Jupyter Survey
I think it would be great if the new jupyter.org would be organised so that people who arrive there with a thought like “I need to solve problem X, I wonder if Jupyter has something for that?” can find an answer to their question.
Right now the landing page presents solutions (the notebook and the hub) not a problem the reader has/wants to solve.
For example a task a visitor might want to complete is “I want to provide a central place where a small team can login and run their notebooks.” which then points to The Littlest JupyterHub.
“I want to write a text book like webpage to accompany my lecture course, lots of examples are written in notebooks already, how do I create a webpage from them?” which points to Jupyter Book.
“I just receive a notebook by email, how do I view this?” which points to nbviewer (??).
“Someone emailed me a .ipynb file, what do I do with it?”
These are great scenarios @betatim! We’ll look at incorporating some of them into our usability testing. We’re going to evaluate how the website addresses these scenarios.
Definitely! You make a really good point, and we have noticed that, too in our evaluations of the website. Actually, since we’re on the topic, our team is putting together a usability test for potential users. They will be unmoderated but recorded with audio and instructions to narrate their thought process, so it will provide us with great qualitative data on how they approach and navigate the website. Here are a few hypothetical/situational tasks that we were considering. (Note that we are targeting non-users from various backgrounds.) What’re your thoughts on these?
- Imagine you’re a student and looking for a new computational notebook. Find out what Project Jupyter’s core values are and what it’s about.
- Imagine you’re in the Finance department, and you’ve heard about Jupyter to analyze large datasets.
Try Jupyter. Now install Jupyter.
- Imagine you’re a professor who wants to setup Jupyter notebooks for your class. You want them all to use the same version of the software and utilize the same dataset. Find how you would do this.
This would be similar to your suggestion: You want to provide a central place where a small team can login and run their notebooks. How would you do this?
- Imagine you’re a developer, and you want to submit an issue or a bug fix for JupyterLab. Find how you would do this.
- Imagine you’re a corporate sponsor and want to donate to Project Jupyter. Find how you could do this.
And then to add your suggestions here:
- Imagine you just received a notebook by email. How would you view this?
- Imagine you are a professor and want to write a textbook-like webpage to accompany your lecture course. Lots of examples are written in notebooks already. How would you create a webpage from them?
- Imagine someone emailed you a .ipynb file. What can you do with it?
Also, going back to what you said about just seeing the solutions on the landing page, we are actually working on that through our interview analyses. We are wrapping up our interviews this week and wanted to say thank you to everyone who has reached out or helped us in any way so far! From these interviews, we will be extrapolating Jupyter’s greatest strengths in order to represent the products in a more compelling way. And a large part of effective storytelling and drawing engagement is in tying our solutions to the user’s potential problems, so we will definitely also consider your hypothetical scenarios when organizing the information architecture
We are looking to launch our usability test by the end of the week, so everyone, feel free to give us feedback for the next few days!
Awesome! Sounds like you have the ideas and a plan to make it happen!
One thing I recently started thinking/realising is that in the grand scheme of things no one knows what Jupyter is. There are a few million notebooks on GitHub which is a huge number, but compared to the number of Word documents or Excel spreadsheets it is probably just “a rounding error”. You can ask random people on the street and they probably know what a Word document is, less will know what an Excel spreadsheet is and no one will know what Jupyter is.
The other thing I think is true that even though people know what word and excel are, what they want to do is not “use word to write a document” or “make some pivot tables in excel”. What they want to do is write a flyer for their lemonade stand or create that three page report for their boss or compute the sales numbers.
Based on all that: I started thinking we should formulate the tasks without using the word Jupyter or notebook or similar. It is super tricky to do but worth it (I guess) .
The Jupyter is community is thriving and growing and so is the number of components/sub-projects around Jupyter. IMHO, Jupyter.org will not scale if it tries to answer all the questions or describe all use cases of all it’s related components/sub-projects. We should also look around and try to learn from other umbrellas organizations and how they provide overall information about the community and redirect users to the sub-projects website which then provides guidance/responses to these questions in the scope of that sub-project.
I’ve got another suggestion for a task: imagine you’re a (technical, semi-technical or non-technical) manager, you’ve never heard of Jupyter before but it was mentioned by someone and you want to have some idea of what they’re talking about before discussing it further and allocating resources to it.
For that, an elevator pitch slide deck might help (mostly to be used by people trying to “sell” Jupyter to their company / deciders), as do showcases (look what type of problem Jupyter can solve, with the following benefits and positive outcomes).
These use cases are super helpful. @cmbui do you think you could make a Google Doc that we could copy these use cases to, and allow others to dump their ideas. We can use these both for user testing, and a way to validate future designs.
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.
Good point and +:100:! I’d use phrases/wording which doesn’t use Jupyter Jargon (JJ) in the description of the link to the sub-pages/third party sites.
One page I find cute (but never actually use) is https://whatcanidoformozilla.org which isn’t about informing people directly but it is a neat design pattern for directing people through a (huge) decision tree.
We’ve been working really hard on the Jupyter website redesign, and as result we’ve fallen behind on updating you all about our progress. Our apologies. We want to spend this week catching you up on everything that we’ve done so far.
First up is our affinity diagrams. We created two: one based on the functional needs of Jupyter, and one based on the emotional and social needs. All of these insights were gathered from our in-depth interviews with Jupyter users, non-users, contributors, and community members. The diagrams helped us create “jobs-to-be-done” for the website and the archetypes that we’ll be designing for. We’re going to share both of those later this week.
Please let us know if you have any feedback!
We aggregated our interview data (using affinity diagrams) and formulated jobs to be done, the emotional, social, and practical needs the new Jupyter.org website needs to fulfill.
We’ll update you with our archetypes, cognitive walkthroughs, and sitemap later this week.
Here are the main archetypes considered in our redesign effort. These archetypes are modeled from a behavioral perspective for potential website visitors. This is a great method for validating user flows and site navigation. It focuses on understanding who does what, when, and why.
Also, here is a summary of our Cognitive Walkthrough. For context, CWs are basic interaction design exercises used to step into the shoes of a potential user and see how they might navigate the site based on their persona and hypothetical needs. In this case, we used the archetypes in the previous post to approach Jupyter.org as first-time visitors. We tried our best to step into the shoes of these archetypes and used this exercise to help our understanding of the site’s information architecture and possible user flows.
(Note: the archetype for “new user” is labeled as “visitor outside of data science” in this image)
Hi friends! My name’s Graham, and I was added to the MHCID team in the beginning of May!
I’m excited to show our first concept for a sitemap of the website redesign:
Here’s a brief explanation of each section with a little more detail than the graphic:
This page will be the landing page for jupyter.org, and act as an introduction to the mission and branding of Jupyter.
- This section will detail the history of the organization and project, including the mission of open-source computing and the goals of the organization.
Hall of Fame
- We envisioned this page as a way to showcase members of the community and entities that have done exceptional work towards Jupyter’s goals
- This page will explain the governance of Jupyter as aqn organization, and link to members’ GitHub handles, similar to the “Steering Council” section on the current website
- This page will house all information relating to partnerships with Jupyter, such as sponsorship and institutional partnership
- We’re really excited about this section, as we’re designing an ecosystem in which each project has control over it’s content and outreach. This will be a catalog of all core projects, including an overview of each project (and a list of their products), their team and contributors, and all the documentation for that project!
- We also wanted to showcase all the projects out there that use Jupyter as a baseline! This page will be a catalog of those projects, linking to each of their unique pages
- This page will hold links to all of Jupyter’s documentation, including contributor and developer guides. The current website has these split, and we hope to streamline that flow for all users!
- Jupyter is such a unique ecosystem of diverse communities built around the organization. We wanted a place to showcase that, and to allow new users to find communities they want to contribute to. This section will act as a catalyst for building each community out there!
- This section will contain a calendar of events, and information on how people may volunteer with Jupyter and/or its various communities.
- Jupyter’s fantastic blog will be showcased here!
We’re so excited to continue to iterate through our design process, and create a website that serves each and every one of you. Let us know what you think - we’ll be coming back soon with much more!
We’re playing around with some new taglines and descriptions and wanted to get your thoughts on our current drafts:
Project Jupyter is a free suite of tools for computing openly, transparently, and collaboratively, built by and for a worldwide community.
Let us know what you think, thank you!