ZespółProdukt i dane · v1.1.0

Product Management Team

Synteza discovery, PRD, planowanie roadmapy, priorytetyzacja i komunikacja wydań.

Discovery synthesis, PRDs, roadmap, prioritisation and release communication.

PRDs where the problem statement is arguable and most of the length goes on edge cases — which is where specifications earn their keep. Synthesis that reports participant counts and evidence strength rather than dressing eleven interviews up as percentages.

Agenci 5

  1. 01prd-writerUse to write product requirement documents, feature specifications and user stories — documents engineering can build from and everyone else can argue with.
  2. 02prioritization-analystUse to prioritise — comparing features, requests and bets against each other with an explicit method, sizing impact, and settling disagreements about what to build next.
  3. 03release-notes-writerUse to communicate what shipped — release notes, changelogs, in-app announcements, feature launch emails and migration guides for breaking changes.
  4. 04roadmap-plannerUse for roadmap and planning work — quarterly planning, sequencing, capacity and dependency management, communicating a roadmap to different audiences, and saying no well.
  5. 05user-researcherUse for discovery — designing and analysing user interviews, synthesising qualitative feedback, building journey maps, and turning support tickets and sales objections into product insight.

Skille 2

  1. 01discovery-synthesisTurn raw discovery input — interviews, support tickets, sales objections, usage data, reviews — into findings with evidence strength and a clear decision. Use when synthesising research, analysing feedback, or answering "what are users actually telling us?".
  2. 02prd-writingWrite a product requirements document that engineering can build from and stakeholders can argue with — problem with evidence, behaviour, edge cases, success metrics and rollout. Use when asked for a PRD, spec, feature document or user stories.

Komendy 2

  1. 01/prdWrite a full product requirements document — problem with evidence, behaviour, edge cases, metrics and rollout.
  2. 02/prioritizePrioritise a backlog or a set of options with an explicit method, visible inputs and a stated recommendation.

Czego ten zespół nie zrobi

It will not invent research findings, usage figures or ticket volumes; present qualitative counts as population percentages; write untestable requirements; commit to dates for unscoped work; or announce something as generally available when it shipped to 5% behind a flag. If the evidence contradicts the plan, it reports that as the finding rather than writing a document to justify a decision already made.

49 €jednorazowo

→ Współpracownicy

Warto zatrudnić też

Wszystkie: zespoły →
Zespół

Web Craft Studio

Zespół webowy prowadzony przez design, dla stron, które wyglądają na zaprojektowane, nie wygenerowane: art direction z własnym zdaniem, ruch z celem, frontend na poziomie rzemiosła, copy, które coś mówi, plus dostępność i wydajność.

6 agentów · 2 skilleProdukt i dane · v1.1.0
79 €bruttozamiast 45 tys. € / mies. na payrollu
Zespół

Data & Analytics Team

Analytics engineering, analiza SQL, projektowanie dashboardów, eksperymenty i jakość danych — wokół definicji metryk, na które wszyscy się zgadzają.

5 agentów · 2 skilleProdukt i dane · v1.1.0
49 €bruttozamiast 37,5 tys. € / mies. na payrollu
Zespół

Migration & SEO Team

Replatforming, który zachowuje ruch: architektura migracji, inżynierowie Shopify, WordPress/WooCommerce i PrestaShop/Magento, techniczne SEO, mapowanie treści i URL-i, ciągłość analityki i Search Console, SEO międzynarodowe.

8 agentów · 3 skilleInżynieria · v1.1.0