Product follow-up log

Raw source preview

Raw, unprocessed file text shown below.

---
title: "Product Follow-Up Log — All Customers"
last_updated: 2026-04-08
---

# Product Follow-Up Log

Master log of product ideas, feature requests, and commitments surfaced during customer sessions. One row per item. For full context, see the per-customer follow-up file in `customers/[name]/follow-up-items.md`.

---

## Open items

| ID | Customer | Raised by | Summary | Session | Owner | Status |
|---|---|---|---|---|---|---|
| MUS-001 | Musgrave | Cliona Kennedy | GBP currency toggle for prize draws (Northern Ireland surveys locked to EUR) | 2026-04-07 | Desmond | Open |
| MUS-002 | Musgrave | Cliona Kennedy | AI chat question probing customisation — ability to steer probe topics in setup UI | 2026-04-07 | Desmond | Open |
| MUS-003 | Musgrave | Cliona Kennedy | Crosstab roll-up feature — review prototype with Musgrave before finalising | 2026-04-07 | Desmond | Open |
| MUS-004 | Musgrave | Cliona + Shannen | Questionnaire reviewer PoC — invite Musgrave as first testers when ready | 2026-04-07 | Desmond | Open |
| MUS-005 | Musgrave | Shannen Kearney | Incentive distribution workflow — streamline voucher process for AI interviews | 2026-04-07 | Desmond | Open |
| MUS-006 | Musgrave | Cliona Kennedy | Report page feedback session — Cliona to give input on new report designs | 2026-04-07 | Desmond | Open |
| MUS-007 | Musgrave | Cliona Kennedy | Hidden variable promotion in team training — not using correctly; needs explicit coverage | 2026-04-07 | Desmond | Open |
| MUS-008 | Musgrave | Cliona + Shannen | Team training on new UX release — mid/senior first, then interns | 2026-04-07 | Desmond + Musgrave | Open |
| PROD-001 | Internal | Desmond | Research Architect UX architecture — open decision: should Research Architect be a separate project type ("New Custom Project") in the new project modal, or the universal first step for ALL projects (brief-first, method-second)? Current modal is method-first. Research Architect philosophy is brief-first. These conflict. See `brand/naming-research-compass.md`. | 2026-04-15 | Desmond + Gary | Open |
| PROD-002 | Internal | Desmond | Research Guard review surface productization — package the governed questionnaire-review flow into a clearer production UI with ordered issues, approvals, design previews, package candidates, revision state, and final QA visibility. | 2026-04-18 | Desmond + Gary | Open |
| PROD-003 | Internal | Desmond | Response-quality companion layer — define and build stronger live-response and post-field quality coverage for speeders, bots, duplicates, breakoff, and suspicious open-end behaviour, so this becomes a real product capability rather than just a positioning gap versus incumbents like Qualtrics. | 2026-04-18 | Desmond + Gary | Open |
| PROD-004 | Internal | Desmond | Security and procurement story packaging — create a buyer-ready deployment, security, access-control, retention, and procurement narrative so Research Guard and the wider platform are not positioned beyond current enterprise-proof reality. | 2026-04-18 | Desmond + Gary + Ops | Open |
| PROD-005 | Internal | Desmond | Import/export bridges for incumbent survey platforms — define the first bridge set for external questionnaire and study assets, starting with Qualtrics and then SurveyMonkey / QuestionPro, so low-friction adoption does not depend on manual work alone. | 2026-04-18 | Desmond + Gary | Open |
| PROD-006 | Internal | Desmond | Trust Centre proof point — capture a quantified quality metric from live pilots (flagging rate, removal rate, or quality improvement figure) to support the Real, Unique, Engaged brand story and create a benchmark comparable to Zappi's publicly stated "6% vs 2%" respondent removal claim. Track from Musgrave and UKOmnibus pilots. Website and sales materials to be updated once data is confirmed. | 2026-04-18 | Desmond | Open |

---


## Closed items

*(none yet)*

---

## How to use this log

- Add a row whenever a customer session surfaces a product idea, commitment, or follow-up
- Use the customer-specific file in `customers/[name]/follow-up-items.md` for full context
- Close items here when they're shipped, declined, or no longer relevant (move to Closed section)
- Reference this log when planning sprints to ensure customer commitments don't get lost