top of page

Surgical Robot UX/UI

UI/UX • 2021

OVERVIEW

Vicarious Surgical is creating a minimally invasive surgical robot that replicates a surgeon's natural human movement. It does this by incorporating a camera and two instrument arms into its design, allowing not only the surgeon's wrists inside the abdomen, but their elbows and shoulders as well. 

​

The success of this robotic system heavily relies on its user experience and user interface design.  It is essential to create an intuitive and seamless experience for both healthcare professionals and patients.

robot-collage.gif
MY ROLE

User research, UI/UX design for the surgeon platform

THE TEAM

2 Designers, 3 Engineers, 1 Project Manager

TIMELINE

May 2021 - Present

SP_Zachary Moore_128 (1).JPG
NDA RESTRICTIONS

Due to NDA restrictions, I am unable to share the progress or visuals of the projects, so please contact me at fstolorz@gmail.com if you want to find out more!

Learnings & Reflections

IDEATING AND PROTOTYPING

I worked with our senior UI/UX designer to create some of the first Unity prototypes that were implemented into the robotic system and tested by surgeons inside of a cadaver. This process involved frequent prototyping, testing, and validating designs with surgeons. It was of the utmost importance to ensure that surgeons were able to quickly pick up on each interaction/interface touchpoint while operating.

DIGITAL DESIGN 

I collaborated with a large cross functional team (software and hardware engineers, human factors, industrial design, clinical, regulatory) to define system requirements for FDA documentation, as well as design digital components of the system--from VR to 3D screens to 2D displays, as well as crafting the UX to determine how they all interacted.

DOCUMENTATION AND ITERATING

Having been given responsibility for the success of several projects, it gave me the opportunity to exercise product strategy and execution. In particular, when thinking about publishing flows, I constantly questioned the intention and proposed solution to see whether it addressed the issue at hand. 

bottom of page