What if There’s No Reason to Eat the Dog Food?
There’s an expression in software about producing a product and market testing it — “seeing if the dogs will eat the dog food.” I’ve heard it mangled many times around the employees of a software company using the software their own company produces as “seeing if the dogs will eat their own dog food.” This is always true in consumer software and service companies.
Employees are often the best users, the power users, and the source of the best feedback to the organization about the product and competition. We certainly saw this phenomenon in spades at MovieFone, where I used to work before starting Return Path. There was no more of a power user to be found than Andrew, the CEO, and there was a frenzy every Thursday and Friday as employees called into 777-FILM to buy their own tickets for the upcoming weekend.
But what if there’s no reason to eat your own dog food? What if your software company develops a specific business application that only one or two people inside your company even care about? Our services are a great example. One or two people in Marketing, maybe one or two people in Technology, are users. When I think about some of the web applications we as a company use, the same must be true of their companies as well.
If this is the case with your company, how do you make sure you get that same level of raw feedback from passionate users inside the four walls of your office, and not just from user groups, which are ok but have some inherent problems in terms of their objectivity and representation.
I’m not sure I have a good answer to this – it’s more of a question to my readers than a prescription. I’ll happily reblog the best responses!