Right. I’m here. (Anyone actually still reading this?)
Sorry. It’s been busy. I’ve been working hard on a project in my day job, only to get given my notice. And in my spare time, I’ve been working hard on a service to provide unique content to your blog every day.
So this blog had to take a bit of a hit, as did some other sites I used to update regularly.
But I’m back now. With more regular posting coming in the future.
….
So, today’s topic. Slow and gradual improvement.
It dawned on me today that making small changes, on a regular basis, is one of the best ways to improve a process in many cases. The process I’m talking about is the writing of content for the UniqueBlogContent.com service I mentioned above.
There is a part of the process that is automated as much as I could in the timescales I had, but which needs some fine-tuning. In today’s case, it’s about capital letters. It took a few seconds to ensure that capitalisation (of letters) was correct in each sentence as I prepare it for publishing to my customers, as it was a manual thing.
So I stopped writing today’s article, took a couple of minutes to amend my software to account for the capitalisation, and then went back to writing. Result? About 30 seconds saved every time I write an article, plus a higher quality output (as sometimes I’ll miss the need for capital letters, I’m sure).
A small change, but one that will reap benefits.
Inspired, I made another change. One that allows me to type in a word, even if it’s not being used in the article, and see a list of words that mean the same. Again, another couple of minutes to write the code (using code I’d already written but in a different way), but it’ll give me a great amount of time-saving as the days roll by.
So, some questions:
- What processes do you do on an hourly, daily, weekly basis?
- What’s the most annoying thing about those processes?
- How can you automate it?