Client: IBM Data & AI, Immersive Experiences Team

Role: UX Designer turned Unity Developer

Deliverables: Working Unity prototype, user flows, interaction systems, in-app footage

I joined IBM's Immersive Data team as a UX designer — and left having redesigned the way data feels. What began as wireframes quickly turned into Unity builds, C# scripts, and full-on app development. I wasn’t hired to code, but when things stalled, I taught myself and shipped faster than the average devs. Thirteen times faster, to be exact.

IBM brought me on as a UX designer for their Immersive Data initiative — a spatial analytics tool built for enterprise teams. But very quickly, the scope of my role expanded. I became the bridge between design and development, and ultimately took on most of the Unity engineering work myself.IBM brought me on as a UX designer for their Immersive Data initiative — a spatial analytics tool built for enterprise teams. But very quickly, the scope of my role expanded. I became the bridge between design and development, and ultimately took on most of the Unity engineering work myself.

I designed the user experience, wrote C# scripts for motion and interactivity, built the Unity prototype, and recorded all app footage myself — no mockups, no After Effects stand-ins. Everything you see was captured directly from the working build. Because if you're going to show someone the future of data, it better be real.

The experience was built for Meta Quest, and allows users to visualize complex data sets inside a spatial, immersive world. Think: filtering sales pipelines by region while standing inside a dynamic 3D globe, or watching customer churn data unfold like a constellation.

My work included:

Designing motion systems and interaction models for AR/VR

Developing Unity scenes and interaction scripts using C# and Visual Studio

Translating raw enterprise requirements into spatial design patterns

Recording and editing footage of the working prototype for stakeholder demos

Build a spatial interface for enterprise data exploration. No gimmicks, no fake footage. Every animation and scene you see was captured live, in-app — because I wanted people to feel what I felt inside the headset: possibility. Like flipping through a tangible memory, only the memory is a spreadsheet you can walk through.

I designed motion systems, coded interactions, and prototyped faster than the team could review. This wasn’t just about making data beautiful. It was about making it understandable, emotive, visceral. The way the globe tilts in your hand, the glow of a filter particle, the subtle pulse of relevance — everything had a reason. Everything was in service of feeling.

You can explore it all here: