UX CASE STUDY

Trimble

Creating a future vision for the support, learn, and community spaces for Trimble

Summary

Trimble Inc. is a global tech company providing smart solutions across industries like construction, agriculture, and transportation. On the Cloud Core team, I focused on improving the user experience of Trimble’s support portal, which is built on Salesforce. My goal was to streamline access to the learning and knowledge base across both the portal and Trimble.com. I also redesigned the community experience to create a more seamless and engaging interface that encourages user interaction.

My role

Lead UX Designer, UX Researcher

The team

Lead UX Designer, Product Owner, Project Manager, Salesforce Engineers

Tools

Figma, Miro, Adobe CC, Jira, Confluence

Timeline

10 months

Business Constraints

Salesforce limitations

Waiting on high-level decisions

Limited resources for research

Business requirements

01

Optimize existing support portal



02

Design a federated search functionality for the support portal



Design a federated search functionality for the support portal



03

Conduct research and provide updated personas



Conduct research and provide updated personas



04

Architecture and navigation for support, learning, and community



05

Concept Car (future state vision)



06

Delivery of a unified support, learning, and community experience



Project lifecycle

01

Heuristic evaluations

02

Competitive analysis

03

Support portal updates

04

Federated search design and launch

05

Research

06

Wires and hi-fidelity designs

Heuristic evaluations

I ran heuristic evaluations on both the support portal and the help center to uncover usability issues. After identifying several violations, I redesigned the support portal to address them and began working on similar fixes for the help center. A lot of the problems came down to usability compliance and clunky user flows. For the help center, many issues fell under heuristic #6—users were being forced to recall too much instead of recognizing patterns, and inconsistent components didn’t help. In the support portal, the biggest challenge was related to heuristic #1: users couldn’t easily see what the system was doing. One clear example was the lack of empty states. I tackled these issues during the portal redesign, building in solutions that improved clarity and consistency.

Competitive analysis

The goal of the competitive analysis was to get a clear picture of how other companies—especially Trimble’s competitors—handled learning, support, and community experiences. Adobe and Autodesk really stood out with their clean navigation and well-structured knowledge bases, which made them feel intuitive and easy to use. I used those examples as inspiration when designing future-state concepts for Trimble’s support, learning, and community spaces. I also looked at both authenticated and unauthenticated user experiences to get a full view of how access and functionality differed.

Research

Understanding competitors and users

I generated proto-personas based on Trimble's existing personas and planned to carry out user interviews to develop new personas using this data. Additionally, I formulated a research plan for the upcoming user interviews. 

Key Personas we were targeting were Account owner, Secondary account owner, Company admin, Product user, IT admin, Internal support agents

I mapped out navigation ideas for the support, learning, and community sections on Trimble.com. The goal was to plan how we’d organize both new and existing content, breaking it out clearly into those three areas. I focused on what content we wanted to include and how to make it easier for users to find what they needed within each section.

Site map

Heuristic evaluations

I ran heuristic evaluations on both the support portal and the help center to uncover usability issues. After identifying several violations, I redesigned the support portal to address them and began working on similar fixes for the help center. A lot of the problems came down to usability compliance and clunky user flows. For the help center, many issues fell under heuristic #6—users were being forced to recall too much instead of recognizing patterns, and inconsistent components didn’t help. In the support portal, the biggest challenge was related to heuristic #1: users couldn’t easily see what the system was doing. One clear example was the lack of empty states. I tackled these issues during the portal redesign, building in solutions that improved clarity and consistency.

Competitive analysis

The goal of the competitive analysis was to get a clear picture of how other companies—especially Trimble’s competitors—handled learning, support, and community experiences. Adobe and Autodesk really stood out with their clean navigation and well-structured knowledge bases, which made them feel intuitive and easy to use. I used those examples as inspiration when designing future-state concepts for Trimble’s support, learning, and community spaces. I also looked at both authenticated and unauthenticated user experiences to get a full view of how access and functionality differed.

Research

Understanding competitors and users

I generated proto-personas based on Trimble's existing personas and planned to carry out user interviews to develop new personas using this data. Additionally, I formulated a research plan for the upcoming user interviews. 

