Skip to content
Contact us ES Contact us ES

SAI case study

Four content types and a publishing workflow the company runs on its own

Products, courses, events, and faculty, each with its own fields, and a review on the live page before publishing.

  • Type of workContent architecture and web development
  • IndustryOrthopedics and trauma
  • Case studySAI

The starting point

Every change went through a developer.

SAI's information came from different teams, and every change to the website depended on a developer.

Engineering wrote the technical data sheet, the surgical technique was in a congress presentation, and clinical judgment came from Medical Affairs. Each piece had a different owner, and none was written to be published.

We gathered information with all the teams together and then with each one separately, to find out who had each piece of data and who had to approve it.

What we found

  • Information spread across teams
  • No validation workflow
  • Changes that depended on a developer

The approach

A form for each content type.

We created custom forms for products, courses, events, and faculty members; a bilingual template that shows whether each data point is approved; and a draft review on the actual page before publishing.

Each content type has its own fields: 106 for a product page, 38 for a course, 9 for an event, and 4 for a faculty member.

Engineering fills in a bilingual template that shows which data points are approved and which aren't. Content is entered as a draft and reviewed in preview on the same page the public will see before it's published. Medical Affairs sets the terminology, and it's used the same way on the product page, in the video, and in the brochure.

What we did

  • Product
  • Course
  • Event
  • Faculty member
  • Bilingual template
  • Draft review

The work

Past courses in a slider, each with its own page.
A course's path, from left to right: courses and events, upcoming courses, a course page, past courses, and a past course page.
An upcoming course and the events and congresses page.
On the phone: past courses, a course page, and the product slider.
Up close: past sessions and surgical technique videos.
SAI Lab and a product page with its video.

What stayed in place

  • 106fields per product
  • 38per course
  • 9per event
  • 4per faculty member

Services applied in this case study

See all services

Content architecture

We model products, documentation, courses, and other content before designing how they're displayed. We define what information exists, how it relates, and the different ways a person should reasonably be able to find it.

Website development

We build websites the team can manage for medical device companies where products, documentation, languages, forms, and content need to live together within a structure that can keep growing.

Team training

We prepare the people who will use and maintain the digital structure to handle routine tasks on their own: adding products, updating documents, publishing content, and recognizing when a change needs a different level of intervention.

SAI manages its own content, with the approval status of each data point visible.

Contact us Take the self-assessment