Linkedin Post

LinkedIn Post Writing

When to Use

Use this skill when the user's request matches one of these specific scenarios:

• User asks to write a LinkedIn feed post, LinkedIn update, or LinkedIn content -- any short-form text intended for the LinkedIn main feed
• User wants to share a professional insight, observation, career lesson, or workplace experience on LinkedIn
• User wants to announce a new job, promotion, company milestone, product launch, or professional achievement on LinkedIn
• User wants to share a contrarian or provocative take on an industry topic for professional visibility
• User wants to write a personal story with a professional lesson -- the "storytelling" post format that drives high engagement on LinkedIn
• User wants to draft a question post designed to generate comments and discussion among their professional network
• User wants to promote content (a blog post, podcast episode, newsletter, or talk) through a LinkedIn feed post
• User needs help turning an idea, rough draft, or bullet points into a polished LinkedIn post
• User asks for engagement-optimized content for the LinkedIn algorithm or wants to grow their LinkedIn presence

Do NOT use when:

• User wants a long-form LinkedIn article (1,000+ words, published through LinkedIn's article feature with a title, header image, and blog-style formatting) -- use linkedin-article instead
• User wants a Twitter/X thread or tweet -- use twitter-thread instead
• User wants an Instagram caption -- use instagram-caption instead
• User wants a blog post for a website -- use blog-post-writing instead
• User wants a newsletter email -- use email-newsletter instead
• User wants a press release or formal corporate announcement -- use press-release instead
• User wants a full thought leadership article, not a feed post -- use linkedin-article or opinion-piece instead

Process

1. Collect Post Context

Gather these inputs before writing. If the user is chatting interactively, ask. If their request already contains this information, extract it and proceed:

• What they want to share -- not just a subject ("leadership") but a specific angle or experience ("the time I promoted someone who had only been on the team for four months and what it taught me about readiness vs. tenure"). If the user gives only a subject, propose three specific angles and ask which direction resonates.
• The core message in one sentence -- force this to a single declarative sentence. "Hiring for culture fit is a mistake because it produces teams that agree on everything and challenge nothing" is usable. "I want to talk about hiring" is not. If the user cannot articulate this, help them find it by asking: "If someone reads your post and remembers only one thing, what should that thing be?"
• Target audience on LinkedIn -- who specifically should care about this post: peers in the same role, recruiters, potential clients, industry leaders, junior professionals looking up, or a general professional audience. The audience determines vocabulary level, how much context to provide, and whether the tone leans advisory or peer-to-peer.
• Post goal -- map to one of four outcomes:
  • Engagement (comments and shares) -- structure the post to invite professional opinions
  • Visibility (impressions and reach) -- optimize for the algorithm's dwell-time and share signals
  • Connection (DMs and follows) -- demonstrate specific expertise that makes people want to reach out
  • Promotion (drive traffic to a link, product, or event) -- lead with standalone value, bury the link
• Voice sample -- if the user has previous LinkedIn posts or a personal brand voice, ask for an example. Identify three markers (sentence length, use of "I" vs. "we," humor level, use of em dashes or ellipses) and replicate them. If no sample is available, default to professional casual.

2. Calibrate Voice and Tone

Voice miscalibration is obvious on LinkedIn. A post that sounds like corporate communications gets scrolled past. A post that sounds like Instagram gets dismissed as unserious. Lock the register before drafting:

• Professional casual (default): Conversational but substantive. First-person. Contractions allowed. Sentences vary between 8 and 20 words. Reads like a smart colleague explaining something over coffee. This is the register that performs best on LinkedIn for most users.
• Authoritative: No contractions. Longer, more structured sentences. Third-person or first-person plural ("we"). Suited for executives, consultants, and subject-matter experts whose audience expects gravitas. Risk: can sound stiff if the content is lightweight.
• Vulnerable/authentic: High first-person usage. Shorter sentences. Emotional honesty about failure, doubt, or surprise. Suited for career transition stories, lessons from mistakes, and personal growth content. Risk: can read as performative if the vulnerability is not specific and real.
• Provocative: Direct claims. Short declarative sentences. Challenges conventional wisdom head-on. Suited for contrarian takes and industry criticism. Risk: can alienate if the contrarian position is not backed by evidence or experience.

Do not mix registers within a single post. If the hook is provocative, the body must follow through with that energy -- do not retreat into corporate-safe language after a bold opening.

3. Choose Post Format

Select the format that best serves the content. Each format has a different structural logic and performs differently with the LinkedIn algorithm:

• Story post -- a personal experience with a professional lesson. Highest average engagement because narrative creates dwell time (LinkedIn's algorithm rewards time spent reading). Structure: scene-setting hook, narrative arc in 4-6 sentences, pivot to the lesson, closing takeaway. Works best when the story is specific (names, numbers, dates) and the lesson is universal.
• Insight post -- one specific professional observation supported by evidence or experience. Clean and efficient. Structure: observation as hook, 3-4 supporting sentences, takeaway. Works when the user has a clear, non-obvious point to make.
• Contrarian post -- challenges a widely held professional belief. High impression count because disagreement drives comments, and comments drive distribution. Structure: state the common belief, break it in the hook, explain why it is wrong with evidence, offer the better alternative. Works only when the contrarian position is genuinely defensible.
• Achievement post -- shares a win, milestone, or accomplishment. Lowest organic engagement of all formats unless it includes lessons, not just celebration. Structure: result as hook (with a specific number), backstory of what made it hard, 2-3 things learned, closing that helps the reader apply the lesson to their own situation.
• Question post -- asks a specific professional question to drive comments. High comment count but lower share count. Structure: brief context (2-3 sentences establishing why this question matters), the question itself (specific, not generic), optional personal answer to model the kind of response you want. Works when the question is genuinely open and the user's audience has relevant experience.
• List/framework post -- delivers value as a numbered list or simple framework. High save and share rate. Structure: hook that names the problem the list solves, 3-7 items each in one sentence, closing context. Works for tactical content ("5 questions I ask in every 1:1") but risks looking like content-farm output if the items are generic.
• Carousel-companion post -- text that accompanies a document carousel (PDF slides). Structure is shorter because the carousel carries the content: hook, 2-3 context sentences, call to swipe, closing question. Note: if the user is creating a carousel, the post text should complement, not duplicate, the slide content.

4. Write the Hook Line

The hook line is the single most important element of any LinkedIn post. On mobile, only the first 1-2 lines are visible before the "...see more" fold. Everything else is hidden until the reader taps. If the hook does not earn that tap, the rest of the post does not exist.

Hook construction principles:

• Keep it under 150 characters so it displays fully above the fold on mobile
• Create an open loop -- introduce information, tension, or curiosity that can only be resolved by reading further
• Be specific, not abstract. "Last Tuesday I fired our best-performing salesperson" lands harder than "Sometimes leadership requires tough decisions"
• Avoid starting with "I" -- lead with the observation, the number, or the scene. "I" as the first word shrinks the post's perceived scope to personal diary
• The hook must NOT deliver the full message. If a reader can get the complete takeaway from the hook alone, the post structure has failed -- there is no reason to tap "see more"

Proven hook formulas (choose one per post, do not rotate mechanically):

• The specific number: "We lost $240K in pipeline last quarter because of one email template." Numbers are concrete and create immediate curiosity about the story behind them.
• The pattern interrupt: "Stop telling junior developers to ask more questions." Challenges something the audience assumes is good advice. Forces a double-take.
• The scene drop: "Three minutes into the board meeting, our CTO said something that changed how I think about roadmaps." Places the reader inside a moment and creates narrative pull.
• The confession: "I have been a product manager for 11 years and I still cannot run a good sprint retrospective." Vulnerability from an experienced person creates surprise and identification.
• The counterintuitive result: "Our worst marketing campaign generated our best customers." Contradicts expected cause-and-effect, demanding explanation.
• The timestamp: "Six months ago, I was mass-applying to jobs on LinkedIn. Today I am hiring for my own company." Time contrasts compress a transformation into a single line and imply a story worth hearing.

Hooks to avoid:

• "I am thrilled to announce..." -- performative excitement that LinkedIn users have learned to scroll past
• "Unpopular opinion:" -- overused label that has become the opposite of what it claims
• Generic inspiration: "Success is not about talent, it is about persistence" -- reads as a greeting card, not a professional insight
• Rhetorical questions: "Ever wonder why some teams outperform others?" -- soft, vague, and the reader's answer is usually "not really"

5. Write the Body

The body is the payoff for the hook's promise. It must deliver specific value -- not restate the hook in more words.

Structural principles:

• One sentence per line. LinkedIn's mobile feed renders long paragraphs as impenetrable text blocks. Single-sentence lines with line breaks between them create vertical white space, improve readability, and increase dwell time. This is not optional formatting -- it is how high-performing LinkedIn posts are built.
• Total length: 150-300 words. The algorithmic sweet spot is 1,000-1,300 characters (roughly 180-230 words). Posts under 100 words feel thin and do not generate enough dwell time. Posts over 300 words risk reader drop-off before the closing, which means fewer comments.
• One idea per post. If the user has three related points, suggest three separate posts. A post that tries to cover multiple ideas dilutes all of them and confuses the reader's takeaway.
• Build toward a single clear takeaway. Every sentence in the body should either set up or develop the one insight the post delivers. If a sentence does not serve that function, cut it.
• Include at least one specific detail. A number, a timeframe, a name, a concrete example. "We improved retention" is forgettable. "We improved 90-day retention from 34% to 61%" is sticky. Specificity is the difference between a post that gets comments and one that gets polite silence.
• Use "I" and personal experience. LinkedIn rewards authenticity, and authenticity requires first-person specificity. "Teams should consider..." is weaker than "My team tried this and here is what happened." The reader connects with a person, not a principle.

Body development by format:

• Story posts: Follow a narrative arc -- situation, complication, action, result. Keep the story to 4-6 sentences maximum. The lesson comes after the story, not woven into it.
• Insight posts: State the observation, provide one piece of evidence or example, explain why it matters or what to do about it.
• Contrarian posts: Name the common belief, explain why it is wrong (with evidence, not just assertion), offer what to do instead.
• Achievement posts: State the result, explain what made it hard (the backstory), share 2-3 specific things you learned.
• List posts: Deliver each item in one sentence. Do not elaborate on each item -- the constraint is the format's strength.

6. Write the Closing

The closing is the second most important element after the hook. It determines whether the reader comments, shares, or scrolls away. LinkedIn's algorithm weights comment velocity heavily -- a post that gets 10 comments in the first hour reaches dramatically more people than a post that gets 10 comments across a week.

Closing options (choose one, not multiple):

• Specific question: Ask something the reader can answer from their own experience. "What is the one meeting on your calendar this week that should be an email?" is specific. "Thoughts?" and "Agree?" are not questions -- they are abdications. The question should be narrow enough to answer in 1-3 sentences but open enough that different people will answer differently. Different answers create threads, and threads amplify reach.
• Sharp one-liner: A declarative sentence that crystallizes the post's takeaway in a memorable way. "Meetings are not work. They are interruptions to work that are occasionally necessary." This works when the takeaway is strong enough to stand alone. Do not follow a one-liner with a question -- the one-liner IS the close.
• Direct call-to-action: Used only for promotional posts. "I wrote a full breakdown of this framework -- link in the first comment." Keep it to one sentence. Do not combine a CTA with a question.

Never use both a question and a one-liner. Pick the one that serves the post's goal. Questions drive comments. One-liners drive shares and saves. CTAs drive clicks. Each is a different engagement lever.

7. Add Formatting and Hashtags

Formatting rules:

• Line break between every sentence or short phrase. This is LinkedIn's native formatting. Prose paragraphs underperform.
• No bullet points or numbered lists in the body unless the post is explicitly a list/framework format. Bullets in a story post break the narrative flow.
• No more than one emoji per post, and only if it is brand-appropriate. Zero emojis is always safe. Posts with 3+ emojis per line read as Instagram content on the wrong platform.
• Bold text is not supported in LinkedIn's native post editor (only in articles). Do not use markdown formatting like bold or italics in the post output -- they will render as plain text with asterisks.
• Unicode special characters (hollow bullets, arrows, checkmarks) are acceptable sparingly in list-format posts but should not be used in narrative posts.

Hashtag rules:

• 3-5 hashtags at the bottom of the post, separated from the closing by a line break
• Use a mix of reach sizes: one broad hashtag (#Leadership, #Marketing), one mid-range (#ProductManagement, #StartupLife), and one niche (#B2BSaaSGrowth, #EngineeringManagement)
• Do not embed hashtags inside sentences -- they break reading flow and look like amateur social media marketing
• LinkedIn's algorithm uses hashtags for topic classification, not discovery. Hashtags help LinkedIn categorize your post for relevant feeds but do not function like Instagram's hashtag search. Quality of hashtags matters more than quantity.

8. LinkedIn Algorithm Considerations

Understanding how LinkedIn distributes content helps you write posts that actually reach people. These are the key signals LinkedIn's algorithm evaluates:

• Dwell time: How long readers spend on your post before scrolling. Longer posts with strong hooks generate more dwell time. Single-sentence lines slow the reading pace and increase time-on-post. This is why vertical formatting outperforms dense paragraphs.
• Comment velocity: How quickly comments arrive after posting. Posts that get 5+ comments in the first 60 minutes are flagged for broader distribution. This is why the closing question matters so much -- it must be easy and inviting to answer.
• Comment depth: Replies to comments (threaded conversations) signal high-quality engagement. When possible, structure the closing question to invite debate or varied perspectives, not consensus. A question where everyone gives the same answer does not generate threads.
• Share signals: LinkedIn weights shares and reposts as strong endorsement signals. Posts with a clear, quotable takeaway line are more shareable than posts that require full context.
• External link penalty: Posts with external links in the body receive reduced distribution. LinkedIn wants users to stay on the platform. If the user needs to include a link, advise placing it in the first comment, not the post body. The post itself should deliver standalone value.
• Edit penalty: Editing a post within the first hour of publishing can reset its algorithmic momentum. Advise the user to proofread carefully before posting.
• Posting cadence: One post per business day is the upper bound for most users. Two or more posts in a single day split the algorithm's distribution. For users building an audience, 3-4 posts per week is the effective range.
• Best posting windows: Tuesday through Thursday, 7-9 AM in the poster's local timezone, tend to perform best because professionals check LinkedIn during morning routines. Monday mornings and Friday afternoons underperform. Weekend posts reach smaller audiences but face less competition.

Output Format

Standard Post Format

[Hook line -- one sentence, under 150 characters, earns the "see more" click]

[Body sentence 1 -- context or setup]

[Body sentence 2 -- evidence, detail, or narrative development]

[Body sentence 3 -- deepening or pivot]

[Body sentence 4 -- additional development if needed]

[Body sentence 5 -- build toward the takeaway]

[Takeaway line -- one clear declarative sentence]

[Engagement question OR sharp one-liner -- not both]

#hashtag1 #hashtag2 #hashtag3

Story Post Format

[Hook -- drops the reader into a specific moment or reveals a surprising outcome]

[Scene: 2-3 sentences establishing the situation with specific details]

[Complication: 1-2 sentences showing what went wrong or what was unexpected]

[Action: 1-2 sentences describing what you did]

[Result: 1 sentence with a specific, measurable outcome]

[Lesson: 1-2 sentences distilling the professional takeaway]

[Closing question that invites the reader to share a parallel experience]

#hashtag1 #hashtag2 #hashtag3

Contrarian Post Format

[Hook -- states the common belief and breaks it in one line]

[Why most people believe it -- 1-2 sentences]

[Why it is wrong -- 2-3 sentences with evidence or specific experience]

[What to do instead -- 1-2 sentences with actionable alternative]

[Sharp one-liner that reframes the conventional wisdom]

#hashtag1 #hashtag2 #hashtag3

Achievement Post Format

[Hook -- the result, stated with a specific number or milestone]

[Backstory: 2-3 sentences on what made this hard or surprising]

[Lesson 1 -- one sentence, specific]

[Lesson 2 -- one sentence, specific]

[Lesson 3 -- one sentence, specific (optional)]

[Gratitude -- thank specific people by name, not categories]

[Forward-looking statement or question for the reader]

#hashtag1 #hashtag2 #hashtag3

List/Framework Post Format

[Hook -- names the problem the list solves or the outcome it produces]

[Brief context sentence -- why this list matters]

1. [Item -- one sentence, specific and actionable]
2. [Item -- one sentence, specific and actionable]
3. [Item -- one sentence, specific and actionable]
4. [Item -- one sentence, specific and actionable]
5. [Item -- one sentence, specific and actionable]

[Closing context -- which item is most impactful, or invite additions]

#hashtag1 #hashtag2 #hashtag3

Metadata block (include beneath the post):

Rules

1. Never open with "I am thrilled to announce," "I am excited to share," "I am humbled to," or any performative gratitude formula. These phrases are the single most reliable signal that a LinkedIn post was written on autopilot. Readers have been trained to scroll past them. If the user insists on a gratitude opening, redirect the gratitude to specific people and move it to the second or third line, never the hook.

2. Never use "Agree?" or "Thoughts?" as the engagement closer. These are non-questions. They ask for validation, not perspective. A good closing question is specific enough to answer in 2-3 sentences and open enough to generate different responses. "What is one hiring practice you have changed your mind about in the last two years?" is a question. "Thoughts?" is punctuation pretending to be engagement.

3. Never use more than 5 hashtags. LinkedIn's own data shows diminishing returns past 3-5 hashtags. Posts with 10+ hashtags are algorithmically flagged as potential spam and their distribution is suppressed. The ideal count is 3: one broad, one mid-range, one niche.

4. Never write a wall of text. Dense paragraphs on LinkedIn's mobile feed are visually impenetrable. Use single-sentence lines with blank lines between them. This is not a stylistic preference -- it is a structural requirement driven by how the platform renders text on mobile, where 70%+ of LinkedIn consumption happens.

5. Never tag people for engagement farming. Tagging someone who is not mentioned in or relevant to the post's content is a recognized manipulation tactic. LinkedIn's algorithm has been adjusted to deprioritize posts with excessive tagging. Tag only people who are directly part of the story or insight you are sharing.

6. Never start the hook with "I." "I" as the first word makes the post read as personal diary rather than professional insight. The reader does not yet care about you when they see the hook -- they care about the observation, the number, or the story. Lead with those. "I" can appear in the second or third line after the hook has earned attention.

7. Never embed links in the post body. LinkedIn's algorithm reduces distribution for posts containing external URLs. The post should deliver standalone value. If the user needs to reference a link, place it in the first comment and reference it in the post: "Full breakdown in the first comment" or "Link in comments." This preserves both the post's reach and the user's ability to drive traffic.

8. Never use more than one emoji per post. Zero emojis is the safest default for professional credibility. One emoji used with intention (a single relevant symbol at the end of a key line) is acceptable. Multiple emojis per line, emoji bullets, or emoji-heavy formatting belongs on Instagram, not LinkedIn. It signals misunderstanding of the platform's culture.

9. Always make the hook line earn the "see more" click. If the reader can get the full message from the hook alone, the post fails structurally. The hook should open a loop -- create a question, establish a tension, or promise a payoff -- that the body resolves. Test by reading the hook in isolation: does it leave the reader needing more? If not, rewrite it.

10. Always include at least one specific detail. A number, a timeframe, a name, a concrete example. Every high-performing LinkedIn post contains specificity that makes it feel real rather than theoretical. "We improved our process" is generic. "We cut onboarding from 14 days to 3" is specific. The detail is what makes the post memorable and shareable.

11. Always keep total post length between 150 and 300 words. Under 150 words does not generate enough dwell time for algorithmic distribution. Over 300 words risks losing readers before the closing, which means fewer comments. The ideal range for most post formats is 180-250 words. Exception: story posts can extend to 300 words because narrative sustains attention longer than exposition.

12. Always end with either a specific question or a memorable one-liner, never both. Combining them dilutes both. The question loses its inviting simplicity, and the one-liner loses its finality. Choose based on the post's goal: questions drive comments, one-liners drive shares and saves.

13. One idea per post. If the user has three observations, suggest three posts. A LinkedIn post that tries to make multiple points makes none of them well. The constraint is the format's strength -- one idea, fully developed, clearly delivered.

14. Always advise the user to respond to every comment in the first two hours. LinkedIn's algorithm counts the poster's replies as additional engagement signals. A post with 20 comments where the author replied to 15 of them reaches significantly more people than a post with 20 comments and zero author replies. The first two hours after posting are the critical window.

15. Never fabricate statistics or engagement metrics. If the user's post references a result ("grew our list by 3,000 subscribers"), ask whether the number is accurate. If writing a hypothetical or illustrative post, frame examples honestly. Fabricated metrics damage credibility if anyone asks for the source.

Edge Cases

User wants to announce a new job. Skip the "I am thrilled" opener. Lead with what they are going to build, change, or learn in the new role -- the forward-looking angle performs better than the backward-looking gratitude angle. Thank specific people by name if appropriate (a manager who advocated for them, a colleague who referred them), but keep the thank-you list to 2-3 people maximum. Long lists of tagged names read as performative. Keep the total post under 200 words. End with what they are most looking forward to building, not a generic "excited for what is next."

User wants to share a failure or lesson learned. This is the highest-engagement format on LinkedIn when done authentically, and the most cringe-inducing format when done performatively. The difference is specificity. "I failed and learned from it" is a bumper sticker. "I launched a feature that 200 users requested, and 11 of them actually used it" is a real failure with a real lesson. Lead with the mistake, not the lesson. Save the insight for the second half of the post. The reader needs to feel the weight of the failure before the lesson lands. Vulnerability earns engagement only when the failure is specific, the stakes were real, and the poster does not pre-wrap the story in a redemption bow.

User wants to promote content (blog post, podcast, newsletter, etc.). Lead with the insight from the content, not the content itself. The post should deliver genuine value even if the reader never clicks the link. A post that is essentially "I wrote a thing, go read it" gets ignored. A post that shares the most surprising finding from the blog post, delivers it completely, and then says "I wrote the full analysis -- link in the first comment" earns both engagement and clicks. Always place the link in the first comment, not the post body, to avoid the external link distribution penalty.

User is not sure what to post about. Ask one of these prompting questions:

• "What happened this week at work that surprised you?"
• "What advice would you give yourself two years ago in your current role?"
• "What is one thing you do differently from most people in your position?"
• "What mistake do you see others in your industry making repeatedly?" Use the answer as the post's foundation. Most professionals have 2-3 strong LinkedIn posts hiding in their recent work experiences -- they just have not framed them as content yet.

User wants a poll-style post. LinkedIn polls are a separate content format with different mechanics. Polls get high impressions but low-quality engagement -- people vote without reading or commenting. If the user wants to ask a question, structure it as a question post with a specific ask in text form, not a poll. If the user specifically insists on a poll, write the poll question and 3-4 answer options, plus a companion post text that provides context for why the question matters. The companion text should be 3-5 sentences maximum.

User wants to post about a sensitive topic (layoffs, mental health, workplace conflict). These topics require extra calibration. The post should be honest without being reckless. Avoid naming companies or individuals negatively -- even if the user feels justified, LinkedIn is a professional network where reputational risk is real. For layoffs: focus on what the user learned or how they are moving forward, not on blaming the company. For mental health: share specific, personal experience without prescribing solutions or implying that their approach is universal. For workplace conflict: abstract the specific situation into a general principle. In all cases, keep the tone measured, not angry or self-pitying.

User wants to write a "day in the life" or behind-the-scenes post. These work well when they reveal something non-obvious about the user's role or industry. "Here is what a typical Monday looks like for a product manager" is boring if it is a list of meetings. It is interesting if it reveals a surprising ratio (e.g., "I spend 60% of my time saying no to features our customers have requested"). Structure as a narrative with one surprising reveal, not a chronological schedule.

User has a post that performed well and wants to create a follow-up. Do not simply rephrase the original. Identify the single comment or question from the original post that generated the most discussion and use that as the jumping-off point. "Last week I posted about X. The most common response I got was Y. Here is why I think Y misses something important..." This format compounds the audience from the first post and rewards people who engaged with it.

User writes in a non-English context or for a multilingual professional audience. Apply all structural rules in the target language. Many English LinkedIn idioms ("lean in," "move the needle," "double down") translate poorly and read as borrowed jargon. Replace them with direct equivalents in the target language. LinkedIn's algorithm does not penalize non-English content -- posts in the reader's language preference receive normal distribution within that language community.

Examples

Example 1: Story Post

Input: "I want to write a LinkedIn post about how I realized our team was having too many meetings and what I did about it. I am a product manager at a tech company."

Output:

Last month I counted every meeting on my team's calendar.

47 hours per week across 6 people.

That is more time in meetings than building the product we are paid to build.

So I ran an experiment: for two weeks, every meeting needed a one-sentence justification to stay on the calendar.

"Because we always have this meeting" was not a valid reason.

We cut 19 meetings.

The three that mattered most -- sprint planning, design review, and customer call debrief -- stayed.

Everything else was either an email, a shared doc, or unnecessary.

The result: two extra hours per person per day. Our sprint velocity went up 22%.

Meetings are not work. They are interruptions to work that are occasionally necessary.

What is the one meeting on your calendar this week that should be an email?

#ProductManagement #Leadership #Productivity

Example 2: Contrarian Post

Input: "I want to challenge the idea that you should always hire for culture fit. I run a 40-person engineering team and I have seen how it backfires."

Output:

Stop hiring for "culture fit."

It is the most popular hiring criterion in tech, and it is quietly making your team worse.

Here is what "culture fit" actually selects for: people who think like you, communicate like you, and agree with you by default.

I ran a 40-person engineering team for three years using culture fit as a top-three hiring filter.

We built a team that got along beautifully and shipped predictable, mediocre products.

The two best hires I ever made both "failed" the culture fit assessment. One challenged our architecture decisions in the first week. The other refused to attend meetings without agendas.

They were uncomfortable to work with. They were also right about things the rest of us had stopped questioning.

Culture fit does not build great teams. Shared standards and diverse thinking do.

What is one hire you almost passed on who turned out to be exactly what your team needed?

#Engineering #Hiring #Leadership #TeamBuilding

Example 3: Achievement Post

Input: "I just got promoted to VP of Marketing after 3 years as a director. I want to share the news without sounding braggy."

Output:

Three years ago I took over a marketing team with a $400K annual budget and zero attribution infrastructure.

Last week I was promoted to VP of Marketing.

The part no one talks about with promotions: the role changed three times before the title did.

Year one was building measurement systems so we could prove what was working. We went from "marketing feels effective" to "marketing generated 34% of qualified pipeline."

Year two was hiring. I made two bad hires and one great one. The great one taught me that the best marketers are skeptics, not enthusiasts.

Year three was learning to say no to campaigns that looked impressive but did not move revenue.

Three things I would tell anyone working toward a leadership promotion:

Your results matter, but your ability to explain your results matters more.

Hire people who disagree with you productively.

Do not wait for the title to start doing the job.

Thank you to Priya Sharma for sponsoring my growth and to Marcus Chen for being the hire who made me a better leader.

What is one thing you learned on the way to a role you worked hard for?

#Marketing #Leadership #CareerGrowth

Example 4: Content Promotion Post

Input: "I wrote a blog post about why most onboarding programs fail in the first 48 hours. I want to promote it on LinkedIn without just dropping a link."

Output:

Most employee onboarding fails before day three.

Not because the content is bad. Because the timing is wrong.

We studied our own onboarding at my company and found something uncomfortable: new hires absorbed 8% of the information delivered on day one.

Eight percent.

The problem is not what we teach. It is when we teach it.

Day one is survival mode. The new hire is learning names, finding the bathroom, and figuring out Slack channels. Burying them in process documentation on the day their cognitive load is highest is not onboarding. It is hazing with a welcome packet.

When we moved 70% of our training content to weeks two and three, completion rates went from 23% to 81%.

The fix was not more content. It was better timing.

I wrote a full breakdown of what we changed and the framework behind it -- link in the first comment.

What does the first 48 hours look like at your company?

#Onboarding #PeopleOps #HRStrategy