Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.
At a glance
Of all VortexIQ-tagged stickies on the configured Mural, the count that have not been moved or edited in 14 days. On Mural this number tells a workshop-shaped story: items left behind two weeks after a session are typically forgotten, not deferred. The card is the post-workshop conscience, the place where the team finds the stickies that nobody owned.
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 holds quarterly audit-triage workshops on Mural. Last workshop: 25 Mar 26. Snapshot taken on 02 May 26, exactly 38 days post-workshop. The card returns 9 abandoned, four over the warn threshold of 5. Drilling in:Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Mural’s own dashboard: Mural does not surface a stale-items view. The closest manual reconciliation is filtering by tag and sorting bylastEditedAt.
Mural app → open the configured mural → search tag:vortexiq:finding → use the Outline panel (View → Outline) to see items with their last-edited timestamp → count items above 14 days old that are not inside the Done frame.
There is no native “stale” filter in Mural; this card exists because the manual lookup is laborious and easy to skip.
Why our number may legitimately differ from a manual count:
Cross-connector reconciliation:
Known limitations / merchant FAQs
Why is the abandoned count always high after our quarterly workshops? Because workshops produce intake faster than steady-state delivery can absorb. Two structural responses: (1) configureworkshop_grace_days: 14 so the connector pauses the abandonment clock for two weeks post-workshop; (2) schedule a “post-workshop-2” review session 14 days after each workshop to drain the abandoned tail before it crosses the alert threshold.
An abandoned sticky just got a comment but no movement. The clock reset. Is that right?
Yes, by design. A comment is engagement. The team is still talking about the item, even if nobody has moved it yet. The Resolution-Rate card ultimately catches the case where comments happen but no closure follows.
Why 14 days, not 30?
Same calibration as the other PM connectors: empirically, items idle past 14 days have <20% probability of recovery. 30 days lets too much rot accumulate; 7 days fires too often during normal-cadence weeks.
My team workshops monthly. The window grace stops at 14 days, but our delivery cycle is 4 weeks. Does that work?
For monthly workshops, we recommend workshop_grace_days: 28 rather than the default 14. The connector accepts any integer; the trade-off is that longer grace windows let real abandonment hide for longer. 28 days is the upper end before the alert becomes useless.
Can I bulk-clear abandoned stickies?
Yes, in Mural directly: select all abandoned stickies (Ctrl-click to multi-select after filtering by tag), drag them into the Done frame or a new “Triaged” frame, and the connector will refresh on the next 60-second poll. Be cautious: dragging into Done implies “we delivered the fix” to downstream cards (Resolution Rate, Throughput); use a Triaged frame and tag vortexiq:reference if the team’s intent is “we decided not to do this” rather than “we did it”.
Does deleting an abandoned sticky count it as resolved?
No. Deletion removes it from both Open and Abandoned counts but does NOT count toward the Resolved tally. If the team’s intent is “we did this and now we are tidying up”, move into Done first, then delete after the metric updates.
Why does this matter to a non-engineering merchant?
Because audit findings sitting on a Mural represent decisions deferred. Five high-severity items abandoned for two weeks is roughly £1-3k/month of accumulated avoidable cost (slow conversion, lost SEO, customer-experience erosion). The card forces the cumulative cost into a single number the founder can read in one second.
The same sticky has been “abandoned” twice this month. How do I stop the cycle?
A sticky bounces in and out of abandonment when the team gives it just enough activity (comment, tag tweak) to reset the clock without delivering. The fix is process, not metric: introduce a “definition of done” check on the audit frame, with a facilitator role responsible for moving items into Done when the underlying issue is verified fixed. The cards measure behaviour; they cannot enforce it.
Compared to Miro, why are my Mural numbers more volatile?
Mural’s workshop cadence creates spike-then-drain rhythms that look chaotic compared to Miro’s steady-state flow. Look at month-over-month rather than week-over-week; Mural metrics smooth meaningfully at monthly resolution while Miro can be read weekly.