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.
| What it counts | Stickies / shapes on the configured Mural, tagged vortexiq:finding, where lastEditedAt is older than 14 days AND the item is NOT inside a frame named “Done”. The clock resets on any edit, including position changes, tag edits, comment additions, or assignment changes. |
| Mural / room scope | The single Mural configured on the connector. Sub-team murals not visible to the connector OAuth user are excluded. |
| Status filter | Only “open” items count (items inside the Done frame are excluded by definition). |
| Item type filter | Stickies, shapes, and icons with the vortexiq:finding tag. Comments-only edits count as activity. |
| Resolution counts | An item leaves the abandoned bucket the moment any edit happens. Comment, tag, position, all reset the clock. Workshop-replay (when a facilitator clones a frame for a follow-up) does NOT count as activity on the original items. |
| Threshold rationale | Same as Miro / Asana / Jira: warn at 5, critical at 15. Calibrated against typical merchant audit cadence; Mural workshop-week spikes are absorbed by the 14-day window. |
| Workshop nuance | If the team flags a known-workshop window (workshop_grace_days: 14), the abandonment clock pauses for those 14 days post-workshop, preventing a false-positive crisis spike. |
| Time window | RT (rolling 14-day idle calculation, refreshed every 60 seconds). |
| Alert trigger | >5 (warn) / >15 (critical) |
| Sentiment key | vortexiq_findings_abandoned, threshold-typed with warn at 5 and critical at 15 |
| Roles | owner, operations |
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:| Sticky | Tag | Last touched | Days idle | Notes |
|---|---|---|---|---|
| S-217 “PDP video autoplay regression” | severity:high | 18 Apr 26 | 14 | Just hit threshold. |
| S-220 “Schema markup missing on collection” | severity:high | 16 Apr 26 | 16 | Owned by Marie; workshop output. |
| S-225 “Klaviyo webhook silent failure” | severity:medium | 14 Apr 26 | 18 | No owner assigned. |
| S-231 “Cart drawer mobile glitch” | severity:high | 12 Apr 26 | 20 | Engineering-bound; never escalated to Jira. |
| S-238 “Newsletter pop-up timing off” | severity:low | 08 Apr 26 | 24 | Low priority; nobody picked up. |
| S-242 “Image optimisation gaps” | severity:medium | 04 Apr 26 | 28 | Workshop suggestion; no follow-up. |
| S-247 “GA4 purchase event misfire” | severity:high | 30 Mar 26 | 33 | Marketing-bound; misclassified as low. |
| S-250 “Adobe order-status email layout” | severity:medium | 27 Mar 26 | 36 | Stuck in design review. |
| S-253 “Returns flow checkout copy” | severity:low | 26 Mar 26 | 37 | Forgotten. |
Sibling cards merchants should reference together
| Card | Why pair it with Abandoned Findings | What the combination tells you |
|---|---|---|
| VortexIQ Findings Open | Abandoned is a subset of Open. Track the ratio. | Abandoned / Open above 30% means workshop output is not converting to delivery. Below 10% is healthy. |
| Finding Resolution Rate (90d) | The flow ratio. Abandoned is the leading indicator. | Rising abandoned + falling resolution rate = team is collecting but not delivering. |
| Avg Time-to-Fix (days) | Cycle time on the resolved subset. Compare against the abandoned tail. | Fast time-to-fix + rising abandoned = team fixes the easy ones during workshops, leaves the hard ones. |
| Throughput Trend | Closure rhythm. Look for the bimodal workshop-week pattern. | Flat throughput + rising abandoned = team running workshops without delivery follow-through. |
| Miro Abandoned Findings | Visual-collab peer. | Same metric, different ownership pattern. Miro abandonment is individual; Mural is session-level. |
| Jira Abandoned-Findings Burst | The Jira-side equivalent. | If both spike together, the cross-tool capacity issue is real. |
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:
| Reason | Direction | Why |
|---|---|---|
| Comments count as activity | Ours lower | A comment thread refreshes lastEditedAt. A merchant counting “items not moved” by hand may include items that have comment activity. |
| Workshop grace window | Ours lower if configured | If workshop_grace_days: 14 is set, items touched during a flagged workshop have their idle clock paused for 14 days. Manual counts do not apply this grace. |
| Frame-name match | Ours higher | If the Done frame is renamed and not updated in the connector config, items in the new “Shipped” frame still count as open and therefore eligible for abandonment. |
| Hidden / private frames | Ours lower | Items inside frames the connector cannot read (sub-team permissions) are invisible to Vortex IQ but a merchant with full access sees them. |
| Polling cadence | Ours stale up to 60s | Same as Findings Open. Sub-minute edits lag. |
| Time zone | None | Idle calculation is rolling against UTC, no period boundary. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
miro.mir_vortexiq_findings_abandoned | Same metric, different visual-collab tool. Different abandonment shape (Miro is continuous; Mural is workshop-bursty). | Mural abandonment correlates with workshop cadence; Miro abandonment correlates with individual capacity. |
jira.jir_vortexiq_findings_abandoned | Definitional twin on Jira. Jira’s enforced workflow makes abandonment less common but more meaningful when it occurs. | Jira abandonment is a process failure; Mural abandonment is often a follow-up failure. |
asana.asa_vortexiq_findings_abandoned | Same metric on Asana, the lightweight-PM peer. | Asana enforces explicit task ownership; abandonment often traces to one assignee. Mural abandonment traces to a session, not a person. |
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.