HomeResourcesStrategyAndrew PershJuly 25, 202610 min read

The Consulting Toolkit: Core Methods, Skills, and Prompts

The consulting toolkit on this page is six methods, in the order a real engagement uses them: frame the problem, structure the argument, communicate it, and a field guide to go deeper. Each one links to its full guide, its exhibit, and the Claude skill pack that turns it into a repeatable prompt.

30,000+ consultants, bankers, private equity professionals

Free skills and prompts for Claude and strategy work

Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.

What the Consulting Toolkit Covers

This consulting toolkit is the small set of methods that carry a strategy engagement from a vague question to a slide a partner will sign off on. Six entries, grouped into the four stages a real engagement actually moves through: frame the problem, structure the argument, communicate it, and a field guide to go deeper once those five are second nature.

Every entry below links to its own full guide, with worked examples, copy-paste prompts, and an exhibit. This page is the map. Read it top to bottom once, then come back to it as a reference whenever you need to pick the right tool for what you are solving right now.

1. Frame and Test the Problem

Before any analysis, get the question right. These two methods structure the problem itself, not the answer, and everything else in this toolkit works better once one of them is in place.

1

Issue Trees

Break one broad, ambiguous question into a hierarchy of smaller, MECE sub-questions you can assign and solve in parallel. It is the right starting point whenever the answer is not yet obvious and the team needs a map before it needs data. issue trees: how to build and present one.

2

Hypothesis-Driven Problem Solving

Start from a testable, best-guess answer instead of an open-ended research plan, then design the fastest test that could prove it wrong. Reach for it once you already have enough early signal to name a likely answer. the guide to hypothesis-driven problem solving.

2. Structure the Argument

Once the problem is framed and the analysis has run, these two methods turn raw findings into an argument that survives a partner's questions.

3

MECE Principle

Check that any breakdown, an issue tree branch, a hypothesis's sub-claims, a slide's bullet groups, does not overlap and does not leave a gap. It is the single test every other method in this toolkit has to pass before it holds up. the MECE principle, with examples and tests.

4

Pyramid Principle

State the governing thought, the one-sentence answer, before the supporting detail, then group the evidence into three or four defensible arguments. It turns validated analysis into an answer a partner can act on in a single read. the pyramid principle in consulting.

3. Communicate It

A structured argument still has to run across a real deck, in an order a busy reader can follow without you in the room.

5

Storylining a Consulting Deck

Sequence a pyramid-structured argument across a deck of action-titled slides, so the titles alone tell the whole story to a reader who skims them top to bottom. It is where the pyramid principle stops being an outline and becomes something you can present. storylining a consulting deck.

4. Go Deeper

These five methods carry most engagements most of the way. When the specific analysis calls for a named framework, a market sizing, a competitive scan, a roadmap, this is the reference to reach for next.

6

Management Consulting Frameworks: The 2026 Field Guide

Once these five methods are second nature, this field guide covers 16 more, from Porter's Five Forces to a RACI matrix, grouped by the stage of the engagement where each one earns its place. the full field guide to consulting frameworks.

The Consulting Toolkit as One Arc

The exhibit below lays out the whole consulting toolkit as a single arc, from framing the question to a finished, editable slide, so you can see how the six methods and the skill packs below connect before reading each entry on its own.

The consulting toolkit mapped across four stages: frame, structure, communicate, and build, ending in an editable slide

Skill Packs for the Consulting Toolkit

Each method above works by hand, but a skill pack saves you from re-explaining it every time. A skill is a small markdown file you upload once to a Claude project, so any conversation in that project can run the method on command. These packs cover the six methods above and the wider engagement around them.

10 Claude Skills for Strategy Professionals

A broad starter set covering the everyday tasks a strategy team repeats: framing, sizing, synthesis, and slide storylines.

5 Strategy Claude Skills for the Full Consulting Engagement

Five skills sequenced to match a real engagement from kickoff to final deck, rather than a grab-bag of unrelated prompts.

50 Tier-1 Strategy Skills for Claude: Full Engagement

A deep, tier-1-grade set spanning every stage of a strategy engagement, for teams who want full coverage rather than a starter pack.

MECE Issue Tree Skill: Consulting-Style Problem Analysis in Claude

Packages the issue tree and the MECE test above into one reusable skill, so every problem gets split the same disciplined way.

A Claude Skill for Consulting-Grade Problem Solving

