Compare proposed product work against supplied customer evidence, effort estimates and business constraints.
A priority list should explain tradeoffs rather than attach arbitrary scores. Agree on the goal and compare candidates using consistent criteria. Effort estimates and expected impact are assumptions unless they have supporting evidence.
Ask your chief to build a comparison table, highlight dependencies and propose an order. Include reasons to defer each candidate and questions that could change the decision. An existing team can discuss the alternatives in a board meeting.
Review whether scoring creates false precision. Unknown engineering work should not be assigned a convenient duration. Your team retains the final decision, and the review does not automatically create tickets or change a roadmap.
Review the product priorities I supply against our goals, evidence, effort and dependencies. Explain tradeoffs, identify unknown estimates and propose an order with reasons. Do not create tickets or promise delivery dates.
Sign in for a written first result before payment setup. Computer work needs an active trial or paid plan and remaining allowance.
Start with the written draft described in the prompt. Ask for missing facts and review the result before requesting a saved file or further action.
An active computer trial or paid plan and remaining allowance are needed for browser, code and saved-file work. A written first preview is available before payment setup, subject to preview limits.
Group customer feedback into themes while preserving source references, exceptions and the limits of your sample.
Explore this workflow ↗
Ask your existing AI chiefs to discuss a business question. Read saved contributions, review the synthesis and follow up in the same conversation.
Explore this workflow ↗Start with one message and route work to an existing AI specialist. Use @mentions, keep a clear handoff and build your team around actual tasks.
Explore this workflow ↗
