Ansys UX Internship

Improving the experience of 3D product design and simulation software

Project 1Project 2Project 3Reflections

In summer 2020, I worked at Ansys as a UX Design Intern. Ansys builds multi-physics engineering simulation softwares for 3D product design, testing and operations. I worked on Discovery product—an enterprise software for 3D modeling and simulation to help design engineers explore ideas, iterate and innovate with better speed, accuracy and overall experience.

Skills recognized, Ansys sponsored my ongoing one-year capstone project and provided the opportunity to explore and integrate AR/VR technology for Discovery software.

During my internship, I worked in a fast-paced environment with a cross-functional team of product managers, designers, developers with two fellow interns. Ansys UX team practices an agile process for software development where the project plans are broken down into small design tasks to respond to changes.

I worked on seven mini projects that had different goals and required different approaches. Out of those seven, I will briefly describe three projects that I find interesting:

1. Discovery design system
2. User flow improvements
3. Dialog box redesign


It is difficult for product designers and developers to manage and reuse the design paradigms of the software. It can lead to a lack of design consistency. How might we establish a shared understanding and a common design language within the team to achieve visual consistency, efficiency and collaboration?

1 PM
1 Sr. UX Designer
1 developer
Me + 2 interns

3 weeks

Discovery Design System

Designed a living document—a website that dictates how each UI component looks and works, how it can be reused, and how it shapes the overall user experience, improving the product design and development process.

Establishing a system from scratch

Discovery Design System as a stepping stone to the Ansys Design System
Ansys owns a large product family (more than 50 software) for design and simulation, many of which were added through small business acquisitions. With every product came it’s own product development process and visual language. Merging all products into a single cohesive style needs a larger Ansys global design system to govern them. To spark a conversation about Ansys design system across the organization, we took the bottom-up approach and created an individual product design system for Discovery software as a starting point.

Why a design system?

We started off by gathering requirements, defining design goals and constraints.
After receiving the project brief, we broke down the software UI into smaller building blocks that need to be included. Because of the time limitations we decided to focus on three basic design elements (or 'atoms' as Brad Frost would put it) initially: Buttons, Typography and Colors. Out of these, I worked on the Buttons page.

Target audience
Out of the two intended user groups of developers and designers, we focused on the needs of designers due to time constraints and technical challenges.

We chose a website over a printable format to capture the dynamic interactions, make quick updates and share document with the consumers easily.

As a newbie in the design systems world, research helped me in navigating the ambiguity.
I watched several talks, read articles and analyzed over 20 popular design systems for inspiration. My exploration and collaboration answered pressing questions regarding the following challenges and guided key decisions about:

Google's Material Design
Atlassian Design System
IBM's Carbon
Fluent by Microsoft

Also, I audited the existing shared platform: The WPF Toolkit, that designers and developers currently use to experiment, manage and test UI components.

Ansys Discovery Toolkit - existing library to test and collect the hi-fidelity design components

The preparation started with the UI audit and I created an Interface Inventory for buttons.
I evaluated the software UI and compiled various buttons and their interaction states in a Figma document that served as an inventory. I classified them into several categories: tabs, toggles/radio buttons, slideshow buttons, buttons with icons, buttons with dropdown menu and selection buttons. I noticed that all buttons in the software have consistent interaction behaviors (states). I validated naming conventions with UX writer and engineers.

Inventory for Buttons
A site map helped me outline the structure and flow of the information.
It was challenging to determine what and how the information needs to be shown because of the broad nature of the design system. I mapped out the information architecture to get a clear picture of the content, structure and relationship between the different sections of the website.
Site map
Then, I fleshed out my ideas in the form of wireframes and validated my concepts by testing them with the team members.
Based on my research, I created low-fidelity wireframes for home page and buttons page, and presented them to the designers and developers for feedback.
Discovery Design System (Buttons Page)
Laid the foundation for Ansys Design System

This is an ongoing project. I discovered my interest in the design systems while working on this project. I learned what it takes to establish brand new design system. Discovery Design System is now published internally for all Ansys employees. I'm honored that my Home and Buttons page design proposals were picked up and adopted by the UX team for further development. This project facilitated the discussion of the need of the global Ansys Design System to unify multiple products in future.

Project learnings:

1. Design system is a living document. That means it requires frequent updates and dedicated personnel to organize and manage it.

2. Design systems don't limit creativity.
In fact, they help product teams to document and automate redundant tasks so that designers and developers can focus on innovation and creative work.

