Capability template for product management
Product sample feedback revision list
After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
When a supplier sends a second or third sample, the comments arrive from every direction: testers and customer panel members. Some refer to a version that has since changed, some have no label, and some pull in opposite directions. This capability turns them into one list that is sorted by sample version and by feature, so the team can see at a glance what is settled and what is not.
Agreed changes sit in one place, each with the notes behind it. Conflicting feedback sits in another, with both sides side by side and the concept brief beside them. Preferences are kept apart from observations, single comments are not dressed up as agreement, and a change the supplier says it made but nobody has tried is flagged. Earlier revision requests are checked against the latest sample, so nothing asked for in round one quietly drops out.
The list ends with drafted notes for the next supplier brief, built only from what is agreed. The product owner resolves the conflicts and approves the brief before anything goes to the supplier. Questions about materials, strength or safety are passed to the right specialist as written, with no judgment attached.
Who starts the work, and when
The product lead starts it when a round of sample feedback is in, and again after each new sample. The product owner reads the list and settles the conflicts. Sourcing and quality read the finished list.
What they supply
- A sample register: each sample's identifier, version, date received, supplier and whether it is labelled, with any changes the supplier says it made.
- The dated feedback notes, each tied to a sample, a person and a feature.
- The concept brief, with its features and what is required of each.
- Earlier revision requests: what was asked, when, and what the supplier said it did.
What comes out
One list in a fixed order: agreed changes by version and feature, conflicting feedback, single comments, what is reported as working, questions for specialists, the status of earlier requests, untested supplier changes, drafted notes for the next brief and the decisions only the product owner can make. Every line points back to a note or the register. A note that cannot be tied to a sample is set aside with a question rather than guessed at.
An invented example
Illustrative example with invented data. The brand, the supplier, the product, the people and every date and note are made up. A product lead at an invented consumer brand is reconciling the feedback on the second sample of an insulated lunch tote from Supplier A.
What the person supplies
Concept brief (product: insulated lunch tote; features and requirements):
- Capacity: fits two 500 ml containers and a sandwich box.
- Closure: opens with one hand.
- Strap: comfortable to carry, adjustable.
- Lining: wipe-clean.
- Colour: sage green.
Sample register (Sample ID, Version, Date received, Supplier, Labelled, Supplier-stated changes):
- S-01, V1, 2026-09-14, Supplier A, yes, first sample.
- S-02, V2, 2026-10-12, Supplier A, yes, zip replaced with a magnetic flap; strap lengthened by 6 cm; inner pocket added; lining unchanged.
Earlier revision requests (Request ID, Feature, Requested change, Sent, Supplier's reply):
- R-1, Closure, replace the zip, which snags on the lining, 2026-09-22, "done in V2".
- R-2, Strap, lengthen the strap, 2026-09-22, "done in V2".
- R-3, Lining, stitch the base seam flatter, 2026-09-22, "will review".
- R-4, Colour, move the green toward the sage swatch, 2026-09-22, "done in V2".
Feedback notes (Note ID, Date, Sample ID, Source, Feature, Comment):
- N-01, 2026-09-18, S-01, Tester 1, Closure, "Zip snags on the lining every second try."
- N-02, 2026-09-18, S-01, Tester 2, Strap, "Too short to carry over a coat."
- N-03, 2026-09-19, S-01, Tester 1, Lining, "Seam at the base catches crumbs."
- N-04, 2026-10-16, S-02, Tester 1, Closure, "Magnetic flap opens with one hand. Good."
- N-05, 2026-10-16, S-02, Tester 2, Closure, "Flap opens too easily. A container slid out when the bag tipped."
- N-06, 2026-10-17, S-02, Customer panel 1, Strap, "Long enough now, but the buckle digs into my shoulder."
- N-07, 2026-10-17, S-02, Customer panel 2, Strap, "Buckle is sharp on the shoulder. Add padding."
- N-08, 2026-10-17, S-02, Tester 2, Colour, "Too grey. I would prefer a brighter green."
- N-09, 2026-10-18, S-02, Customer panel 1, Colour, "Love the muted green."
- N-10, 2026-10-18, S-02, Tester 1, Lining, "Seam at the base still catches crumbs."
- N-11, 2026-10-19, S-02, Customer panel 2, Lining, "Smells strongly of chemicals when new. Is it safe for food?"
- N-12, 2026-10-19, (blank), Tester 2, Capacity, "The green bag from the second box fits three containers."
- N-13, 2026-10-20, S-02, Customer panel 1, Capacity, "Fits two 500 ml containers and the sandwich box with room to spare."
Settings: agreed means two different people; the product owner resolves conflicts and approves the brief; the materials and safety questions go to the person the brand names for them (no name supplied); date of the run, 2026-10-22.
What comes out
SAMPLE FEEDBACK REVISION LIST: Insulated lunch tote, V1 to V2
For: Product owner. Prepared for the product lead on 2026-10-22. Notes dated 2026-09-18 to 2026-10-20.
Notes read: 13. Placed: 13 (earlier requests 3, agreed 2, conflicting 4, single 1, working 1, specialist 1, set aside 1).
Samples covered:
- S-01, V1, Supplier A, received 2026-09-14, labelled.
- S-02, V2, Supplier A, received 2026-10-12, labelled.
Set aside before sorting: 1.
- N-12: no sample ID. The register holds one V2 sample, but the note refers to "the second box". Ask Tester 2 which label the bag carried.
AGREED CHANGES
V1 (S-01): None. Its three notes (N-01, N-02, N-03) are covered by requests R-1 to R-3, shown under Prior requests.
V2 (S-02):
- Strap: change the buckle area so it does not press on the shoulder. Notes: N-06 (Customer panel 1), N-07 (Customer panel 2). N-07 suggests padding; the remedy is for the product owner and the supplier. Brief: comfortable to carry, adjustable.
CONFLICTING FEEDBACK
- V2, Closure: N-04 (Tester 1) says the flap opens with one hand. N-05 (Tester 2) says it opens too easily and a container slid out. Type: observation. Brief: opens with one hand. The product owner decides.
- V2, Colour: N-08 (Tester 2) finds the green "too grey" and says "I would prefer a brighter green" (a fact and a wish in one sentence, treated as preference). N-09 (Customer panel 1) likes the muted green. Type: preference. Brief: sage green. The product owner decides.
SINGLE COMMENTS (not yet agreed)
- V2, Lining: the base seam still catches crumbs. N-10 (Tester 1), who raised it on V1 as N-03. One person so far.
REPORTED AS WORKING
- V2, Strap (length): long enough now (N-06). Brief: comfortable to carry, adjustable.
- V2, Capacity: fits two 500 ml containers and the sandwich box (N-13). Brief: fits two 500 ml containers and a sandwich box.
FOR SPECIALIST ASSESSMENT
- N-11, V2, Lining (Customer panel 2): "Smells strongly of chemicals when new. Is it safe for food?" Route to: the person the brand names for materials and safety (no name supplied). No revision is proposed and no judgment is made here.
PRIOR REQUESTS
- R-1, Closure: addressed in S-02. The supplier replaced the zip and no note reports a snag on the new flap; N-04 reports easy opening. A new issue is under Conflicting feedback.
- R-2, Strap (length): addressed in S-02 (N-06).
- R-3, Lining (base seam): still open in S-02 (N-10). The supplier states the lining was unchanged.
- R-4, Colour: unclear in S-02. N-08 and N-09 disagree.
UNTESTED SUPPLIER CHANGES
- S-02: inner pocket added. No note mentions it.
DRAFT NOTES FOR THE NEXT SUPPLIER BRIEF (not approved; do not send)
1. Strap: change the buckle area on the next sample so it does not press on the shoulder (S-02, N-06, N-07).
2. Lining: the base seam on S-02 still catches crumbs, as on S-01 (restates R-3; one person so far, N-10). Ask what can change.
3. Not in brief, inner pocket: confirm the inner pocket added in S-02; no feedback on it yet (S-02 register).
Held back from the brief: Closure and Colour (conflicts), N-11 (specialist), N-12 (set aside).
DECISIONS FOR THE PRODUCT OWNER: 5
1. Closure: keep the magnetic flap as it is, or ask for a firmer hold? N-04, N-05; the brief requires one-hand opening.
2. Colour: keep the green as the brief states, or change it? N-08, N-09; the brief says sage green.
3. Lining seam: restate R-3 in the brief on N-10 alone, or wait for a second view? The brief requires a wipe-clean lining.
4. Who assesses the question in N-11, and whether the brief waits for the answer?
5. Approve, change or remove brief items 1 to 3.
Every line traces to the notes, register, brief and requests supplied.
The list changes no records and sends nothing to the supplier.
Where it fits
- Product management, where the revision list is the working record between one sample and the next.
- Consumer brands, for teams developing products with outside suppliers.
- E-commerce & retail, for own-label ranges developed with a supplier.
- Hardware & physical technology, for devices and accessories that go through several sample rounds.
- New business lines, when the first product in a new category goes through its first samples.
- Growth & scaling, when more people comment on samples and the notes no longer fit in one head.
This is different from customer feedback themes, which groups what customers say about a product already on sale, and from the acceptance criteria sheet, which defines done for a software story. This one reconciles feedback on specific samples, version by version.
What has to change for your company
List the features you review a sample on, and use the same words in the concept brief and the notes. Decide how many different people must raise a point before it counts as agreed; the default is two. Name who resolves conflicts, who approves the supplier brief, and which specialist takes technical, materials and safety questions. Fix your sample label format. Decide how the brief is sent to the supplier; this capability never sends it.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried on its invented example in Claude on 10 November 2026, and run again after the wording was clarified; the record of the second run is published with it. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past sample round your product lead already knows, with cases written in advance: a note with no sample label, two testers who disagree, a supplier change nobody tried. The product lead checks every line against the original notes before anyone relies on it. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: