Monday, March 7, 2011

I wanna be a Solutions Architect

Well it does involve on sight work which I hate. But I could limit it to 2 days/week. I can put in the contract I'm only flying first class, and if my hourly rate is like $200 the client will respect every second I spend with them and feel honoured.

This is what I'm seeing. We reached a point in the project where we could say educated the client on the tools they bought (without evaluation, of course), and provided them with our solutions and started working on it. So know the ball is on their end. Yes, we'd need input. For that they should work... Solution to avoid this is:
  1. Re-arrange project plans so we - as vendor - will be busy restructuring our work to meet the new deadlines
  2. Bring an expensive solutions architect on board (see first paragraph) who knows all the tools they've bought so they can ask the very same questions we answered a half a year ago.
Point 1 and 2 applies at the same time.

However I'm not sure if a company who's very existence is depending on the success of this project should follow such strategy. But this is not my problem really, now is it?!

A solutions architect in a situation like that can only answer the questions by reading up the appropriate sections of the User's Manual of the system the client is going to use :) For $200/hr please hit me with a job like that! Shall I put this in my LinkedIn status message? :)

No comments:

Post a Comment