3. Design systems are followers, not leaders.
Product teams build products. As the design of the product evolves, patterns emerge and by capturing those patterns, the design system also evolves.‍


Two features—1. Online Help and 2. Parameters Table can be accessed and discovered in multiple ways. Research shows that users struggle to use these features. Evaluate the interactions of these features and provide recommendations to improve their usability.

1 Sr. UX Designer
Me + 2 interns

2 weeks


User flow improvements with prototyping

1. How might we minimize the steps to reach the Online Help?

We studied how users are using Online Help feature through multiple access points (see the pictures below). To make it easily discoverable and accessible, we provided an in-context search bar at the top right corner of the software. It minimized the number of clicks to reach the online help option. I prototyped the flow that got approved and will be implemented in the next software release.

Adding an in-context search option at the top

2. How might we modify the Driving Dimensions and Parameters manager tables to make them more connected, discoverable and intuitive?

From usability testing, we found that the current placement of Driving Dimensions inside the advanced selection menu is not very intuitive. Also, two different tables to manage the same entity 'groups' causes a disconnection in the data and that is unexpected for the users. By applying the law of proximity, I optimized the interaction by relocating and combining the Driving Dimensions and Parameters table, making it more seamless and cohesive.

Two tables combined

Dialog boxes communicate system feedback to the user. Currently they are not consistent with the design paradigms of the product. How might we standardize them for different types of messages and make reusable for other products?

1 UX Manager
1 developer
2 Sr. UX Designers
Me + 2 interns

3 weeks

Dialog box redesign

Redesigned the dialog box for three message types: information, warning and error, three themes: dark, medium and, light and three button states: hover, tabbed and default. We made it visually consistent with other modals in UI without losing the legibility.

How did we get there?

I collaborated with two designers on this task and started by studying the current dialog box design and themes from Discovery Toolkit. Our goal was to create a dialog box that is consistent in visual style with the current software UI.


Initial sketches

After gathering the basic requirements, I brainstormed some initial ideas and sketched out several layouts. These rough sketches led to the questions such as - 'what are the different types of messages?', 'How to color code them?', 'what changes can I make to the current layout and size?', etc.

Iterations and explorations

We transformed those sketches into medium-fidelity mockups to get a better understanding of colors, UI themes and dimensions. At this stage, we presented our concepts to the manager and other lead designers, and sought feedback.

Behind the scenes
Narrowing it down

Based on the feedback received from our team, we identified common key attributes of the Discovery visual style and made our designs more consistent with them. Some of the visual design attributes we considered and compared were outline, background gradient, colored bar, background pattern and icon style.

Below are the three dialog box alternatives that I came up with:

High-fidelity mockup

We eliminated some concepts by dot-voting, iterated on the remaining and combined them in a final design. We presented our final designs to the team in the context of the software UI.

Hand-off to developers

We created multiple variants of the final design of dialog boxes for different text lengths and heights, themes, message types and button states and presented them to the entire team. Also, we discussed if there are any potential technical challenges that might occur during the implementation.

Long text w/ scroll
Long text w/o scroll
Medium text
Short text
Finally, we presented the design specifications to the developers in a meeting and discussed how visuals are laid out. We communicated our design decisions, recommendations and got their buy-in. Dialog boxes have been developed and shipped in the latest release.
Practice collaboration
To be a good leader, you have to be the best team player first. Ensure that everyone is heard, involved and valued equally. Soft skills including facilitation, organizing, planning, maintaining positive energy and communication are extremely important.
Understand product goals
Ask questions to understand the product from business and user's standpoint. In-depth understanding of the context will help in framing and exploring the problem space. Asking 'why' is important and necessary to identify right problem and test the work early on.
Balance trade-offs
Every design decision comes with consequences, both good and bad. Anticipating tradeoffs and striking the right balance between them provides clear direction to move forward. Support every design decision with a solid rationale and evidence.
Be a quick learner
Every problem brings new opportunities. It calls for new approaches, tools and methods to be employed. Be ready to pick up new things quickly and adapt to the environment. Strong grasp of concepts and best practices makes it easier to navigate in an unfamiliar domain.
Thank you for reading!
Ansys AR
Integrating Augmented Reality with Discovery 3D modeling and simulation software
Assisting remote working parents with a smart scheduler in Google Calendar
© Designed by Shriyash Shete in 2020 using Webflow