I’ve been focused on blogging over at EMC’s InFocus blog for the last year, but I want to get back to the Practical Polymath and start blogging more frequently about a wider variety of topics. First up is some thoughts on a topic I’ve been spending a lot of time thinking about these days: Bespoke IT versus Fit for Purpose. We’ve spent a lot of time on bespoke IT in the industry, building new applications, silos, architectures, etc. to meet a specific need based on the skills and tools we are familiar with. We often don’t have the luxury to go out and investigate what the right tools would be and learn them in order to best apply them. If I think of this in sartorial terms, we make some outstanding, finely fit suits, but it might be in last decade’s style or colors. The suit might be of the highest quality and yet might not meet the needs of the wearer, or might stand out for all the wrong reasons in a crowd. Just because it’s bespoke doesn’t mean it’s the best way to approach the problem.
This is a long lead in to what I really want to talk about, the idea of Fit for Purpose. EMC acquired Adaptivity and I’ve been lucky enough to get to work with that great team, and learn a lot about how they think about IT, Applications and Infrastructure. They have a lot of talent on that team and I’ve learned a lot in conversations and brainstorming with them. Their Chief Scientist is Sheppard Narkier and he’s started to share many of his ideas, thoughts, and experiences on InFocus, see his post on Lessons Learned: The Quality of Design is not Fuzzy. On the surface , “Fit for Purpose” is nearly self explanatory, the idea of designing IT and Business systems based upon what they’ll be used for and how they’ll consume infrastructure. But to those not used to thinking in that paradigm, this explanation could be considered too coarse grained as a definition, let me explain a bit further. Continue reading