Team Brief — CI System Design Decisions

Team Brief — CI System Design Decisions

From: Oscar (CEO) To: Pablo, Fiona, Max, Ada, Camille, Dana Date: 2026-03-18 Subject: 3 open design questions for the factory CI system

Context

We're formalizing a continuous improvement (CI) system for the factory. The goal: capture lessons learned, bugs, and improvement ideas continuously — from clients, from delivery sessions, and from factory workers themselves — not just at project milestones.

This memo has one purpose: get your input on 3 unresolved design questions before we lock anything in. Each of you is tagged on the questions relevant to your role.

Q1 — Lessons learned per skill: where do they live?

As skills are used in production runs, we accumulate observations: what worked, what broke, what needs refining. We need a consistent home for those notes.

Options:

  • A: Companion file alongside the skill (ea-exigences-note-revue-lessons.md)
  • B: Section at the bottom of the skill file itself (## Lessons Learned)
  • C: Central product file (lessons-learned.md) with one section per skill

Asked: Pablo, Max, Quinn (note: Quinn is not on this distribution — Pablo or Max, please loop him in if his view is needed before you respond)

What we need from you: Pick an option and give one reason. If none of the above fits, propose an alternative in one sentence.

Q2 — Factory backlog triage: who owns it?

Product feedback (client bugs, improvement requests) is clear: Fiona routes to Max or Pablo. That part is handled.

The gap is factory-side improvements: WO template gaps, process fixes, pattern updates, assembly issues. Right now no one owns triage for those items.

Asked: Oscar (CEO), Pablo, Fiona

What we need from you:

  • Pablo: Do you want to own factory process triage, or should it be shared?
  • Fiona: When you surface factory-side issues during feedback analysis, who do you hand them to today?
  • Oscar will weigh in once Pablo and Fiona respond.

Q3 — CI review cadence: when does the team review the backlog?

Options:

  • A: Tied to Fiona's 30/60/90 day client feedback schedule
  • B: Separate factory rhythm — weekly or bi-weekly /ci-review
  • C: On-demand — triggered when backlog hits N items, or when a new production run starts

Asked: Pablo, Fiona, Dana

What we need from you: Pick an option (or a hybrid) and flag any operational constraint from your side that would make one of the options unworkable.

Next Step

Replies by end of week. Oscar will synthesize into a decision (TFD format) and share with the full team before implementation begins.

Talent Factory — Internal memo. Not for distribution.