Research Insights 



I conducted stakeholder interviews, user surveys, and content audits, and the research revealed three recurring pain points:

Fragmented Access – Resources were scattered across email threads, shared drives, and outdated wikis, making it difficult for users to locate product information.

Onboarding Bottlenecks – New team members reported that it often took weeks to locate the appropriate training or process documentation, slowing their ramp-up.

Inconsistent Content – Multiple versions of similar resources were scattered across different places, leading to confusion and inefficiencies.








Design Approach





Site MapTo bring clarity and scalability, I created a structured site map anchored by a Home Page with five main sections: News, Enablement, Processes, Onboarding, and Initiatives.

I also built in flexible “sub-article” pages that could fit under multiple categories, ensuring the system could grow with the organization. This structure balanced immediate usability with long-term scalability.








Wire-framing
Wireframes were designed for long-form readability with seamless access to supporting Workday Success Plan resources.

There were four main goals of the wireframes:

  1. Focus on long-form readability
  2. Content hierarchy
  3. Support of contextual links and resource modules
  4. Organization of supporting materials






    “Wireframes were designed for long-form readability with seamless access to supporting Workday Success Plan resources.”







    Discovery: Balancing Density and Usability
    In discovery, I quickly realized one of the biggest pain points: sections like Processes and Enablement were overflowing with long, detailed documentation. The conflict was clear—too much detail made the site unusable.

    The resolution came with collapsible groups, which gave users a way to scan at a glance and expand only when they wanted the detail. 

    They were able to achieve these goals:

    1. Manage content density 
    2. Reduce visual clutter 
    3. Support different user needs
    4. Scalable structure