Turns the hypothesis-driven method above into a skill Claude runs on command, from the day-one claim to a validated answer.

The Claude Skill Factory for Strategy: Build Your Own Skills

For methods that do not match a pre-built pack, a skill for building new skills out of your own team's playbook.

Quick Reference: When to Use Each Method

Use this table to jump straight to the right method without reading every entry above first.

Issue Trees
The problem is broad and you need to split it before you can assign it.
Hypothesis-Driven Problem Solving
You already have a candidate answer and want to test it fast.
MECE Principle
You need to check a breakdown for overlaps or gaps before you trust it.
Pyramid Principle
You have a validated answer and need to structure it for a reader.
Storylining a Consulting Deck
The argument is structured and now has to run across a real deck.
Framework Field Guide
You need a specific analytical tool, like a 2x2 or a value chain map.

How the Toolkit Runs on One Engagement

Say the question is whether a mid-size retailer should launch a subscription program. Here is the same six-method toolkit run start to finish.

1

Frame. An issue tree splits the question into three MECE branches: will customers want it, can the retailer operate it, and does it make economic sense. Early interviews already point toward yes, so the team writes a day-one hypothesis instead of researching all three branches open-ended.

2

Test. The hypothesis, "a subscription program is viable if churn stays under 5 percent and margin holds above 20 percent," splits into two testable sub-claims. The team runs the fastest, most decisive test on each one first.

3

Structure. Once both sub-claims hold, MECE checks that the supporting evidence does not overlap. The pyramid principle then compresses everything into one governing thought and three supporting arguments a partner can read in one pass.

4

Communicate. The pyramid becomes a ten-slide storyline with action titles that carry the argument on their own, then the team builds the deck in Oria from that storyline instead of formatting slide by slide.

Every step above is one Claude conversation and one Oria prompt, and every method it uses is covered in full, with its own prompts and exhibit, in the guides linked from this page.

Common Mistakes When Using This Toolkit

Picking a framework before the decision question is actually clear.
Building an issue tree and skipping the MECE test because it "feels" complete.
Writing the pyramid structure after the deck instead of before it.
Installing a skill pack without first learning the method it automates.
Storylining slide by slide instead of testing the action titles as a set.
Treating this hub as a one-time read instead of a page to come back to.

Try One Method Right Now

You do not need to read all six guides before trying the toolkit. Paste your own problem into the prompt below and Claude will hand you back a MECE issue tree, the first step of the whole method, in under a minute.

Frame a new problem with an issue tree

Here is the problem I am trying to solve: [state it in one sentence]. Restate it as a single decision question, then build a MECE issue tree three levels deep: branches that are mutually exclusive and collectively exhaustive, with no overlap and no gap. For each branch, state the hypothesis and the fastest test that would prove or kill it.

Tip

Once one branch clearly looks strongest, switch to the hypothesis-driven method and test that branch directly instead of finishing the whole tree.

Frequently Asked Questions

What is the consulting toolkit on this page?

The consulting toolkit is the small set of methods that carry a strategy engagement from a vague question to a slide a partner will sign off on: issue trees, hypothesis-driven problem solving, MECE, the pyramid principle, and storylining, plus a field guide to 16 more analytical frameworks and the Claude skill packs that turn each method into a repeatable prompt.

Where should I start if I am new to these methods?

Start with issue trees and the MECE principle. Every other method on this page, hypothesis-driven problem solving, the pyramid principle, and storylining, assumes you can already split a problem into parts that do not overlap and do not leave a gap. Once that habit is automatic, the rest follows in the order listed here.

What is the difference between a method and a skill pack?

A method, like the pyramid principle or MECE, is a way of thinking you apply by hand, described in a full guide with worked examples. A skill pack is that same method packaged as a small file you upload to a Claude project once, so Claude runs it the same way every time without you re-explaining it.

Do I need all six methods on every engagement?

No. Most engagements use an issue tree or a hypothesis to frame the question, MECE to check the structure, and the pyramid principle plus storylining to communicate the answer. The field guide's 16 additional frameworks get pulled in only when the specific analysis calls for them, a market sizing, a competitive scan, or a roadmap.

How do these methods connect to building the actual slide?

Each guide linked from this page ends with the prompts and the exhibit for that method, so the thinking and the slide layout come from the same place. Once the analysis is done, describe it to Oria in one line and it returns 2 to 5 fully editable design options in 30 to 40 seconds, on your own template.