For Consultants

Debate

Dialectical Reasoning

Thesis, antithesis, synthesis. Stress-test ideas through formal argumentation.

The Transformation

Before scenario
(Coming soon)

After transformation
(Coming soon)

See It In Action

Scenario: “Build vs Buy: Should we develop in-house or purchase a solution?”

Thesisarg-001
Confidence:72%

We should build authentication in-house for complete control and long-term cost savings

Antithesisarg-002
Confidence:78%
Responds to arg-001Contradicts arg-001

We should buy a proven auth solution (Auth0, Okta) for faster time-to-market and enterprise security

Dialectical Exchange
Objectionarg-003
Confidence:65%
Responds to arg-002Supports arg-001Contradicts arg-002

The vendor dependency creates unacceptable strategic risk for our authentication infrastructure

Rebuttalarg-004
Confidence:70%
Responds to arg-003Supports arg-002Contradicts arg-003

Modern abstraction patterns and multi-vendor strategies effectively mitigate vendor risk concerns

Synthesisarg-005
Confidence:85%
Responds to arg-004Supports arg-001Supports arg-002

A hybrid approach—buying core auth while building an abstraction layer—maximizes benefits and minimizes risks

Dialectical Resolution

Adopt hybrid approach: Start with Auth0 for core auth (2-week launch), build abstraction layer in month 2, add custom flows as needed. Revisit full build-vs-buy at 10K MAU threshold when we have more data on our specific needs.

Contradicts
Supports
Synthesizes

When to Use Debate

  • 1
    Testing the strength of your position
  • 2
    Exploring opposing viewpoints systematically
  • 3
    Preparing for stakeholder objections
  • 4
    Finding weaknesses in proposals
  • 5
    Reaching synthesis from conflicting ideas

Works Well With

Pro tip: Chain Debate with Council → Decide for comprehensive analysis.

Ready to use Debate?

Add Think to your AI assistant in one command

npx @anthropic-ai/claude-code mcp add think-mcp
View all tools•GitHub