ZimmerBiomet (ZB) is a major player in the medical device industry with a focus on robotic-assisted technology. The company has a global presence and is well-established in markets such as the United States, the European Union, Japan, Canada, the UK, Australia, and New Zealand.
ZB specializes in designing, developing, and manufacturing orthopedic products that are used for joint replacements. This includes everything from the patient’s implants to the robots that assist in the operating room, as well as the software that powers these robots.
UX Case study
Creating a templating tool for total hip replacement
In this case study, we will delve into the intricacies of developing the next-generation product after the success of ONE Planner Hip. ONE Planner Hip, also known as OPH, is a successful template tool that allows surgeons to create a precise total hip arthroplasty plan from an X-Ray. The project’s main challenge was the development of a 3D browser-based web planner that would allow surgeons to plan hip surgeries with similar or greater accuracy.
Problem
Why this project?
This project has been initiated as a natural progression of an already successful product available in the market. ONE Planner Hip has been widely adopted by the medical industry, but its limitations of working on 2D X-rays make it difficult for surgeons to predict some of the finer details that come from 3D planning. Therefore, the need to create ONE Planner Hip 3D (OPH3D) became evident. Additionally, ZimmerBiomet needed to respond to its main competitor in the market, Stryker.
Desired outcome
Our original goal was to create a superior product that would outperform anything currently available on the market.
We had the opportunity to learn from our competitors’ mistakes and carefully examine their products.
We quickly realized that to succeed, we needed to streamline our workflow, allowing surgeons to template a surgery in under 10 minutes.
Service’s design
How does it work?
One of the key advantages that ONE Planner Hip 3D has over its predecessor is the ability to template a surgery in 3D. However, this new service requires CT scan data instead of X-rays. CT scans can capture the X, Y, and Z dimensions of an object to maximize accuracy. To use OPH3D, hospitals must be equipped with CT scanners. Therefore, OPH2D still has a place in the market since not all countries, insurance plans, country healthcare policies or even healthcare facilities have access to the necessary tools required for OPH3D.
Within ZimmerBiomet, we offer three solutions that a patient and their data go through from a service design point of view.
Audience
For whom are we building this?
The ONE Planner Hip 3D is designed for orthopedic hip surgeons who specialize in total hip replacement surgeries. This group can be further divided into three subgroups:
- Enthusiasts: They are generally professors in universities or leading speakers in the field. They understand that new technologies come with new issues. And that includes re-training on a process that they’ve done for more than a decade.
- Producers: These surgeons typically work in public hospitals in the US. They prioritize speed and cost efficiency over everything else.
- Traditionalists: These surgeons are not so keen on new technologies. They prefer new tools that adhere to the medical framework and produce results that meet their medical expectations.
It’s important to note that there are significant differences between countries in terms of surgical practices, which can be attributed to the medical industry’s impact on the economy. For instance, a Japanese surgeon working in a public hospital may prioritize precision over speed, while an American surgeon working in a public hospital may prioritize cost efficiency. This is largely due to differences in healthcare costs across countries.
Roles and responsibilities
Team’s setup
The business case and priorities were developed by our product owner and management board. Our team was responsible for determining the approach and timeline for achieving those priorities. The tasks related to user experience were divided among the UX designer (me) and two developer engineers (Maite Gieskes & Lars van Loo) who guided me with research and documentation. A product owner (Ivo Flipse) was present to guide us in each phase and help set the next targets. The team was composed of several developers.
My responsibilities
The definition of each responsibility can be found below in the Step by step description.
Among them include: Competitor benchmarking, Design ideation, Wireframing, Generating a testable prototype, User testing, User results analysis and documentation.
Scope and constraints
Limitations
One of the distinguishing features of the medical field is the high cost of summoning professionals to test a product. Therefore, it is natural that user testing would run into thousands of dollars to conduct. In addition, unlike regular commercial products, one cannot simply A/B test a feature by putting it out in the field, as this could potentially risk a patient’s health or even life.
The nature of the medical industry means that iterative development cannot be applied in the same way as in other commercial fields. Auditor rounds are common, risk assessments are carried out on every single change, no matter how minimal it may be, and everything has to be documented thoroughly. A surprise audit can happen at any moment, and one does not want to be the reason for a multimillion-dollar fine by a regulatory agency.
For this reason, user tests are limited to a few occasions per year. These tests are rather long, and the user (usually a surgeon) is subjected to multiple tests from multiple teams in a single day.
Scope of tests
Duration
We ran 4 in-person tests (labs), and 1 online test. They were carried out along the 2 years of development of the application.
Audience
The tests or labs were composed exclusively of orthopedic surgeons and professors at medical universities. There were on average 12 participants.
Location
Aside from the online test, all the other tests were carried out in Phoenix (2022 & 2024), Montreal (2023) and Detroit (2023).
Tests / Labs
Some were traditional UX tests of a qualitative nature. The two Phoenix events included a cadaver lab, where the surgeon would perform additional tests.
Process
Step by step description
1. Scope mapping
Initially, there was an unclear concept of what a 3D templating planner should entail and what its requirements were. Every stakeholder had a different opinion on what to do, leading to a nebulous cloud of different ideas. With the help of the Product Owner, a set of requirements was written and explained. Fortunately, we had the advantage on hindsight of ONE Planner Hip 2D already on the market, so we knew it had to support at least what the previous generation planner did.
Initial arranged list of requirements based on ONE Planner Hip 2D. See in PDF
Cloud of use cases in the process of being arranged. See in PDF
2. Competitor benchmarking
As always, it is necessary to explore if there are similar solutions available in the market. Unfortunately, obtaining access to competitor products was particularly difficult this time. Unlike other industries, the competing products in this field are kept behind physical devices in hospitals. It was not feasible to go to hospitals just to try out the tools used by other surgeons. Moreover, surgeons are often restricted by legal obligations from disclosing how their products work to the public.
Fortunately, various tutorials and marketing videos were available on platforms like VuMedi where surgeons and sales representatives provided explanations about how their products work. This abundance of information helped me to create a visual catalog of user experiences and develop ideas for refining the competitor’s products. These ideas were later incorporated into our product, providing us with a competitive edge over anything that is currently available on the market.
Competitor benchmark: User flow of Mako 4.0 Total Hip Replacement by Stryker
Competitor benchmark: User flow of ONE Planner Hip 2D by ZimmerBiomet
Competitor benchmark: User flow of Formus Labs
Complete competitor benchmark. See in PDF
3. Grand design
During the design process, the Product Owner and I (UX) held iterative sessions where we added a new iteration every day. These iterations were then presented to the development team for discussion. We spent a few months finalizing the overall design concept for the application, taking into account the opinions of the development team and stakeholders. Our goal was to capture the essence of the concept without defining every single detail about the application.
Earliest documented iteration of the Grand design. See PDF for the complete iteration history.
3.1. Scoping
The team followed the Agile principles of software development and conducted the activity in accordance with the Scrum rules established in their charter. Once the grand design stage was completed and tested with users, the team began iterative development. The grand design aimed to cover the fundamental concepts of the application and allowed users to provide feedback.
4. Testing grand design
We tested our grand design early on via online interviews due to Covid-19 restrictions. Users were presented with an introductory presentation, followed by a clickable wireframe made in Figma. We gave minimal guidance and encouraged users to ask questions and share their thoughts on the prototype.
The two core screens that were designed the earliest in the grand design
5. Developing the happy path
The entirety of the happy path was designed. We decided to have a phase of grand design to secure the surgeon’s acceptance of the concept and minimize risks. Once the concept of the happy path was designed we began developing the other branches that deviate from the happy path.
Architecture of the happy path in OPH3D. The purple arrows represent the quick route (less than 5 minutes to perform per case). The black arrows represent the detailed route (10 or more minutes to perform per case).
6. Producing Hi-fidelity screens & refining concept
In this stage, we started coding to create OPH3D. However, some parts of the concept needed more refinement, design, and user testing. We also created micro-interactions and formalized a style guide. At this point, we began testing OPH3D with users in real-world environments in Montreal (2023), Detroit (2023), and Phoenix (2004).
8. Cadaver labs, Personal interviews & User tests
As mentioned earlier, there were a total of 4 large-scale tests and one set of personal interviews online.
8.1. Online interview (2021): Validation of concept
In November and December 2021, we conducted qualitative interviews online. The participants were all surgeons and/or professors from medical research institutes. In addition to the interviews, we invited the surgeons to complete a questionnaire about the concept. The questionnaire included questions about desired features, interface design, and perceived priorities.
Analysis of results from the 1st questionnaire. See in PDF
8.2. Phoenix Lab (2022): Cadaver Lab
In November, the surgeons collaborated with several teams from ROSA Hip to conduct a series of experiments and trial surgeries on cadavers. The primary objective was to test the Shell editor. Additionally, they wanted to reassess their priorities and make sure they were developing the right product.
Shell editor micro-interactions: Slice of the acetabulum and different visualizations of the pelvic bone.
8.3. Montreal Lab (2023): Review & ROM
During our research in Montreal, we conducted extensive testing on various topics. These included understanding the requirements for the Review screen, which serves as the landing page of the app, range-of-motion test interactions, and gathering early insights on the Stem editor. The findings were further refined in subsequent labs.
Stem editor micro-interactions: The user is able to change the position, type, brand, and size of the stem as well as see the stem in 3D
8.4. Detroit Lab (2023): Stem editor
The lab in Detroit had a specific focus on developing the Stem editor. Additionally, there was a small-scale review of the Shell editor. During this time, initial insights were gained regarding the neck cut, which will be further tested in the Phoenix (2024) lab.
8.5. Phoenix Lab (2023): Neck cut
During this lab, we made further adjustments to the Stem editor, Shell editor, and Review screen, with a focus on confirming our theories on working with the Neck cut of the Stem editor.
During the lab, we developed a feature for surgeons who desire Pelvic Tilt. However, this feature received less attention.
9. Documentation for regulatory bodies
Each change made to OPH3D was carefully documented through a Design Control Procedure. This procedure included Acceptance Criteria, a Risk Analysis for the patient, an Impact Analysis that specifically described which sections of the product documentation were modified, and a Verification evidence section to visualize the alterations. The changes were directly documented in the user story. The Product owner and the Developer Engineers were in control of these documents.
Conclussion
Results
We have received a lot of positive feedback from our users, even though the number of users is limited. These users are quite influential in the small orthopedic surgeon market. They always look forward to our product updates and consider our product to be streamlined, fully featured, and different from anything currently available in the market.
We are confident that we are headed in the right direction of development because our user flow is designed to guide users through the intended process. In contrast, many other 3D templating tools on the market are a hodgepodge of features that lack coherence and a clear design, even those with the most extensive feature sets.
Learnings
OPH3D has the potential to be sold as a standalone product, independent of the ROSA ecosystem. However, since it is a product of ZimmerBiomet, the development of OPH3D is closely linked with that of the entire ROSA Hip system. As per the structure of ZimmerBiomet, the ROSA robots and software need to be fully developed before ONE Planner Hip 3D can be introduced to the market.
The field of Medical UX has the potential to provide double benefits by improving the lives of patients directly (through applications that patients use) or indirectly (through applications that practitioners use). This leads to increased satisfaction and also helps in reducing medical errors, preventing medical malpractice, and reducing the costs of medical procedures. In our case, cost of use and precision are two main gains.
Looking for me on LinkedIn?
Appendix
Appendix; the extra bits
This is the part where the research branches out
While not directly relevant to the primary issue we aimed to address, the following information contains valuable insights that influenced some of the design decisions made for the interface.
How is a CT Scan processed?
Our team has extensive expertise in CT scanning, which has enabled us to develop innovative products for hip preservation. One of our notable products is Move Forward, which offers an alternative to hip replacement surgery. Maurice Veerkamp leads this segment of our team. All of our scan engineers utilize a proprietary tool that we created in-house called Arbiter, which is not yet available for commercial use. However, we are working towards developing it as a stand-alone software that can process CT scans of any type.
Current user flow and user pain points for Arbiter. See in PDF
New user flow (so far) for ArbiterONE. See in PDF
Get to know me
Let's work together
I live and work in the Randstad area of the Netherlands (Amsterdam, Rotterdam, Utrecht, The Hague, Leiden, Delft, Harlem, etc).
For the SEO optimization guys. Thank you for your offers. But I am not interested in your services. This is a personal portfolio. I do not seek to have millions of visitors.