> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omnifact.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Thinking Step by Step (Chain of Thought)

> Guide Omnifact through complex reasoning processes for more accurate and transparent results.

<Card title="Break It Down for Better Results" horizontal>
  When you ask Omnifact to think through problems step by step, you often get better answers and can see the reasoning behind them.
</Card>

## What is Chain of Thought Prompting?

Chain of Thought prompting is asking Omnifact to show its work—to break down complex problems into smaller, logical steps rather than jumping straight to conclusions. This technique can improve accuracy for tasks involving analysis, logic, or multi-step reasoning.

**The core principle:** Guide Omnifact to work through problems methodically, just like you would explain your thinking to a colleague.

When you ask for step-by-step reasoning, you often get:

* **Better accuracy** because Omnifact considers each part of the problem
* **Clearer thinking** so you can follow the logic
* **More helpful analysis** for complex business scenarios

## Pair Step-by-Step Prompts with the Right Response Mode

Chain of Thought works best when the AI can use the sources your reasoning depends on:

* **[Auto](/en/platform/core-features/chats/response-modes)** (default): Best for multi-step analysis that may need web search, attached files, or Uploaded Files retrieval.
* **Quick Response:** Fine for logical puzzles or drafts from general knowledge, but the AI will not search documents or the web. Do not use it when your steps require external data.
* **Simple Lookup:** Use in Spaces when each step must cite only your uploaded documents.

<Tip>
  In Spaces, combine step-by-step phrasing with **Simple Lookup** when you need transparent reasoning grounded entirely in your team's documents. Learn more in [Keeping Responses Accurate and Factual](/en/guides/prompt-engineering/intermediate/staying-grounded).
</Tip>

## Key Phrases That Trigger Step-by-Step Thinking

Use these phrases to encourage step-by-step reasoning:

<CardGroup cols={2}>
  <Card title="Starting Phrases" icon="play">
    * "Let's think this through step by step"
    * "Work through this systematically"
    * "Break this down into steps"
    * "First, analyze... then..."
  </Card>

  <Card title="Guiding Phrases" icon="arrow-right">
    * "Consider each factor separately"
    * "Evaluate the pros and cons"
    * "Walk through the process"
    * "Show your reasoning"
  </Card>
</CardGroup>

## Basic Step-by-Step Structure

Use this reliable pattern for complex tasks:

```
[TASK] + "Let's think through this step by step:" + [CONTEXT/DATA]
```

**Example:**
"Determine the best pricing strategy for our new software feature. Let's think through this step by step:

* Current customer base: 500 small businesses
* Development cost: \$50,000
* Competitor pricing: \$25-40/month
* Our current plan: \$30/month base"

## Real-World Examples

**Budget Analysis:**
**Without Chain of Thought:** "Should we approve this \$15,000 marketing budget request?"

**With Chain of Thought:** "Evaluate this \$15,000 marketing budget request. Let's think through this step by step:

1. First, analyze if this aligns with our quarterly goals
2. Then, compare to our current marketing spend and ROI
3. Finally, assess the potential impact on revenue

Budget details: \[budget breakdown]
Current performance: \[metrics]"

**Process Improvement:**
**Without Chain of Thought:** "How can we improve our customer onboarding?"

**With Chain of Thought:** "Identify improvements for our customer onboarding process. Let's break this down:

1. First, analyze current onboarding metrics and pain points
2. Then, identify specific bottlenecks or friction areas
3. Finally, prioritize solutions based on impact and effort

Current process: \[process description]
Metrics: \[performance data]"

## Advanced Step-by-Step Techniques

### Multi-Layer Analysis

For complex business decisions, structure your request with multiple analysis layers:

```
Evaluate this partnership opportunity. Let's approach this systematically:

BUSINESS ANALYSIS:
1. First, assess strategic fit with our goals
2. Then, evaluate potential revenue impact
3. Finally, identify risks and mitigation strategies

OPERATIONAL ANALYSIS:
1. Consider resource requirements
2. Assess timeline and implementation complexity
3. Evaluate ongoing management needs

Partnership details: [information]
```

### Comparative Reasoning

When comparing options, guide Omnifact through structured comparison:

```
Compare these three vendor proposals step by step:

STEP 1: Evaluate each vendor's technical capabilities
STEP 2: Compare pricing and contract terms
STEP 3: Assess implementation timeline and support
STEP 4: Weigh pros and cons for final recommendation

Vendor proposals: [details]
```

## When to Use Step-by-Step Reasoning

<AccordionGroup>
  <Accordion title="Complex Problem Solving">
    **Perfect for:** Multi-variable decisions, process optimization, strategic planning <br />
    **Example:** "Evaluate whether to expand to a new market. Let's think through this systematically..."
  </Accordion>

  <Accordion title="Analytical Tasks">
    **Perfect for:** Data interpretation, performance analysis, cause-and-effect relationships <br />
    **Example:** "Analyze why our customer retention dropped last quarter. Break this down step by step..."
  </Accordion>

  <Accordion title="Planning and Prioritization">
    **Perfect for:** Project planning, resource allocation, timeline development <br />
    **Example:** "Create a launch plan for our new feature. Let's work through this methodically..."
  </Accordion>

  <Accordion title="Risk Assessment">
    **Perfect for:** Identifying potential problems, evaluating options, compliance checking <br />
    **Example:** "Assess the risks of this new vendor relationship. Consider each factor separately..."
  </Accordion>
</AccordionGroup>

## Common Mistakes and Solutions

<AccordionGroup>
  <Accordion title="Skipping the Setup">
    **Problem:** Asking for step-by-step thinking without providing context <br />
    **Solution:** Always include relevant background information and specific areas to consider <br />

    **Instead of:** "Think through this decision step by step: Should we hire more staff?" <br />
    **Try:** "Evaluate our staffing needs step by step: Current team: 12 people, Workload increase: 40%, Budget: \$200K, Timeline: Next quarter" <br />
  </Accordion>

  <Accordion title="Too Many Steps">
    **Problem:** Asking for overly detailed breakdowns that become confusing <br />
    **Solution:** Focus on 3-5 key steps for most business decisions <br />

    **Instead of:** "Break this into 15 detailed steps..." <br />
    **Try:** "Think through the 3-4 most important factors..." <br />
  </Accordion>

  <Accordion title="No Clear Structure">
    **Problem:** Asking for steps without guidance on what to analyze <br />
    **Solution:** Provide a framework or specific areas to consider <br />

    **Instead of:** "Analyze this step by step" <br />
    **Try:** "Analyze this step by step: 1) Financial impact, 2) Resource requirements, 3) Timeline feasibility"
  </Accordion>
</AccordionGroup>

<Tip>
  The more complex the decision, the more valuable step-by-step reasoning becomes. Start with simpler tasks to build the habit, then apply it to your most challenging business problems.
</Tip>

## Other Intermediate Guides

* Review [Separating Data and Instructions](/en/guides/prompt-engineering/intermediate/separating-data-instructions) to structure your prompts clearly
* Explore [Using Examples](/en/guides/prompt-engineering/intermediate/examples) to show exactly what you want
* Master [Avoiding Hallucinations](/en/guides/prompt-engineering/intermediate/staying-grounded) to keep responses factual and grounded