Platform Style: The Story We Write for Instagram, LinkedIn, Telegram and YouTube

You take a good story and publish the same text in four places. It lands in none of them. That is not a failure of the story; it is a failure of copying. Every platform has its own reading contract: the reader arrives with a different intent, a different patience and a different gesture — scrolling, tapping, listening, searching.

This article belongs to the story is everything series and has one job: choosing the shape. Across seven surfaces we separate the reading contract, the narrative shape and the common mistake, then close with a goal-to-platform table.

One note: this piece says nothing about numeric limits on any platform; those numbers move. Reader behaviour moves more slowly, and it is what sets the shape.

Why being native matters: each platform has its own reading contract

Before the first sentence, the reader has already made four unwritten decisions, and those decisions set the shape:

• Intent: looking for an answer to a specific question, passing time, or waiting for news from someone they follow?
• Patience: in a feed the decision takes one glance; in a newsletter the reader set aside time on purpose; in a podcast, staying depends on the rhythm of the voice.
• Gesture: they scroll, tap, listen, or scan the page. Each gesture changes the unit of narrative.
• Social exposure: on LinkedIn and X a reaction is visible to others, which makes the reader more conservative.

Being native is not about length; it means separating the heart of the story from its skin. The heart stays: person, want, obstacle, change. The skin changes: first sentence, length of a scene, order of disclosure, where the lesson sits, the shape of the ask. Leave the skin untouched and you have pasted one text in several places.

So write one reference version holding every fact and detail, then build the native versions from it. Compressing narrative for a feed is micro-fiction's job; this is about shape, not size.

Instagram: the image first, a short text, an unfinished story

The contract. The reader is scrolling and decides with one glance. The image is judged before the text, and the text at its best continues the image rather than repeating it. Nobody spends time here; they pause.

The shape. One scene, one turn, and a closing line that leaves a gap. The first line has to work alone. An unfinished story means withholding something so the reader builds it — not a manufactured "more in the comments" hook.

Example. A home-goods shop: "The customer came back and said the lamp was too bright for her daughter's room. We tried three models and found the problem was never the lamp — it was the mounting height." A complete scene with one small change.

The mistake. Posting the article's first paragraph as a caption; it was written for a reader who clicked and chose to stay. The second is the sales ending: build a good scene, then land on a discount in the last line.

LinkedIn: work experience, a transferable lesson, no direct selling

The contract. The reader is in a professional frame and judges two things at once: does this person know the work, and could I work with them. Because the reaction is public, they avoid endorsing an ad.

The shape. A work incident, the tension, the decision, and a named lesson. "The customer always comes first" is not a lesson; "when a customer says it is expensive, find out what they compare you to before you discount" is one.

Example. A training school: enrolment was thin and the team assumed advertising was broken. They talked to fifteen people who did not enrol; the issue was class timing, not price. Decision: two evening groups.

The mistake. A motivational story with no specifics, or a humble-brag ("I never expected it to go this well"). The third is a sales call to action at the end; if the story exists to sell, take the template from storytelling for sales.

Telegram: a run of messages with one complete arc

The contract. The reader subscribed, so they granted permission; but your message lands in a list holding other things too. Reading is sequential and often delayed, and forwarding strips context.

The shape. Several short messages that build one arc: the first opens the scene, the middle advances it, the last closes with the decision. Each message needs some independence, because some readers enter in the middle.

Example. An app team can tell the story of one bug across messages: release night, the user's message, the decision, the lesson that went into the docs. The same story becomes an engineering article on the blog.

The mistake. One long block in a single message, or a mechanical cut into messages that each hold half a sentence. The third is having no arc: the reader cannot tell where this goes and drops out at message two.

X: one quotable sentence and a thread that keeps moving

The contract. Fast reading, fast judgement, quotation. Threads are mostly read by people who arrive later and read top-down.

The shape. In a single post, one sentence with internal tension. If the story is longer, break it into beats, and each beat must mean something alone. Do not withhold the conclusion to farm attention; a reader who never arrives gains nothing.

Example. A clinic: "Half of our referred patients never showed up. It was not the reminders; it was the car park route." One line, with a person, an obstacle and a turn. The next post carries the detail.

The mistake. A thread that is really an article chopped up; total dependence between posts; reaction baiting with a provocative question unrelated to the story.

YouTube: the hook in the first thirty seconds and a clear promise

The contract. The viewer decides within the first seconds and can leave at any moment. Sound and image work together, so anything that can be shown should not be narrated.

The shape. Open on the moment of tension, not an introduction; then state the promise, then advance through distinguishable sections. Write the narration for the ear: short sentences, clear verbs, deliberate pauses.

Example. A training school opens on the teacher erasing an exercise: "I rewrote this three times, because the class kept making the same mistake." Then the promise: what changed.

The mistake. A logo sting up front; asking for a follow before giving value; reading an article over a static image; promising one thing and telling an unrelated story.

Blog and newsletter: long text, scannable structure, a story inside the argument

The contract. On a blog the reader usually arrives from search with a specific question; they scan the headings and leave if the answer is missing. In a newsletter the permission is expensive and is withdrawn faster than anywhere else.

The shape. On a blog, story sits inside the argument, not in place of it: claim, narrative as evidence, then the rule. Headings should carry the argument themselves. In a newsletter: one story, one lesson, one ask.

Example. The clinic story becomes an article with a clear title, three mid-headings and one usable rule at the end; in a newsletter it becomes a short story with a single lesson line.

The mistake. An article that is only a story, leaving the reader unsure what to take; a newsletter that is internal company news; a long warm-up before the story. If one long text should become a connected set of articles, the method is in from long text to a series.

Podcast: a story for the ear, with no visual references

The contract. The listener moves forward linearly and cannot go back; they are often in motion with part of their attention elsewhere. No heading exists to rescue them; the only tools are voice and clean sentences.

The shape. Name people clearly and repeat the names; "he" and "the other one" dissolve in audio. Build the scene with sound rather than pointing at an image. Keep sentences short and give directions with verbal signposts.

Example. The training-school story opens on classroom noise, the narrator says what they saw, and halfway through summarises once so a distracted listener is not lost.

The mistake. Reading a written article aloud; writing and speech have different rhythms. The second is a visual reference ("as you can see in the figure"); the third is too many similar names.

The matching table: goal, platform, shape, common mistake

Start from the goal in this table, not from the platform. Pick the wrong goal and even the best execution goes nowhere.

The rule for choosing: if the reader is looking for something, blog; if you are looking for the reader, a feed; if they set aside time, newsletter and podcast; if the relationship already exists, Telegram. Before publishing, run the pre-publish checklist once so that platform's recurring mistakes are caught early.

None of these seven versions is better than another; each respects a contract. Keep the heart fixed and change the skin.