Dandy
The original SOP (Standard Operating Proceedure) was frequently misunderstood, especially by overseas designers, some that were using translation tools. Key issues included language barriers, misinterpretation of standards, and lack of awareness from systems teams—resulting in costly model errors and confusion across departments.
The existing SOP created widespread confusion among both domestic and overseas designers, often leading to inaccurate model production. These errors misled dentists, resulting in unnecessary remakes and increased operational costs.
Key challenges included:
Misinterpretation of Standards: Designers often misunderstood key instructions, causing errors in model creation and misattribution of issues.
Language Barriers: Overseas teams relied on translation tools, but the SOP wasn't written with multilingual clarity in mind.
Communication Gaps: Systems teams lacked insight into the day-to-day challenges designers faced, leading to ineffective training and misaligned updates.
To resolve these issues, I applied UX principles to redesign the SOP with a user-first mindset:
User-Centric Rewrite: Rewrote the SOP with clear, accessible language optimized for both native and non-native English speakers. Chose terms compatible with translation software.
Improved Navigation: Added divider bars and anchor links to streamline document navigation, helping users find answers quickly and reducing missed details.
Proactive User Support: Used Slack channels to gather insights directly from users, uncovering pain points and recurring confusion that informed the redesign.
Iterative Refinement: Monitored usage via Guru Cards and Google Sites analytics, adjusting content based on feedback and regional discrepancies.
Cross-Team Collaboration: Facilitated discussions between managers, designers, and systems teams to ensure alignment. My dental background helped bridge communication gaps and build empathy for users.
The redesigned SOP led to more accurate model production, fewer remakes, and better collaboration across teams.
By prioritizing usability and continuous feedback, I transformed the SOP from a static reference into a dynamic, evolving tool. The project not only streamlined workflows but also helped systems teams better understand the realities of designer challenges—paving the way for long-term improvements.
By treating the SOP as a product, I applied UX principles—usability, clarity, and iteration—to transform it into a living resource that actively supported users. The result was a smoother workflow, faster onboarding, and deeper cross-functional alignment that laid the groundwork for scalable process improvements.