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 cards on the configured Miro board, the count that have NOT been moved or edited in 14 days. These are the findings that fell through the triage cracks: the team saw them, parked them on the board, and never came back. On a Miro board this pattern is common because cards are frictionless to add but easy to forget; this number forces the abandoned tail back into view.
| What it counts | Cards on the configured Miro board, tagged vortexiq:finding, where modifiedAt is older than 14 days AND the card is not in the rightmost (Done) column. The clock resets on any edit, including position changes, tag edits, comment additions, or assignee changes. |
| Board / frame scope | The single Miro board configured on the connector. Findings on archived frames count too unless exclude_archived: true is set. |
| Status filter | Only “open” cards are eligible (cards in the rightmost column never count as abandoned, by definition). |
| Item type filter | Sticky notes and cards with the vortexiq:finding tag. Comments-only edits count as activity, so a thread with replies in the last fortnight does NOT show as abandoned even if the card position never moved. |
| Resolution counts | A card leaves the abandoned bucket the moment it is touched, not only when moved to Done. Comment, edit, assign, all reset the clock. |
| Threshold rationale | Warn at 5, critical at 15. Why 5? Because a finding ignored for two weeks is statistically unlikely to be picked up later (audit data shows <20% recovery rate after the 14-day mark). Why 15? Because at 15 the team has lost more than the equivalent of a full sprint’s audit detection. |
| Time window | RT (live count over the last 14 days of card-history, 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 Miro 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 DTC homeware brand on Shopify runs all design and ops review on a Miro board. The team is six people; the audit-finding board has been live since 02 Jan 26. Snapshot taken on 02 May 26 (today) at 11:00 BST. The card returns 8 abandoned, two over the warn threshold of 5. Drilling into the board:| Card | Tag | Last touched | Days idle | Notes |
|---|---|---|---|---|
| C-1041 “Remove duplicate hero banner” | severity:medium | 14 Apr 26 | 18 | Dropped during a redesign sprint; nobody re-prioritised. |
| C-1052 “Schema.org missing on PLP” | severity:high | 12 Apr 26 | 20 | Owner left the company 16 Apr; never reassigned. |
| C-1058 “Image alt-text gaps” | severity:medium | 10 Apr 26 | 22 | Marked “later” by design lead; no follow-up. |
| C-1069 “Newsletter pop-up flash” | severity:low | 06 Apr 26 | 26 | Low priority; shipped fix bypass-route, card never closed. |
| C-1071 “Cart drawer mobile glitch” | severity:high | 02 Apr 26 | 30 | Awaiting frontend QA; QA capacity bottleneck. |
| C-1080 “Checkout 500ms latency spike” | severity:high | 28 Mar 26 | 35 | Datadog finding; engineering scoped, then deprioritised. |
| C-1085 “GA4 event misfire on PDP” | severity:medium | 22 Mar 26 | 41 | Tagged for marketing; never claimed. |
| C-1088 “Klaviyo flow webhook stale” | severity:low | 18 Mar 26 | 45 | Forgotten; integration partner alone with context. |
severity:high cards (C-1052, C-1071, C-1080) are the cost-of-inaction in this list, schema gaps hurt SEO weekly, the cart glitch hurts mobile conversion daily, the latency spike hurts everyone. The merchant assigns owners on those three within 30 minutes, leaving the medium / low for the next standup.
Why 14 days, not 7 or 30? Empirically, audit-board recovery looks like this: items touched within 7 days get fixed >70% of the time; items idle 7-14 days get fixed ~40% of the time; items idle >14 days get fixed <20% of the time. The 14-day boundary is the inflection point where the probability of fix drops off a cliff, so it is the most useful “act now” alert.
The flip side: the same brand on 28 Mar 26 had 2 abandoned, all low-severity. Below the warn threshold, no alert. The board was healthy for six straight weeks, then the redesign sprint pulled attention off the audit cadence and the abandoned count climbed to 8 in three weeks. The card surfaces this drift before it becomes 15.
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 the team triages on intake but stops following up. Below 10% is healthy. |
| Finding Resolution Rate (90d) | The flow ratio peer. Abandoned is the leading indicator; resolution rate is the lagging confirmation. | Rising abandoned + falling resolution rate = capacity crunch. Falling abandoned + steady resolution = process improving. |
| Avg Time-to-Fix (days) | Cycle time on the cards that DID get fixed. Compare against the abandoned tail. | If average time-to-fix is 6 days but abandoned is rising, the team is fast on the easy ones and skipping the hard ones. |
| Top Assignees Overloaded | Surfaces the capacity bottleneck. Abandoned cards usually concentrate on overloaded owners. | Cross-reference assignee on each abandoned card; if 3+ trace back to one person, the bottleneck is human, not process. |
| Datadog Active Incidents | If criticals are abandoned while incidents are ongoing, the blast radius compounds. | Abandoned + active incidents = you are accumulating known problems on top of unknown ones. |
| Jira Abandoned Findings Burst | The Jira-side equivalent for teams that mix tools. | Spike on both means cross-tool capacity issue, not a single-tool process gap. |
Reconciling against the vendor’s own dashboard
Where to look in Miro’s own dashboard: Miro does not surface a “stale cards” view. The closest manual reconciliation is to filter the board by tag and sort cards bymodifiedAt ascending.
Miro board → open the configured board → Tags panel (left sidebar) → click vortexiq:finding to filter → use the Outline panel (View → Outline) which shows cards with their last-modified date → count the cards above 14 days old that are not in the Done column.
There is no native “abandoned” filter in Miro; the team has to cross-reference dates manually, which is exactly why this card exists.
Why our number may legitimately differ from a manual count:
| Reason | Direction | Why |
|---|---|---|
| Comments count as activity | Ours lower | A comment thread on a card refreshes modifiedAt even if the card itself has not moved. Some merchants intuitively only count “card moved” as activity, leading them to count more cards as abandoned than we do. |
| Tag edits count as activity | Ours lower | Adding a severity:high tag triggers an edit; if a teammate adjusted tags in the last 14 days the card is fresh. |
| Connector mapping | Possible mismatch | The 14-day threshold is hard-coded in the engine. If the team has a documented “we review monthly” cadence, this card will mark 14-30 day cards as abandoned even when they are within the team’s intended SLA. Plan support for configurable thresholds is on the roadmap. |
| Polling cadence | Ours stale up to 60s | Same as Findings Open. A card touched in the last minute may still appear abandoned here. |
| Time zone | None | Day boundaries are computed in UTC; the 14-day calculation is rolling so timezone drift averages to zero. |
| Audit pause | Ours misleading | If the team paused audit detection (e.g. for a freeze window) but cards from before the pause still sit on the board, those cards continue accruing idle time and will eventually be marked abandoned even though the team’s expectation was “nothing happens during the freeze”. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
jira.jir_vortexiq_findings_abandoned | Definitional twin on Jira. Same threshold, same rule. | A finding can be active on one and abandoned on the other if dispatch went to both surfaces and only one surface saw activity. |
mural.mur_vortexiq_findings_abandoned | Same metric on Mural. Mural’s facilitation features (timer-driven workshops) sometimes cause spikes after big sessions when many cards are added but few touched. | Healthy under workshop cadence; alarming under steady-state cadence. |
datadog.dd_alerts_summary | If audits are predominantly Datadog-sourced, the abandoned tail concentrates on monitoring findings. | High overlap means an observability-cleanup sprint will clear most abandoned. |
Known limitations / merchant FAQs
Why 14 days, not 7 days? Audit-board recovery curves drop off sharply after the 14-day mark. Items idle for under a fortnight have a high probability of being picked up; items idle for longer fall into the “we forgot” zone. Setting the alert at 7 days produces too many false positives during normal-cadence weeks; setting it at 30 days lets too much real abandonment accumulate before the alert fires. The count went up after a workshop. Is that a problem? Not necessarily. Workshop weeks add many cards in one session and most of them legitimately sit untouched for two weeks while the team digests the output. Look at the worked example pattern: if abandoned cards are predominantly low-severity ideation outputs from a workshop, that is normal. If they are operational findings from the audit feed, that is the alarming pattern. A teammate “touched” an abandoned card just to clear the count. Does that work? Mechanically, yes; it is a known anti-pattern. Vortex IQ deliberately does not detect this: any edit resets the clock because in 95% of cases an edit IS engagement (re-reading, re-prioritising, commenting). If your team is gaming the metric, that is a culture issue, not a metric design issue. The 90-day Resolution Rate card is harder to game because it requires actual closures. Why does it matter to a non-engineering merchant? Because abandoned audit findings are accumulated cost-of-inaction. Every day a critical card sits idle is a day the underlying issue (slow checkout, broken schema, untracked event) keeps costing revenue. Five abandoned criticals at £200/day each is £1,000/day of recurring loss the merchant cannot see in any single transaction; this card is the only place the cumulative cost surfaces. The card ages out cards I deliberately keep on the board for reference. Can I exclude them? Yes. Add the tagvortexiq:reference to any card you want excluded from the abandoned tally. The connector treats vortexiq:reference as a permanent shelf and skips them from both the Open count and the Abandoned count. Use sparingly, every reference card is one less item the abandoned alert can warn about.
My team archives finished frames at end of sprint. Will that re-abandon old cards?
No. Archived frames remain timestamped at their last edit; archiving itself counts as an edit, so any cards on a freshly archived frame have their modifiedAt reset. The Abandoned count only triggers when nothing has happened to the card OR its containing frame for 14 days.
Why is the threshold critical at 15? My team has 30 abandoned and we are still functional.
The thresholds are calibrated against the typical 6-10 person merchant team running 2-week audit cadences. Larger teams (>20 people) routinely sit at 30-50 abandoned without it being a crisis because their fix-throughput is also higher. Open the connector settings and override abandoned_critical_threshold if your team’s normal range is consistently above 15. The default protects the typical merchant; the override exists for the edge cases.
How does this card differ from Oldest Open (days)?
Different lens on the same data. Oldest Open tells you the single longest-standing card; Abandoned tells you how many cards have crossed the 14-day mark. A team can have Oldest Open at 60 days while Abandoned is 1, because most of the queue is fresh except for one ghost. The opposite (Oldest Open at 20 days, Abandoned at 12) means the team is broadly behind, not stuck on one card.