Process versus Procedure

Process versus Procedure

Couple of years ago, in a fit of picque, I purchased an online package that promised to teach me how to expand my business, get the number one spot in Google, and otherwise, whiter teeth, fresher breath, more vibrant colors that don’t fade.

That one marketer I purchased from was, is, actually quite good at his job. What he had was a step-by-step outline for generating traffic. It wasn’t difficult.

The process, although this one product, digital product, was outlined as a web page with bullet points and icons, the process is straightforward.

Write engaging content.

Over the years, engaging content becomes anchor text that draws in “eyeballs.” That generates targeted visitors who eventually become paying customers.

The procedure, although the current content farms have been rendered pretty much useless, the process is still valid.

In the specifics, that one marketer suggested, for those who don’t want to write their own stuff, delegate. Get a ghost to author material, has to be original. The web does not reward duplicate content.

Obviously, I write all my own stuff.

The search engines parameters differ, and the search engines change how material is handled. Still, quality text and context is rewarded.

The procedure is the same, even if the specifics change in how the material is handled.

Here, at the top, in Gemini.

Process versus Procedure

Whether it’s building web pages, or delineating an astrology chart, what I teach, what I do?

Process, not procedure.

This popped up from two distinct sources in my feeds, and while I think I linked to it, I didn’t make a comment. However, carefully reading the post a second time, I found that tasty nugget.

“Posting to a blog first and then Twitter second seems like a simple idea, but it is extremely powerful.”


To me, seeing it in print, from an “expert” validates my process. What’s more amusing? I’ve been doing this, and calling it like this, for years. Literally, years. At least five – maybe more.

When AOL first picked me up, the then-manager suggested I take down my website, since AOL was carrying my work. I demured. Just seemed lie a good idea to have one place where I retain complete control of my own material. Previously, I’d seen my own stuff hacked to peices by editors.


Sometimes getting totally re-written by an editor is a good experience. Still, I like having one place where my original copy sits, untouched.

Build a process that works.

4 Trackbacks and Pingbacks

Leave a Reply

Your email address will not be published. Required fields are marked *