Don’t adopt this conventional wisdom

You may be able to up your technical blog post game with a simple trick that shuns conventional wisdom.

Many well-meaning teachers advise writing the important stuff last: intro, conclusion, and headline. I think you’d be better off writing them first, especially the one readers will see first.

At a minimum, write your headline first. You can always change it, but aim to include high-quality draft headlines in your technical content calendar.

A good headline will:

• Declare your point of view
• Set expectations for readers
• Aim the post in a specific direction

It’s also what developers will eventually click in search results, emails, and wherever else it’s shared. Need help brainstorming your next headline? Our team may be able to help.