CHRISTINA BUÌ
Jupyter.jpg

Website Redesign - In Partnership with Project Jupyter

Project Jupyter Website Redesign

6 Months

In a partnership with UCI, Project Jupyter worked with my team to redesign their website, Jupyter.org. Throughout the process, I led the research efforts to ideate, validate, and revise our mockups and prototypes. Awaiting implementation, the redesign was handed off and well received by the stakeholders and open source community. Below is a brief recount of the research methodologies and findings. Or you can check out this booklet that we produced for key stakeholders.

Jupyter_Redesign_Poster.jpg

Deliverables

Produce a redesign of the Project Jupyter website by conducting thorough UX research to support and optimize design and content strategies.

Timeframe

5 Months to complete all research
6 Months to hand off design to developers for implementation

  • Hi-Fi Mockups
  • Design Guidelines
  • Editorial Guidelines
  • Design System
  • Overview of final user testing results

Role

Lead UX Researcher

Methods

Discovery Research

  • Heuristic Evaluation
  • Competitive Analysis
  • Market Research
  • User Interviews / Contextual Inquiries
  • Archetypes
  • Cognitive Walkthrough
  • Jobs to be Done Framework
  • Surveys - Qualitative & Quantitative

Information Architecture & Usability Testing

  • UserTesting.com: unmoderated and remote
  • Validately.com: unmoderated and remote
  • In person: moderated and unmoderated

Prototyping Tool

Figma

Reflection

Project Jupyter is a very complex ecosystem. Jupyter tools and technologies are even more so. My team came on acting as a UX agency team. We set out to learn all that we can about how Jupyter works, what they offer, and why people use them. Furthermore, we were tasked with what seemed like the impossible: design Jupyter.org to help visitors--across all levels of technical knowledge--understand Project Jupyter and encourage them to join the community.

My main 3 takeaways:

  • Research never stops.
    Our biggest struggle was communicating the values and definitions of Jupyter to a diverse audience. But in order to do so, we ourselves had to understand Project Jupyter and the offerings. As non-users ourselves, we went through 3 major pivots in our understanding of the organization and its technologies. It took many many interviews to really understand what these ideas were. And then subsequently, many iterations of restructured IA and continuous user testing to finalize the wireframe that reflected this understanding. Ultimately, we were satisfied with the results as the final test results revealed that the content resonated with a diverse audience. However, more research can still be done and improvements can still be made.

  • Process is king. And be flexible when necessary.
    Because we had to pivot our thinking, our research methodologies, and our design so many times, we had to constantly remind ourselves of the project plan, timeline, and process to stay grounded and move forward. However, this didn't mean that no changes were made. We were constantly re-evaluating process changes against our objectives and adapted appropriately when necessary.

  • Stay true to the users.
    This was by far the most important lesson, despite seemingly so obvious to a user researcher. For this project, the open source community was our greatest asset. What started out as a constraint--keep the community informed at all times on the progress of this project--turned into an incredibly supportive and constructive resource for feedback. However, we had to remind ourselves that community of existing users is only a subset of the targeted users. We were also designing to inform new and unfamiliar users. This meant that while the feedback was appreciated guidance, we ultimately let the user testing results dictate the direction of the design. We compromised where necessary and balanced the design for both existing and potential users.