Key Personas we were targeting were Account owner, Secondary account owner, Company admin, Product user, IT admin, Internal support agents

Site map

I mapped out navigation ideas for the support, learning, and community sections on Trimble.com. The goal was to plan how we’d organize both new and existing content, breaking it out clearly into those three areas. I focused on what content we wanted to include and how to make it easier for users to find what they needed within each section.

Federated search

I was responsible for designing a custom federated search for the support portal—something that would let users search across multiple data sources with just one query. Since the out-of-the-box Salesforce components didn’t meet our needs, we had to build a solution from the ground up. To shape the design, I looked at how search works on platforms like Google and other major sites, pulling in the best features to create a more intuitive and powerful search experience for our users.

Support landing, search results, and search detail pages

Support landing, search results, and
search detail pages

Support landing, search results, and search detail pages

Search results page

The search results page was redesigned to be more intuitive and user-friendly. A prominent search bar was added at the top, with sort and filter options on the left—each showing the number of matching results. On the right, a new “Related Articles” section helped users discover additional relevant content. To round it out, breadcrumbs were added across all support portal pages to create a more consistent and navigable experience.

Search detail page

To make the detail pages more informative and engaging, article-type labels and publication dates were added to give users better context about each piece of content. Share functionality and the option to follow specific articles were also introduced, helping users stay connected to updates and encouraging more interaction within the platform.

Support landing, search results, and search detail pages

Concept car

Creating the future vision for support, learning, and community spaces


I collaborated with another designer and the UX Director to develop concepts for the future appearance and functionality of the support, learning, and community spaces. These concepts were intended to be transformed into a video presentation, allowing us to effectively communicate our vision to stakeholders.

Journey maps

I developed journey maps that illustrated the current user experience for seeking assistance and identifying various pain points within the process. In contrast, the remaining journeys depicted in this image were designed for distinct personas, showcasing the envisioned future state of diverse user interactions when seeking support.

Script and storyboard

Collaborating with the UX director and another designer, I crafted a script for the concept car video, and together, we devised storyboards using wireframes and illustrations. Subsequently, I translated these visual concepts into. wireframes and then high-fidelity designs.

Journey maps

I developed journey maps that illustrated the current user experience for seeking assistance and identifying various pain points within the process. In contrast, the remaining journeys depicted in this image were designed for distinct personas, showcasing the envisioned future state of diverse user interactions when seeking support.

Script and storyboard

Collaborating with the UX director and another designer, I crafted a script for the concept car video, and together, we devised storyboards using wireframes and illustrations. Subsequently, I translated these visual concepts into. wireframes and then high-fidelity designs.

Customer journey map (Before redesign)

Customer journey map (Before redesign)

Customer journey map (Before redesign)

Customer journey map (Before redesign)

Scene 1 concepts

Persona: A Construction worker using a 3D scanning system in the field



Scene one features a construction worker out in the field receiving real-time updates and support for his 3D scanning system. He’s using the Trimble SX12 Scanner & Robotic Total Station, a tool that enables him to capture and analyze 3D data for construction and surveying tasks.

User gets update on his tablet out in the field.

User is able to login to support via his phone to get personalized information. He can also scan a QR code to get help with a specific issue.

User can access support via his phone. He can see device status and receives alerts when his device needs repairs.

Scene 1 concepts

Persona: A Construction worker using a 3D scanning system in the field



Scene one features a construction worker out in the field receiving real-time updates and support for his 3D scanning system. He’s using the Trimble SX12 Scanner & Robotic Total Station, a tool that enables him to capture and analyze 3D data for construction and surveying tasks.

Scene 2 concepts

Persona: an architect using 3D modeling software

The second scene features an architect persona working with 3D software, emphasizing the need for seamlessly integrated, cloud-based tools that support file sharing across multiple applications. The scene also highlights in-app assistance, access to community support, and the ability to add extensions. A key moment in the narrative includes the use of a chatbot directly from her device, enhancing the interactive and supportive experience.

Scene 2 concepts

Persona: an architect using 3D modeling software

