Snapshots

No partner words on record yet, so no theme is customer voice

Waiting on you
  • Every job and worry wording in the old book is Sample, awaiting real words.
  • The feedback log has 5 partner rows, all actions and none quotes.
  • Our team's themes sit in their own section, so taste is never sold as voice.
  • A theme needs words from at least two partners to count as a partner theme.
  • Card notes and Not for me are collected but nobody reads them yet.
5partner rows, all actions
Your call

Who reads the card notes every week?

Research and insights · 16.3

Voice of the customer

DraftLast checked Mon Oct 26Owner Param

Answer

Themes across partner calls and feedback, in their own words; no partner words are on record yet, so the themes below are our own team's, mostly Param testing as a stand in founder, and they must never be quoted as customer voice.

Today

Partner words on record

  • None. Every job and worry wording in the old book is Sample, to be replaced with real words given with permission brand-directions/book/content/b.js:281-301
  • The feedback log holds 5 partner rows and all are actions, not quotes handbook product/partner-feedback-log.md

What partners did, which speaks for them

Date Partner What they did Source
15 Oct Arata Agreed its team notes may stay public on the demo memory brew-audit-2026-10-15
19 Oct Arata Uploaded an audit and a campaign plan for the feed to work to memory brew-absorb-all-learnings
22 to 23 Oct Arata Connected Meta Ads and Shopify, the only partner with real accounts handbook product/partner-feedback-log.md

Our team's themes, from the feedback log

Our classification of the team rows in the feedback log, with each row's date; one row can sit in two themes.

Theme Rows, by date Source
Every number and claim must be true and proven 14, 16, 19 four times, 20, 23 and 25 Oct handbook product/partner-feedback-log.md
Pages must be simple and look finished 14, 16, 18, 19 three times, 20, 25 three times and 26 Oct handbook product/partner-feedback-log.md
A making button must make the thing the card names 17, 19 twice, 20, 23 and 24 Oct handbook product/partner-feedback-log.md
The feed must be specific and stay fresh 16, 19 three times and 22 Oct handbook product/partner-feedback-log.md
Keep the brand's data and connections safe 22 and 23 Oct twice handbook product/partner-feedback-log.md

Param's own words, dated

Date Words Source
15 Oct "we are not building the product, we are building a realistic prototype" memory brew-prototype-repo
17 Oct On Make our version: "first understands what those creatives/ads are, uses the same angles and hooks and styles, our products in a very similar style" memory brew-go-live-2026-10-17
19 Oct "the goal is whatever their learnings are from the real world - we absorb it as context and populate the much richer feed, just for them" memory brew-absorb-all-learnings

Where the product already collects their voice

  • Not for me on every card page, and a written note on a card, saved per brand brew/public/app.js:2037 brew/feed-service.js:2056
  • The engine view counts card feedback with the target "Read by the Brew team weekly"; no one is assigned to read it brew/feed-service.js:1274

Tomorrow

Item Version Tag Notes
Partner quotes, with permission, under each theme v1 New From the weekly calls
Sample job wording replaced by partners' words v1 Changes In Jobs to be done and Personas
Card notes and Not for me read each week into this page v1 New One line per theme that moved
Our team's themes kept in their own section, apart from partners v1 Stays So team taste is never sold as customer voice

How we do it

  1. Each week, read new rows in the interview and call library and the feedback log.
  2. Put each quote under one theme, with the date, who and "with permission".
  3. Read the card notes for the five partners in the engine view and add any repeated point as a theme row.
  4. A theme needs words from at least two partners before it is called a partner theme.

Numbers

Metric Definition Where measured Status
Partner quotes Quotes with permission on this page This page 0 today
Partners quoted Partners with at least one quote This page Proposed; target all five
Card notes Written notes plus Not for me per brand Engine view, feed-service.js metrics Measured in the build; not read yet

Open

  1. May we quote partners by name inside the handbook? Proposal: yes, inside only; never outside without written permission.
  2. Who reads card notes each week? Proposal: Sai, every Monday, for the five partners.
  3. Should Param's testing keep its own section? Proposal: yes, labelled our team, until partner words outnumber it.
Sources
  • brand-directions/book/content/b.js:265-327 b-4 main-job, jobs-by-person, small-jobs
  • handbook: product/partner-feedback-log.md, product/jobs-to-be-done.md, product/personas.md
  • memory: brew-absorb-all-learnings, brew-audit-2026-10-15, brew-go-live-2026-10-17, brew-live-stores, brew-prototype-repo
  • brew origin/main a559de6: feed-service.js:1274, feed-service.js:2056, public/app.js:2037

Source file content/research-and-insights/voice-of-the-customer.md · For agents: Markdown · JSON