Brief Overview
Incorporating IT effectively is one of the most effective ways to accelerate scale of your program. The DAP Architect (often an IT Architect, IT Engineer, or IT Manager) is one of the required competencies in the Standard DAP Roles and Responsibilities and will be critical for your success in operationalizing this component.
There should be two aspects of an IT Operating Model:
- New Application Onboarding
- Ongoing Application Needs
How This Impacts Your Program
❌ The following are common pitfalls and adverse outcomes of not having an IT Governance strategy:
- No deployment strategy → Bugs, issues, and inhibits scale
- No technical validation prior to project initiation → 2-3x elongation of project timeline
- No user permissions oversight → Potential security risk
- No standardized segmentation strategy → Inability to analyze trends across user journey
Who is Involved
Creating and monitoring an IT Governance model is a cross-functional endeavor. The following outlines important groups and their key responsibilities:
Your WalkMe Account Team
- Editor feature flag configuration
- Hosting configuration
- API integrations
- Supports audit/security review questions
IT
- SSO
- Extension deployment plan & execution
- IDP connection
- Security reviews
- Change management (process) eg. browser support
Refer to the following article: DAP Roles and Responsibilities
Product
- Test & Prod system access
- Snippet deployment plan & execution
- Additional information/ variables for user-level attribute tracking or segmentation
- Release cycle roadmap & timeline for content maintenance
DAP CoE Team
- New Editor generation
- Determines hosting method
- Configures DXA
- Segmentation setup
- Reporting setup
- User Management/ Permissions
- Content naming conventions and folder governance
Key Considerations
When creating Standardized Operating Procedures for IT, consider the following:
- How does your company make software purchasing decisions?
- What is the architecture of your IT organization? Who are the primary sponsors of WalkMe and where do they sit?
- Is your IT organization siloed, and if so, how might this add risk to compliance with central CoE governance?
- Does IT hold the budget for WalkMe? Is there any cost-sharing mechanism in place for licenses or service delivery?
Sample Flow Diagram
Consider having your first deliverable be a flow diagram noting the phase, responsible stakeholder(s), and high priority activities. You will likely have a Content Delivery Flowchart for your content delivery phases/ownership - if you create a separate IT-friendly flowchart, ensure the phases align with the phases in your Standardized Content Delivery.

Get Started
Your People
- List the current champions and potential detractors in your IT organization
Your Focus Areas
- Discuss typical IT risks at your organization (in context of both WalkMe and other cross-functional initiatives)
- Use these to prioritize which areas of IT involvement with WalkMe you need to start with
Additional Resources & Peer Connections