While I never met Bruce Barrington, one of the reasons I really admire him is something he said long ago about the things that programming tools make you do when building a program.
Anything you have to do every time shouldn’t have to be done at all.
photo credit: babasteve
Frankly, I think you can apply this to a lot of things in business – at least systems and processes-wise.
Here’s an example: Last Friday, I’m logging into Aweber to add a new message to my email newsletter. At the bottom of the list, I notice that my last message had a SpamAssassin score of 0.4.
Call me anal-retentive (or fastidious, whatever) but I don’t like seeing those scores on my emails.
Not. Even. Zero. Point. One.
So I click the SpamAssassin score link, which is supposed to show me which parts of the message caused the score to result. When I click the link, Aweber’s system tells me this:
There was an error in processing your SpamAssassin score. This is usually due to the message having lines that are greater than 80 characters long. If you still get this error message, then please contact customer support.
Tell me this.
Why in the world do I need to contact customer support? If you’re aweber (whose service I really like), wouldn’t you want to know *every single time* that this problem occurs?
Assuming that’s true, they already know who they are and how to contact themselves<g> and they already know who I am, since I’m logged into Aweber and working on my emails. So why don’t they have their system automatically open a support case on this issue?
I simply shouldn’t have to do this manually.
What do you make your clients do every day, every time they do business with you, every time they use your product, service, software or what not…that they shouldn’t have to do?
Fix it. Get started today.
It’ll make your clients appreciate you more because you’re saving their time.
It’ll make your business stronger and more productive because your stuff will have that much more value, and it’ll be easier to use.