ga('require', 'GTM-5F6ZV6B');
Process documentation

Process documentation

*This will be yet another short one.

One of the most helpful things I’ve ever done is begin to document the process.

When doing something new, I’ve found it to be rather difficult to remember the steps that I took to reach a certain objective.

If you can’t remember the steps, it’ll be a pain in the arse to reach that objective again in the future or to even teach someone else how you did a certain thing.

This post is going to be rather short because it will just go over how I go about documenting the things I do.

  1. I do an outline of the things necessary to complete something.
    1. This is usually the thing I do before I even start the project. It just goes over the things I see as being necessary before I even start the project.
  2. Next, I do research
    1. I have to see what other people have used. This lessens the learning curve immensely because I’m learning from other individuals mistakes. It also gives me a base with which I can add or take away from. It’s very helpful.
  3. I dive in and then I step back and write
    1. After I’ve actually gone in and seen what it was that I needed to do, I reminisce on the entire thing. I write down every single thing I did and how I did it. I write down my mistakes. I write down my victories.
  4. I do it again and then I document again
    1. After I go through and do it again, I write down what I did, again. This time I switch the things that didn’t work last time up. If these things work, I keep them in the draft.
  5. Last, I repeat step 4
    1. I keep switching things up until I find the recipe for success. This is what I’ve found to work for me. Mainly because it enables me to critique my process easier.

This is what I do. And it works for me.


*It’s a long-term process



Take advantage of your time. Follow your plan. That's my motto. I'm an entrepreneur from birth who has tons of philosophical thoughts.

Leave a Reply

Close Menu
%d bloggers like this: