Purpose

• Ensure WalkMe DAP feels like a trusted, invisible extension of the application—not an overlay competing with the UI.

1. Brand Strategy & Ownership:

• DAP positioned as execution support, not training
• Branding intentionally subtle
• Owned by Enablement COE / WalkMe Admin
• Corporate brand applied lightly
• Tone defined: concise, directive, neutral

2. Global Theme Configuration (Admin Controlled)

• Location: WalkMe Editor → Theme / Appearance
• Single global theme defined
• Primary color used sparingly (headers, CTAs)
• Neutral backgrounds to avoid UI conflict
• Button styles standardized
• Font sizes optimized for speed and readability
• High-contrast validation completed
• Control rule: Asset-level overrides are discouraged and governed.

3. Walk-Thru Styling Standards

• Step layout consistent across Walk-Thrus
• Button labels standardized (Next, Continue, Finish)
• Imperative language used (“Select,” “Enter,” “Confirm”)
• One instruction per step
• No mixed styles across steps

4. SmartTip Styling Standards

• Icons standardized
• Text minimal and scannable
• Placement consistent for similar actions
• No overlapping or competing tips
• Colors do not conflict with application UI

5. ShoutOuts & Notifications

• Used sparingly and intentionally
• Message tied to business impact
• Avoid feature announcements
• Visual style matches DAP theme

6. Language & Terminology

• Business process names standardized
• System codes secondary or omitted
• Terminology aligned to Learning Arc taxonomy
• No conflicting guidance across assets

7. Governance & Quality Control

• DAP design standards documented
• Templates enforced
• QA required before production release
• Periodic usability and consistency audits