Um Prompt de matriz de decisão ponderada para escolhas mais rápidas em equipe
Why this prompt matters
Teams waste weeks revisiting the same decision when criteria are implicit, stakeholders optimize for different goals, and nobody can explain why an option won. A weighted matrix turns vague debate into an auditable decision record and exposes where disagreement actually lives.
What we use it for
Use this when you need to choose between several real options under time pressure, such as selecting a project management tool, vendor, framework, or job offer, and you want a defensible recommendation instead of gut feel.
Prompt
Role: Act as a senior strategy analyst helping me make a high-stakes decision with a transparent weighted scoring model. Context: I am deciding between [OPTION 1], [OPTION 2], [OPTION 3], and [OPTION 4] for [DECISION CONTEXT]. The decision matters because [WHY THIS DECISION MATTERS]. My constraints include [BUDGET], [TIMELINE], [TEAM SIZE], and [NON-NEGOTIABLE REQUIREMENTS]. Task: Build a weighted decision matrix that compares the options across the criteria I provide. Use these criteria and weights, adding up to 100: [CRITERION 1 + WEIGHT], [CRITERION 2 + WEIGHT], [CRITERION 3 + WEIGHT], [CRITERION 4 + WEIGHT], [CRITERION 5 + WEIGHT]. Score each option from 1 to 10 on every criterion, explain each score in one or two sentences, calculate weighted totals, rank the options, and recommend the best choice. Then stress-test the recommendation by showing which option would win if the top-weighted criterion changed by plus or minus [SENSITIVITY %]. Constraints: Do not use vague language. If information is missing, list the missing inputs explicitly and make the smallest reasonable assumption. Do not force a tie. Call out hidden risks, second-order effects, and cases where the highest-scoring option may still be the wrong practical choice. Output Format: 1) Decision summary, 2) assumptions and missing data, 3) weighted decision matrix in table form, 4) ranking with weighted totals, 5) recommendation with rationale, 6) sensitivity analysis, 7) next steps before committing.
Result
Decision summary: Based on the weighted matrix, Notion is the strongest fit for a 12-person remote product team choosing a project management platform for the next 18 months. It does not win every category, but it delivers the best overall balance of flexibility, cross-functional collaboration, documentation, and cost. Jira remains the better pure engineering tracker, while Asana is the easiest to adopt quickly, but neither matches Notion's combined score across the broader operating model this team needs.
Assumptions and missing data: I assumed the team needs one shared workspace for product, engineering, design, and operations, with a monthly software budget below $500. I also assumed the company values fast onboarding and documentation quality as much as sprint planning. Missing inputs that would affect the outcome include existing tool lock-in, compliance requirements, and whether the engineering team needs advanced issue hierarchy and release reporting.
Weighted decision matrix: Criteria were weighted as follows: collaboration and documentation 30, ease of adoption 20, engineering workflow support 20, automation and integrations 15, total cost 15. Notion scored 9, 8, 7, 8, and 9 respectively, producing a weighted total of 8.30. Jira scored 6, 5, 10, 9, and 7 for a total of 7.20. Asana scored 8, 9, 6, 7, and 6 for a total of 7.35. ClickUp scored 7, 6, 7, 8, and 8 for a total of 7.10.
Recommendation with rationale: Choose Notion if the company wants one system that supports planning, documentation, meeting notes, lightweight roadmapping, and cross-team visibility without adding another knowledge base. Its main weakness is deeper engineering workflow structure, so teams with strict release governance may still prefer Jira despite the lower blended score.
Sensitivity analysis: If engineering workflow support rises from 20 to 35, Jira becomes much more competitive and may overtake Notion, especially if the company already uses GitHub and wants stronger issue discipline. If collaboration and documentation fall below 20, Asana also narrows the gap. That means the decision is robust only if the organization truly values a shared operating system over a specialist tracker.
Next steps before committing: Run a two-week pilot with one live project, measure onboarding time, check migration friction, and ask each function to list one blocker that would make the chosen tool fail in practice.
Escolher entre várias opções boas é exatamente onde as equipes perdem tempo. A conversa parece produtiva, mas os critérios continuam implícitos, a voz mais alta empurra o resultado e a decisão volta à mesa duas semanas depois. Este Prompt corrige isso ao obrigar que os tradeoffs apareçam em uma matriz ponderada que toda a equipe pode revisar.
A estrutura importa. A seção Role coloca o modelo em modo analista, em vez de brainstorming genérico. A seção Context define o que está em jogo, as restrições e os pontos inegociáveis, mantendo a recomendação presa a uma decisão real de negócio e não a uma preferência abstrata. A seção Task faz o trabalho pesado: pontuar cada opção, explicar cada nota, calcular os totais ponderados e depois testar o resultado com sensitivity analysis.
Essa última parte é o que faz este Prompt valer a pena. Um Prompt de comparação comum entrega apenas uma lista ordenada. Um Prompt melhor mostra se o vencedor continua vencendo quando o critério mais importante muda. Se uma pequena alteração de peso inverter o resultado, o problema real não é a ferramenta nem o Vendor. É o alinhamento entre stakeholders.
Este Prompt também evita uma falha comum da AI: respostas confiantes construídas sobre dados ausentes. A seção Constraints manda o modelo explicitar lacunas de informação, fazer a menor suposição razoável possível e apontar situações em que a opção com maior pontuação talvez não seja a escolha prática certa. O resultado fica mais próximo de um decision memo do que de um palpite bem escrito.
Use-o para escolher software, tomar decisões de contratação, avaliar agências, comparar modelos de preço, resolver tradeoffs de roadmap ou qualquer outra escolha em que várias alternativas competitivas disputem critérios diferentes. A saída é fácil de colar em um documento, defender em uma reunião e revisitar depois se as premissas mudarem.