Changing roles - programming to user facing consultant

[WhoreLex]

I'm currently a web developer which is ok but I much prefer interacting with people.

My ideal role would be as a customer/user consultant where I would go to the customer discuss requirements in a language they understand and then head back to the office and discuss the users requirements with the technical team.

I think I would be suited to the role as I'm good with people and can break down technical issues into concepts a user understands.

Anyone got any pointers on this?

thanks

Tom

[MadDad]

I think you are describing a technical architect position, you need to take a business brief or requirement and create a technical solution from it. A very interesting position, I have worked with some exceptionally good TA's in the past and they all have similar skills; excellent understanding of business dynamics and processes, very technically astute (know what technology solves what business issues), very strong client relationship skills (including the ability to tell a client that their business is not performing well or needs 'fixing' - harder than you would think!), ability to communicate requirements to a development or project team, understanding the dynamics of project finance (its great to create a sexy solution but if it costs more to create and implement that it will deliver then its a turkey) and also an ability to charge clients a lot of money for advice!

Seriously, sounds like you are looking for a TA role (which can be very rewarding both financially and also in a non-tangible way), but it is hard work and although the client facing side can be fun, justifying your salary can be hard work!

Good luck!

[WhoreLex]

That sounds good, to monster I go

[sagt550]

Consultancy is certainly the way to go if it is the whole customer interaction piece that really appeals to you. Whether you would be able to walk into a TA type role is another thing as a lot of organisations would expect you to demonstrate your ability to consult before letting you loose as a TA. The main problem here is how do you define a TA vs a consultant... ?

I think the previous poster summed it up pretty well - i.e. understanding the customer's business process as opposed to just the technical requirements (and dare I say it - take a "holistic" view of the problem) would fall under the remit of a TA with a consultant reporting into him/her and maybe taking the technical lead on a particular workstream etc... (or gathethering the requirements for their particular field of expertise).

There again I am talking about this from an infrastructure consultancy perspective which may operate differently than that of the development world.

Either way - the main skill without a shadow of a doubt is good communication skills followed by an appreciation of how the technology addresses their needs. Never forget this - the technology addresses their business needs - if you think like this you can't go far wrong.