All about the Strategy, Design, Customisation, Deployment and Development of SharePoint and its related Technologies

  Administration   All Me!! Baby!!   BDC   Book Review   Business   CKS   Conferences   CQWP   Development   Duffer Moments   Email   Errors   Family   Fixes   General   Groove   How To   How To Code   InfoPath   iPhone   IRM   Longhorn   Lotus Notes   Migration   Mobility   Office System 2007   Personal Projects   Powershell   Records Management   REST Services   Search Server   Security   SEO   SharePoint   SharePoint 2010   Silverlight   SQL   Tech Ed 2008   Testing   Vista   VSTO   WCF   WSS   XSL

[12/12/2008] Administrator, Specialist, Consultant, Architect or Guru
 
Categories: Business, General
 

Like most of you I would assume that you have had various job titles and sometimes they change with the times. I started life as an IT Trainer, progressed to an Internet Developer, had a few more in-between and am now a Principle Consultant. I remember when it was kind of cool to be called a technologist or an evangelist but now you don't see many jobs asking for that anymore. So what is so special about job titles and why do we get so hung up on them?

While working in the SharePoint Team I have been known as the following:

  1. Technical Consultant
  2. SharePoint Consultant
  3. Collaboration Consultant
  4. SharePoint Architect
  5. Solution Architect
  6. Principle Consultant

Even though the job titles have changed I really have not changed my roll, I still design, develop and implement SharePoint solutions. I still do pre-sales work and help the sales guys win the business. So nothing has changed. If we look on Wikipedia we see what a consultant is:

Consultant

A consultant is usually an expert or a professional in a specific field and has a wide knowledge of the subject matter. A consultant usually works for a consultancy firm or is self-employed, and engages with multiple and changing clients. Thus, clients have access to deeper levels of expertise than would be feasible for them to retain in-house, and to purchase only as much service from the outside consultant as desired.

Architect

If we look at what an Architect is we find that you can only get details for one of the following titles:

  1. Enterprise Architect
  2. System Architect
  3. Systems Architect
  4. Solution Architect

The table below indicates many of the differences between various kinds of architects:

Architect Type

Strategic Thinking

System Interactions

Communication

Design

Enterprise Architect

Across Projects

Highly Abstracted

Across Organization

Minimal, High Level

Application Architect

Component re-use, maintainability

Centred on single Application

Single Project

Very Detailed

Solutions Architect

Focused on solution

Very Detailed

Multiple Teams

Detailed

 

So I suppose the question is what is the difference between them?

If we are all delivering solutions and mostly getting our hands dirty surely we should just be called "SharePoint Delivery People". I know it sounds silly but realistically what does a job title mean?

In some people's eyes it means a pay rise, looks better on a CV or might even mean career progression. After interviewing people over the past year it has become evident that these job titles don't actually work, as it can be very subjective. When I was called a solution architect I met one of the .NET Solution Architects from Microsoft and quickly realised that I was nowhere near their level.

So how do you decide if you are at the "Consultant" or "Architect" level?

The industry general dictates length of service but that does not always work, peers often use you as the "font of all knowledge" and you become the "guru" or you are just generally great at what you do not just inside your company, but with clients and in the community. I am advocating that we all take some time and re-evaluate what we are called and not be so hung up on the title that we have. I have a hard time when I see people who are classed as Architects and are really no-more than a good consultant; I would rather be a fantastic consultant who thinks they are an Architect. To me an Architect is all about every facet of the platform, not just a one part all the framework. I always had a vision of what a "Solution Architect" was in my head and what level I assumed them to be. In my eyes and my opinion I feel that the jobs titles that we have, are given or the ones we see are becoming diluted because job titles mean promotion.

Let's take a look at what we are called and exam if we really do fit the bill, if we do fantastic, if not let's look at improving. Let's bring back the hierarchy of career progression.

For Developers

  1. System Analyst
  2. Developer
  3. Senior Developer
  4. Developer Architect
  5. Application Architect
  6. Solution Architect
  7. Systems / Enterprise Architect

For Consultants

  1. Technical Consultant
  2. Senior technical Consultant
  3. System Architect
  4. Solution Architect
  5. Systems / Enterprise Architect

 

My personal opinion would be I would rather hire someone who is at the right level for their job title than someone who is trying to pitch above their level.

This is why Microsoft has the Architect and Master programs to assist in us in seeing who the "gurus" are on the planet!!

Anyway this is my personal opinion so no backlash allowed!!

 
3 Comments
 

Comments

Saturday, 13 Dec 2008 03:06 by Matt Taylor
Well written piece Liam and I couldn't agree more with your conclusions. As a freelance SharePoint consultant from a technical background I pitch myself as a technical or development consultant, not because I like the sound of it but simply because it's what I do. I come across lots of "architects" in my work and many of them I wouldn't give the time of day. One of most important life lessons I want to get across to my children is that life isn't a competition, there's a place out there for all of us and we can all work hard to achieve our own personal best. I'm always really excited to talk and work with SharePoint experts who are more knowledgeable than me (of which there are plenty) but it doesn't de-value my ability or what I can offer my clients.

Thursday, 18 Dec 2008 05:11 by Andy Burns
Agreed - and I think that there is this thing about being higher in an organisational structure is still seen as 'better' and so a lot of folks pass themselves off as something they're not. This is despite that manager and technical expert are reliant on each other. Of course, for those of us who ain't self employed consultants, the thing about job titles is it's relationship with how much the customer is charged...

Wednesday, 24 Dec 2008 10:17 by Slash
Could not agree more with the last statement bud. As you know we know a few people like that trying to punch above there weight :) Merry Christmas my friend see you in the new year !!

Name:

URL:

Email:

Comments: