Thursday, February 12, 2009

Dirty Technology

My freshman year of undergrad in my comparative politics class, we discussed how people who were forced to be cost and time efficient would sometimes sacrifice on quality. Manufacturing plant workers, illustrated in a case example, were throwing mud into the mix to save on the cost of cement. In the long run, things fell apart. These workers might have (1) FELT that making management happy by meeting cost expectations outweighed what they might have (2) THOUGHT that the ensuing consequences of their actions would have on the longevity of the company.

While the heart might be the focus for marketers, it is clear that situations when the heart outweighs the head are not always advantageous. True efficiency generally requires a significant degree of intimacy, and worthwhile intimacy requires efficiency.

When identifying technology solutions for an enterprise or business unit, intimately understanding their needs is critical in being able to determine the appropriate system. Are silos always the wrong way to go? Probably not, depending on the size and scope, a highly focused software package might be best implemented for a niche part of the company. At the same time, if only such solutions existed in a large enterprise, everything, as demonstrated in class, is highly likely to become very twisted and inefficient.

You don't want mud when you need cement. Intimate knowledge of your needs and capabilities maximizes your ability to engage efficient solutions.

No comments:

Post a Comment