- When you need stronger HR service delivery orchestration outside of Workday
- If your employee support experience is primarily run through ServiceNow and you require richer HRSD workflows, dashboards, and cross-enterprise workflow orchestration, ServiceNow Employee Journey Management may be more suitable.
- When you want a Teams-first employee experience layer with published, modular pricing
- If your workforce operates primarily in Microsoft Teams and you need communications/communities/learning/insights surfaced there, Microsoft Viva may provide a more direct surface.
- When you require strict task validation and compliance-grade completion tracking
- Community feedback indicates Journeys steps can sometimes be completed without underlying task verification; regulated onboarding and compliance workflows may require stronger enforcement mechanisms.
- When you lack a change-management operating model
- The value of Peakon and Journeys depends on leaders acting on insights and on teams maintaining journeys and knowledge; without that operating model, tooling investments may not drive the intended KPI changes.
- When procurement requires transparent, self-serve pricing
- Workday pricing is typically quote-based with add-on SKUs; smaller organizations may find this procurement model burdensome.
- Current limitations acknowledged or implied via community discussions
- Journeys task completion and enforcement
- Risk that a journey’s completion state does not equate to process compliance, depending on configuration.
- Distribution constraints
- Business Process distribution recipient limitations have been reported in some contexts
- Pre-hire distribution constraints have been reported
- Feature requests
- Time-delayed steps and richer card formats are commonly requested enhancements
- Product cohesion
- Post-acquisition integration of Peakon into Workday has led some practitioners to report operational separation or administration friction
- Roadmap / release timing
- Workday issues biannual releases and periodic service updates; this report does not include specific release commitments for Journeys features.
- Scale limitations
- Not explicitly evidenced in the sources reviewed for Journeys/Employee Experience.
- Security/compliance considerations
- Not identified as gaps in public sources, but buyers should validate Peakon confidentiality/anonymity controls and data separation/integration boundaries.
- API limitations or integration constraints
- Peakon integration scheduling is reported to be controlled on the Peakon side in some implementations.