top of page

Making complex enterprise data workflows clear

4 hours ago
2 min read

What I did: Simplified complex admin workflows for MODIS (Microsoft Organizational Data Ingestion System), enabling secure data imports from SAP, Workday, and Oracle into M365.

Role: Lead content designer

Impact: Completed 251 content design requests, improving clarity across workflows.


The challenge

Enterprise customers need accurate organizational data to power Microsoft 365 experiences. But importing data from SAP, Workday, and Oracle involves complex workflows, terminology, and decisions affecting data quality, privacy, and compliance.


Making complex workflows clear

I partnered closely with product managers and designers to simplify administrative experiences across data connections, attribute mapping, validation, and publishing.

  • Clarify: Reworked technical instructions to help admins understand what information was required and what would happen next

  • Simplify: Reduced unnecessary language, standardized terminology, and made complex steps easier to follow

  • Collaborate: Worked through ambiguous requirements with PMs and designers, balancing clarity, technical accuracy, and privacy considerations


A closer look: Small words, important decisions



BEFORE

Review your custom attributes and confirm the data types. These imported custom attributes cannot be renamed. Custom attributes are not required by any Microsoft 365 and Viva applications. To change custom attribute names, update the CSV and reimport your data.

AFTER

Review your imported custom attributes and select a data type for each entry. Once set, these attributes cannot be renamed, but changes can be made by updating the CSV and reimporting your data.

WHAT CHANGED

  1. Consolidated 4 choppy sentences into 2 for a more natural flow

  2. Removed "not required" wording, which belonged in an earlier workflow

  3. Reduced copy from 49 to 39 words (20%) while preserving critical details


More examples


WHAT CHANGED

  1. "When data is shared" feels passive and abstract

  2. Use more active language to clearly explain the consequences



RECOMMENDATIONS

  1. Shifted focus from the admin to the problem, offering alternatives based on urgency:

    • Your organizational data connector needs attention. (Less personal)

    • There's an issue with your organizational data connector. (More urgent)

    • Action needed: Review your organizational data connector. (Most urgent)


Impact


What people are saying


 
 
bottom of page