Turn a Work Win or Lesson into a LinkedIn Story Post That Avoids Humblebragging

Paste your notes about a work win or lesson and get a ready-to-post LinkedIn story with setup, tension, turning point and lesson, plus a humblebrag check.

You getPost, beat map and humblebrag check

Prompt

Prompt
Act as a LinkedIn ghostwriter who turns real work experiences into story posts people read to the end.

I will paste a work win or lesson right after this prompt. It may be rough notes, a Slack message or a messy draft. Turn it into one LinkedIn post.

Rules:
1. Use four beats in order: setup (who, where, what was at stake), tension (the problem, mistake or doubt), turning point (the specific decision or action), lesson (one takeaway a reader can apply this week).
2. Keep every fact, number, name and outcome exactly as I gave it. Do not add results, quotes or details I did not provide. If a beat lacks facts, keep it short and list the gap under Missing details.
3. The first line is under 12 words and creates curiosity without clickbait.
4. Paragraphs of 1-2 sentences, under 220 words total, at most 3 hashtags at the end, no emojis unless my notes use them.
5. Review your draft for humblebragging: lines that praise me, stack titles or awards, or fake modesty. Flag each one.

Output format:
1. Post: the full post, ready to paste.
2. Beat map: table with columns Beat | Opening words of that beat.
3. Humblebrag check: each flagged line, why it reads that way, and a plainer rewrite.
4. Missing details: up to 3 facts that would make the story stronger.

End with one line stating any assumption you made about my audience.

Example output

At a glanceStory beats in the returns-processing LinkedIn postHow the post moves from setup to lesson
  1. SetupReturns at the Leeds warehouse took 9 days
  2. TensionTwo temps added; processing rose to 10 days
  3. Turning pointPriya mapped one return crossing the building four times
  4. LessonFollow one item on foot before adding capacity

Example for: a warehouse operations manager whose team cut returns processing from 9 days to 3 after a failed first attempt.

1. Post

Our first fix for returns made things worse.

Last spring, returned orders at our Leeds warehouse took 9 days to process. Customers waited for refunds. Support tickets piled up.

I assumed we needed more people. We added two temps for six weeks. Processing time went up to 10 days.

The problem wasn't hands. It was the walk.

When Priya on the night shift mapped one return from dock to restock, it crossed the building four times. Inspection sat at one end, relabeling at the other.

So we moved both stations next to the returns dock. No new software. One weekend of shifting tables.

Three months later, returns take 3 days. The temps went back to picking.

What I took from it: before adding capacity, follow one item through the whole process on foot. The slowest part is often the distance, not the people.

What's the last fix you tried that made things worse first?

#Operations #Logistics #ContinuousImprovement

2. Beat map
BeatOpening words of that beat
Setup"Last spring, returned orders..."
Tension"I assumed we needed more people."
Turning point"When Priya on the night shift mapped..."
Lesson"What I took from it..."
3. Humblebrag check
  • Line from your notes: "Proud to say my team delivered a 67% improvement, which leadership called the best result in the region."

    • Why it reads that way: the percentage plus leadership praise shifts focus from the lesson to your status.
    • Rewrite used: "Three months later, returns take 3 days." The numbers speak without the endorsement.
  • Line from your notes: "I'm humbled that such a simple idea worked."

    • Why it reads that way: "humbled" often signals the opposite.
    • Rewrite used: removed; the "one weekend of shifting tables" line shows simplicity directly.
4. Missing details
  1. How many returns per week the warehouse handles, to show scale.
  2. Whether ticket volume dropped, and by how much.
  3. Whether Priya agreed to be named publicly.

Assumption: your audience is operations and supply chain peers, not customers.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • The four-beat structure gives the post a real arc, so readers reach the lesson instead of scrolling past a list of results.
  • Locking facts and listing gaps separately stops the model from inventing numbers or outcomes to make the story sound bigger.
  • The humblebrag check shows each risky line with a rewrite, so you see exactly what changed and why.

Use after a project lands or a mistake teaches you something. Have your rough notes and real numbers ready, then paste them below the prompt in ChatGPT, Claude or Gemini.

Common edits

  • Ask for a 3-sentence version for X or a LinkedIn comment.
  • Ask for two alternative opening lines so you can pick the one that fits your voice.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Social Media