It’s probably already evident that a lot of the focus of this blog is going to be on “blocking and tackling” principles related to running information technology at a reasonable-sized company. Curiously, those basic principles often seem to get ignored, which is one way that lots of companies end up in crises of information systems delivery and operations.
This post, then, is going to be about the most basic of basics: reading and writing, and their importance (“critical success factor” importance, in fact) to the overall success of a CTO/CIO’s projects and department.