As our visualization platform expanded to handle multiple 3D data types and external information sources, the interface began to strain under its own complexity.

Different teams used inconsistent naming conventions, duplicated logic, and lacked a shared understanding of what a “core object” actually represented.

Before this initiative, every group saw the 3D environment differently:

• For developers, it was primarily a rendering feature.

• For designers, a visual workspace.

• For leadership, a strategic differentiator.

These perspectives rarely converged, leading to fragmented priorities and unclear feasibility.

My challenge was to translate that complexity into shared clarity — bridging technical architecture and user experience, while maintaining full confidentiality and avoiding exposure of client or system data.

(The example below illustrates a recreated 360° interaction case — a mock representation of the usability issues identified in early testing, not an actual system screenshot.)

Confidentiality Notice:

This case study has been anonymised to comply with my confidentiality obligations under the Company Personal Declaration of Secrecy.

Product and system names have been generalised, and all visuals are conceptual or recreated for demonstration purposes.

 

All visuals shown in this case study were generated using AI tools and do not depict any real products, data, or systems. They serve solely as illustrative representations to support the design narrative. No confidential or proprietary information has been used or disclosed.

The initiative aimed to deeply understand how users interact with large-scale 3D environments in an industrial visualization platform.

My objective was to uncover hidden usability barriers, clarify visual and interaction patterns, and translate these findings into scalable UX recommendations for future visualization products.

Serving as the bridge between design, product, and engineering, I aligned user insights with technical realities and business goals — ensuring that design decisions not only improved navigation, interaction, and clarity, but also helped operational teams work with complex spatial data more efficiently and confidently.

Before introducing frameworks and object models, the team first needed a shared vision of what a scalable 3D experience could mean.

Different groups envisioned different futures — some focused on visual fidelity, others on usability or platform scalability.

To bridge those perspectives, I designed a Vision Type exercise: a rapid, low-fidelity exploration that encouraged everyone to imagine possibilities without debating feasibility.

“Let’s explore to align — not to decide.”

We used visual metaphors — layers, portals, and “objects as doors” — to help participants see the experience from a user’s point of view, not only a technical one.

This exploration produced a unifying phrase that captured our intent:

“A 3D environment where every object understands its context.”

That simple statement became the north star for subsequent design decisions — influencing how we approached naming, navigation, and interaction patterns throughout the project.

Understanding Users

Because of strict confidentiality and safety protocols, no recordings or screenshots could be shared externally. Instead, I conducted contextual discussions with internal experts — including engineers, visualization specialists, and product leads — to capture recurring pain points and mental models.

Designing for industrial visualization systems means designing for professionals who depend on accuracy, speed, and clarity — often in demanding operational environments.

Before exploring features, I focused on understanding how users actually interact with 3D information in their daily routines.

Through these sessions, several consistent patterns emerged:

• Frequent context switching between 3D environments, image views, and document references.

• Confusion around navigation modes (such as orbit, walk, or fly).

• Limited recovery options when errors occurred — users often restarted their view to re-establish context.

• A need for faster, in-context data linking to reduce back-and-forth between systems.

Even without exposing raw data, the anonymized insights made one theme clear: users weren’t just struggling with tools — they were struggling to maintain mental continuity in complex environments.

To share these findings safely, I translated them into abstracted user flows and scenarios, enabling teams across disciplines to empathize with real behaviors without exposing proprietary information.

“Explore to align — not to decide.”

That principle guided our collaboration: rather than debating interface details, we experienced the user journey together.

By replaying these anonymized journeys during workshops, the team aligned around a shared goal — a system that helps users always understand where they are, what they’re seeing, and what action is possible next.

To ground the concept work, I began by mapping how different user groups interact with the visualization environment.

For example:

• Operational specialists need to review and compare visualized components.

• Integration teams connect incoming data sources and maintain logical hierarchies.

• Product leads monitor readiness across multiple initiatives.

By reviewing workflows and observing collaboration patterns, I identified where misunderstandings and inconsistencies occurred.

The key insight was simple but powerful: everyone used the same words — but meant different things.

