Structure Your Thinking Before You Speak

Complex arguments need visual organization. A clear hierarchy makes your reasoning easy to follow.

The Basic Structure

Main Claim (Top Level)

• Supporting Argument 1
  • Evidence A
  • Evidence B
• Supporting Argument 2
  • Evidence C
  • Evidence D
• Supporting Argument 3
  • Evidence E
  • Evidence F

Student Example: Essay Outline

Thesis: Universities should embrace online learning

Support 1: Accessibility

• Evidence: Students in remote areas gain access
• Evidence: Reduces commute time and costs

Support 2: Flexibility

• Evidence: Students can learn at their own pace
• Evidence: Accommodates work schedules

Support 3: Cost-effectiveness

• Evidence: Lower infrastructure costs
• Evidence: Reaches more students per dollar

Professional Example: Business Presentation

Proposal: Expand to Market Y

Support 1: Large addressable market

• Evidence: 50M potential customers
• Evidence: $5B market size

Support 2: Low competition

• Evidence: Only 3 competitors
• Evidence: No dominant player

Support 3: We have the capabilities

• Evidence: Existing distribution network
• Evidence: Similar customer profile

Why It Works

Clean hierarchy = clear thinking. If you can't map it, you don't understand it well enough.

Lead with Your Main Point, Then Support It

Most people build up to their conclusion. Effective communicators do the opposite.

Traditional (Bottom-Up)

"We surveyed 500 customers. 80% want feature X. Competitors don't offer it. Engineering says it's feasible. Therefore, we should build feature X."

Problem: Listener is waiting to see where you're going.

Pyramid (Top-Down)

"We should build feature X. Here's why: customer demand is high (80% want it), competitive advantage (nobody offers it), and feasibility (engineering confirms it's doable)."

Benefit: Listener immediately knows your point and can follow your reasoning.

Professional Structure

Top Level: Conclusion/Recommendation Second Level: 3-5 grouped supporting arguments Third Level: Evidence for each argument

Example

"We should expand to Market Y" (Top)

Why? Three reasons:

• Large market (Second level)
  • 50M potential customers (Evidence)
  • $5B market size (Evidence)
• Low competition (Second level)
  • Only 3 players (Evidence)
  • No dominant brand (Evidence)
• We're capable (Second level)
  • Existing distribution (Evidence)
  • Similar customer profile (Evidence)

When to Use

• Executive presentations
• Business proposals
• Any communication where people are busy

Mutually Exclusive, Collectively Exhaustive

Your arguments should cover everything (exhaustive) without overlapping (exclusive).

What MECE Means

Mutually Exclusive: No overlap Collectively Exhaustive: Covers all possibilities

Student Example: Analyzing Study Time

Not MECE:

• Weekday studying
• Weekend studying
• Morning studying
• Evening studying

Problem: "Morning" and "Weekday" overlap!

MECE Version 1:

• Weekday studying
• Weekend studying

MECE Version 2:

• Morning studying (6am-12pm)
• Afternoon studying (12pm-6pm)
• Evening studying (6pm-12am)
• Night studying (12am-6am)

Professional Example: Revenue Analysis

Not MECE:

• Product A sales
• Product B sales
• Online sales
• Retail sales

Problem: "Product A" can be sold "Online" or "Retail" - overlap!

MECE:

• Product A revenue
• Product B revenue
• Service revenue

OR

• Online channel revenue
• Retail channel revenue
• Direct sales revenue

Why It Matters

MECE ensures:

• Nothing falls through cracks (exhaustive)
• No double-counting (exclusive)
• Clear, logical categories

How to Check

Can an item fit into multiple categories? (Not exclusive) Is there something that doesn't fit anywhere? (Not exhaustive)

Some Arguments Depend on Others

Not all supporting arguments are independent. Some only work if others are true first.

Understanding Dependencies

Independent Arguments: Each stands alone

• Argument A can be true even if B is false
• Argument B can be true even if A is false

Dependent Arguments: One relies on another

• If Argument A is false, Argument B collapses
• B is built on the foundation of A

Example: Expanding Business Hours

Independent Arguments:

1. Customers want later hours (survey data)
2. Competitors offer late hours (market research)

If #1 is false, #2 still supports the decision.

Dependent Arguments:

1. Later hours will bring more customers
2. More customers will increase revenue
3. Revenue will exceed the staffing costs

If #1 is false (late hours don't bring customers), then #2 and #3 automatically fail.

Why This Matters

In debates, attack the foundational arguments. If you topple the foundation, dependent arguments collapse without needing to address them individually.

How to Map Dependencies

1. List all your arguments
2. For each one, ask: "Does this require another argument to be true?"
3. Draw arrows showing dependencies
4. Ensure your foundation is rock-solid

Professional Application

In project planning, map dependencies to know which risks are critical vs secondary.

Turn Mapping into a Habit

The best debaters and communicators map their arguments before presenting them.

The Exercise

Step 1: Take your next presentation, essay, or proposal

Step 2: On paper (or digital whiteboard), map it:

• What's my main claim?
• What are my 3-5 supporting arguments?
• What evidence backs each one?
• Are there dependencies?
• Is it MECE?

Step 3: Ask someone to review your map

• Can they follow your logic?
• Do they see gaps?
• Are there weak links?

Step 4: Revise the map, THEN create your actual content

Why Maps First, Content Second

Problem: Most people write/speak first, then try to organize Solution: Organize first (via mapping), then write/speak

Mapping reveals:

• Weak arguments you should drop
• Missing evidence you need to find
• Better ordering for impact

Student Application

Before writing a term paper, map your argument. Your outline will be clearer and writing faster.

Professional Application

Before big presentations, map on a whiteboard with your team. Polish the logic before polishing the slides.

Success Metric

If you can't draw your argument as a clear map, you're not ready to present it.