I have had an exciting first week at my new job. It is a hectic environment, so I may be dragged into a meeting without any notice. Either someone will drop by my cube and ask me to join them, or I will receive an electronic meeting invitation ten minutes after the meeting started. It is not unusual to find that I have been "double booked." I've worked in similar environments before, and so far, I have managed to keep up.
I don't have my work email and calendar sync'd up to my Blackberry, yet, so I occasionally miss a meeting. I've submitted a request to have that done, so that should be taken care of in a few days.
I'm reviewing project proposals prior to our submitting a response. These are all for technologies that I have worked with, so I know what to look for. I've read proposals for three state-wide HIEs, and at least one for a regional HIE. It looks like I should be a part of the project teams for most of those.
I am being asked to consult existing project teams to explain technical options to them.
I've written use case narratives that will be handed off to developers.
I am getting better at finding my car in the parking structure after work. The first couple of days, I wandered around for five minutes or so before locating my car. I think that I have that figured out, now.
It has been a good week. I am looking forward to my second week.
Showing posts with label covisint. Show all posts
Showing posts with label covisint. Show all posts
Friday, May 13, 2011
Sunday, May 1, 2011
My New Job: Healthcare Solution Architect
I will start a new job on May 9. I will be working for Covisint as a Healthcare Solution Architect. I am really looking forward to this.
When I started the Masters program at Northwestern, this is the sort of job that I was hoping that the degree would prepare me for.
I did get a curious question when I was interviewing for the position. The question was, "Will you be comfortable not doing any of the development?" My roll will be to design or "architect" the systems and to outline the deployment plan, but then I will get to hand the real work off to others. Hmmm.... I hadn't thought of that. I have been building IT systems for over twenty years. I think that I will be able to live vicariously through the work of the teams that will be implementing the solutions that I design. I think that my years as a developer will give me a better understanding of what I need to provide the developers so that we can succeed.
Winston Churchill said that "However beautiful the strategy, we must occasionally look at results." I intend to make sure that we have success metrics in place before we begin implementing so that we can see whether we successfully implemented.
It should be an interesting transition, and I am looking forward to a new role and challenges.
When I started the Masters program at Northwestern, this is the sort of job that I was hoping that the degree would prepare me for.
I did get a curious question when I was interviewing for the position. The question was, "Will you be comfortable not doing any of the development?" My roll will be to design or "architect" the systems and to outline the deployment plan, but then I will get to hand the real work off to others. Hmmm.... I hadn't thought of that. I have been building IT systems for over twenty years. I think that I will be able to live vicariously through the work of the teams that will be implementing the solutions that I design. I think that my years as a developer will give me a better understanding of what I need to provide the developers so that we can succeed.
Winston Churchill said that "However beautiful the strategy, we must occasionally look at results." I intend to make sure that we have success metrics in place before we begin implementing so that we can see whether we successfully implemented.
It should be an interesting transition, and I am looking forward to a new role and challenges.
Subscribe to:
Comments (Atom)