The front door. A new team should understand what Pendo is, why Actimize uses it and who to ask within a minute.
What is Pendo
A plain-language overview of what Pendo does and how it applies to Actimize.
Why we use Pendo at Actimize
What are we trying to achieve? Built around our four strategic goals, shown below.
Who to contact
The Actimize COE team (Peter and Sigal), the Pendo team, and where to ask for help.
What we are trying to achieve
Where a team starts. The rollout plan shows the whole programme. The 30/60/90-day plan shows what one team does once it is on.
Rollout plan at Actimize
Which teams come on, in what order and when. Act One goes first, then the other solutions.
30/60/90-day plan
What a new team should do in its first 30, 60 and 90 days.
Training outline
What each training covers and who it is for.
Permissions and roles
Which role to give each user, and how to request access.
What a team needs to get Pendo live and keep the data clean.
Installation requirements
What a team needs before installing.
Metadata
The metadata we need to pass to Pendo, and why we need it.
The shared standards that keep one Pendo subscription tidy as more teams join.
Naming conventions and best practices
How we name pages, features, tracks, segments and guides, and the habits that keep them easy to find and reuse.
Where Actimize can see what Pendo is changing, and share it.
Use case tracker
One tracker for all teams: pain point, planned change, expected outcome and status. Each entry links to a strategic goal.
Success stories
Short examples of what Pendo has helped Actimize teams achieve.
ROI story template
A simple template for writing up the value of a change.
Use case tracker: how it could look
Illustration only. Two use cases from our planning sessions. Wording and status are for discussion.
| Team | Pain point | Planned change | Expected outcome | Strategic goal | Status |
|---|---|---|---|---|---|
| SAM | Filter configurations are lost between sessions. We don't know which widgets matter by role. | Track widget clicks and filter saves. Review adoption of the New Workbench. | More than 60% of users interact with two or more widgets per session. | Increase adoption of high-value features | Baseline to capture |
| ActOne | Tasks to change a step are spread across several screens. | Measure the step-change funnel. Guide users off the legacy screens. | More than 70% Workflow Manager adoption. Half the clicks. | Reduce time-to-complete critical workflows | Baseline to capture |