✦ Guide · Intermediate

AI for product teams

Feedback themes, market research, the investor or roadmap deck and a coordinated plan as a team of flexible workers that traces every claim to a source.

4 lessons21 min Self-pacedUpdated 30 Sept 2026
Start guide

YOUR OUTCOME

You will run a product pod that finds themes in feedback with counts and quotes, researches the market with sources, builds the deck from both, and plans the work with owners.

Themes with counts and example quotes, each traced to a source A number you cannot cite is marked, never rounded into a claim The deck is graded against checks written before it existed
01

The team for this work

Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.

4 min
02

Hire the first wave

Import, rename, and give a goal with the deliverable, the sources and the finish line.

6 min
03

The team and the second wave

Run the team in one room; hire the rest once the first deliverable exists.

6 min
04

The routine that keeps working

One recurring job on a schedule, then a status round and a grade.

5 min

What each lesson covers

The guide, lesson by lesson.

01

The team for this work

Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.

Start from the work, not the tool: Feedback themes, market research, the investor or roadmap deck and a coordinated plan as a team of flexible workers that traces every claim to a source. The team is Ivy · Feedback (Customer feedback analysis), Ren · Research (Research assistant), Noor · Decks (Presentation building), Cass · Plan (Project coordinator). Each starts from a Marketplace template, imported as your own copy, renamed and re-goaled on the setup card; nothing personal and no creator credentials come with a template.

Practice. Open Marketplace, Worker templates, and read the Instructions and Integrations of each template on this list before you import anything. Note which sources each one will ask you for.

Marketplace → Worker templates → open Customer feedback analysis. Read Instructions, then Integrations.

02

Hire the first wave

Import, rename, and give a goal with the deliverable, the sources and the finish line.

Import worker creates your copy as a flexible worker and opens the setup card. Rename it, replace the goal with yours, and choose When to work. Feedback analysis is the first hire because the research question and the deck both come out of the themes it finds.

Practice. Import Customer feedback analysis, rename it Ivy · Feedback, and paste your goal on the setup card. Choose Now, once, and Continue. Check its first deliverable in Doc Manager before the next hire.

Name: Ivy · Feedback. Goal: Read the attached 400 support tickets and app reviews. Group them into themes, give each theme a count, three example quotes with their source, and a severity. Do not invent a theme that fewer than five items support. When to work: Now, once.

03

The team and the second wave

Run the team in one room; hire the rest once the first deliverable exists.

Click New team, name it Product pod, add Ivy · Feedback, and post what the team is for. Then hire the second wave with goals that start by reading the first wave's document. @Name directs one member, @everyone the room, and Work in the member row opens what that member did in the team. Research answers the question the top theme raises; the deck builder turns themes and research into slides; the coordinator plans the work behind the top three themes.

Practice. Create Product pod, add each hire as it joins, and ask every member to post what it made and the one thing it would flag.

@everyone Welcome to the product pod. Ivy's themes are in the workspace. Ren: research the top theme with sources and mark anything you cannot verify. Noor: build the roadmap deck from Ivy's table and Ren's brief. Cass: plan the work behind the top three themes with owners.

04

The routine that keeps working

One recurring job on a schedule, then a status round and a grade.

Feedback keeps arriving; a weekly themes routine tells the team what changed, not just what exists. Each run shows on its worker's Runs tab. Close each cycle with a status round, "@everyone one line each", and a grade against the acceptance checks each worker wrote first.

Practice. Add the time in When it runs, use Run now to get today's first report, then run one status round in Product pod.

When it runs → Add a time. Name: Weekly feedback themes. What should it do? Read the tickets and reviews received since the last run, update the themes table with new counts, and report which themes grew, which appeared, and three new quotes with sources. Repeats: Every week, Monday, 08:00.

Keep going

Product learning path

Make the learning stick

Start with one real piece of work.

Open Oppermind beside the lesson, apply each step, and leave with something you can use.

Open the quickstart docs