Visible Language
Visible Language is the oldest peer-reviewed design journal. It advocates the teaching, research, and practice of visual communication design to enhance the human experience.
Published by the Visible Language Consortium: University of Leeds, University of Cincinnati, and North Carolina State University. Next Generation Archive
The future of research journals is digital. I was tasked with expanding the existing Visible Language journal into a digital archive. Highlighting the history and prestige of previous Visible Language editions while forecasting the future journal.
Existing Research
Prior to my involvement in Visible Language, my supervisor (D.J. Trischler), had done preliminary research. Focusing on surveys and interviews to understand the experiences of readers on a digital version of the journal.
My Research
With the groundwork already laid out, I was able to focus on visualizing the previous insights. I focused on developing a mobile version as a proof of concept. The main features were a landing page, search functionality,
Initial Observations
As I familiarized myself with the project, I began quickly creating a Figma prototype using the previously established design system. The objective was to begin developing a layout and hierarchy. By doing this I could start highlighting areas of improvement.
Wireframing
After establishing the early phase of visual development, I took a step back. By shifting my focus to low-fidelity, it allowed me to quickly iterate different user flows. This allowed me to test and focus the conversation on the layout and experience.
Paper Prototyping (Pilot Testing)
Using the 3 different flows, this prototyping allowed me to witness the users interacting with the "app" in real time. Allowing me to ask about friction points as they came up and analyze where they "clicked".
Design Critiques
After identifying the desired flow, I began iterating 3 different visual styles. These options were used in an A/B test by pinning up for a design critique. This critique was conducted with Master of Design students at University of Cincinnati DAAP. Each student provided critical feedback on each slide of the archive.
Paper Prototyping (Stakeholder Testing)
After landing on a desired path and visual style, I started usability testing. This was done with 9 paper prototyping sessions using think aloud protocol.
I gathered a mix of academics, practioners and students to go through the prototype as if they are searching for research articles. These sessions were recorded so I could do a content and task analysis based on their individual processes.
At the end of each session I had:
- General comments (interview transcript)
- Task flow (video recording)
- Co-Designed slides (participant sketches)
Content & Task Analysis
Personas
Academic
Practitioner
Student
Goals & Motivations:
Goals & Motivations:
Goals & Motivations:
- Wants to get into the search immediately. With no wasted time or additional effort.
- Desires a traditional academic experience as opposed to conversational.
- Bookmark and/or download relevant articles
to read later.
- Notifications of newly published articles related to their areas of interest.
- The ability to view articles on multiple
connected devices.
- Wants to periodically read articles related to their interests. Not always actively researching a particular topic.
- Wants flexibility in their literature search to cater towards varying projects.
- Benefits from the tools while not always needing to go as in-depth in their review.
- Would like to search specific issues not the entire archive.
- Wants to learn how to successfully conduct literature reviews.
- Would like a simple and approachable interface.
- Wants the ability to use filtering to identify specific literature.
- Would like a variety of tools to improve the searching, reading and annotating experience.
Design Criteria
After the stakeholder prototyping sessions and persona development was done, I was able to create a design criteria. This is meant to highlight key features for each user group. Along with the 3 stakeholder tiers are 3 design tiers:
- Expected: could be done today
- Ideal: based on user-feedback this is where we should be at
- Speculative: would require more time and technology to accomplish
"Final" Prototype
Coming soon!
Next Steps
Upon finishing up my time at University of Cincinnati and Visible Language, there are some key next steps. The largest being the official development, final testing and publishing of a digital Visible Language archive.
Reflection
This was one of my most rewarding projects.
Problems that I ran into...
1. I am not the most experienced UX/UI designer when it comes to mobile applications.
2. Working on a project for multiple semesters has its lulls.
3. When I started I hadn't had much experience building prototypes in Figma.
How I pivoted...
1. I embraced the challenge and leaned on my experience as a more traditional communication/graphic designer and my understanding of user experience research.
2. I accepted that I will have weeks I enjoy working on this project more than others. Continuing to progress and remaining creative helped ease the lulls.
3. I kept trying, making, creating. I wasn't going to learn until I was willing to try, fail and then try again.
