Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Business & Strategy

Turning away customers

Freshness Warning
This blog post is over 21 years old. It's possible that the information you read below isn't current and the links no longer work.

That’s nice. I found a problem on Major League Baseball’s Web site and sent their general-contact email address a short message detailing the problem and gave them a solution. My email was immediately returned to me.

Hi. This is the qmail-send program at mail1.chek.com.
I’m afraid I wasn’t able to deliver your message to the following addresses. This is a permanent error; I’ve given up. Sorry it didn’t work out.

fanfeedbackreply@website.mlb.com:

Sorry, your intended recipient has too much mail stored in their mailbox. Your message totalled 2314 bytes, which would bring them over quota. However a smaller message might go through should you wish to inform the person you tried to email.

There’s so much wrong with this that I don’t even know where to start.

  • You provide an address for people to contact you for help and that address is broken (of all the addresses to put a quota on, this wouldn’t be it).
  • When an error occurs, you send a message back to them that’s filled with tech-speak.
  • You offer a solution that is technical enough that most people won’t be able to figure out. (Go ask your dad how many words would fit into 2314 bytes.)
  • The response message has spelling and grammatical errors. (Totalled should be totaled and however needs a comma after it.)
  • The fact that your mailbox is full in the first place indicates that you don’t check it very often.

Go grab a pen and write this down. If a customer is going to go to the trouble of contacting you, it’s important, at least to them. Make sure you’ll see it.

Recently Written

Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.
Roadmap Outcomes, not Features
Sep 4: Drive success by roadmapping the outcomes you'll create instead of the features you'll deliver.
Different roadmaps for different folks
Sep 2: The key to effective roadmapping? Different views for different needs.
Micromanaging and competence
Jul 2: Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system
Jun 24: A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes
May 14: Being a product manager means never having to say, "that's not my job."

Older...

What I'm Reading