Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Ignoring 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.

I assume that the Web host (who will remain nameless) that I emailed last week has all the customers they can handle right now. They are apparently so busy with them that they don’t even have time to answer email sent to their sales department.

I was willing to give them the benefit of the doubt. Email gets lost. Someone misfiles it. Deletes it accidentally. Things happen. So yesterday afternoon I sent my questions to them again.


The silence, rather than being deafening, says a lot. They don’t need me as a customer. They don’t need my clients as customers. They just don’t need customers.

If you aren’t in the enviable position of having too many customers, make it a habit to answer your email several times a day. Every message, no matter how trivial, should get answered. If you run an Internet company, answer your email at least once an hour. It shows people that you are paying attention to little details. And you never know when one of those trivial messages is from someone who might be in a position to buy from you.

May 23, 2006 1:42 PM

I have also had a horrid experience with BN. I made an in-store cash purchase on 5/15/06 and discovered that I had purchased the wrong book. When I tried to return it 5/19/06 I was met by a very rude manager who said that I would not get my money back ($102) and all she would do for me was a store credit. I do not want a store credit, I want my money back, I will never purchase from BN again! I have tried contacting the district manager and she has not returned my calls. I strongly discourage anyone from making a purchase from BN.

This discussion has been closed.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2024 Adam Kalsey.