No one else has responded, so I'd like to contribute something, as you're clearly investing time in this. Technical writing is often cold, fact-based writing.

No one else has responded, so I'd like to contribute something, as you're clearly investing time in this. Technical writing is often cold, fact-based writing. There is the need to be 100% correct and caveat explicitly where necessary. Technical articles also should assume to require a user's attention, and popular articles deliver a quick fix. Promoting the use-case for a product isn't technical writing, it's marketing, providing clearly linked outcomes to causes/problems/opportunities that an audience should be aware of (should be). I had a quick look at your blog, for example 'Solve All Your Cryptography Problems in 3 Easy Steps' * The title is popularist, implying a quick-fix for readers that need a quick thirst-quench. Not that business, as it isn't quantified. A bit like a 20 second page-view blog post. * The content is not. It is long and quite detailed. But now I'm thinking, so who's the audience? If the audience is 'business' write to them with appropriate diagrams and do link to much more highly technical implementation and justification - using external references can help a lot here. * If the audience is implementers, stroke the technical side. How it is not hard, exotic or difficult, but is interesting, well supported, and could also gain some credit if they used the material to bring a business case themselves. Improve the quality of the writing: Split your audience into buckets of people with different needs, and address those needs. About learning Photoshop: Forget that. If you want more diagrams, do them in PowerPoint, export as a PDF, then export from Acrobat as an image. Absolute zero learning curve.