UI/UX Design for Automation Machinery Manufacturer
- Business Consulting
- Confidential
- May 2022 - Feb. 2023
- Quality
- 4.5
- Schedule
- 4.0
- Cost
- 4.0
- Willing to Refer
- 4.5
“The team did a good job with market landscaping.”
- Manufacturing
- San Francisco, California
- 51-200 Employees
- Phone Interview
- Verified
UXReactor provided UI/UX design services for an automation machinery manufacturer. They guided the client through defining user personas and creating mock-ups, then created high-fidelity designs using Figma.
The client was happy with UXReactor’s work and their collaborative approach. The team was accommodating and excelled at project management using Confluence. They communicated effectively through Slack, Zoom, phone calls, and email. Their excellent research skills were also outstanding.
A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.
BACKGROUND
Introduce your business and what you do there.
I’m the president of product, technology, and operations for Guardhat Inc. We’re building the first industrial internet of people’s platform. In a way, we’re an 80-year-old startup trying to transition away from being a hardware company towards being a SaaS-based company. Our goal is to build an ecosystem.
OPPORTUNITY / CHALLENGE
What challenge were you trying to address with UXReactor?
We started as a device manufacturer; we built a smart helmet and a unique hardware set that has won many prizes due to its innovative design and features. The helmet has a lot of built-in technology with a backend platform to funnel in all the device data and make use of it by building solutions on top of it for enterprises and workers.
As our journey progressed, we noticed the challenges of hardware manufacturing due to supply chain and logistical issues, certifications, and sales challenges. Over the last 12–18 months, we made a strategic change in our focus to de-emphasize device manufacturing and focus on the software side of the business.
We decided to invest in building an internet of people’s platform and the ecosystem around it. We needed help building that ecosystem and wanted a partner to think about a UI and put the user and their experience first and the design third. I wanted to understand our user personas, the problem we had to solve, and the best-in-class experience we could provide to help solve that problem.
SOLUTION
What was the scope of their involvement?
UXReactor designed our product's UX for two of the user personas we identified. Initially, we wanted to take a broad approach and design an experience for each user persona. However, we later decided to focus on one specific kind of user and two user personas tied to them.
They helped us identify the user personas and solve their entire experience. UXReactor did their own research and managed our internal research process, acting as a quarterback and guiding us through getting user feedback, interfacing with the users, and creating mock-ups.
With UXReactor's guidance, we used a third party to find the right people in the industry to interview based on the personas we had identified. We had an internal session to determine the project we needed to solve, the flow, and the features we wanted to provide. UXReactor worked with our product management team to determine how we needed the product to behave.
From there, we created low-fidelity click-through mock-ups. Then, we interviewed 5–10 users to get feedback on the mock-ups and identify pain points. UXReactor helped us assimilate the feedback to ensure the UX matched the requirements. They created another version of the mock-ups. Through an iterative process, UXReactor created the high-fidelity design.
Using Figma, UXReactor delivered the UX designs for two personas across the desktop and native mobile experiences. The team delivered a complete design system that outlines the product's visuals, colors, and fonts.
What is the team composition?
Lalatendu (Senior Experience Design Strategist) was our main point of contact. Initially, we worked on the research track with a research lead and a support resource. Then, the design team took over; we had a design lead and several other teammates.
UXReactor also provided a project management team, and Satyam (Managing Partner & Chief Experience Officer) was also involved.
How did you come to work with UXReactor?
We created a detailed RFP that we sent to providers we knew of asking for proposals. Some of the other design firms that sent me prior work had better visuals and a better 'wow' factor than UXReactor. However, Satyam asserted that the 'wow' factor is short-lived, and what carries over is the complete experience.
UXReactor was focused on understanding the user persona; they first defined the experience and then focused on the design because the entire duration of the experience is more critical. This focus aligned better with our goals, so I went with them.
What is the status of this engagement?
We worked together from May 2022–February 2023.
RESULTS & FEEDBACK
What evidence can you share that demonstrates the impact of the engagement?
UXReactor was very collaborative and accommodating. We didn't always make things easy for them because we didn't have the right level of product management resources, but UXReactor was very amenable. Ultimately, we developed a good camaraderie with UXReactor. Although we wanted to continue our engagement, we decided to end it due to internal financial decisions to focus on implementation and execution.
How did UXReactor perform from a project management standpoint?
Initially, we had a six-month contract, but as we decided to narrow our focus to two user personas, we collaborated with UXReactor. Once we chose the whole native experience for two personas, UXReactor extended the contract without charging us more.
We used Slack, Zoom meetings, phone calls, and email to communicate. We used Confluence pages to document our timeline. For the research portion, I met with Lalatendu and the research lead to discuss what we had learned and needed to address. Then, our design lead coordinated the design efforts.
After every meeting, the project management team summarized the feedback and sent us a recap with reaction items they followed through on. They recorded the meetings, action items, and artifacts on a Confluence page.
What did you find most impressive about them?
UXReactor's strength was their project management in terms of corralling and handover. Additionally, they were very strong in the research part of the project. Even though they didn't have domain expertise and it took us time to get them up to speed, once they understood the landscape, they were great at doing research against the user personas. The team did a good job with market landscaping; they laid out our competitors and how to convert our solution into a transformative experience.
Are there any areas they could improve?
Our development team had some technical challenges that weren't obvious to me when we started the project. I understood UXReactor would provide everything our developers needed, such as converting Figma to HTML, but that wasn't the case.
We initially thought we could achieve a broader spectrum of UX design. Although readjusting expectations and narrowing the project was a mutual decision, the ultimate result has made me wonder if we got the full value of the money we paid. Although this process could have improved, it's been a learning experience for us.
In the first month and a half, we ended up educating them on the landscape, which was a bit of a waste of our resources. I would expect UXReactor to have domain knowledge on their own to some extent.
Do you have any advice for potential customers?
Be narrower and more profound in what you're trying to achieve. While you should still paint the bigger picture, your project should be focused. We took a couple of months to narrow down the project and should have done that from the beginning.
Additionally, it would be best if you had a solid project management team that could operate with UXReactor's design team. The design team is looking at a higher level of UX, so they can't be a substitute for a product team. You should define the broader use cases or requirements for the development team. Therefore, there should be a layer between the design team and your engineering team. On the other hand, ensure you understand you need a UI engineer to convert the Figma design to your programing language.
Although there are cheaper options, at the end of the day, you get what you pay for with UXReactor. You should balance out the cost and temper your expectations, especially if you're a startup. Think through how to make the most efficient use of your dollars because an investment like this is a big decision.
RATINGS
-
Quality
4.5Service & Deliverables
-
Schedule
4.0On time / deadlines
"We had some challenges with the timeline and had to readjust our expectations."
-
Cost
4.0Value / within estimates
"Although they delivered everything, I would have expected more value for money."
-
Willing to Refer
4.5NPS
"I’ve already recommended them many times.