Please log in to continue
WalkMe stores your data in the region chosen during account setup.
We have data centers in the US and EU that follow local privacy and compliance laws. If you're not sure which region to select, check with your admin.
UI Design is about how your WalkMe implementation looks and feels, including the color schemes, button shapes, font choices, animations, and all the visual aspects that facilitate user interaction. UI Design is often likened to graphic design but with a focus on interactivity. It's about creating aesthetically pleasing interfaces that are consistent, cohesive, and effectively guide users through the product's interface.
Consistent, branded assets fosters end-user trust, reduces content development effort, and helps create streamlined, efficient deployments for your project.
Design approach can differ depending on the end-user audience of your software.
Not sure what company brand guidelines look like? See ours here.
The Project Lead should communicate design expectations to stakeholders during the Kickoff and Discovery stages of an implementation.
Example language for the Digital Adoption Team to use with your stakeholders:
“[Company] has a standard CSS format that is used across all apps in the enterprise. The design standard is easily deployed, scalable, and matches [Company] brand requirements. The standard design will be applied to your Editor upon creation.”
Some stakeholders may want a custom, localized design that differs from your global standard. Here's how the delivery resources on the Digital Adoption Team should handle those conversations and set proper expectations.
Key talking point: Global design is easiest for scaling and maintenance.
Ask your stakeholder: Do you have someone to handle upkeep if changes are needed?
Key talking point: Changing visual elements (via CSS) is the easiest/lowest level of effort for custom design, while changing HTML takes time/development work. In general, removing design aspects from WalkMe's templates requires less effort than adding new design aspects.
Ask your stakeholder: Are you prepared to absorb adjustments to a project timeline if needed, to accommodate additional time needed for adding design aspects to templates?
Key talking point: If a design deviates significantly from the existing HTML structure, it may introduce fragility and risk.
Ask your stakeholder: Do you have someone to handle upkeep if changes are needed? Is this a high-visibility item that would cause significant distress if it was broken?
Key talking point: Understanding level of accessibility compliance is important.
Ask your stakeholder: Does your organization require UI elements follow strict accessibility standards? Ex. color contrast, keyboard accessibility, etc.
Watch these two videos to see how three customers have utilized DAP implementations as a way to reinforce their unique brands with their users. Discover how characters, colors, and a focus on improving users' experiences led to small changes that made big impacts.
This customer brought a Designer to his centralized program team to do an in-depth brand for his DAP Center of Excellence, to support continued stakeholder awareness, professionalism, and scale.
Creating and Testing CSS - Tips from Experts