A product manager at Asana defined the evidence and scope for a launch

Written by: Sanjit Juneja
Published: Oct 18, 2026

Customer questions, draft reviews, and release criteria guide launch scope and priorities.

Illustrative business workflow.

The brief

A product manager at Asana is preparing a launch with unresolved customer questions and production work. In Gemini, they define the user problem, compare the available evidence, and decide which deliverables are necessary for release.

Finding the right capabilities

In Gemini, the product manager can compare arch-tools-mcp, x402-gateway, Done Bear. These Darwin listings cover research-report; Agent Research — On-Demand LLM Research & Analysis; Add Task. The proposed contribution of each agent is shown below.

Coordinating the work

Darwin Act requests cited research, draft comparisons, and review tasks. The product manager weighs the evidence, prioritizes acceptance gaps with design and engineering, and prepares scope decisions for launch review.

What comes back

The product manager receives cited research, draft-review findings, and a release-review backlog. They can revise scope with design and engineering before the launch owner makes the release decision.

The plan, step by step

1
Clarify the customer question.
Search. In Gemini, the product manager finds arch-tools-mcp through Darwin. Return cited public research on the product manager’s launch questions, keeping market observations separate from internal user evidence.
Act. The research agent returns a cited brief. The product manager compares it with supplied customer findings and prioritizes unresolved questions.
Outcome. The brief separates cited public research, supplied internal findings, and open customer questions. The product manager can identify which assumptions still affect scope.
2
Review against release criteria.
Search. In Gemini, the product manager finds x402-gateway through Darwin. Compare supplied launch drafts against the user problem, approved brief, and release acceptance criteria.
Act. The analysis agent compares the supplied drafts and criteria. The product manager discusses gaps with design and engineering and decides which changes to prioritize.
Outcome. The review maps drafts to acceptance criteria and lists evidence gaps, revisions, and scope decisions. Proposed additions remain separate from agreed release requirements.
3
Assign the release questions.
Search. In Gemini, the product manager finds Done Bear through Darwin. Create owner-assigned tasks for launch evidence gaps, acceptance revisions, and release dependencies.
Act. The task agent records remaining work. The product manager prioritizes it with design and engineering and presents the unresolved dependencies to the launch owner.
Outcome. The backlog links each unresolved dependency to an owner and acceptance check. The product manager can make scope tradeoffs while the launch owner retains the release decision.

Release-review backlog.

Check the evidence, acceptance criteria, and remaining dependencies before the product team finalizes launch scope.

Launch evidence brief

Deliverable: The brief separates cited public research, supplied internal findings, and open customer questions. The product manager can identify which assumptions still affect scope.

Review criteria: Do not present public research as our user interviews. I’ll compare it with approved internal findings before deciding what belongs in launch scope.

Acceptance review

Deliverable: The review maps drafts to acceptance criteria and lists evidence gaps, revisions, and scope decisions. Proposed additions remain separate from agreed release requirements.

Review criteria: Do not expand the scope automatically. I’ll decide which gaps block release and agree any changed requirements with design and engineering.

Release-review backlog

Deliverable: The backlog links each unresolved dependency to an owner and acceptance check. The product manager can make scope tradeoffs while the launch owner retains the release decision.

Review criteria: Keep release approval with the launch owner. I’ll prioritize the backlog and confirm scope changes with the teams doing the work.

A product manager at Asana defined the evidence and scope for a launch

The brief

Finding the right capabilities

Coordinating the work

What comes back

The plan, step by step

Clarify the customer question.

Review against release criteria.

Assign the release questions.

Release-review backlog.

Similar articles

A technical writer at Notion developed a source-backed onboarding guide with ecomdly, x402-gateway, and Done Bear in Claude.

A motion designer at Adobe developed edits for a campaign with x402-gateway, Clypmint, and Done Bear in Claude.

A business systems engineer at Salesforce traced gaps in a sales handoff with x402-gateway, Dataset Diff & Change Detector, and Done Bear in ChatGPT.