In-product Feedback 

UI/UX Designer
Guild Education

In order to provide space for users to give feedback on their experience with Guild Education's service, I iterated, tested, and designed an experience for users to give feedback in the product.

My role

  • UI/UX designer who would have contact with our UserVoice representative to design a feedback solution

  • Conduct research to understand where the most visible and findable location is for a feedback module

Results

  • Designed a feedback module that can be input on any page in the Guild product with minimal engineering effort

  • Research results that validated the visibility and findability of the final design

Users first choose the relevant parameters to select robots for their application. They can select up to three to compare.

Multiple robots report.png

Once they've selected their robots, they can input their load data for summation and see if it's approved for the robots.

Multiple robots report graphs.png

Users can generate a report to show KUKA the robot purchase is approved for their payload.

Product clickthrough

Design process

As we prepared for the launch, new features needed to be added to match the current product.
  • Adding additional payloads to the analysis.

  • Reformatting the current analysis reports

Screenshot 2018-01-31 09.56.07.png

The old selection and analysis software

Source: KUKA.Load

Adding payloads

The initial layout was fine for simple analyses with one load case. But it wasn't future-proof for adding more payload data.

Problem 1: Adding the main payload data for each robot was cumbersome.

 

Problem 2: The current layout didn't work well for adding additional separate payloads.

Analysis multi.png

First layout

Layout iteration examples

 
Adding payloads - Final design
flange data inertia disabled fields.png

I organized all editable data on the left and the results on the right. This is consistent with the paradigm on the filters page.

Analysis reports

In order to get approval to use the selected robots, users need to download and submit a report and sign-off sheet to KUKA.

Problem 1: The current report had too many pages for all the payload and analysis data.

Problem 2: The style of the report needed to be aligned with the style of the app.

Screen Shot 2020-06-10 at 9.52.56 AM.png

The old report design

Report design iterations

 
Analysis reports - Final design
Multiple robots report.png
Multiple robots report graphs.png

I removed all images since they were unnecessary and I prioritized the data. I then optimized the charts for size and readability to use the space as efficiently as possible.

I've done more on Compose and Selector and I'd be happy to talk more about it. Thanks for reviewing!