Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.
At a glance
Open Vortex IQ-tagged Lucidspark cards that have had no field change in 14+ days. Lucidchart is unusual among the supported destinations: it is a diagramming tool whose Lucidspark whiteboards are sometimes used as the team’s primary planning surface (post-incident reviews, architecture-change boards, customer-journey audits). The abandoned bucket here represents finding cards on Lucidspark boards that the team filed but never moved, which is the silent-leak risk of treating a visual whiteboard as a finding inbox without explicit triage discipline.
| What it counts | Open Lucidspark cards on vortex_iq_outbound-tagged boards where customField:vortexiq_finding_id is set AND the card has not been moved, edited, commented on, or assigned in 14+ days. |
| What counts as movement | Any of: card position change (move within board, move to different section / column), assignee change, status (section name) change, comment posted, label edit, link added, attachment added. Reading the card does not count (Lucidspark does not surface read events). |
| Project / board scope | All Lucidspark boards tagged vortex_iq_outbound in connector setup. Most teams use a single quarterly or always-on board. |
| Status filter | Cards with state NOT IN done / closed / won't fix (sections labelled this way OR cards explicitly marked done via the API). |
| Issue type filter | All Vortex IQ-tagged cards included. |
| Resolution counts | N/A; abandonment is about the open population only. |
| API endpoint | GET /api/v1/cards?board={board_id}&customField=vortexiq_finding_id, paginated. The 14-day staleness clock evaluates against lastUpdatedAt on every webhook event and on a 5-minute scheduled refresh. |
| Time window | RT |
| Alert trigger | >5 warn, >15 critical. Lucidchart-using teams typically have lower finding volumes than Jira or Asana teams, so the absolute thresholds catch issues earlier in proportion. |
| Sentiment key | Threshold-based, {warn: 5, critical: 15}. |
| Time zone | Lucidspark stores lastUpdatedAt as ISO-8601 UTC; the 14-day cutoff aligns to UTC. |
| Visual-context note | Cards on Lucidspark boards have spatial position (x, y on the board); the card does not consider position as movement, only explicit field changes. A card moved across the board counts as movement; a card sitting still does not. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Lucidchart 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 14-person ecommerce ops team using Lucidspark as their primary post-incident-review and customer-journey-audit surface. Single Lucidspark board labelled “Q2 2026 Audit Review” taggedvortex_iq_outbound. Snapshot taken on 02 May 26 at 13:30 BST.
| Section on the Lucidspark board | Open cards | Abandoned (>14d no movement) | Notes |
|---|---|---|---|
| Inbox (unsorted, freshly filed) | 6 | 1 | One card filed 18 days ago, never moved out of Inbox. Single-card abandonment. |
| In Triage | 4 | 3 | Three cards stuck in Triage 16 to 22 days; this is the cluster. |
| Assigned to Engineering | 5 | 2 | Two cards assigned but no comments / movement; classic “assigned and forgotten” pattern. |
| Assigned to Marketing Ops | 3 | 1 | One card from the Easter-campaign meta-description audit. |
| In Progress | 4 | 0 | Healthy; cards in flight are getting touched. |
| Total open | 22 | 7 | Above warn (>5), below critical (>15). |
- Triage section is the bottleneck. Three abandoned cards stuck in Triage means findings are being filed into Lucidspark but the triage owner is not picking them up. This is the Lucidspark-specific risk: visual whiteboards make it easy to add cards but harder to enforce queue discipline. Action: assign one ops lead as Triage owner with explicit responsibility to walk the Triage section weekly.
- The Inbox card sitting unsorted for 18 days is a red flag. Cards in Inbox are findings that were never even triaged. If this becomes a pattern, the connector routing should be reconsidered; if Lucidspark is not getting triaged at all, route to Asana or Jira instead.
- The “assigned and forgotten” cards in the Engineering section are the highest-leverage fix. Two engineering-assigned cards with no comments / movement means the engineer has not engaged with the card. On Lucidspark, “assigned” is informational, not enforcing; engineers don’t get the visibility they would in Jira. Action: cross-post a Slack message linking each abandoned card to the assignee.
- Pair with
luc_vortexiq_findings_open. A growing open count is acceptable on Lucidspark if the team uses the board as a working canvas; abandoned-rate spike alongside growing open means the canvas is becoming a graveyard. - Right action: a weekly 30-minute “abandoned walk” of the board. Run with the ops lead. For each abandoned card: if no real merchant impact, drag to the
Done / Won't Dosection and mark via the API. If real merchant impact, reassign and add a comment with a deadline. This is the best practice on Lucidspark-using teams. - Consider routing engineering findings to Jira instead. Lucidspark works for design / customer-journey / ops findings where visual context helps. Engineering findings (checkout errors, slow queries, infra issues) are typically better routed to Jira / Linear where the team’s existing workflow lives. Override in Settings, Connectors, Routing.
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. The ratio is the steadier read. | Abandoned ÷ Open above 30% on a Lucidspark board = the canvas is becoming a graveyard. |
| Cards by Section | Where abandonment concentrates within the board. | Cards stuck in Triage = triage-owner bottleneck; cards stuck in Assigned = engineer disengaged. Different fixes. |
| Cards by Assignee | Tells you whether abandonment concentrates on one person. | If 70% of abandoned cards sit on one assignee, the fix is reassignment. |
| Datadog Health Score | Independent peer for technical findings. | Datadog elevated + Lucidspark abandoned rising on technical cards = engineering firefighting + audit work falling behind. |
| Shopify / BigCommerce Refund Rate | Downstream cost metric. | Abandoned on returns / refund-flow cards drives refund rate up over a 4 to 8 week window. |
| Customer Service Sentiment | NPS-side outcome. | Sustained abandoned predicts CSAT drop within a quarter. |
| Routing decision (cross-tool) | If abandoned is consistently elevated on Lucidchart, consider routing primary findings to Jira / Linear / Asana instead and reserve Lucidchart for visual-context findings only. | The routing decision often matters more than the in-tool triage discipline on Lucidchart. |
Reconciling against the vendor’s own dashboard
Where to look in Lucidchart’s own UI:Lucidspark and open the board taggedThis card is the canonical reading on Lucidspark; manual reconciliation requires walking the board. Why our number may legitimately differ from a manual board walk:vortex_iq_outbound. Lucidspark does not ship a “stale cards” filter natively; the closest is to use the search bar (top right) to filter cards bycustomField:vortexiq_finding_idand then visually scan for cards that have not been touched recently. The Activity panel (right rail) shows the most recent edits across the board. Lucidchart does not have a dedicated “abandoned cards” report.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary day off | Lucidspark stores lastUpdatedAt as UTC; the card uses UTC for the 14-day cutoff. The agent’s local-timezone view in the Activity panel can show a different “calendar day” for the same edit. |
| Position-change movement | None | Position changes (drag a card from one section to another) DO count as movement; a manual walk that ignores position changes will undercount. |
| Custom-field deletion | Ours lower | If vortexiq_finding_id is cleared from a card, the card drops out of the count even though it is still abandoned operationally. |
| Cross-board aggregation | Either | Card aggregates across all vortex_iq_outbound boards; a manual walk typically scopes to one board. |
| Webhook delay | Up to 60s stale | A movement from the last minute may not have reached the card. |
| Lucidchart vs Lucidspark | Card scopes to Lucidspark only | The card uses Lucidspark cards; Lucidchart’s traditional diagrams (flowcharts, swimlanes) are not used as finding inboxes and are excluded. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
datadog.dd_incidents_active | Independent. Datadog tracks live engineering incidents; Lucidspark tracks the audit-side remediation work for findings routed there. | Both elevated = engineering firefighting + audit work falling behind. |
shopify.refund_rate | Inverse correlation; abandoned on returns / checkout findings drives refund rate over a 4 to 8 week window. | Abandoned on cosmetic / structural findings only = no refund correlation. |
shopify.customer_service_sentiment | Inverse correlation; 2 to 4 week lag. | Sustained abandoned predicts CSAT drop. |
Known limitations / merchant FAQs
Lucidspark shows my card was edited yesterday but the card says abandoned. What is wrong? Almost always one of two things. (1) The “edit” was someone moving an unrelated card past it on the board (Lucidspark’s Activity panel includes neighbouring-card edits in some views); the card looks at the specific card’slastUpdatedAt, not nearby activity. (2) The “edit” was a Copilot suggestion shown but not accepted; the card treats only accepted changes as movement. Open the card and check the activity history for an explicit edit / move / comment in the last 14 days.
Why does the count include cards in the “Done” section?
Because Lucidspark’s data model treats sections and explicit completion as independent. Moving a card to a “Done” section does NOT mark it complete; only setting state via the API or marking the card via the dropdown does. If your team’s workflow is to drag-and-drop into Done without explicitly marking, the count looks high. Fix: the Vortex IQ-Lucidchart connector watches sections labelled done, closed, or won't fix, but ONLY if the card has been moved INTO that section in the last 14 days. A card moved to Done >14 days ago without being explicitly marked complete still counts.
The 14-day window feels arbitrary. Can we tune it?
Yes, in Settings, Connectors, Lucidchart, Abandonment threshold (days). Default is 14 days. Lucidchart-using teams running quarterly review boards often tune up to 21 or 28 days because their cycle time is naturally slower; teams using Lucidspark for active sprint work tune down to 10 days.
We use multiple Lucidspark boards. The count looks alarming.
Open the per-board stack panel from the connector drawer to see which board drives the abandoned count. Most Lucidchart-using teams find the abandoned bucket concentrates on the older / quarterly boards while the active-sprint board stays clean.
Velocity dropped, abandoned count rising. What changed?
Standard playbook. (1) Check who owns the Triage section; if the owner is on PTO, cards stack up there. (2) Check whether the team is using a different board (sometimes teams migrate from board to board mid-quarter without updating connector tags). (3) Cross-check the engineering team’s primary tool (Jira / Linear) for parallel-tool drift; teams often start using Lucidspark less when sprint pressure rises.
The abandoned count appears suddenly higher overnight. Why?
Because the 14-day clock keeps ticking. If five cards were last touched on the same day exactly 14 days ago, all five become abandoned at the same time the next day. Normal and self-corrects within 24 hours of the team picking the queue back up.
Should I close abandoned cards or fix them?
Both, depending on triage. Run a weekly 30-minute “abandoned walk” of the board with the ops lead. For each abandoned card: if no real merchant impact, drag to the “Done / Won’t Do” section AND mark complete via the API (or the card dropdown). If real merchant impact, reassign and add a comment with a deadline.
Should I be using Lucidchart for findings at all?
Depends on the use case. Lucidchart shines when audit findings have a visual / spatial component (customer-journey audits, architecture-change reviews, post-incident timeline boards). It is poor as a generic finding inbox; engineering findings in Jira, ops findings in Asana, design findings in Lucidchart is the typical good-fit pattern. If abandoned is consistently elevated, the routing decision matters more than the in-tool triage discipline; consider rerouting non-visual findings to Jira / Asana / Linear.
A finding important enough to fix manually but we never moved the Lucidspark card. Do we close it?
Yes. Either drag the card to “Done / Won’t Do” AND mark via the dropdown, or delete the card. Otherwise it stays in the abandoned bucket. Vortex IQ does not auto-close findings just because the underlying audit signal cleared.
Why doesn’t Lucidspark surface a “stale cards” view natively?
Lucidspark is designed for canvas-style brainstorming and visual collaboration; a “stale cards” report is a list-style read that runs against the grain. The card’s added value: cross-board aggregation, position-change movement detection, threshold-based alerts, historical trend.
Multi-team boards: my company has Engineering, Marketing, and Customer Operations boards. Does the card aggregate?
Yes by default if all are tagged vortex_iq_outbound. Open per-board stack panel for breakdown. Most teams concentrate Vortex IQ findings on one or two boards rather than spreading across all of them.
Can we automate closing low-impact abandoned cards?
Partially. Lucidspark does not have a Jira-Automation-style rule engine; you would need to use the Lucidchart API and a scheduled script. Most teams instead adopt the manual weekly “abandoned walk” pattern. If you want automation, the better path is to route engineering findings to Jira where automation is native, and reserve Lucidchart for findings that need the visual context.
Is this card the right primary watch metric for Lucidchart-using merchants?
Yes within the limits of the tool’s role. Lucidchart-using teams typically use Lucidchart as one of several tools, not as their primary PM tool. The abandoned card here is the in-tool-discipline signal; pair with the abandoned card on your primary PM tool (Jira / Asana / Linear) for the full picture.