What is something that people believe that you don’t think is true or fully true? Say why and use data and reasoned arguments to back up your points.

Does the piece guide readers through any valuable tasks? Distill the core steps into a social post.

Sum up the major insights from the piece in a thorough but concise fashion

Highlight one detail from an individual section in the piece that might surprise, excite, or concern your community.

Directly advertise your content and tell people what they’ll learn by clicking through and reading it.

What experiences and insights will you carry from this work into your next project?

Does the piece look different to you now that it’s been out in the world for a while? Do any of its opinions seem particularly prescient or off-base? Would you change anything about it in retrospect?

Positive feedback is great social proof – and negative feedback can be a great conversation starter.

Does your post ask a question or make a comparison (e.g., SQL vs NoSQL)? Summarize your main takeaway and then ask your readers what THEY think. Keep the conversation going in the replies.

How might the patterns identified in the piece evolve in the next year? How about the next ten years? Ask the question of your audience and lay out your own theories.

How are people in your community responding to the challenges presented in the piece?

Did you create a compelling chart or illustration for your article? If they’re useful to readers of the blog post then they’ll probably be useful to folks in your social feed too.

Does your piece quote a compelling statistic? Consider including data that may not have made it into the article.

Select a quote from a source cited in your article and turn it into a social post.

Anyone outside of your team who was consulted for the piece. This includes people you quoted but also people who helped you informally refine the content as well.

Anyone who is doing interesting work around the subject that you covered in the piece. Experts, academics, writers, businesses, nonprofits, etc. They don’t have to be people you know first-hand.

Books, reports, art… anything that informed your work on this piece or simply inspired you.

Writers, editors, researchers, producers, designers. Anyone who had a hand in producing this content. Celebrate the unique contributions they made.

Did something you think would be easy end up being hard? Document technical or procedural challenges you ran into, what made it unexpectedly hard, and document in detail how you overcame it.

What about a given production, data point, conclusion, or response was particularly difficult for you to deal with?

How has your own perspective changed in the course of publishing this post? This doesn’t have to be an epic tale, just a simple change of heart.

If you’ve interviewed people for a piece then a few human stories probably made their way in. Distill those for social posts. Focus them on the people as much as possible.

Talk about a time you implemented a technology, architecture, or design strategy discussed in the article. Or, talk about a time you DIDN’T implement it - and what the consequences were.

What are customers saying about the real-world challenges they face? Discuss how the content of the piece addresses that challenge.