All Things Muse
Muse Academy

How to Get Genuinely Useful Results from Your AI Assistant

Most disappointing AI answers come from thin prompts, not a weak model. Give context, be specific about the output, and iterate like an editor.

Professor Muse By Professor Muse3 min read
Jolly holding a glowing chat bubble with a lightbulb

Most disappointing answers from an AI assistant come from a thin briefing, not a weak model. (If you’re delegating to an agent specifically, our guide to writing task briefs goes deeper.) The assistant only knows what you tell it, so thin input produces thin output. A few habits fix most of it.

The short version

  • Most disappointing AI answers come from thin prompts, not weak models.
  • Add the context a smart colleague would need: who it’s for, your constraints, what you’ve already tried.
  • Describe the shape of the output, not just the topic: format, length, tone.
  • Iterate like an editor. Specific feedback beats re-rolling the same vague prompt.

1. Give It the Context It Can’t See

An assistant doesn’t know your situation unless you say so. Before asking, add the background a smart colleague would need:

  • Who this is for: “I’m writing for first-time homebuyers” beats “write about mortgages.”
  • Constraints: budget, deadline, tone, length, tools you actually use.
  • What you’ve already tried: so it doesn’t suggest the obvious things you’ve ruled out.

One or two sentences of context routinely matter more than clever prompt tricks.

2. Describe the Output, Not Just the Topic

“Write about productivity” can produce anything. Instead, specify the shape of what you want back:

  • Format: a checklist, a draft email, a comparison table, bullet points
  • Length: “about 200 words” or “a one-page outline”
  • Tone: “direct and casual” or “formal, for my manager”

If you know what done looks like, say so. You’ll skip a whole round of revisions.

3. Iterate Like an Editor, Not a Slot Machine

The first draft is a starting point, not a verdict. Treat the assistant like a junior colleague: give specific feedback and ask for a revision.

  • “This is too long. Cut it to half the length.”
  • “Keep the second paragraph, rewrite the rest in plainer language.”
  • “Give me two alternatives to the opening line.”

Two or three rounds of this beats re-rolling the same vague prompt five times.

4. Ask It to Check Its Own Work

Before you trust an important answer, ask follow-ups:

  • “What assumptions did you make in that answer?”
  • “What’s the strongest argument against this plan?”
  • “Walk me through your reasoning step by step.”

This doesn’t guarantee correctness, and you should still verify anything that matters, but it surfaces weak spots fast.

5. Keep the Good Stuff

When you land on instructions that work well, save them. Many assistants let you set persistent preferences or custom instructions. A short note like “I prefer concise answers with examples” pays off in every future conversation.

Before

"Write about productivity": a thin prompt that can produce anything, so it usually produces nothing useful.

After

Context up front, a clear picture of the deliverable, honest feedback on the draft, and the same assistant becomes a capable collaborator.

The One-Sentence Version

Brief your assistant the way you’d brief a capable new hire: context up front, a clear picture of the deliverable, and honest feedback on the draft.

None of this requires technical skill. It just requires treating the conversation as a collaboration.

Keep reading