Having been involved in IT for quite a number of years I have been personally across an extensive list of faults, projects and to-do lists. Where the faults have ranged all the way from printing problems on a PC to Active Directory synchronization errors across multiple global domains. Where the projects have included things like office relocations, SAN upgrades and WiFi rollouts. And where to-do lists (IT strategies) have revolved around understanding the needs of multiple stakeholders, the timing of investment decisions and the availability of resources.

And one of the critical abilities that is common to all of these is the ability to think critically.

Not in the sense of being critical about others, but the process of thought and reasoning.

I’ve seen fellow IT professionals simply content to hit refresh buttons and just go for the software re-install.

I’ve seen projects fall over because some first and second order impacts weren’t considered.

And I’ve seen action items added to strategies for no other reason than it just felt right to the sponsor.

Sigh!

So, while the following list can apply to other areas of endeavor that requires fault analysis, project management or strategic approaches, all of these aspects of critical thinking do apply to the full gamut of activities associated with information technology.

Eight principles of critical thinking:

1. define the purpose
2. what is the question you are wanting to answer
3. collect information
4. consider your inferences
5. check your assumptions
6. be clear about the concepts in use
7. what exactly is your perspective
8. what are the implications

Regarding purpose. What is the objective of that project? What is it that is really trying to be achieved?

Regarding question. How clear are you about the fault you are trying to fix? What are its symptons and underlying causes?

Regarding information. Do you have all the facts and evidence with respect to that fault? How long has it been going on, under what conditions is it triggered, and so on.

Regarding inferences. Looking at that set of strategic objectives, what interpretations and conclusions can you draw out from that body of proposed work?

Regarding assumptions. What beliefs and biases do you hold, and what beliefs and biases do you believe that others hold?

Regarding assumptions. With respect to that project, what are you taking for granted? With respect to that strategy, what are you assuming about the business?

Regarding concepts. What exactly is that idea you have about the cause of that fault? What is the theory you have about the use of that particular technology for that project?

Regarding perspective. Can you step back and see your point of view dispassionately? In the project management discussions, is your point of view valid?

Regarding implications. When you take that step to fix up the fault, what will happen? What is likely to occur as you execute that strategy?

The ability to think critically is increasingly important. Do you take the time and effort to apply any or all of these eight aspects of thought and reasoning to the tasks at hand?

 
For more of what I have to offer, visit Dellium Advisory, follow on Twitter, connect using LinkedIn, or review my strategy and futures-centric blog.

Advertisement

As you go along, you come across (and have to manage) “new” and different technologies. It may be data deplication and virtualisation. Or even stuff you haven’t managed before like ISA, VLAN’s and so on.

The thing with IT is that there’ll always be something new (even if its new from the perspective of something you haven’t managed, installed or advised on before). So as long as you have an open mind, a willingness to learn & a grasp on some fundamentals – it all should go well.

And so, there’s a new section in this blog – “Research and Understanding”. It covers some of the Information Technology infrastructure that I’ve had personal experience with.