A post about your own mistake
Writing about a failure so it adds trust rather than spending it.
Der Prompt
You are an editor who helps people write about mistakes without self-flagellation and without humblebragging. What happened: {the mistake} What I thought at the time: {the logic then} How it ended: {consequences} What I understood: {the lesson} How long ago: {time} Build: 1. The check: is this worth writing at all? Three signs a mistake makes a good post, and three signs to keep quiet. 2. First line: a number or a fact, not a confession. "I want to tell you about a mistake I made" is weak. 3. How to explain your reasoning at the time so the reader recognises themselves in it. Without that the post reads as "I was stupid" and nobody tries it on. 4. What exactly went wrong, step by step, briefly. 5. The lesson: specific and usable, not "plan better". Test your own lesson against that. 6. What to avoid: the humblebrag disguised as a mistake. Name the signs. 7. The ending: what to ask readers. 8. Two lengths: a short post and a long one. Do not turn the mistake into a success story. "But I learned so much" is exactly why nobody believes these posts any more.
Alles in geschweiften Klammern ersetzen Sie durch Ihre Angaben.
Beispielergebnis
First line: "I spent $1,600 advertising a product that was out of stock." The logic then: the shipment was moving, the delay was three days, stopping the campaign felt like more work than leaving it. Lesson: not "plan better" but "pause ads on day one of a delay, not day three: the money leaves at a steady rate, the customers' patience does not". Humblebrag: "my mistake was working too hard".
Ähnliche Prompts
The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.
Write 20 opening lines for Threads posts on the topic "{topic}". Audience: {who} My role: {who you are to them — practitioner, seller, observer} Hard limits: — No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land. — No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past. — No caps lock, no emoji chains. Give 4 groups of 5: 1. Personal experience with a specific number or timeframe. 2. Disagreement with received wisdom in the niche. 3. An observation the reader recognises in themselves. 4. An open question they have something to answer from their own experience. After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Beispielergebnis zeigenBeispiel ausblenden
Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
Write a Threads post on the topic "{topic}" designed to pull replies. What I know about it: {your experience, facts, numbers} Audience: {who} What I want to hear in the replies: {e.g. how other people solve this} Rules: — No longer than 500 characters, that is the platform limit. 300 is better. — The first 90 characters must work as a standalone hook; the rest is what people unfold themselves. — End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice. — Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say. Don't do this: — "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to. — Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow. Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Beispielergebnis zeigenBeispiel ausblenden
Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischaltenA link in the body sends people off-platform, and the feed accounts for that. The scheme: the post stands alone, the link comes as the first reply.
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischalten