ROLE
Product Design Co-op
TIMELINE
May 2022 - Dec 2023
ORGANIZATION
OSENSA Innovations
TEAM
EdgePi
PLATFORM
EdgePi Portal
TYPE
B2B + B2C
RESPONSIBILITIES
Component Creation
UI Design
UX Research
User Testing
Wireframing
User Flows
Prototyping
How Might We ...
Create an intuitive, human centric platform, that captures the full functionality of an Industrial PC/PLC/IoT device, while simplifying its inherent complexity in order to cater to both professionals utilizing EdgePi for industrial factory automation, and novice/ hobbyists utilizing EdgePi for home & school projects.
Led the end-to-end experience for EdgePi Portal as the sole designer. Saw the portal from ideation, to MVP Testing with community users, to its ultimate release.
Instilled a design culture within the organization by conducting collaborative co-design ideation sessions in order to familiarize stakeholders with the design process and its methods.
Created an EdgePi design system to ensure long-term scalability of the platform, and consistent branding throughout EdgePi's many marketing touch-points including its marketing website, web storefront, packaging and other branding designs shipped by me.
EdgePi was a complicated industrial PC with both hardware and software elements that required specific technical knowledge that I did not possess. At the beginning, it was important for me to spend some time understanding the context of the product before I head into ideation.
Primary phase of my user research involved inquiring about EdgePi as an Industrial PC, expectations for the interface from the team, and possible pain points that may arise.
OSENSA Innovations
Chief Technological Officer
Gathered insight into the capabilities of EdgePi, the context of the problem, and the functionalities the portal must possess.
“The EdgePi Portal is what sets our Raspberry Pi Powered industrial PC from our competitors. A good balance will have to be struck between the inherent complexity of an industrial PC and learnability of our portal interface in order to cater to our broad target audience.”
OSENSA Innovations
Back-end Developer
Gathered insight into the development logic that the EdgePi Portal UI will use in order to control the EdgePi device remotely.
“We will be primarily using AWS IoT Device Shadow Service to control the device. The EdgePi Portal interface should present the state of each configuration on the EdgePi and have input controls for users to change those said states.”
OSENSA Innovations
Front-end Developer
Gathered insight into how the portal interface would be implemented and any constraints or feasibility issues that may arise.
“The EdgePi Portal interface would be coded using ReactJS and Chakra UI. Both of these programs have component libraries that could be used in the design to make my life easier, although new design elements can also be created if needed.”
OSENSA Innovations
Back-end Developer
Gathered insight into the hardware anatomy of an EdgePi device such as its ports, microchips and boards.
“EdgePi in summary is a cloud integrated industrial PC, PLC (Programmable Logic Controller), and IoT edge device, with multiple channels of input and outputs. Most of the ports will have to be configured somehow using the portal.”
Secondary Phase of my user research involved scheduling a walkthrough with a mechatronics engineer to walkthrough the real-world use cases of EdgePi.
Understanding EdgePi is still a work-in-progress
Visited the in-house cleanroom where the first batch of EdgePi's are being built. Prototypes are currently undergoing QA and QC testing before full production.
Understanding EdgePi in a Home and School setting.
Visited a mechatronic's workspace where different breadboard setups were being set up, imitating what it would look for hobbyists and students using EdgePi.
Understanding EdgePi in an Industrial Automation setting.
Visited the mechatronic lab where different boards were being tested to cater towards professionals using EdgePi in an industrial setting such as factory automation.
Final phase of my user research comprised of gaining an understanding of existing related products in the market in order to gauge EdgePi's strength and weaknesses.
EdgePi was a complicated industrial PC with both hardware and software elements that required specific technical knowledge that I did not possess. At the beginning, it was important for me to spend some time understanding the context of the product before I head into ideation.
After consolidating my data gathered from the design ethnography stage, I chose to go into the define phase of the design process collaboratively with the team at OSENSA in order to familiarize the team that is relatively new to the field of interaction design to its methods, and to gain critical feedback early onbased on my colleague's expertise.
During the define phase, I created a physical affinity map to encourage my coworkers to join in on the conversation and help form insights and brainstorm ideas collaboratively.
The affinity mapping helped me organize the extremely diverse information from different stakeholders gathered from the design ethnography into a coherent and meaningful presentation. After the map was set up, some recurring themes and patterns began to appear.
EdgePi's 2 main target audiences were then presented as user persona archetypes, a mechatronics university student that regularly conducts personal electronic projects at home as a hobby, and a CEO looking for an cloud-based industrial PC to aid in factory automation.
These 2 archetypes was extremely useful in helping me ground my design and made sure I was cognizant of my user's diverse goals, preferences, and pain points. Often during setbacks that required design iterations, I would often go back to my personas to remind myself who I was designing for.
Lastly, I created a journey map to create a visualization of the many processes and steps the user would go through when interacting with the EdgePi Portal. Each step of the map gave me potential areas of improvement as well as insight into steps that required a higher mental load from users.
The actor and POV of the journey map was one of my user personas. Unfortunately the data to inform the creation of the journey map was not 100% based on real data as I did not have the opportunity to interview a mechatronic student /hobbyist. I instead used the data that I've received from the in-house user interviews, field studies, and competitive analysis and try my best to link it to an individual from this user archetype.
The ideation of the Dashboard was an iterative process and I went back and forth between sketching, wire-framing and creating low-fidelity designs on Figma.
As many hardware and software components of the EdgePi was still being worked on, there would often be times where my requirements would change or new functionalities or restrictions would be added at a moments notice, forcing me to modify existing ideas or brainstorm new ones.
However as development of the EdgePi continued, with some major changes to the hardware of EdgePi, coupled with the software backend side learning more capabilities about the AWS IoT Device Shadow Service, EdgePi can now provide users with a lot more customizations to its functionalities through its portal than previously thought.
The portal originally thought to only control and store data from components as a module such as inputs, outputs, LED's, was later discovered that each individual port can now be manipulated by the user and have their data logged onto the cloud.
With the changes, I had to quickly pivot but soon realized that with the current ideation direction that there were simply too many configurations to have all actions on one screen.
I returned back to my affinity map and began modifying it to reflect some of the changes. I started brainstorming a design that incorporated the new functionality requirements while being mindful of EdgePi's target audiences as demonstrated by the 2 user personas created.
Reviewing the user journey, I began conceptualizing a Dashboard that was divided into View Mode and Edit Mode, in which the Dashboard will show the readings of each components and all configurations would be done through modal screens.
Learning from my previous mistake of increasing the fidelity of my interface ideations too quickly, I returned to the sketching phase to explore and iterate on various ideas.
With low fidelity sketches, it provided a high level exploration of how the EdgePi portal user interface would work without getting bogged down by the details. I was able to quickly visualize different concepts and present it in meetings that aided collaboration and communication. Based on the feedback from the team, I would adjust and refine the sketches accordingly.
With the first iteration of the Edgepi portal conceptualized and implemented, the first batch of EdgePi’s was sent out to members of the mechatronics community for user testing and feedback.
Participants was asked to run through the onboarding process and conduct several common core tasks and then share their thoughts through a questionaire at the end. Along with the team at OSENSA, we decided to set a number of key metrics and KPI's to gauge the success of the EdgePi Portal.
Given users, both industrial and recreational, having prior basic mechatronics knowledge ...
Task Success Rate
<80%
participants should be successful in completing the assigned core tasks using the portal.
Time on Task
<30sec.
participants should spend no longer than 30 seconds to configure a specific port.
SUS Score
<70pt+
participants should be ranking the portal MVP, a system usability scale score of greater than 75.
CSAT Score
<75pt+
participants should be ranking the portal MVP, a satisfaction score of greater than 75.
The results of the 10 questionnaires was incredibly constructive in providing me with many areas of improvement and insights based on the key metrics set beforehand.
Albeit the small sample size, behavioural KPI’s such as the task success rate was an overwhelming 90%, with time on task hitting an average of 28 seconds depending on the core task. Attitudinal KPI’s however was missing the mark with both SUS and CSAT scores missing the benchmark.
Task Success Rate
90%
participants successfully completed the assigned core tasks using the portal.
Time on Task
28 sec.
was the average time participants spent to complete an assigned core task.
SUS Score
65pts
was the average score participants rated the MVP in regards to its usability.
CSAT Score
70pts
was the average score participants rated the MVP in regards to their satisfaction.
Although most test users are able to successfully complete the assigned core tasks, attitudinal KPI's were lagging.
From the questionnaire, users are quoting the logic for more complicated tasks between ports can be better presented in the UI. Test users using EdgePi within an industrial context had concerns the the readings were too small to be presented on a big screen and also requested some sort of pinning functionality.
The Differential (DIFF) and Resistance Temperature Detector (RTD) requires the use of multiple ports. Users were getting confused with the repeated readings shown.
Iterating on the feedback, I decided to add an icon composed of connector lines that groups the relation between the ports and the DIFF or RTD in an attempt to utilize "natural mapping" to make the experience feel more intuitive.
Changing the operating mode within a port's settings modal will in turn change the configurations under it. Users were confused why configuration options was changing.
By grouping the configurations available for each operating mode and styling it in a way where the configurations are under the operating mode in a hierarchal sense, inputs are presented to users in a more logical manner.
For users with multiple sensors and devices attached to EdgePi, finding the reading for a specific device proves to be difficult. Users requested some sort of pin functionality.
Added an enlarge and minimize functionality to specific readings for custom cards, allowing users to tailor the interface based on their own preferences and needs.
More advanced users provided insight into areas where more novice users would encounter confusion and recommended further context and tips that could be added.
Added insightful tooltips and error messages to eliminate error prone conidtions for novice users.
I made a lot of mistakes, but it was an incredible learning opportunity nonetheless.
EdgePi was my first ever professional end-to-end experience that I shipped. I've learnt to trust the process.
Designing for EdgePi was particular daunting as it was an interface solution for a product that I had no expertise or background knowledge in. Luckily, the team at OSENSA was extremely sympathetic, provided me with a lot of insight into the product, and most importantly actively participated in the design process. They trusted me fully and I am truly very fortunate to be given this opportunity.
Real-world requirements often change... learning to adapt is a critical skill.
Unlike school projects, projects done in a professional context often have many interconnected parts and changing variables.
Requirements change, new variables gets introduced, and problems often arise requiring me to think of workaround or rethink my solution completely. This experience really highlighted the importance of a structured iterative design process, with each step building off of the next.
Involving stakeholders early on in the process when possible was critical.
The UI design of the interface is only one part of a bigger picture. As the UX Designer, my work revolves around many other disciplines.
Throughout my co-op, I worked closely with the development team, making sure to bring them in right from the beginning of the design process. Looking back, this was the correct decision as team members was able to freely add their expertise into the conversation.
EdgePi Website
Designed using Figma and implemented using Wix the EdgePi website that goes into depth the device's applications, software and hardware capabilities, as well as a forum and blog for enthusiasts to keep up to date with our development.
EdgePi Packaging
Designed the packaging box the EdgePi will be shipped in. Ideated on Figma and refined on Adobe Illustrator. Conducted supplier relations by contacting different vendors, compared samples, and prepared the relevant design files.
EdgePi Enclosure
Designed the printed label on the EdgePi's enclosure. Used Adobe Illustrator to design a label that labels each of the physical ports in a compact yet intuitive manner. Again, conducted supplier relations and prepared the design files.
