أداة بناء مصفوفة القرار: حوّل قراراً متعدد الخيارات إلى توصية مرجّحة وقابلة للدفاع
لماذا تهم هذه المطالبة
Undocumented gut-call decisions get re-litigated the moment results are anything less than perfect, because there's no record of what was actually weighed. A written, weighted analysis with an explicit sensitivity check settles the argument the first time, and gives you a concrete artifact to revisit if the underlying assumptions change, instead of relying on someone's memory of a conversation that happened weeks earlier.
فيم نستخدمها
You're facing a decision with three or more viable options — a vendor selection, an infrastructure migration path, a hiring choice between finalists, a build-versus-buy call — and need to present a recommendation that will hold up when a skeptical stakeholder asks why you didn't pick a different option.
المطالبة
Role: Act as a senior decision-analysis consultant who helps executives and teams make high-stakes, multi-option decisions using structured, defensible frameworks — the kind of analysis that survives being challenged in a leadership meeting. Context: - The decision I'm facing: [DESCRIBE THE DECISION IN 1-2 SENTENCES] - The options I'm considering: [LIST 3-6 OPTIONS, ONE PER LINE] - The criteria that matter for this decision: [LIST 4-8 CRITERIA, e.g. upfront cost, time-to-value, team capacity required, reversibility, strategic fit] - Any hard constraints or dealbreakers: [LIST ANYTHING THAT AUTOMATICALLY DISQUALIFIES AN OPTION, OR WRITE "NONE"] - Who else needs to be convinced by this analysis: [E.G. "MY CO-FOUNDER," "THE BOARD," "MYSELF ONLY"] Task: 1. First, propose a weighting (out of 100 total points) across the criteria I listed, and explain your reasoning for each weight in one sentence. Pause here so I can adjust before you proceed. 2. Score each option against each criterion on a 1-10 scale, with a one-line justification for every score — no unexplained numbers. 3. Calculate the weighted total for each option. 4. Identify the top-scoring option and flag any options that are statistically too close to call (within 5% of each other). 5. Run a sensitivity check: identify which single criterion, if reweighted by plus or minus 15 points, would change the recommended option. State explicitly if this exists — a fragile recommendation should be labeled as such. 6. Write a final recommendation in plain language, including the strongest argument against your own recommendation and why you're making it anyway. Constraints: - Do not silently round close scores into a false sense of certainty — say explicitly when the decision is close. - Do not use vague criteria labels — operationalize each one in half a sentence before scoring. - If any option violates a stated hard constraint, exclude it from scoring entirely and explain why. - Keep the tone analytical and neutral — no cheerleading for any option. Output Format: 1. A markdown table: rows = options, columns = criteria plus weighted total, sorted highest to lowest. 2. A short "How I Weighted This" section (2-4 sentences). 3. A "How Close Is This" section flagging any near-ties or fragile results. 4. A final recommendation paragraph including the steelman case against it.
النتيجة
How I weighted this
I weighted Time-to-Value highest (30 points) because your Friday deadline and board skepticism suggest speed-to-first-results matters more than long-term elegance right now. Risk of Outage (25 points) comes second since you're mid-fundraise and a customer-facing incident would be costly beyond the technical fix. Team Capacity Required (20 points) reflects your 12-person team's limited bandwidth. Reversibility (15 points) and Total Cost Over 12 Months (10 points) round it out — cost matters less than the other three given your current runway.
| Option | Time-to-Value (30) | Risk of Outage (25) | Team Capacity (20) | Reversibility (15) | Cost (10) | Weighted Total |
|---|---|---|---|---|---|---|
| Lift-and-shift | 9 — deployable in 2 weeks with minimal refactoring | 6 — moves existing fragility as-is, doesn't fix root causes | 8 — low engineering lift | 9 — easy to roll back to on-prem if needed | 5 — higher ongoing cloud spend from unoptimized resources | 78.5 |
| Containerize-and-migrate | 6 — 6-8 week timeline for containerization work | 8 — improves isolation and rollback granularity | 5 — requires Docker/K8s ramp-up for two engineers | 7 — moderately reversible, some rework needed | 7 — better resource utilization | 67.5 |
| Full re-architecture | 2 — 4-6 month timeline, misses your deadline entirely | 9 — addresses root causes directly | 2 — consumes most of the team's bandwidth for two quarters | 3 — hard to reverse once started | 8 — best long-term unit economics | 44.5 |
How close is this
This isn't close — lift-and-shift leads containerize-and-migrate by 11 points, well outside the 5 percent fragility threshold. The one criterion that could flip the recommendation is Time-to-Value: if you reweighted it down by 15 points (to 15) and shifted that weight to Risk of Outage, containerize-and-migrate would edge ahead by roughly 3 points. Worth flagging to your board member if they push back on speed as the top priority.
Recommendation
Go with lift-and-shift for this cycle. The strongest argument against this: it doesn't fix any of the architectural problems that got you here, and you'll likely be having this exact conversation again in 9-12 months once traffic grows. But given your Friday deadline and board skepticism, a working migration you can demo now is worth more than a better migration you can't show yet. Plan the containerize-and-migrate path as your Q2 follow-up, not a competing option for this decision.
تُتخذ معظم القرارات عالية المخاطر ذات الخيارات المتعددة بناءً على الحدس المُلبَّس ثوب التحليل — يختار القائد الخيار الذي "شعر بأنه صحيح"، ثم يُهندس تبريراً عكسياً إذا سأل أحدهم. يسير هذا بخير حتى يسوء القرار، وعندها لا يوجد سجل لما تم وزنه فعلاً، وتتحول المحادثة إلى "لماذا لم نفكر في الخيار س" دون إجابة مقنعة.
لماذا صيغ هذا الـ prompt بهذه الطريقة
يطلب الـ prompt من النموذج اقتراح الأوزان أولاً والتوقف للتأكيد قبل تسجيل أي نقاط. هذا الترتيب مهم: إذا حدث الوزن والتسجيل في مرحلة واحدة، يسهل على نموذج (أو شخص) أن يُهندس عكسياً بلا وعي أوزاناً تنتج الإجابة التي كان يريدها أصلاً. فصل الخطوتين يجبر منطق الترجيح على الوقوف بمفرده، قابلاً للدفاع بمعزل عن الخيار الذي سيفوز في النهاية.
التعليمة بتبرير كل نقطة فردية بجملة واحدة — لا مجرد المجاميع النهائية — هي القيد الثاني الحاسم. مصفوفة مرجّحة بأرقام غير مُفسَّرة ليست أكثر صرامة من قرار حدسي؛ إنها قرار حدسي يرتدي زي جدول بيانات. إجبار تبرير من سطر واحد لكل خلية يجعل التفكير قابلاً للتدقيق.
الخطوة التي تتخطاها معظم الأطر
فحص الحساسية — تحديد أي معيار واحد، إذا أُعيد ترجيحه بمقدار ±15 نقطة، سيقلب التوصية — هو ما يميز هذا عن قالب تسجيل ثابت. معظم مصفوفات القرار تقدم لقطة في نقطة زمنية واحدة وتوحي بثقة زائفة. قرار قريب سينقلب بترجيح متواضع ومعقول يختلف جوهرياً عن قرار متين عبر نطاق واسع من الترجيحات المعقولة.
أين يُثبت هذا الـ prompt جدارته
هذا ليس للقرارات التافهة — اختيار مكان للغداء لا يحتاج مصفوفة مرجّحة. إنه مصمم لحفنة القرارات ذات الخيارات المتعددة في كل ربع سنة التي يكلف الخطأ فيها كثيراً وحيث تهم العملية الموثّقة بقدر أهمية الإجابة: اختيار المورّدين، مسارات ترحيل البنية التحتية، المرشحين المتنافسين للوظيفة، قرارات البناء مقابل الشراء.