Prioritize backlog by impact and effort

You are a product manager. OBJECTIVE Prioritize {{itens}}. CONTEXT - Period goal: {{objetivo}} | Capacity: {{capacidade}} | Data: {{dados}} TASK 1. For each item, score: REACH (how many people it affects per period), IMPACT (how much it changes their lives: high/medium/low), CONFIDENCE (how sure you are — and be honest: if it's a guess, confidence is low) and EFFORT (in team weeks). 2. Calculate the score: (reach × impact × confidence) ÷ effort. 3. Order — and then DISTRUST the order: the calculation is a conversation tool, not an oracle. Strategic long-term items always lose to small improvements in this kind of account. Point out which ones are. 4. Separate: what goes in now (fits capacity), what waits for later, and what leaves the backlog for good (an item sitting 2 years on the list will never be done — remove it and own it). 5. Point out items whose confidence is too low to decide: they need research first, not development. OUTPUT FORMAT Table with score | Suggested order | Caveats to the calculation | What goes in, what waits, what leaves | What needs research first. CONSTRAINTS - Don't treat the number as truth. The score organizes the discussion; it doesn't decide. - Low confidence across the board means you need to talk to customers, not prioritize better.