I had a couple of minutes last week, so I looked in the enterprise phone book. This is like Googling yourself. It turns out my new employer....er...client thinks I'm an Architect/Designer.
The boss says she doesn't have a problem with that because a. I can do and b. I pretty much am doing it, as a sort of junior- deputy-assistant, associate Architect. That means I have no clue about process, people or things. But I'm learning.
Anyway, I wanted to know what the heck an IT Architect does since I thought it was like a super Team Lead- the kind of person who lives and breathes data layers, web services and other tools we BAs usually nod at like we understand what they're saying. I figure as long as they draw the graphics, they can call that stuff anything they want.
It turns out, I was close- especially on the technical end. But it turns out it's more of a blend of skills and knowledge:
Designer? Yeah. I'm not a full fledged Information Architect, oooops! An Information Architect at my client's site is a regular old software architect, not a trained designer and requirements gatherer. Actually, that's the group I'm in.
Anyway.
I'm not a full-fledged web-designer-user experience specialist, but I play one on television. Everyone other than my boss thinks it's amazing I have more than one skill set. Muahahahahaha.
So, I'm writing and drawing, drawing and writing. We came up with the concept in the first couple of weeks and are now making the case for Knowledge Management. Oops. Sorry. Knowledge Sharing.
You have any idea how cool it is working for a place that could care less what titles and functions mean on the outside? It's confusing as hell. But its pretty cool.
The boss says she doesn't have a problem with that because a. I can do and b. I pretty much am doing it, as a sort of junior- deputy-assistant, associate Architect. That means I have no clue about process, people or things. But I'm learning.
Anyway, I wanted to know what the heck an IT Architect does since I thought it was like a super Team Lead- the kind of person who lives and breathes data layers, web services and other tools we BAs usually nod at like we understand what they're saying. I figure as long as they draw the graphics, they can call that stuff anything they want.
It turns out, I was close- especially on the technical end. But it turns out it's more of a blend of skills and knowledge:
Architecture is a business in which technical knowledge, management, and an understanding of business are as important as design.- wikipedia
Designer? Yeah. I'm not a full fledged Information Architect, oooops! An Information Architect at my client's site is a regular old software architect, not a trained designer and requirements gatherer. Actually, that's the group I'm in.
Anyway.
I'm not a full-fledged web-designer-user experience specialist, but I play one on television. Everyone other than my boss thinks it's amazing I have more than one skill set. Muahahahahaha.
So, I'm writing and drawing, drawing and writing. We came up with the concept in the first couple of weeks and are now making the case for Knowledge Management. Oops. Sorry. Knowledge Sharing.
You have any idea how cool it is working for a place that could care less what titles and functions mean on the outside? It's confusing as hell. But its pretty cool.
Posts
