This skill should be used when the user asks about the VRU, Void Reclamation Unit, UX opportunity hunting, qualifying a UX opportunity, logging to the VRU board, scanning for missed UX work, checking if a project needs UX, or anything related to the Caylent Experience Design pipeline. Trigger phrases include: "is this a UX opp", "hunt this", "qualify this opportunity", "VRU checklist", "scavenger", "interceptor", "reclaimer", "what's on the board", "missed UX", "position UX value".
The VRU exists to hunt missed, overlooked, or under-scoped UX opportunities and ensure Experience Design has a seat at the table early, often, and with impact.
Mission: Go where no one is looking. Dig through the mess. Find the value others missed.
The Void Reclamation Board (Opportunity Tracker) is the single source of truth for all UX opportunities being pursued.
1Y6nRhU9BnLBk0H5o_lh3DbvhMTiKESMzsT_hIWK2Cfc| Column | Field | Notes |
|---|---|---|
| A | Opp ID | Format: VRU-### (auto-increment) |
| B | Date Found | MM/DD/YYYY |
| C | Client Name |
| D | Source | Slack, EVO, Salesforce, Insider Tip, Gong, etc. |
| E | Link | Salesforce URL, Slack thread, or doc link |
| F | Related Project / Initiative |
| G | Opportunity Type | New / Expansion / Follow-on |
| H | What Fell Into the Void | The specific UX gap or missed signal |
| I | UX Value | AI UX, data visualization, workflow design, etc. |
| J | AE / CSA | Account Executive / Customer Success contact |
| K | Potential Value | Small / Medium / Large |
| L | Priority | Low / Medium / High |
| M | Assigned Role |
| N | Owner |
| O | Scavenger | Person who found it |
| P | Hunter | Person qualifying it |
| Q | Interceptor | Person activating it |
| R | Reclaimer | Person converting it |
| S | Reclamation Stage | See stages below |
| T | Next Action | Specific next step |
| U | Next Action Date / Deadline | MM/DD/YYYY |
| V | Status Notes | Running notes |
| W | (separator) |
| X | Outcome Reason | If closed/lost |
| Y | Learnings | What we learned |
1. Scavenged — Signal found, raw opportunity logged2.a Needs Hunter — Ready for qualification2.b Ready for Interceptor — Qualified, needs activation3. Intercepted — In conversation with Sales/Delivery4. Reclaimed — UX is officially part of the engagement7.a Lost / Not Pursued — Decided not to pursue7.b Lost – Budget — Lost due to budget7.c Lost – Client has UX — Client has own designers7.d Parked – Follow Up Later — Timing isn't right yet7.e Won — UX successfully added| Role | Focus | Success Signal |
|---|---|---|
| Scavenger | Discovery — scans channels/calls, logs raw signals | "I found something interesting." |
| Hunter | Qualification — validates UX relevance and value | "This is worth pursuing." |
| Interceptor | Activation — reaches out to Sales/Delivery, positions UX | "We're in the room." |
| Reclaimer | Conversion — shapes scope, strengthens positioning | "UX is officially part of the engagement." |
| Recovery Lead (Mel) | Oversees strategy, prioritization, and evolution |
Before qualifying or dismissing any opportunity, run through these signal categories. See references/signal-patterns.md for the full list.
Immediate red flags that signal UX need:
Delivery Risk Check — escalate UX if 2+ apply:
When you hear "they already have UX," always clarify:
If gaps exist → UX can add value.
One-liner for Sales intercept:
"This project has user-facing workflows and AI elements. Without UX, we risk unclear MVP and rework. A short UX engagement could define workflows and reduce delivery risk."
Right-size UX framing:
Position as: "Reduce rework + protect delivery + increase adoption"
When hunting for opportunities, check:
For full signal patterns and the complete hunting checklist, see references/signal-patterns.md and references/hunting-checklist.md.