Grid-Tools

When deploying software, start with the company, not the product

News   •   Jul 13, 2012 14:22 BST

If you start with the company and end with the product, assuring all of those elements, you'll get a better result

By Rob Enderle | CIO US | Published 17:25, 10 July 12

In short, a company that is well-aligned with your business, understands the product and has an experienced team can do a better job with a bad product than a company with none of those advantages can do with a good one. It occurs to me that if you start with the company and end with the product, assuring all of those elements, you'll get a better result regardless of the product than if you start with the best product and pick a company that is missing any one of those elements.

Let's explore that.

Inexperienced teams make email system deployments difficult

My first experience with this was while I was working at Giga. Giga, which was the only third-generation IT research firm, repeated the mistake that is common with virtually all research firms and didn't actually use its analysts to pick or deploy products. (It's a power thing. Ask Gartner sometime if the IT organisation follows its own analysis.) Anyway, we needed an email system that could support the firm's embrace of collaboration. Giga decided to deploy Lotus Notes over the objection of the email analyst. By coincidence, it was me- I thought Notes kind of sucked as an email system. Fun times.

To read the full article click here.