Write an Opinion Post That Argues Your Position and Answers the Best Objection

You get a structured opinion post built from your own view and reasons, with the strongest counterargument stated fairly, a direct rebuttal, and notes on claims that need sources.

Prompt

Prompt
You are an experienced op-ed editor who helps people turn their own views into clear, persuasive posts.

Your job: write an opinion or thought-leadership post that argues my position, built only from my view and my reasons.

Before writing, ask me these questions in one message, then wait for my answers:
1. What is your position, in one or two sentences, and who is the post for?
2. What are your 2-4 main reasons, plus any real examples or numbers you can share?
3. What is the strongest objection people raise against your view?
4. Where will it be published, and roughly how long should it be?

Rules:
- State the position within the first two sentences. No opening anecdotes I did not give you.
- Each body section makes one reason and backs it with my example, or a hypothetical clearly labeled as one.
- Present the strongest counterargument in terms its supporters would accept, then rebut it without strawmanning. Concede what is true.
- Do not invent quotes, statistics, studies, credentials or personal experiences. List any claim that needs a source in the notes.
- Keep paragraphs to 4 sentences or fewer and end with one concrete takeaway or ask.

Output format:
Headline, plus one alternative
Opening that states the position
2-4 sections with subheads, one reason each
The best case against this, and my reply
Closing with a takeawayNotes: claims needing sources and assumptions made

If my reasons are thin or the objection is stronger than my reply, say so plainly in the notes.

Example output

At a glanceWhat daily standups cost a team of nineFigures from the example opinion post on replacing standups
Standup booked vs actual length
15 → 25 min
Regularly ran over
Focus lost per engineer daily
~40 min
Including context switching; author's estimate
Team time spent on status daily
~6 hours
Across a team of nine
Suggested trial length
2 weeks
Written check-ins plus one live session weekly

Example for: an engineering manager arguing that daily standups should be replaced with written check-ins, for a company blog read by tech leads, about 600 words.

Our Team Stopped Daily Standups. Write Them Down Instead.

Alternative: The Standup Meeting Is a Habit, Not a Process

Daily standups cost more than they return for most distributed teams. Replace them with a short written check-in, and keep live meetings for problems that actually need a conversation.

Fifteen minutes is never fifteen minutes

On my team of nine, the standup was booked for 15 minutes and regularly ran 25. Add the context switch before and after, and each engineer lost close to 40 minutes of focus a day. Across the team, that is roughly six hours daily spent reporting status out loud.

Spoken updates disappear

When someone said "blocked on the payments API" at 9:30, half the team was half-listening and nobody could search it later. Since we moved to a written thread, blockers sit in one place, get a reply from the right person, and stay findable a week later.

Time zones turn standups into a tax

With engineers in Lisbon and Austin, any standup time is early for someone or late for someone else. Written check-ins let each person post at the start of their own day.

The best case against this, and my reply

Supporters of standups say the meeting is not really about status. It is about connection: seeing faces, catching tone, and noticing when a teammate is struggling in a way they would never type. That is a fair point, and a text thread does lose some of it.

But a daily status ritual is a weak tool for connection, because the format pushes people toward short, guarded updates. We kept one 30-minute live session on Tuesdays with no status agenda, just problems and pairing. People speak more openly there than they ever did at 9:30 every morning.

Try it for two weeks

If your standup routinely runs over or spans time zones, run a two-week trial: written check-ins on weekdays, one live problem-solving session per week. Then ask the team which they want to keep.


Notes

  • The "40 minutes of focus" figure is your own estimate. Label it as such or add how you measured it.
  • Assumed a fully remote team. If some of your team works in an office together, address that.
  • Your rebuttal is solid, but readers will ask how you spot a struggling teammate without a daily meeting. Add one sentence on how you handle that.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • The questions pull out your actual reasons and evidence, so the post argues your case instead of generic talking points.
  • Requiring the strongest objection in its supporters' terms prevents strawmen and makes the rebuttal more credible.
  • Banning invented quotes, stats and credentials, with a notes list for unsourced claims, keeps the post honest and safe to publish.

Use in ChatGPT, Claude or Gemini when you have a clear opinion for a blog, LinkedIn or newsletter. Have your position, your reasons, any real examples and the objection you hear most.

Common edits

  • Ask for a 200-word LinkedIn version with a one-line hook instead of a headline.
  • Request a more provocative or more measured tone to match your audience.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Writing