The Flows Dashboard gives you a centralized view of how your guided step-by-step processes are performing across your organization. From monitoring creation velocity and publication status to identifying exactly where users are dropping off or encountering errors — this dashboard helps you keep your Flows effective, accurate, and discoverable.
⚠️ Legacy Feature Notice: Flows is a legacy feature available only to organizations that had it enabled prior to deprecation. If you do not currently have access to Flows, this dashboard will not be visible in your Analytics tab.
📌 Quick-Jump Topics
1. What is the Flows Dashboard?
The Flows Dashboard is designed to give Content Creators and Admins a complete picture of how guided processes are being created, published, and used. It helps you:
- Gauge Engagement: See completion and not-started rates for each Flow at a glance.
- 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 across your library.
2. Getting Started with the Flows Dashboard
Access Requirement: You must 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.
3. How to Review Flow Creation and Publication Health
Start here when: You want a high-level view of your Flow library's health, monitor whether new Flows are being created consistently, or confirm that drafts are being published and made available to users.
| Metric | What It Tells You | What to Do If It's Concerning |
|---|---|---|
| Total Flow Creators | Total number of unique users who have created a Flow | A low count suggests Flow creation is concentrated — identify and empower additional creators to distribute the workload |
| Total Flows Created | Total volume of Flows developed across the organization | Cross-reference with Total Published Flows to understand how many are still sitting as drafts |
| Total Published Flows | Total number of Flows actively available to users | A large gap between Total Created and Total Published signals drafts that need to be completed and released |
| Last Created Date | Time elapsed since any new Flow was created | If this number is high (e.g., more than 7 days), content creation may have stalled — investigate whether creators are facing roadblocks |
| Last Published Flow | Time elapsed since any Flow was last published or updated | A recent date confirms active maintenance, which is critical for guided processes tied to live applications |
Flows Created (Bar Chart)
This chart shows Flow creation volume over time. Use it to:
- Identify periods of inactivity where creation has stalled
- Correlate creation spikes with system updates, new tool rollouts, or onboarding initiatives
- Plan content resources for upcoming projects that will require new Flows
✅ Creation and Publication Health Best Practices
| ✅ Best Practice (Do This) | ❌ Avoid This! |
|---|---|
| Regularly audit your Total Flows Created vs. Total Published Flows ratio — a growing gap means drafts are piling up and users aren't getting access to content that's ready for them. | Leaving Flows in draft status indefinitely — unpublished Flows aren't helping anyone and create clutter in your library. |
| Monitor Last Created Date and Last Published Flow together — recent creation with no recent publishing suggests a bottleneck in the review or approval process. | Assuming a high Total Published count means everything is healthy — published Flows that haven't been updated in a long time may be broken or outdated. |
| Use the Flows Created bar chart to anticipate resource needs during large projects or system updates and plan accordingly. | Only creating Flows reactively — proactive creation during system changes prevents user confusion before it starts. |
4. How to Audit Flow Performance and Errors
Start here when: You want to understand how users are engaging with your Flows, identify which ones have high error rates, and prioritize which need immediate attention.
The Flows Table gives you a full view of every Flow in your library and its performance metrics:
| Column | What It Tells You | What to Do |
|---|---|---|
| Audience Size | Number of users targeted by the Flow | Confirm the Flow is published only to the necessary user groups — over-broadcasting reduces relevance |
| % Completed | Percentage of targeted users who completed the Flow | A low completion rate signals friction somewhere in the Flow — use the Flow Drilldown table to find where |
| % Not Started | Percentage of targeted users who haven't begun the Flow | A high not-started rate suggests the Flow isn't discoverable or relevant — consider promoting it via a Spotlight or linking it to a related Spek |
| Status | Published or Draft | Audit all Draft Flows — determine whether they should be completed and published or deleted |
| Number of Errors | Total errors encountered since the last publish date | High error counts mean the Flow is broken or the underlying application has changed — prioritize immediate repair |
| Flow Link | Direct link to the Flow | Use this to quickly access and debug a Flow when errors are identified |
What to prioritize:
| Scenario | What It Means | Action |
|---|---|---|
| High errors + high audience size | A broken Flow is impacting a large number of users | Drop everything and fix this immediately — every error is a user hitting a wall |
| High % Not Started + large audience | Users aren't engaging with an important Flow | Promote the Flow via a Spotlight or link it to a relevant Spek to improve discoverability |
| Low % Completed + low errors | Users are starting but not finishing | Review the Flow's length and complexity — it may be too long or the steps may be unclear |
| Draft status + old creation date | A Flow was started but never finished | Decide whether to complete and publish it or delete it to reduce library clutter |
✅ Flow Performance Best Practices
| ✅ Best Practice (Do This) | ❌ Avoid This! |
|---|---|
| Treat Number of Errors as your most urgent metric — a Flow with errors is actively blocking users from completing a guided process. | Monitoring only completion rates — a Flow with zero completions and zero errors may simply be undiscovered, not broken. |
| Review % Not Started alongside Audience Size — a high not-started rate on a large audience is a much bigger problem than the same rate on a small audience. | Ignoring Draft Flows entirely — they represent unfinished work that either needs to be completed or cleaned up. |
| Use the Flow Link to test Flows yourself after any application update — errors often appear when underlying UI elements change without a corresponding Flow update. | Waiting for users to report errors — by then the Flow has already frustrated multiple users and damaged trust in the guided process. |
5. How to Pinpoint and Resolve Friction Points
Start here when: You've identified a Flow with high errors or low completion rates and need to find the exact step where users are getting stuck.
The Flow Drilldown Table lets you isolate a specific Flow and analyze its performance step by step. For each step you can see:
| Column | What It Tells You |
|---|---|
| Step Index | The position of the step in the Flow (e.g., Step 3 of 5) — identifies the exact point of failure within the sequence |
| Step Name / Description | The content and target of the instruction — audit this for clarity and accuracy |
| Total Errors | Number of errors on this specific step since the last publish date |
How to interpret step-level errors:
| Pattern | What It Means | Action |
|---|---|---|
| Errors concentrated on one step | That specific step is broken or confusing | Re-record the step immediately and verify the target element (button, field, etc.) still exists in the application |
| Errors spread across multiple steps | The entire Flow may be outdated | Review the full Flow against the current state of the application and re-record as needed |
| High errors on Step 1 | Users can't even get started | Check whether the Flow's entry point or trigger is still functioning correctly |
| Errors spike after a specific date | An application update likely broke the Flow | Cross-reference the error spike date with any recent application changes and update the affected steps |
✅ Friction Point Resolution Best Practices
| ✅ Best Practice (Do This) | ❌ Avoid This! |
|---|---|
| After fixing a high-error step, republish the Flow immediately — errors reset on republish, giving you a clean baseline to monitor going forward. | Re-recording steps without testing them afterward — always run through the full Flow after any update to confirm the fix worked. |
| Use Step Name and Step Description to audit whether the instruction is still accurate after an application change — the target element may exist but the description may no longer match. | Only fixing the step with the most errors — review all steps in a broken Flow to catch secondary issues before they become problems. |
| If a Flow has a high % Not Started, use a Spotlight to promote it to the relevant audience — a great Flow that nobody knows about isn't helping anyone. | Rebuilding an entire Flow from scratch when only one or two steps are broken — use the Step Index to surgically fix only the affected steps. |
6. Suggested Alerts and Dashboard Agent Questions
📬 Suggested Scheduled Alerts
Use the ellipsis menu (...) on any table or the share icon at the bottom of the dashboard to set up alerts and scheduled deliveries. Here are some high-impact alerts to set up for the Flows Dashboard:
| Alert Idea | Condition | Table |
|---|---|---|
| Weekly Flows performance summary | Scheduled – Weekly | Entire Flows Dashboard |
| New errors detected on a published Flow | Results have changed | Flows Table |
| Flows with high % Not Started | Any results returned | Flows Table |
| Flows with low % Completed | Results have changed | Flows Table |
| New Draft Flows that haven't been published | Any results returned | Flows Table |
| Step-level errors spike on a specific Flow | Results have changed | Flow Drilldown Table |
🤖 Suggested Dashboard Agent Questions
Use the ✨ Dashboard Agent to dig deeper into your Flows data. Here are some questions to get you started:
- "Which Flows have the highest error counts right now?"
- "Which Flows have the lowest completion rates?"
- "Which Flows have the highest percentage of users who haven't started?"
- "Are there any Flows still in draft status that haven't been updated in over 30 days?"
- "Which step in my most-used Flow has the most errors?"
- "How has Flow creation volume changed over the last 90 days?"
- "Which Flows have the largest audience but the lowest completion rates?"
- "Are there any Flows that haven't been published or updated in over 6 months?"