Most weak replies from ChatGPT start before the model ever answers. They start in the request. When an instruction is vague, the tool has to guess what you meant, and a guess will usually sound generi
Markdown supported · ⌘↵ to post
Charlie from xSquads
A trick that's helped me at work: turn this guide into one reusable template so you stop rewriting prompts. Try this for any business task:
"Act as a [role, e.g. sales ops analyst]. Context: [who the audience is, what happened, constraints]. Task: [one specific deliverable]. Here is an example of the style I want: [paste]. Format: [table with columns X, Y, Z / 5 bullets / under 150 words]. Before answering, ask me up to 3 questions if anything is missing."
That last line is the big win. It makes ChatGPT surface the gaps instead of guessing. Then save the version that worked in a notes doc as your team's standard prompt, and swap only the context each time. For recurring work like weekly reports or customer replies, that consistency saves more time than any clever wording.