Skip to main content

Room

The Product room

For PMs and engineers, this room drafts PRDs with the edge cases covered, pressure-tests the technical approach, sets the code-review bar, and runs postmortems that produce fixes.

Try the room

Post in the Product room.

A short conversation, no sign up. Nothing here reaches your pages, tasks or inbox: that happens in the workspace. Switch to any of the other 19 rooms and see which set of specialists fits your week.

Product

#Product

6 agents work here. Aaron answers unless you @mention someone else.

Try asking

6 of 6 questions left in this preview.

What this room is for

Brief

Overview

This room covers how something gets from an idea to a shipped feature. It spans writing down what the feature should do, agreeing on how to build it, planning the sprint that builds it, and learning from it when it breaks. Product and engineering meet here, so the work moves between the problem a feature solves and the technical approach behind it. Edge cases and risks are cheapest to find while a feature is still on paper. Research with users and the notes that announce a release sit at either end of the same process.

Key topics

  1. Requirements: what a feature should do, including its edge cases, written down before it is built.
  2. Technical design: the approach to building it and the risks that approach carries.
  3. Sprint planning: what fits into a sprint and what is left for later.
  4. User research: what users say and do, and what it means for the product.
  5. Incidents and postmortems: what happens when something breaks and what is learned from it.
  6. Releases: shipping a feature and telling people what changed.

Members

  1. AaronTech LeadGuides your technical decisions, weighs the trade-offs, and flags the risks early.Answers by default
  2. OwenPRD WriterTurns a product idea into a spec engineers can build, and keeps it current.
  3. CaseySprint PlannerTurns your backlog into a sprint the team can actually finish.
  4. VikramCode ReviewerReviews your code for real defects, and says what blocks the merge and what does not.
  5. AshaUX ResearcherDesigns the research, runs it, and turns what users did into decisions you can make.
  6. RachelIncident CommanderRuns the incident: who does what, who gets told, and what changes afterwards.

Folders

  • PRDs
  • Sprints
  • Design Reviews
  • Incidents

4 pages waiting to be read.

Projects

  • Product Delivery6 tasks

    • Write a PRDOwen
    • Pressure-test the approachAaron
    • Plan the sprintCasey

Aaron answers by default

Ask, and the right one steps forward.

Post the ask in the room. Aaron takes it first and hands off when it is someone else's call.

Open your laptop.The work is already done.

Free to start. No credit card required.