Rolner Alliance

Profile Design Guidance


Company Name


Desktop, Mobile

The objective of the employee profile guidance document is to help align designers on shared patterns and components. Sharing these patterns helps them become reinforced throughout the profile experience as well as across platforms.


Now that domain profiles live in a shared location, there is a growing concern that the profiles feel too dissimilar. ADP leadership wanted to see a more cohesive experience. The profiles feel like they are designed by multiple when it should feel like it’s one designer. Designers are struggling to create these experiences because design decisions on patterns are silos within their teams.

Main Goals

  • Document all shared patterns and components
  • Make it accessible to UX designers, UX Writers, and developers connected to employee profile projects
  • Created a guidance document that would be platform-agnostic, so that it’s useful to all ADP platforms

This page is the starter page. Versions of this document were created in Figma. With Figma, we made the documentation accessible to all product team members with a Figma account. The main purpose of this document is to be a record, a record of all the agreed-upon components and patterns for a cohesive profile experience.

We offered interactive layout examples that designers could copy and paste into their sigma files to speed up their design process.

This screen highlights a big concern our director had. Many of the pages in the guidance document felt far too prescriptive. He wanted us to push for recommendations, but to stay clear from giving specific directions. Being too prescriptive would have put far too much responsibility on our team.
We are not subject-matter experts (SMEs) for other domains and should not put ourselves in that position.

The guidance content has been reduced since receiving that critique.

Some pages offer examples of preferred profile layouts
The newest addition was the card anatomy page. This page is a card homunculus; it contains every component that a card design could use. These components are also what we agreed makes sense for a profile experience. Every component is tagged with a numbered badge. This badge number also matches a component name in the directory list. Badge and component names are links. These links send designers to pages with more information about that component.
If a designer selects a link on the card anatomy directory page, they are segued to a page that gives guidance on that specific card component.