TWINe

In 2018, a 25 year old construction estimation software product, called WinEst, was being phased out and being replaced by a modern cloud-based software, named TWINE (The World Is Not Enough). I had the opportunity to support the senior UX designer on the team to conduct user research, design solutions, and test those solutions for the estimation feature of the product. The goal of the redesign was to align the new product with the users' needs and prune unnecessary components. Users in this niche industry will now be able to complete tasks faster and easier.

Project Snapshot

CLIENT
RESPONSIBILITIES
PROGRAMS USED
DESIGN PROCESS
OUTCOME
TEAM MEMBER

Trimble Inc.

  • User research

  • Create sketches of possible interaction design

  • Create clickable prototype

  • Test prototype

  • Provide feedback to product team

Pencil and paper, Sketch App, Invision & remote communication tools

A two week sprint that included surveying a focus group, one-on-one interviews, compiled data for design solution, created sketches, designed a low-fidelity prototype, created a clickable prototype, and tested design​

  • Understood users pain points

  • Understood which WinEst features were useful to keep for new design

  • Created a low-fidelity clickable prototype that was tested which provided insightful feedback

  • Delivered data-driven designs to team to implement in final product

Kathy Davies, TWINE Senior UX Designer

Gathering Insights

DISCOVERING THE PROBLEM

In order to redesign the estimation feature of the software, I first needed to understand where the pain points were. I met with stakeholders, the product team, and conducted user research (a survey as well as more in-depth one-on-one interviews), specifically, to understand what filtering and formatting features of the old product were being used, what needed to be pruned, and what would be useful to have in the new product.

USER RESEARCH FINDINGS

I conducted several surveys and one-on-one user interviews. Based on the research, I discovered users want:

  • Limited formatting and filtering options from 100+ to five

  • Refine the companies ability to customize the software to their needs

  • To be able to utilize the new software on any browser

Product Designs & Iterations

SKETCHES

I created two rapid, low-fidelity prototypes of what the new software might look like and incorporated the features that users found necessary. With these sketches, the UX team was able to blend the designs together to create an improved interaction design and product layout that was found to likely be the best.

WORKFLOW PROTOTYPE

I then created a clickable prototype on InVision App to prepare for usability testing. Below are the screens that show the workflow design and the order and sections in which I tested. 

View prototype design

Usability Testing

My designs were validated by testing the low-fidelity prototype that I had created. The user was an administrative professional in the construction estimation field. I conducted this test by creating a workflow and asking the participant open ended questions to see what actions he took in order to complete the tasks. The designs remained in sketch form due to time sensitivity.

FINDINGS
  • Core components, such as filters, views, formatting options, etc., were easily accessible

  • Participant found certain icons unclear and yet was able to learn certain icons quickly​

  • When asked how he thought changing the name of the file would work, the participant correctly assumed

  • Participant correctly navigated adding an item for the estimation simulation

  • Provided insightful and important information about how users would use the search functionality in adding an list item

Wrap Up & Next Steps

FINAL NOTES

Overall the two week sprint was a success, providing data-driven designs to the product team to produce a useful, useable, and marketable product. The usability test of the new design provided invaluable data for the product team to refine the designs. These designs were then incorporated into the rest of the software. Collected data that was of value included:

  • The users' pain points in regards to the estimation feature of the software

  • Which WinEst features were useful to keep for TWINE

WHAT'S NEXT?

Although my internship was at a close, if I had the time I would:

  • Incorporate gathered data results from prototype testing into new product design

  • Create high fidelity mockups using company design standards

  • Finalize usability of product by conducting more usability tests