Why this blog?

What's the purpose of this blog? Checking your work - or double-checking, actually, since that's the name of this blog - "checkyourwork" was already taken - is a dull subject. Who would want to read about this dull stuff?

Probably, not so many people. But, the point is, I need to do *something* about my constant lack of thorough checking - really any checking - which is annoying beyond words. The latest fiasco is, after I spend about a gazillion hours getting some data ready last week, I sent the lady the wrong link. She sent me an email at midnight asking if I had sent the wrong file. Luckily, I checked my email this morning and got it off to her.

But, that's not all. Our QC person had originally noticed an error, which I thought I had fixed. But, the lady noticed the problem. It turns out I had fixed 1/2 of it, but not enough of it. No checking.

Or, the fact that I named one file with "2000" instead of "2012". She didn't bother mentioning that.

Or, that I sent an email with a link, but without the link.

Why do I do this stuff? How can I prevent it in the future? How can I avoid that awful, egg-on-the-face feeling by getting stuff done right the *first* time?

Here are some ideas:
1) Send emails to myself first and read them.
2) Write down checklists. Or have electronic ones. Review them before you send stuff out.
3) Do stuff mindfully. Read the words as you write them. The spellchecker doesn't catch everything.
4) Savor the work you do. Re-read it and enjoy the excellence of it. Before you send it out.
5) Don't rush! Rushing *always* causes errors.
6) In you mind, ask yourself - what's the probability that this is right? If you're not confident - check.
7) Eyeball check stuff. Look at it, review, ask yourself - does this look right?
8) Get systems in place for checking. E.g. 1) Did I read my email over before sending it? 2) Did I send it to myself first? 3) Did I do at least a cursory check of the files that were sent? 4) What is a nice, easy check?
9) For software, you need to check out jUNIT and test driven design.
10) Use your QC people.
11) Get Zen about it.
12) Be *mindful* of what you're doing, saying and writing.
13) Ask a friend or colleague to check your stuff.
14) Blog about your double-checking gains.
15) Any item of work is always in two phases - the initial phase, then the checking/feedback loop. If the second part isn't done, then the work's not done.
16) Keep your emails and blogs small. That way, there's less chance of error.
17) After you create you email, take a walk before sending it. Settle down. Stop the urge to rush.
18) Use mistakes as motivation. You don't want to repeat them.
19) Pretend you had a lot of time to do each email.
20) Get good at this: what's a good check?
21) Get good at this: what have I done to check my work? WRITE IT DOWN.
22) Get good at this: what changed? What's fresh? AND FOCUS ON THAT.
23) Do retrospectives. Where did I screw up? Why?
24) Never, ever send anything to anyone with out doing at least two checks.
25) Failing that, use Leo Babuatta's trick - start TINY. Do some minute thing.

Ok. That's my initial entry. I plan to come back to this early and often until the habit of checking is totally engraved in my soul - till it become part of me.

Checks on this work:
Copied to a word processor and read there.
Was mindful and re-reading as I wrote
Took a walk before sending.
Previewed before sending.

Confidence level: 50% - found slight typo in post reading.