What went wrong? Redux

My "What Went Wrong" experiment has been interesting. As usual, I haven't been fastidious about logging items, but I did document some situations. I'm glad I've done this: reviewing the file makes me feel as though this exercise is helpful.

At the bottom of each entry, I try to include a sentence or two about the lesson to take away. Just for fun, the current lessons are below:

• Start simple; don't complicate things unless you know you have to.
• Ask people when they need stuff done by; stay calm.
• Make sure the boss know what we're doing in R+D.
• Don't capitulate into other peoples' pressures that you should be doing a certain thing (except the boss's).
• Just because someone invites you to a meeting, doesn't mean you have to go.
• Don't automate everything until you know the value of automating it.
• A purist approach is no match for a pragmatic approach when you're trying to get something done.
• Take the time to write very clear specs, especially when they'll be going to outside vendors.
• Know your tools!
• Don't assume you did the right thing. Be careful when cleaning up your drive.
• Mac OS X is not impervious to viruses. You should not be a moron.
• Be very careful what you say when you're criticizing something. Think about the impact it will have on the entire situation.
• Know the problem. Know why you're doing what you're doing.
• When you feel like you're doing something wrong, you are.

What are the recurring themes in all of this? Focus. Thoughtfulness. Purposefulness. Competence. Simplicity. That sounds about right.

I'll continue with the WWW file into the new year, but I think now it's also time to start with the What Went Right file.