The project was started with the need for building a self-hosting-used PaaS platform that belonged to dept. of CSIE in NYCU. The clients, two alumni from dept. of CSIE, who were also the engineers in the project, asked us for cooperation. In this project, I was in charge of structuring UX research and designing the user interface with a regular meeting to sync up once a week. The final solution was a platform with clean, simple and intuitive design based on our user research.
UX Researcher & Designer
User Research, Workshop, Wireframing, Usability Testing
2 UX designers, 1 PM, 2 engineers
2021.08 - 2022.03
This is the home page after log-in. At first, the engineers thought this page should be like intro of CScloud and there is another page for monitor.
---
Based on the research, the monitor is combined with home page by the reason that the most frequent activity from the users is to check the monitor after creating a service successfully.
This page shows all the apps that have been installed. Users can take quick actions to edit, view, and delete the apps.
--
I made this page clean and clear with hover buttons so that the users can easily find what they want by hovering or clicking without being bothered by discription characters.
There are two ways for app creating. One is to use ready-made apps from the marketplace.
--
I made the action of creating an app into a drop-down hover button on the nav bar from the insight I learned in the workshop. The final design is according to the users' goal by naming the button "app creating", not "marketplace."
Another way to create an app is connecting to the image coded by the users.
--
There are only essential elements on this page because the users' perference is close to minialist design when going through this process from findings of the user research.
My role in this process was UX researcher & designer. I led the design from structuring user research to the final design. Overall, we started with a series of user research including user & stakeholder interviews, prototype testing, persona building, and value proposition mapping. We also host an ideation workshop to get border ideas before the final design.
In order to understand the users' need and the stakeholders' attitute, we conducted 5 user interviews and 2 stakeholder interviews.
To help us build empathy with our stakeholders, who were also the engineers, we not only asked questions about the users' experience, goals, points of view, and painpoints, but also asked their opinions about the prototype based on the stakeholders' thoughts.
—— Key Insights
To make sure our solutions could align with the stakeholders' goals, the questions were mostly asking about motivations, goals, constraints, and expectations for the project.
Screenshot of online user interviewing
Three user personas were bulit accroding to the behavior variables, which were summarized from the interview data. Considering their goals, behavior variables, and the scenarios we learned from previous studies, we regarded two of them were "primary persona," and another one was "served persona."
After building personas, we used value proposition canvas to see if the values of the product and the values that users needed could fit each other. Based on the above information and disscusion with the stakeholders, we eventually extracted two key HMWs:
How might we make the design clean and simple with user-friendly flow ?
How might we help our users create an app intuitively ?
Value Propositoin Canvas
I was the host who led the workshop and from warm-up, brainstorming, ideation section to sharing time. The result of the workshop was a collection of ideas about the solutions to our key HMWs.
—— More Details
We recruited 10 PaaS users and separated them into 2 groups by a questionnaire beforehand. The questionnaire was made to see if the participants' personalities were more like the first group(平台背包客-oriented) or the second group(社群學習活躍者-oriented). It was a 2-hour-long workshop held on Butter, an online meeting platform, and Miro, an online collaborative whiteboard.
To give the paticipants ownership and warm them up for the next part, we firstly told the participants our story about this project, and then warmed them up by an exercise that asked them to write down user painpoints and needs from one specific scenario we gave.
Screenshot of the workshop in the beginning
Screenshot of the workshop while using Miro
To get more design ideas from the participants, we made two rounds of crazy 8s with the rules that the participants had to write down one idea/solution in every minute. We led the discussion and voting section after each round to let the participants understand more points of view and get inspired.
Screenshot of the crazy 8s canvas
To see the participants' UI perference without abstract concepts, we used a canvas which had a set of UI components for the participants to make their design ideas visualized.
Screenshot of ideation sketching co-creation
To ensure that we are on the same page regarding the result of each group, we invited the participants to share their ideation sketching and made further discussion if needed.
Screenshot of ideation sketching co-creation
After two meetings with the engineers for modifying the flow chart, we ended up using this version of UX flow as the reference when drawing the wirefarme.
UX flow chart of CScloud
Based on the previous information, I made this wireframe after three revisions.
Wireframe of CScloud
The UI design was our final solution which were already shown on the upper part of this page. I made it an interactive prototype with the help of Figma.
CScloud Demo
The stakeholders were glad that our design met both the users' and their goals. Moreover, they are willing to make iterations if needed. As for the real-world impact, since the platform is still developing now, it will be seen in 2-3 months.
It was my first time designing with web-hosting knowhow. Thus, I still had a lot to improve. Below were my reflections that push me to do better in the future!
First of all, in user interviewing, the note taker and I was not familiar with IT knowledge so we lost some user data. Although we tried to compensate it by asking the engineers afterward, it wasn't good enough. On this issue, my refIection was that I could learn more technical terms beforehand, and the note taker could be the one with IT background if possible.
Secondly, we aimed too high at the outcome of workshop. We initially wanted to get not only the ideas for HMW solutions but also UI suggestions. It ended up breaking the flow of our workshop because the result of "step 2 - Crazy 8s" was not really directly correlated with "step 3 - Ideation Sketching." My reflection was only focusing on one issue in one workshop.
Last but not least, we haven't made RWD for mobile phones. For those who want to monitor their services without computers, it's nice to have a mobile version for them to access the platform.