|
SKIP AHEAD TO: 🔑 Access Requirements and Navigation 1. Action: Review Creation and Publication Health |
An advanced guide for optimizing user adoption and fixing friction points in guided processes.
What is the Flows Dashboard?
The Flows Dashboard is designed to give Content Creators and Admins a centralized view of how guided step-by-step processes are performing. This dashboard makes it easier to:
- Gauge Engagement: See the percentage complete and not started for each Flow.
- Identify Friction: Drill down into individual steps to pinpoint exactly where users drop off or encounter errors.
- Audit Creation: Track Flow creation volume and monitor publication status.
Note: Not all Spekit organizations have the Flows feature enabled.
🔑 Access Requirements and Navigation
To start, ensure your organization has Trackable Links enabled and you have Account Admin, Team Admin, or Expert-level access.
- Step 1: Open the Spekit Web App.
- Step 2: Navigate to the Analytics tab.
- Step 3: Click on the Flows dashboard to view all metrics.
1. Action: Review Creation and Publication Health
This section provides high-level metrics for auditing the pace of flow creation and the status of published guides.
Key Flow Governance Metrics
| Data Point | What It Measures | Actionable Insight |
|---|---|---|
| Total Flow Creators | Total number of unique users who have created a Flow. | Identify Experts: Find and empower your Flow creation specialists. |
| Total Flows Created / Total Published Flows | The total volume of Flows developed and actively available to users. | Track Publication Rate: Ensure your creation team is converting drafts into published, accessible content efficiently. |
| Last Created Date (e.g., "7 days ago") | The time elapsed since any new Flow was created. | Monitor Velocity: If this number is high, content creation may have stalled; investigate roadblocks. |
| Last Published Flow (e.g., "2 days ago") | The time elapsed since any Flow was last updated or published. | Verify Freshness: A low number confirms active maintenance, which is essential for guided processes. |
| Flows Created (Bar Chart) | Historical trend showing Flow creation volume over time. | Resource Planning: Use historical data to anticipate resource needs during large projects or system updates. |
2. Action: Audit Flow Performance and Errors
The Flows table provides the usage and error statistics required to manage your library.
Flows Table Details
| Data Point | What It Measures | Actionable Insight |
|---|---|---|
| Audience Size | The number of users targeted by the Flow. | Scope Check: Ensure the Flow is published only to the necessary user groups. |
| % Completed / % Not Started | User engagement with the Flow. | Identify Gaps: A high "% Not Started" suggests poor promotion or relevance. A low "% Completed" suggests friction. |
| Status (Published / Draft) | The current availability of the Flow to end-users. | Governance: Audit "Draft" Flows to see if they should be completed and published. |
| Number of Errors | Total errors encountered since the last publish date. | Fix Critical Bugs: High error counts indicate the Flow is broken or the underlying application has changed. **Prioritize immediate repair.** |
| Flow Link | Direct link to the Flow. | Troubleshooting: Use this link to quickly access the Flow and debug issues identified by the "Number of Errors" metric. |
3. Action: Pinpoint and Resolve Friction Points
The Flow Drilldown table allows you to isolate a specific Flow and analyze its performance step-by-step to find exactly where users are struggling.
Flow Drilldown Table Details
| Data Point | What It Measures | Actionable Insight |
|---|---|---|
| Step Index | The position of the step in the Flow (e.g., Step 3 of 5). | Location: Identifies the exact point of failure within the sequence. |
| Step Name / Step Description | The content and target of the instruction. | Review: Audit the description and target element to ensure clarity and accuracy. |
| Total Errors | Number of errors in the specific step since the last publish date. | Friction Indicator: A high count here indicates the target element moved, the description is confusing, or the user is getting stuck. |
| ✅ High Error Counts (Resolution) | ❌ High % Not Started (Resolution) |
|---|---|
|
Resolution for High Step Errors Action: Re-record the specific step immediately. Verify that the target element (button, field, etc.) still exists in the application. |
Resolution for Low Usage Action: Promote the Flow! The guide isn't discoverable. Use a Spotlight or link it to a relevant Spek. |