Guides · Writing

How to write a good tweet

A good tweet says one thing clearly, earns the first line, and gives the reader a reason to react. Here is a repeatable way to get there.

Updated November 4, 2026 · 3 min read

Start with one idea

Most weak tweets try to say three things. Before you write, finish this sentence: “The reader should walk away knowing that…”. If you need “and” twice, you have more than one tweet.

Good single ideas tend to be one of these: a tip, an observation, an opinion, a short story, a question, or a result with the reason behind it.

Earn the first line

The first line decides whether anyone reads the second. Lead with the most interesting part: the result, the surprise, the claim. Background can come later or not at all.

Weak openingStronger opening
“So I've been thinking a lot about pricing lately…”“We doubled our price and lost almost no customers.”
“Here are some thoughts on remote work.”“Remote teams don't need more meetings. They need better docs.”
“I wanted to share a quick tip.”“Write the email subject line last.”

How to write hooks has twelve patterns you can borrow.

Be specific

Specific details make a tweet believable and memorable. Replace adjectives with facts: numbers, timeframes, names of tools, the actual thing someone said.

  • “Grew a lot” → “Went from 40 to 400 subscribers in four months”
  • “A useful tool” → “A $5 kitchen timer”
  • “Recently” → “Last Tuesday”
  • “Customers love it” → “Three customers emailed to ask for it back”

Cut until it hurts, then format

Write the draft, then remove every word that doesn't change the meaning. Filler like “really”, “just”, “I think” and “in order to” usually goes first. Shorter tweets are easier to read and leave room to react.

Then format for a phone screen. Short lines, a blank line between ideas, and no more than three or four lines in a block. If you're writing on desktop, check how it looks on mobile before posting; the free text formatter and the tweet character counter help.

Give it a finish

The last line is what readers react to. End on something that lands: the takeaway, a twist, or a question people can actually answer. Avoid “Thoughts?” on its own; ask something specific.

  • A takeaway: “Clarity beats cleverness.”
  • A twist: “The fix took four minutes. Finding it took four weeks.”
  • A specific question: “What's one tool you dropped this year and didn't miss?”

Not every tweet needs a question at the end. A strong takeaway is often better than a forced prompt, and people reply to clear statements on their own. Save questions for when you actually want the answers.

Six tweet types worth knowing

Most good tweets fit a handful of shapes. Knowing them makes the blank page easier.

TypeShapeTemplate
TipDo this, because of thatQuick tip tweet
OpinionA clear position, then one reasonUnpopular opinion tweet
QuestionA specific question your audience can answerQuestion tweet
MilestoneWhat happened, what it took, what's nextMilestone tweet
AnnouncementWhat's new, who it's for, where to get itProduct announcement tweet
ObservationSomething you noticed that others will recognizeTweet ideas
An observation (a product manager)
  1. Y

    Your name@you

    The best feature requests I get never mention a feature. They describe a Tuesday afternoon that went badly. The feature is my job. The bad Tuesday is the data.

Before and after

Before (a bakery owner)
  1. Y

    Your name@you

    I just wanted to say that we have been working really hard on some new things at the bakery and we think you are going to love them. We have some exciting news coming soon so stay tuned for more updates!

After
  1. Y

    Your name@you

    We tested 31 versions of our sourdough before we found one that stays soft for three days. It goes on the shelf Saturday. The secret was a longer, colder proof. Not a new flour.

The second version has one idea, a specific number up front, a concrete date and a detail people can repeat. It needs no hype words.

A quick tip that works (a developer)
  1. Y

    Your name@you

    Before you open a pull request, read your own diff in the review view. You'll catch the debug logs, the commented-out code and the file you didn't mean to touch. Two minutes. Saves your reviewer twenty.

Checklist before you post

  1. It says one thing.
  2. The first line works on its own.
  3. There's at least one specific detail.
  4. Every word earns its place.
  5. It reads well on a phone.
  6. The last line lands or asks something specific.
  7. No link in the main post unless it's the point.
  8. It sounds like you. Reading it aloud is a quick test.

Extudio's tweet generator drafts tweets from a topic or rough idea using your brand voice, and lets you rewrite a single line until it reads right.

Questions

Something else? support@extudio.dev

Your next week of posts,
done this afternoon.

Sign up with your email, set your brand, and start writing. Upgrade when you want AI and auto-posting.