Module 6 · Analytics
Analytics
A procedure that people abandon halfway is telling you something. Analytics show where people stop, restart or flag a step, so owners know what to fix first.
Example
Reading the signals
In the demo, usage is counted in your own browser. Follow a procedure, leave halfway, and the drop-off appears against that step.
- Step People follow “Handle a refund request”
- Exception Most stops happen at “Outside the standard window”
- Source Flags say the escalation rule is unclear
- Outcome Owner rewrites the step and publishes v2
Capabilities
What’s included
Each item is marked with its real status. “In the demo” works today in the public Studio demo, which runs in your browser with sample data. “Planned” is on the roadmap and not available yet.
Usage
- Starts and completions per procedureIn the demo
- Drop-off by stepIn the demo
- Restart countsIn the demo
- Feedback flags on stepsIn the demo
- Execution durationPlanned
- Decision-branch analysisPlanned
Improvement
- Recent changes alongside usageIn the demo
- Searches with poor resultsPlanned
- Content freshnessPlanned
- Before and after comparisonsPlanned
- Exportable reportsPlanned
In the demo works today in the public Studio demo (runs in your browser, sample data)In development being built now, not yet availablePlanned on the roadmap, not available yet
Related
Works together with
See it working on a sample procedure.
The Studio demo runs in your browser with sample data. No account needed.