Becoming an AI Power User

2.2Working With the Model

They match the input medium to the task because voice, text, and images each capture different context

Developing

Choose an input method that lets you explain the task well. If typing a project update leaves out the background you would tell a colleague, try speaking it. If the task depends on figures in a spreadsheet, connect or attach the spreadsheet. Useful context can arrive through several channels, and the best fit depends on you and the task.

How you hand a task in decides how much context survives

Writing a prompt can require you to recall facts, choose words, and organize an explanation at the same time. You may shorten it to avoid that effort. Some people find speaking easier; others think more clearly by writing. The question is which method helps you supply the information the task needs.

When speaking feels natural, describe the situation first and decide how to organize it afterward. The assistant can then summarize your goals, constraints, and open questions. That separates capturing the idea from editing the explanation, which can also be done with rough typed notes.

Exact wording sometimes deserves deliberate typing. A deadline, a quoted phrase, or a constraint may need careful revision before you submit it. Combining methods may fit: speak the background, attach the source, and type the wording that must remain exact.

Voice recording, text, an image and a source file provide different kinds of context around what the task needs. — Voice, text, images, and files can supply different kinds of context. Choose the combination the task needs, then check the important details.

Choose a medium that helps you explain the whole task

Suppose the task is a project update. A thin request is 'Write a project update.' A spoken or typed note might say: 'The member portal was meant to launch Friday. Login works, but two password-reset tests still fail. We need one more day to fix and retest them. Tell the team to keep the preview internal, and ask Robin to send the next test result by noon.' Those details give the assistant something specific to communicate.

A draft based on that note could read: 'The portal launch needs one more day because two password-reset tests are still failing. Please keep the preview internal while we fix and retest them. Robin, send the next test result by noon so we can confirm the launch timing.' Check that it preserves the unresolved issue, the internal-preview instruction, and the requested update. Voice helped if it made those details easier to supply; the same details work in text.

Explain the details you normally take for granted. In the portal update, the team needs to know that 'working' includes successful password recovery as well as login. Ask the assistant to interview you about such distinctions: 'What would you need to know before drafting this update?' Speaking may help you recall the answer; examples and follow-up questions can help too.

A voice memo separates capturing your thoughts from organizing them

A memo lets you explain the situation in the order you remember it. You might state the deadline first, remember a stakeholder concern halfway through, and correct a detail near the end. Ask the assistant to organize that account into facts, constraints, and unresolved questions before drafting.

Recording separately can help when you are away from your desk or want to finish a train of thought without interruption. Direct conversation can help when follow-up questions would clarify the request. Choose the version that lets you supply and check the relevant context.

Capture the situation, check the details, then draft

Use an input method your assistant supports: direct voice, an accepted audio attachment, or a transcript. If it cannot read the recording, use your device's transcription or dictation feature and provide the text. Audio support varies by tool and mode; a transcript is a useful fallback.

Talk through the situation. State the goal, audience, constraints, and details that might change the answer. Stop when you have explained what the assistant needs to proceed.
Provide the recording or text. Use supported audio input or paste a transcript. Check names, numbers, dates, and any corrections you made while speaking.
Ask AI to organize the account. Try: "List the facts, constraints, and open questions from this memo. Flag contradictions or uncertain names and numbers. Then draft the update from the confirmed details."

Direct dictation can remove the separate recording step. If your assistant or device supports it, speak into the message field and review the text before submitting. Keep a separate memo when you want to revisit the recording. Both routes can convey the same information.

Each medium keeps a different kind of context, so the fit decides

Choose the medium that communicates the relevant information with manageable effort. Speech can help you explain background; a screenshot can preserve a layout; an attached document can supply exact figures. Combining them is often useful: provide the spreadsheet and dictate the question you want it to answer.

Compare the available media by what they communicate well and what needs an additional check. These common uses can help you choose.

Voice supports thinking aloud. Try it for background you find easier to explain than type. Review exact wording, names, and numbers afterward.
Text supports deliberate wording and revision. Use it for exact phrases and constraints, or whenever writing helps you think. Rough notes can preserve spontaneity too.
A screenshot keeps visual state and gives up the surrounding story. Reach for it when what you are pointing at is on a screen, like an error, a layout, or a chart, where words would lose the exact arrangement the model needs to see.
A document or file preserves source detail. Attach or connect the report, spreadsheet, or the task depends on, and say which question to answer from it.

When a draft misses context, compare it with the input you supplied. Ask the assistant to identify the detail the task needed and whether that detail was present, readable, and used correctly. If a layout was hard to describe, try a screenshot with an explanation of the problem. For the three-medium comparison, add a trial using the document or screenshot your task depends on. Compare that result with the typed and spoken trials using the same goal and checks. Differences in supplied facts help explain the result; they do not establish that one medium is generally superior.

Compare the context your voice memo supplied

Turn a voice memo into a structured deliverable

Claude extracts the facts, constraints, and open questions from your memo, drafts the deliverable, and compares input methods when you supply the other trials.

Copy the promptUse the copy button above the box.
Paste it in Claude or CodexMake sure your active project is enabled.
Answer the questionsGive clear answers so it understands what you want made.
Test it to see if it worksTry the output and refine until it does what you need.

Problem: I have spoken notes that need to become a clear deliverable. Intent: I want you to organize the task-relevant details and draft from what I supplied. Use my attached memo or pasted transcript. If neither is available, ask me for the recording or transcript; if you cannot read the recording, ask for its text. Ask what deliverable I want if the notes do not specify it. 1. Extract the facts, goal, audience, constraints, and unresolved questions. Flag contradictions and uncertain names, numbers, or dates. 2. Ask about a gap if guessing would materially change the result. 3. Draft using the supplied details. Do not add facts or commitments I have not provided. 4. List the details that informed the draft. If I supply a typed trial or a trial using a document or screenshot, compare the actual inputs and outputs against the same goal and checks. Identify missing details, errors, and any differences in effort I report. If a trial is missing, state that it has not been compared; do not invent what another medium would have captured. Show the draft and the comparison or details list. Treat any explanation of why one trial performed better as a hypothesis to test on similar work.

A between the ramble and the build lets you review intent before execution

For a deliverable with several requirements, ask the assistant to write a before drafting: a short account of what the result should contain, who it is for, and how you will check it. Review the interpretation while the requirements are easy to inspect. This is useful when a misunderstanding would affect much of the finished work.

For the portal update, the intermediate might be: 'Write a short internal update. State that the launch needs one more day for password-reset fixes and retesting. Keep the preview internal. Ask Robin for the next test result by noon. Do not announce a confirmed launch time.' Those requirements give the review a specific target before the assistant writes the message.

A short lets you correct the interpretation before the assistant builds on it. If it says the portal will launch tomorrow, correct that commitment before drafting: the note requested another day of testing, not a guaranteed release. Use a separate session when a clean handoff helps; the same assistant can also draft from the reviewed .

An intermediate helps when several decisions must stay consistent. A proposal may need an agreed scope, price, exclusions, and timeline. Ask the assistant to write those requirements from your notes, resolve any material gaps, and then draft. A routine message may already be clear enough to write directly.