The second scene features an architect persona working with 3D software, emphasizing the need for seamlessly integrated, cloud-based tools that support file sharing across multiple applications. The scene also highlights in-app assistance, access to community support, and the ability to add extensions. A key moment in the narrative includes the use of a chatbot directly from her device, enhancing the interactive and supportive experience.

User follows conversations and gets support via the community on Trimble.com.

User has access to extensions for her 3D software.

Scene 3 concepts

Persona: an IT Sec Ops & Support person IT Admin (internal)

The third and final scene introduces an internal IT support persona who stays ahead of the curve by proactively streamlining knowledge sharing on key support topics for employees. Alerts are received on both her phone and desktop, ensuring timely communication and efficient issue resolution.

Scene 3 concepts

Persona: an IT Sec Ops & Support person IT Admin (internal)

The third and final scene introduces an internal IT support persona who stays ahead of the curve by proactively streamlining knowledge sharing on key support topics for employees. Alerts are received on both her phone and desktop, ensuring timely communication and efficient issue resolution.

In addition, it appears on her dashboard on her computer. Within moments she kicks off the fix and alerts the customer support teams in Trimble and customers as needed.

Next steps and outcomes

Next Steps

The next steps included wrapping up the concept car and kicking off user interviews focused on support, learning, and community. Insights from those interviews would help shape updated personas and inform the design process. From there, the plan was to create wireframes and high-fidelity comps for the future-state experiences, followed by thorough documentation to support a smooth handoff to developers.

Outcomes

I stayed closely involved in the development of the federated search feature, reviewing progress and ensuring the implementation matched the design specifications. One of Trimble’s subsidiary companies reviewed our work and responded with strong, positive feedback on the improvements we introduced.



As for the concept car project, we were just about to hand off our work to the team responsible for producing the final video when an unexpected round of layoffs impacted our entire team, bringing the project to an abrupt end.

User follows conversations and gets support via the community on Trimble.com.

User has access to extensions for her 3D software.

Scene 3 concepts

Persona: an IT Sec Ops & Support person IT Admin (internal)

The third and final scene introduces an internal IT support persona who stays ahead of the curve by proactively streamlining knowledge sharing on key support topics for employees. Alerts are received on both her phone and desktop, ensuring timely communication and efficient issue resolution.

IT customer support receives a critical IT security alert on her phone.

In addition, it appears on her dashboard on her computer. Within moments she kicks off the fix and alerts the customer support teams in Trimble and customers as needed.

Next steps and outcomes

Next Steps

The next steps included wrapping up the concept car and kicking off user interviews focused on support, learning, and community. Insights from those interviews would help shape updated personas and inform the design process. From there, the plan was to create wireframes and high-fidelity comps for the future-state experiences, followed by thorough documentation to support a smooth handoff to developers.

Outcomes

I stayed closely involved in the development of the federated search feature, reviewing progress and ensuring the implementation matched the design specifications. One of Trimble’s subsidiary companies reviewed our work and responded with strong, positive feedback on the improvements we introduced.



As for the concept car project, we were just about to hand off our work to the team responsible for producing the final video when an unexpected round of layoffs impacted our entire team, bringing the project to an abrupt end.

User can access support via his phone. He can see device status and receives alerts when his device needs repairs.

Scene 2 concepts

Persona: an architect using 3D modeling software

The second scene features an architect persona working with 3D software, emphasizing the need for seamlessly integrated, cloud-based tools that support file sharing across multiple applications. The scene also highlights in-app assistance, access to community support, and the ability to add extensions. A key moment in the narrative includes the use of a chatbot directly from her device, enhancing the interactive and supportive experience.

User follows conversations and gets support via the community on Trimble.com.

User has access to extensions for her 3D software.

In addition, it appears on her dashboard on her computer. Within moments she kicks off the fix and alerts the customer support teams in Trimble and customers as needed.

User is able to login to support via his phone to get personalized information. He can also scan a QR code to get help with a specific issue.

Next steps and outcomes

Next Steps

