Bord Bia Brand Builder post-mortem

Raw source preview

Raw, unprocessed file text shown below.

---
title: "Bord Bia Brand Builder Post-Mortem"
status: processed
source_type: meeting transcript
session_date: 2026-03-20
duration: "1h 9m 32s"
product_area: "Brand Builder / ClientBrief client portal"
evidence_scope: bespoke-client-delivery
eiq_interaction: false
participants:
  - Desmond Leo
  - Danny Bowles
  - Gary Walsh
  - Michelle Healy
  - Fernando Guevara
tags: [bord-bia, brand-builder, client-portal, bespoke, post-mortem, product-improvements]
---

# Bord Bia Brand Builder Post-Mortem

## Evidence Boundary

Brand Builder was a bespoke portal for the Bord Bia engagement. This session is evidence about client delivery and an adjacent workflow, not about use of EIQ or any product in the EIQ platform. Do not cite it as EIQ adoption, EIQ customer satisfaction, or repeatable EIQ demand.

The canonical customer-level record for this work is the [Bord Bia bespoke Brand Builder dossier](../../../customers/Bord%20Bia/bespoke-brand-builder/README.md).

## Source Files

- [Bord Bia Post Mortem - Reviewing the overall experience.docx](<./Bord Bia Post Mortem - Reviewing the overall experience.docx>) - original Word transcript/recording export.
- [source-transcript.txt](./source-transcript.txt) - plain-text extraction from the Word file.
- [improvement-checklist.md](./improvement-checklist.md) - working checklist of next-round fixes.
- [ux-ticket-briefs.md](./ux-ticket-briefs.md) - plain-language UX ticket briefs for design.
- [Bord Bia Brand Builder UX Ticket Briefs.docx](<./Bord Bia Brand Builder UX Ticket Briefs.docx>) - formatted Word export of the UX ticket briefs.

## Context

This session reviewed the Bord Bia Brand Builder / ClientBrief portal after the first round. Danny Bowles, Empathy's main client contact, reported a positive customer response: the client found the platform useful, easier than the previous process, and a visible step-change in how Empathy handled the project. The end client did not participate in this post-mortem, so this is reported customer feedback rather than a direct customer quotation.

The improvement work is mostly operational. The platform helped the team push clients toward better questions, but the internal review, checking, status management, and handoff-to-scripting workflow created avoidable manual effort.

## Core Read

The biggest product issue was that too much survey-building material lived in one free-text blob. That forced the team to parse client inputs, question text, options, instructions, stimulus rules, and statements manually in Excel before scripting.

The next version should move toward a structured notepad-style workflow: simple input for the client, structured fields for the research team, and script-ready export from the platform.

## Next-Round Deadline Signal

The session points to clients re-engaging around December for the next wave, with the system notionally always open earlier. Existing roadmap notes place the delivery work in the September/October 2026 window.