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

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

Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.
What branding can teach about culture
Jan 8: Culture is your company’s point of view in action—a framework guiding behavior, even in the unknown. You can’t copy it; it must reflect your unique perspective.
Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.

Older...

What I'm Reading