Skip to main content

Whitepaper

Essentials for Enterprise UX Designers

In the fast-evolving landscape of UX design, a designer’s role extends beyond the pixels on the screen. Since I work as a UX designer at an enterprise, I can see how the craft of design is synonymous with solving complexities. Over my two-and-a-half-year experience at Nutanix, I have noticed that good design is not necessarily a direct reflection of good skills but an amalgamation of good skills and good strategy.

Image credits: UX collective
Image credits: UX collective

“A mentor once told me that asking the right questions is the job half done and I couldn’t agree more.”

Although I have put together these thoughts for UX designers at an enterprise, I feel they may still stand relevant irrespective of the domain and type of customers. So, here are those four key considerations to keep in mind:

  1. UX and product strategy
  2. Requirements before solutions
  3. Ownership while collaborating
  4. Handling error scenarios.

1. UX and Product Strategy

Designing for the enterprise goes beyond the conventional boundaries of a PRD (Product Requirements Document) or a specific problem statement. Successful UX designers understand the importance of thinking holistically and contributing to the formation of the PRD. Our value as designers can be enhanced outside of the visuals and mocks we often present to shape the product with a strategic mindset. Solid UX research can in-turn help build the PRD based on what the user actually needs. Make sure you are adding value from the start! We should actively participate in the early stages of product conceptualization, identifying overlaps, potential edge cases, and main use cases.

“Addressing these issues proactively ensures a cohesive user journey.”

Secondly, when we are neck deep in work it’s easy to forget that customers don’t perceive a product as separate projects, and inconsistencies can significantly impact their overall experience. Holistic thinking is thus vital for any project small or large.

Image cource: https://www.nutanix.com/products/prism
Image source: https://www.nutanix.com/products/prism

For example, at Nutanix, many solutions that are sold as discrete products sit under the mothership application — Prism Central. Although the sections are different, there are multiple areas with significant overlap. The Prism Central dashboard is a primary landing page. The settings section also houses configuration and customization details for features. Since Nutanix sells bundled solutions to manage infrastructure, workflows within one product are impacted by workflows in another.

Consider scenarios where different teams work on distinct parts of a product — which is true for most of us. If not addressed comprehensively, this may lead to disjointed experiences. Being a designer, I also find myself heavily critiquing some government website or just a poorly designed app I am forced to use due to its utility. What I don’t think about often though, is the root cause of this experience. It’s probably the absence of UX strategy too, that also adds on to poor design.

2. Requirements Before Solutions

In agile environments, the problem area can be identified by any team be it backend, product management, design or QA. It is only natural to start thinking of a solution once a problem surfaces. In such scenarios when we jump to a solution brainstorming phase the conversation is bound to revolve around tech feasibility, release deadlines, existing code dependencies, et all. Now it is hard to hit the brakes, take a U-turn and go back to the problem statement to make sure you are solving the right problem. Hard but vital nonetheless.

An example that comes to mind is when our eng. team at Nutanix was designing the APIs as per new guidelines and was racing against time. After a couple of brainstorming sessions with the involvement of designers, developers, and product managers, we soon realized that they were chasing a problem that is not customer-driven! This is also why our initial solution seemed odd and could have led to a domino effect of UX changes across the entire product. We took a step back, analyzed the need, and re-framed the problem statement. The solution now was simple and non-disruptive. A UX designer can play a fundamental role in these team dynamics by pressing for discussion of the requirements and use cases that are aligned to user needs and not internal constraints.

API design and UX design go hand-in-hand
API design and UX design go hand-in-hand

3. Ownership While Collaborating

Smooth collaboration is at the core of successful projects, and successful people! It’s always helpful to establish clear ownership while working with cross-functional teams. Here is what I think can help:

Setting Expectations: From the outset of a project, clarity on which parts each team member will contribute to is essential. Whether it’s design elements, presentations, or timelines. Also understanding the strengths of co-workers and how they complement each other contributes to an efficient working relationship. Complex projects make it easy for teams to lose track, and the RACI chart is a great tool used for project management.

Clear Communication: Ownership involves clear communication. Clearly defined roles and responsibilities prevent misunderstandings, and regular check-ins ensures everyone is on the same page. Within the design team we follow some processes that enable smooth collaboration and transparency like bi-weekly team check-ins, meeting agendas before a call and meeting notes post the call to identify action items, clear documentation even in figma files with links to resources and points of contact, etc

Image credits: Hoozin
Image credits: Hoozin

4. The Big World of Error Scenarios

Error scenarios are an inevitable aspect of any complex system, and enterprise products are no exception. Understanding how these scenarios can impact the main workflow and happy paths leads to effective UX design. Although typically edge and error cases should not define the workflows for primary use cases, their frequency and magnitude can have a significant impact.

Edge Cases: Some examples are empty value scenarios, value overlaps, conflicts within the flow, or issues stemming from screens not directly related to the product. All these demand thoughtful consideration. For example, in input fields where a user need to add in correct ranges, edge cases could be:

  1. Only first value of the range is added
  2. Unsupported characters have been typed
  3. Same range has been entered twice, etc

Error Resolution: How designers frame error resolution statements is as important as identifying the errors themselves. UX writing is also a core skill that is almost always overlooked. In-product copy can make or break the user experience. A good way to construct error copy is by communicating clearly about the issue, its impact, followed by the resolution. This not only adds clarity but is also vital for building trust and confidence in the product.

An example of a bad error message. Image copyrights: Nutanix
An example of a bad error message. Image copyrights: Nutanix

In conclusion, excelling as a UX designer in an enterprise setting involves more than just creating visually appealing interfaces. It requires a strategic approach, an understanding of the broader context, and effective collaboration with diverse teams. Thus, we as UX designers can make a lasting impact on the user experience within the complex world of enterprise products.

Thank you for reading :)

Related Articles

Be part of something irresistible.

Unlock your potential to build, dream, innovate

Join our Talent Community to stay informed about the latest opportunities, events, and updates at Nutanix.

Join our Talent Community