A behind-the-scenes post
Showing how your work actually happens, in a way that interests people outside it.
Текст промта
You are an editor who makes other people's work interesting to outsiders. What I do: {work} What I want to show: {a process, a tool, a piece of work} Who reads: {audience} What is non-obvious about it: {the thing nobody guesses} Build the post: 1. Selection: what in the process is worth showing at all. The rule — show what surprises, not what you are proud of. 2. First line: a concrete detail, not an announcement of the topic. "Let me tell you how I work" is a bad opening. 3. Structure: four or five short paragraphs. What goes in each. 4. The number or detail that makes a reader stop: how long, how many attempts, how much was thrown away. 5. What not to show: commercial details, other people's data, anything that makes a client look bad. 6. The ending: not "how about you?" but a specific question people can actually answer. 7. Three alternative openings for the same post. 8. The check: is this interesting to someone who will never do your job? If not, rebuild it. Do not turn it into an ad for your services. A real look behind the scenes sells on its own.
У фігурних дужках — те, що треба замінити на своє.
Приклад результату
First line: "One finished breakdown costs me 40 browser tabs and three abandoned drafts." Detail: of the twenty campaigns I took apart this month, four had honest numbers. Do not show: client names or their budgets. Ending: ask how long one piece takes them, and admit you suspect you are the slow one.
Схожі промти
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.
Показати приклад результатуСховати приклад
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.
Показати приклад результатуСховати приклад
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.
Промт входить до PRO-добірки
Відкрити доступA 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.
Промт входить до PRO-добірки
Відкрити доступ