At a glance
Of every audit finding that landed on the configured Mural in the last 90 days, the percentage moved into the Done frame. The headline number for “is the workshop-led audit cycle actually delivering, or is it just collecting and discussing?” Pair with workshop cadence to grade post-session follow-through.
Calculation
Calculated automatically from your Mural data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US wellness brand on Adobe Commerce runs the audit-triage Mural with quarterly workshops (last on 25 Mar 26). Snapshot taken on 02 May 26. Trailing 90 days: 03 Feb 26 → 02 May 26 (89 days).
The two channels are running similar rates, so neither is the dominant problem. Looking at severity:
Same shape as Miro’s example: criticals get done, highs mostly, medium half, low under half. The composite 66% is dragged by the long tail.
What the merchant does: identifies that Mural is not the right place for low-severity items. Reconfigures the auto-dispatcher to send only
severity:high and severity:critical to Mural, with medium / low going to a separate Slack-thread digest. Within 90 days the rate climbs to 80% as the denominator stops including items the team never intended to deliver.
Compare to 30 days ago. Same brand, snapshot on 02 Apr 26: rate was 78%, in good band. The drop from 78% to 66% over a month is the normal post-workshop dip; the next workshop is scheduled for 25 Jun 26 and historical pattern says rate will recover to 76-80% before then.
The dangerous reading: rate at 38% with 50+ items created in the window. That is “we are running workshops but never delivering”; the alert fires below 50%. By 38% the team has lost a quarter’s worth of intake to the abandoned tail; intervention required (capacity, scope, or stop running workshops without delivery follow-up).
Healthy comparison values for Mural-led teams:
- Steady-state (no recent workshops): 75-85%
- 0-2 weeks post-workshop: 60-70% (transient dip)
- 4-6 weeks post-workshop: 75-85% (recovery)
- Sustained <55% across multiple workshop cycles: process problem
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Mural’s own dashboard: Mural does not provide a native flow-rate dashboard. The closest manual reconciliation is to filter by tag and inspect creation vs. Done-frame timestamps over the last 90 days.
Mural app → open the configured mural → Tags panel → vortexiq:finding → Outline panel → manually count stickies in the Done frame vs. all tagged stickies created in the trailing 90 days.
For most teams the manual reconciliation is impractical (40-60 stickies with creation-date filtering by hand), which is why this card exists.
Why our number may legitimately differ from a manual count:
Cross-connector reconciliation:
Known limitations / merchant FAQs
Why does my rate drop 10-15 points after every workshop? Workshop sessions add 10-30 stickies to the denominator overnight. The numerator (closures) only catches up over the following 4-6 weeks. Expected pattern, not an alert. Configure the gauge to expect bimodal behaviour by averaging across two workshop cycles rather than reading the instant value. My rate is 100% but I only have 3 stickies in the window. Is that real? Statistically thin. With under 10 stickies, the rate is too noisy to trust. Look at the absolute Resolved count or extend your auditing routine before relying on this number. The card is most meaningful at 30+ items in the window. The team uses Mural for facilitation but does delivery in Jira. Should this card stay green? Probably not, the question is whether the audit-feed dispatches to Mural at all. If the team’s delivery happens in Jira, route audit findings to Jira and disable the Mural target. Mural-with-no-audit-routing is fine; Mural-as-decoration with unhappy resolution rate is misleading. Why is my rate higher than my Miro counterpart’s? Less common but possible. Two reasons: (1) The Mural team has tighter workshop cadence and clears the post-session tail aggressively; (2) The Mural workflow excludes low-severity items from intake while Miro accepts everything, raising Mural’s denominator quality. Does deleting an abandoned sticky improve the rate? No. Deletion removes from both numerator and denominator and pulls the historical rate slightly toward the average; it does not artificially lift the visible number. The clean way to “decline” a finding is to move it into Done with a comment explaining the decision; this counts as resolved (because the team made an explicit call) and is honest about the team’s actions. My rate is sub-50% but the team’s morale is high. What gives? Workshop-led teams sometimes confuse “we had a good discussion” with “we delivered”. The rate measures only the second. If morale is high but rate is low, the team is enjoying the discovery loop without closing it; the founder or operations lead should align expectations before the gap becomes visible in customer outcomes (slow site, unfixed bugs, drift). Should this card be on a designer’s dashboard or only an ops lead’s? Both. Designers benefit from seeing whether their workshop output is getting delivered (the rate IS their feedback loop). Ops leads benefit from seeing whether the delivery system is keeping up with intake. Different use, same number. A workshop frame got archived. Will the items still count? Yes. Archived frames remain timestamped and counted unlessexclude_archived: true is set on the connector. Archive does not equal “delete from metric”; if the team wants to retire stale items, move them to Done first or apply vortexiq:reference.
Why is the alert at 50%, not 60% or 70%?
50% is the line where intake equals exit. Above 50% the team is net-clearing the queue (good); below 50% the team is net-accumulating (bad). The threshold is the inflection point, not the target. The good band starts at 75% because that is the empirical median for healthy Mural-led merchants.