القائمة
Isolate the 20% of inputs driving 80% of results, and explicitly name what you're deprioritizing. Outputs a blockquote (vital 20%) plus a list (deprioritized 80%). Use for ruthless prioritization, "what should we focus on", or step 4 of a strategic analysis.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apply the 5 Whys technique to drill from a surface problem to a root cause. Outputs five sequentially numbered "Why?" lines with brief answers, ending in a root-cause statement. Use after an issue tree to drill the critical branch deeper, or any time the user wants to test whether the apparent cause is the actual cause.
Structure a recommendation top-down — Barbara Minto's Pyramid Principle. Outputs a single-sentence top-line answer, three to five supporting arguments, and one layer of evidence under each. Use to convert analysis into executive communication, or to structure a board-meeting talk track.
Tier-1 strategy-consultant analysis using seven frameworks in sequence — MECE, Issue Trees, 5 Whys, Hypothesis-Driven, Pareto, So What?, and Pyramid Principle. Use when the analysis needs both deeper root-cause drilling AND executive-ready communication structure. Heavier than the 5-framework master; reach for it on high-stakes work.
Tier-1 strategy-consultant analysis tailored for edtech / online-learning problems — activation, completion, learning outcomes, monetization. Same five frameworks with edtech-aware MECE defaults, vocabulary, and root-cause priors.
Tier-1 strategy-consultant analysis tailored for fintech / payments / lending / fraud problems — approval rates, fraud loss, delinquency, regulatory friction. Same five frameworks with fintech-aware MECE defaults, vocabulary, and root-cause priors.
Tier-1 strategy-consultant analysis tailored for public-sector / civic-ops problems — backlogs, processing cycle time, citizen satisfaction, procurement. Same five frameworks with government-aware MECE defaults, vocabulary, and root-cause priors.
| name | pareto-principle |
| description | Isolate the 20% of inputs driving 80% of results, and explicitly name what you're deprioritizing. Outputs a blockquote (vital 20%) plus a list (deprioritized 80%). Use for ruthless prioritization, "what should we focus on", or step 4 of a strategic analysis. |
In most systems, ~80% of the outcome comes from ~20% of the inputs. Strategy consultants use this constantly: figure out which 20% of customers, products, channels, or root causes drive the lion's share of impact, and ignore the rest until later.
The discipline isn't naming the vital 20%. It's having the spine to explicitly deprioritize the 80%. If everything is important, nothing is.
Two parts, in this order:
> **The vital 20%:** [Specific factors/segments/causes that drive the majority of impact.]
**Actively deprioritized (the 80%):**
- Item 1
- Item 2
| Default | When to flex |
|---|---|
| 1–4 items in the vital 20% | If the 80/20 genuinely points to one thing, use one. Don't pad. |
| 5–10 items in the deprioritized list | List enough to make the deprioritization visible — but if there are only 3 real alternatives, list 3. |
| Specificity in the vital 20% | Don't flex — "our top customers" is too vague. Name them. |
| Explicit deprioritization | Don't flex — implicit deprioritization is no deprioritization. |
The hardest discipline: writing down something that genuinely matters into the deprioritized list. If your 80% list is full of things that don't matter, you haven't really prioritized. Real Pareto says: "Yes, X matters. We're not doing X this quarter."
Problem: A mid-stage SaaS engineering team has 47 tracked tech-debt items. Leadership wants a focused six-month plan.
The vital 20%: Three items account for ~80% of incident pain and velocity drag: (1) the legacy auth middleware causing 60% of P2 tickets and forcing every new feature to add custom session handling, (2) the deploy pipeline averaging 47 minutes (preventing the team's stated daily-deploy cadence), and (3) the absence of integration tests on the billing module (the source of 4 of the last 6 customer-impacting incidents).
Actively deprioritized (the 80%):
Notice: several deprioritized items are real concerns. The point is naming them as not-this-half so the team has cover to focus.
strategy-consultant — Pareto is step 4 of 5. Run mece-framework and issue-trees first to enumerate the 100% before you can isolate the 20%.Adapted from Analyst Academy on YouTube — 5 Consulting Frameworks to Solve Any Problem. MIT-licensed; see LICENSE.