# Troubleshooting Bad AI Outputs

If the AI answer is bad, fix the system.

## Too generic

Add your audience, goal, examples, constraints, and output format.

## Making things up

Ask it to separate facts, assumptions, guesses, and questions. Verify important
facts outside the AI.

## Too long

Tell it the exact format, length, and decision you need.

## Feels risky

Stop and run the owner-gate checklist. Keep the output draft-only.

## Hard to judge

Ask AI to create a review checklist before rewriting.

## Keeps failing

Your workflow may be too broad. Pick one smaller task. Test one input. Improve
one instruction.

## Repair prompt

```text
This answer is not useful yet. Diagnose why.

Separate:
1. missing context;
2. unclear goal;
3. risky assumptions;
4. format problems;
5. facts that need verification;
6. one smaller version of the task.

Then rewrite the prompt I should use next time. Keep risky actions draft-only.
```

---

## Important boundary

DWAI shares practical AI and AI-developer-path resources for thinking,
drafting, organizing, researching, reviewing, learning, coding, debugging,
testing, building small AI apps, and shipping owner-controlled projects. This is
not therapy, counselling, diagnosis, ADHD or addiction treatment, medical advice,
legal advice, financial advice, tax advice, crisis support, regulated
professional advice, or a guarantee of clarity, productivity, income, saved
time, business results, jobs, clients, or any personal outcome. AI outputs are
drafts. The owner approves risky action.

---

## How to use this download

Use this resource for: How to fix generic, risky, too-long, hallucinated, or hard-to-judge AI answers by fixing the workflow.

- If you are new, start with the 20-Minute AI Starter Workflow, then use the
  full book and workbook as your main path.
- Keep the Owner Approval Checklist nearby before acting on anything risky.
- Use PDF for reading/printing, HTML for browser reading, and Markdown/TXT for
  AI study sources where available.
- Treat AI outputs as drafts. Use PASS / HOLD before money, accounts, public
  posts, deletes, deploys, customer/private data, code changes, or regulated
  claims.

## Optional: learn it with NotebookLM

NotebookLM is a third-party Google tool. If you use it, upload only public DWAI
downloads or copied public resource URLs. Do not upload private notes, secrets,
customer data, account screenshots, or completed workbook pages.

1. Create or open a NotebookLM notebook.
2. Add the public DWAI PDFs, Markdown files, or public resource page URLs as
   sources.
3. Ask NotebookLM: "Using only these DWAI sources, explain the path in plain
   English, make me a 7-day study plan, quiz me, and flag anything involving
   secrets, accounts, money, public posting, deletion, deployment, customer or
   private data, code changes, or regulated claims as HOLD."
4. If your NotebookLM account has **Video Overview**, generate one for a
   video-style walkthrough. If Video Overview is not available, use Audio
   Overview, briefing docs, study guides, or source-grounded Q&A instead.
5. Check NotebookLM's answer against the source citations before acting. AI
   study aids are drafts, not owner approval.

Do **not** upload completed workbook pages, context cards, customer/private data,
private business records, passwords, API keys, 2FA or recovery codes, medical,
legal, financial, tax, crisis, or sensitive personal details unless you have
intentionally replaced them with placeholders and accept the tool's data terms.