Saturday, December 08, 2007


Manager of Business Intelligence Architecture

Lots of people ask me what I do for a living, and usually it's easiest to just say "I work in IT." Of course, most people immediately think that I'm a computer technician (which I don't feel qualified to claim despite my degrees in Computer Science and Electrical Engineering). So, I often used to add "I do software development," which is sort of true, but "software development" in an IT organization is a bit different than "software development" at Microsoft; and the kind of development I did was mostly about putting information in databases. Not something that most people can picture, because I wasn't building anything with a user interface. It's a little easier now that I'm a manager, because some people are willing to just stop at "manager" with assumptions about pointy-haired bosses; but when I have to start explaining what everyone on my team does, it gets even harder than it used to be because my current team has about 6 different roles.

For the unindoctrinated, here's the break-down of my title and an explanation of what that means I do (at least according to my current employer):

Manager of
...some who spends a lot of time in meetings, tries to organize and direct the work of other people but usually just makes things more complicated than they need to be, and should be required to have unexpected degrees in social work, psychology, political science, and anthropology.

...the art and science of making money doing something for someone that they're willing to pay for.

...a measure of aptitude or acumen. In the context of "business intelligence" how "smart" a company can be about delivering the right services or products to the right people in the most efficient way.

...the overall design or patterns or rules used in governing the construction of a thing.

Does that help?

No comments: