Journal Rules For Other Projects
The VARecipes project is not the only website I’m running. Given that writing an accountability journal of some form seems a good idea, I have decided to post updates on my other projects as well. These updates won’t be as detailed and won’t follow exactly the same rules as the journal for my 1MDBP entry.
What to expect
Reporting period
Initially I thought I should follow a similar pattern of weekly updates, separately for each project. In the end however I decided against it. I have a few more projects planned and don’t want to end up at some point spending more time writing updates and keeping up with the schedule than I actually do work.
This blog is not meant as a business, but as a way for me to stay organized and potentially accountable, so it cannot overtake my schedule. This lead me to decide on a monthly update cycle for my non 1MDBP sites.
Format
Each post will have the following headings: Tasks Acomplished, Lessons Learned, Finance & Stats, Tasks Planned.
Tasks Accomplished – a summary of what has been completed from the planned tasks from the previous month. Potentially with details on how to accomplish a specific task and if there were any difficulties.
Lessons Learned – partially might be covered under the previous heading. It would also include any insights not related to the tasks accomplished (or not). Although the updates are monthly, I might post “lessons learned” only posts more often, as things pop-up.
Finance & Stats – as the name suggests an update on income (and expenses), visitor stats, etc. This will be more of a highlights section, unlike the full disclosure for my VARecipes project.
Tasks Planned – what I plan to achieve by next month, divided into weekly blocks for easier planning.













