Supporting evidenceProduct and SKU readiness

EIQ and research-team platform catch-up

Researchers identified projects that fit the current platform, recurring workflow needs and explicit capability boundaries for launch and future prioritisation.

Repo path

research/interviews/2026-07-09-eiq-research-team-platform-catchup/README.md

Notes

No additional notes recorded.

Raw source preview

Raw, unprocessed file text shown below.

---
title: "EIQ and research-team platform catch-up"
status: processed
source_type: internal portfolio and workflow review
session_date: 2026-07-09
duration: "48m 25s"
participants:
  - Sabine Cronick
  - Lesley Kelleher
  - Leanne Willins
  - Danny Bowles
  - Michelle Healy
  - Desmond Leo
  - Gary Walsh
product_area: "Portfolio / Quant Surveys"
tags: [portfolio, quant-surveys, capability-gaps, internal-practitioner, prioritisation]
---

# EIQ and research-team platform catch-up

## Source file

- [monthly-platform-catchup.docx](./monthly-platform-catchup.docx) — original Microsoft Teams transcript export.

## Evidence relevant to launch

- The research team identified concrete Quant limits, including conjoint, MaxDiff, advanced allocation and conditional-text cases (2:15 onward).
- Lesley identified recurring demand for categorising open text and described current use of ChatGPT followed by researcher checking (19:09–20:46).
- Leanne described reviewing AI-generated codes and manually correcting uncategorised or misclassified answers (23:46).
- Sabine said saving even half of Leanne's weekly effort would be worth trialling (23:23).
- The team identified a future phone-survey project that could run on the platform, while recommending that long-running trackers with valuable historical data remain on their incumbent system (44:34–47:57).

## What this supports

Working researchers are actively identifying eligible projects, recurring workflow needs and capability boundaries. It provides useful prioritisation and launch-boundary evidence.

## What this does not prove

This was an internal planning session, not a customer-demand interview. Several discussed capabilities were future or incomplete, and no payment or external adoption signal was recorded.