Chapter 339

Common Problems and Solutions

1 min read

Problem 1: Generic, Bland Outputs

Symptoms: - Responses feel like they could apply to anything - Lacking specific details or personality - Cookie-cutter language

Diagnosis: Your prompt lacks sufficient context and constraints.

Solutions: ```text INEFFECTIVE: Write about productivity

EFFECTIVE: You're a productivity coach who specializes in helping creative professionals. Write about the "Power Hour" technique, specifically how graphic designers can use focused 60-minute sprints to overcome creative blocks. Include a real-world scenario, and three specific implementation tips. Use an encouraging but practical tone. ```text Quick Fixes: 1. Add specific role assignment 2. Include concrete examples 3. Define your target audience 4. Specify desired tone and style 5. Provide success criteria

Problem 2: Off-Topic Responses

Symptoms: - AI discusses something different than requested - Tangential information dominates - Core request gets buried

Diagnosis: Ambiguous language or competing instructions in your prompt.

Solutions: ```text INEFFECTIVE: Tell me about communication in the workplace and how teams work

EFFECTIVE: Focus specifically on asynchronous communication tools for remote teams. Explain: 1) Top 3 tools and their best use cases, 2) Common mistakes to avoid, 3) Implementation timeline for a 50-person company. Ignore general team dynamics—only discuss communication tools. ```text Quick Fixes: 1. Use "Focus specifically on..." 2. Number your requirements 3. Add "Ignore..." for what to exclude 4. Break complex requests into steps 5. Use clear section headers

Problem 3: Wrong Format or Structure

Symptoms: - Information presented differently than needed - Missing organizational elements - Inconsistent formatting

Diagnosis: Insufficient format specification or conflicting structure requests.

Solutions: ```text INEFFECTIVE: Give me information about project management

EFFECTIVE: Create a structured guide with these exact sections: