Strategy-Consultant-5-Consulting-Frameworks

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.

Tier-1 strategy-consultant analysis tailored for manufacturing / industrial-ops problems — OEE, defect rate, yield, supply chain. Same five frameworks with manufacturing-aware MECE defaults, vocabulary, and root-cause priors.

Tier-1 strategy-consultant analysis tailored for nonprofit / fundraising / donor-retention / program problems. Same five frameworks with nonprofit-aware MECE defaults, vocabulary, and root-cause priors.

Decompose a core problem into root causes with an ASCII tree. Outputs a fenced code block using box-drawing characters. Use for root-cause analysis, drilling from a high-level problem down to testable sub-problems, or step 2 of a strategic analysis.

Tier-1 strategy-consultant analysis with parallel sub-agents — one per framework (MECE, Issue Trees, Hypothesis-Driven, Pareto, So What?) — synthesized into a single whiteboard-style response. Use for high-stakes or complex problems. Requires Task/Agent tool.

Tier-1 strategy-consultant analysis. Apply five frameworks (MECE, Issue Trees, Hypothesis-Driven, Pareto, So What?) sequentially with strict whiteboard-style visual output. Use for root-cause breakdown, strategic problem framing, or "consultant-style" thinking on a business problem.

Tier-1 strategy-consultant analysis tailored for healthcare / hospital ops problems — readmissions, length of stay, access, outcomes, throughput. Same five frameworks as the generic master, with healthcare-aware MECE defaults, industry vocabulary, and common root-cause patterns. Use for clinical-operations problems.

Tier-1 strategy-consultant analysis tailored for retail / hospitality problems — same-store-sales, foot traffic, basket size, mix, store ops. Same five frameworks as the generic master, with retail-aware MECE defaults, industry vocabulary, and common root-cause patterns. Use for retail-specific problems.

Tier-1 strategy-consultant analysis tailored for SaaS / B2B software problems — ARR, churn, pipeline, NRR, product-led growth. Same five frameworks as the generic master, but with SaaS-aware MECE defaults, industry vocabulary, and common root-cause patterns. Use for SaaS-specific problems; for cross-industry framing use `strategy-consultant`.

State a falsifiable hypothesis, then build a Markdown table comparing what you'd Expect to see if it's true vs. the Actual data (or what data is needed). Use for designing analysis plans, pinpointing where reality diverges from expectation, or step 3 of a strategic analysis.

Categorize the factors of a problem so they don't overlap (Mutually Exclusive) and nothing is missed (Collectively Exhaustive). Outputs nested Markdown bullets. Use for problem structuring, "make sure I've thought of everything", or step 1 of a strategic analysis.

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.

Translate analysis findings into an actionable insight using three labeled sections (Process, Result, Insight). Use when the user has data but needs a recommendation, when an analysis ends without action, or step 5 of a strategic analysis.