The next steps included wrapping up the concept car and kicking off user interviews focused on support, learning, and community. Insights from those interviews would help shape updated personas and inform the design process. From there, the plan was to create wireframes and high-fidelity comps for the future-state experiences, followed by thorough documentation to support a smooth handoff to developers.

Outcomes

I stayed closely involved in the development of the federated search feature, reviewing progress and ensuring the implementation matched the design specifications. One of Trimble’s subsidiary companies reviewed our work and responded with strong, positive feedback on the improvements we introduced.



As for the concept car project, we were just about to hand off our work to the team responsible for producing the final video when an unexpected round of layoffs impacted our entire team, bringing the project to an abrupt end.

Scene 3 concepts

Persona: an IT Sec Ops & Support person IT Admin (internal)

The third and final scene introduces an internal IT support persona who stays ahead of the curve by proactively streamlining knowledge sharing on key support topics for employees. Alerts are received on both her phone and desktop, ensuring timely communication and efficient issue resolution.

User can access support via his phone. He can see device status and receives alerts when his device needs repairs.

In addition, it appears on her dashboard on her computer. Within moments she kicks off the fix and alerts the customer support teams in Trimble and customers as needed.

Next steps and outcomes

Next Steps

The next steps included wrapping up the concept car and kicking off user interviews focused on support, learning, and community. Insights from those interviews would help shape updated personas and inform the design process. From there, the plan was to create wireframes and high-fidelity comps for the future-state experiences, followed by thorough documentation to support a smooth handoff to developers.

Outcomes

I stayed closely involved in the development of the federated search feature, reviewing progress and ensuring the implementation matched the design specifications. One of Trimble’s subsidiary companies reviewed our work and responded with strong, positive feedback on the improvements we introduced.



As for the concept car project, we were just about to hand off our work to the team responsible for producing the final video when an unexpected round of layoffs impacted our entire team, bringing the project to an abrupt end.

User is able to login to support via his phone to get personalized information. He can also scan a QR code to get help with a specific issue.

User can access support via his phone. He can see device status and receives alerts when his device needs repairs.

Scene 3 concepts

Persona: an IT Sec Ops & Support person IT Admin (internal)

The third and final scene introduces an internal IT support persona who stays ahead of the curve by proactively streamlining knowledge sharing on key support topics for employees. Alerts are received on both her phone and desktop, ensuring timely communication and efficient issue resolution.

In addition, it appears on her dashboard on her computer. Within moments she kicks off the fix and alerts the customer support teams in Trimble and customers as needed.

Next steps and outcomes

Next Steps

The next steps included wrapping up the concept car and kicking off user interviews focused on support, learning, and community. Insights from those interviews would help shape updated personas and inform the design process. From there, the plan was to create wireframes and high-fidelity comps for the future-state experiences, followed by thorough documentation to support a smooth handoff to developers.

Outcomes

I stayed closely involved in the development of the federated search feature, reviewing progress and ensuring the implementation matched the design specifications. One of Trimble’s subsidiary companies reviewed our work and responded with strong, positive feedback on the improvements we introduced.



As for the concept car project, we were just about to hand off our work to the team responsible for producing the final video when an unexpected round of layoffs impacted our entire team, bringing the project to an abrupt end.

Scene 2 concepts

Persona: an architect using 3D modeling software

The second scene features an architect persona working with 3D software, emphasizing the need for seamlessly integrated, cloud-based tools that support file sharing across multiple applications. The scene also highlights in-app assistance, access to community support, and the ability to add extensions. A key moment in the narrative includes the use of a chatbot directly from her device, enhancing the interactive and supportive experience.

User follows conversations and gets support via the community on Trimble.com.

Scene 2 concepts

Persona: an architect using 3D modeling software

The second scene features an architect persona working with 3D software, emphasizing the need for seamlessly integrated, cloud-based tools that support file sharing across multiple applications. The scene also highlights in-app assistance, access to community support, and the ability to add extensions. A key moment in the narrative includes the use of a chatbot directly from her device, enhancing the interactive and supportive experience.

User has access to extensions for her 3D software.

User follows conversations and gets support via the community on Trimble.com.

User has access to extensions for her 3D software.