That realization made the object-oriented approach essential. Rather than debating interface features, we aligned around shared nouns — the conceptual entities that form the foundation of the system. I facilitated a series of collaborative mapping sessions to identify these entities, define their attributes, and visualize how they relate to each other.

While the actual names and data relationships are proprietary, the process followed the Object-Oriented UX (OOUX) framework to help the team unify language, reduce overlap, and create a shared foundation for scalable UX.

“When teams agree on the objects, they naturally align on how the system should behave.”

By the end, the team had a single conceptual map connecting design intent, technical structure, and user goals, building a bridge between UX reasoning and system logic.

♠ Note: All visual diagrams accompanying this section were generated using AI tools for illustrative purposes only. They do not represent real system data or architecture.

Once the shared framework was established, we used the conceptual object map to guide design discussions on how users should navigate and interact with complex visual data environments.

Instead of relying on traditional file-based navigation, we introduced a more context-aware exploration model , where selecting a key element dynamically reveals all related information and visual layers within the same workspace.

This approach reduced cognitive load and connected user actions directly to the underlying logic of the system.

Example (abstracted):

Selecting an element now reveals its related visual components, references, and contextual data — all within a single, unified view rather than across multiple separate screens.

Design focus areas:

• Contextual filtering based on object type or role.

• Unified side panels that adapt to the selected data or visualization layer.

• Relationship-based navigation breadcrumbs, ensuring users always know where they are and how to return to previous contexts.

This model not only improved orientation and efficiency but also established a scalable foundation for future multi-view interactions across visualization tools.

♠ Note: All visual diagrams accompanying this section were generated using AI tools for illustrative purposes only. They do not represent real system data or architecture.

Because the system was still in active development, we conducted rapid internal usability sessions with cross-functional collaborators — designers, engineers, and domain experts.

These short, focused rounds allowed us to validate interaction concepts early and refine terminology, hierarchy, and visual structure before implementation.

Key learnings:

• Terminology clarity: Certain technical terms created confusion for non-specialist users, so we replaced them with more intuitive language.

• Hierarchy simplification: Deep relational structures caused navigation fatigue; we streamlined them into a clearer, two-level model.

• Context visibility: Participants wanted to maintain spatial and informational awareness at all times, leading us to introduce a persistent contextual panel that adapts to user focus.

These lightweight tests provided fast, actionable feedback and strengthened cross-team understanding of how conceptual design decisions translate into practical usability gains.

Applying the OOUX framework made collaboration with engineering teams far more structured and transparent.

Together, we co-created a shared terminology and reference guide that linked design language with underlying system logic — allowing both disciplines to communicate with clarity and consistency throughout the development process.

Key collaborative outcomes:

• A centralized design glossary ensuring consistent terminology across teams.

• A component specification framework that connects interface behavior with system rules.

• Interaction pattern guidelines to standardize how relationships are represented and handled.

This shared documentation evolved into a living design–engineering contract , a foundation that helped both sides make informed decisions faster, reduce misalignment, and maintain design intent throughout implementation. (Link to System & UX Architecture)

Measuring Impact (within enterprise constraints)

Working within a large-scale enterprise environment meant that direct access to product analytics and user telemetry was beyond our team’s immediate scope.

Instead, we focused on behavioral signals, cross-team adoption, and qualitative validation to evaluate how the new structure improved collaboration and usability in practice.

Our primary goal was to ensure that the OOUX framework and interaction model helped users feel more in control — while also enabling designers, engineers, and domain experts to share a unified design language.

Even without quantitative analytics, these outcomes reflected a measurable increase in clarity, consistency, and shared ownership across disciplines.

By shifting the mental model from file-based workflows to object-based interaction, the team began to experience the platform as a connected ecosystem — rather than a set of isolated tools.

“We finally talk about the same objects, not just the same screens.” — Team Member

The next phase will include structured usability testing and data-driven validation to assess improvements in:

• Task flow efficiency across complex visual environments

• Navigation accuracy and recovery rates

• Cross-view linking and contextual awareness

These metrics will further validate what our qualitative signals already show — that clear structure and shared understanding lead to faster workflows, reduced friction, and stronger trust in the system.