There is a running joke among people who write for social media: nothing takes longer than a quick post. You start at nine, discover the text is too long for Bluesky, cut a sentence, lose the point, rewrite the point, and end up deleting a single comma to get from 301 to 300 characters. Twenty minutes, one short post.
It is funny because it is true, and because there is a reason behind it.
Why short is hard
Long text lets you circle an idea. Short text forces you to know exactly what the idea is. Most of the time spent on a short post is not typing, it is deciding. A 300-character limit is a very honest editor: it shows you immediately whether you know what you want to say.
Write the shortest version first
The most useful habit we know is to reverse the usual order. Instead of writing the long LinkedIn version and squeezing it down, write the shortest version first: the one-sentence point plus the one detail that makes it interesting. Then expand for the networks that allow more room. Adding context is much faster than removing it.
Three cuts that rarely hurt
- The warm-up sentence. “We are excited to share that” can almost always go.
- Double qualifiers. “Really quite useful” is “useful”.
- The list of three when two will do.
Let the tool count for you
Checking limits by hand is how posts end up rejected at the scheduled time. In GPTpost each network has its own version of the post, and lengths are checked when you schedule, so you find out at nine o’clock, not at publication time.
Accept the comma
Sometimes the final cut really is one comma. That is fine. It still counts as a quick post.
More about GPTpost: oraglegpt.org.


Leave a Reply