Why I'm an Obsessive Learner
As I sit here this afternoon, trying to finish some writing on the SharePoint 2010 book (and not being too distracted by some Gemini stuff I was tinkering with), I am reminded of a term I use often in self-description: "obsessive learner".
I have several friends who have reached very senior positions in their organizations who often call me crazy for the late nights and weekend work I do "learning the next new thing". I argue that the greatest value I offer as a service provider is to be useful (I actually strive to become 'essential'). In that context, I am always trying to find new/better ways to refine and extend the expertise I possess. I've tried to illustrate this philosophy in the image below...
In my mind, I know (and others recognize) that I have become good at something when I have achieved efficiency in execution. That means I do my task well, with the least amount of effort and time to deliver high quality. That's the output. There are a couple of ways to look at inputs. The first is 'Project Work'. Project work gives you experience with your task. As part of your experience, you gather knowledge and ultimately turn it into expertise... which prepares you for the next similar project. The second is 'Knowledge'. Gathering knowledge about a particular task helps you build a portfolio of expertise that can be leveraged in specific project work. This project work provides experience which can then be leveraged to better identify the next bunch of knowledge you hope to acquire.
To me, the second is far more powerful than the first in two important ways: (1) you are always better prepared for project work and (2) you proactively flow toward the project work that best fits your expertise. See the difference?
Obsessive learning isn't about being a super geek; it's about discipline and investing in yourself and staying focused on the areas where you want to stay "essential".
