If you keep track of your analytics, it can help you keep track of ideas for content – the kinds of content that are working, and how users (and what types of users) are arriving at that content. 

Hewitt says how-to’s should be kept to under 800 words when you’re talking about blog posts. If it needs to be longer, break it up into different posts for different parts of the process. People generally don’t want to read incredibly long posts, particularly if they’re trying to get something done. 

Write about something you know about. It’s a good idea to talk to experts and research what others have written (and attribute credit accordingly) to fill in the gaps in your own knowledge on the subject. 

Define what Hewitt refers to as your "standards for success". Does your piece solve a problem? Make something function properly? Allow the person to achieve the goal without hurting themselves physically? It depends on the subject and the audience. You have to define your own standards for success.

When writing the piece, consider things like shortcuts, decisions and choices involved, situational changes, customizations, substitutions, and alternative methods. Make sure these are clear to the reader. 

Test the article out. Can you walk through the steps and reach the goal? Can someone else you know do the same? 

When it comes to style, be direct, concise, and unambiguous, Hewitt says. Use short, declarative sentences with only a single step in one sentence. Use consistency with you word choices. For example, if you are talking about a software program and call it "the program", continue calling it that throughout the article, as opposed to calling it "the application". 

If you use graphics, only use them if they make the process easier to follow (which they often can). They should clarify the process, whether they are illustrations, photos, flowcharts, slide shows, or videos. Hewitt mentioned some pros and cons with screenshots in particular. They can accurately show results of steps, make things easier to comprehend, and make presentations look more authoritative, but they can also take up visual space, make instructions look cluttered, and can become obsolete without notice. They can also be hard to read on mobile devices and hard to print well. 

Finally when it comes to order and grouping, Hewitt says to number steps when the order of the steps is important, when the steps are short, and when they require little discussion. Don’t use them when order is less important, each step does require discussion, and/or you’re writing in a casual voice (that last one’s probably debatable). Use unordered lists to group similar items (like tools/resources). Use bullet points and keep items brief when possible. 

Include results immediately after a step or when the step creates a change. Hewitt talks about this all in more detail here.