A Product Architect?

On a search for an identity on what I do for living I've found myself performing a role that they call "Product Architect."

So, what does this person do? This is what I've found:
Product Architect (n) --
1. a cross between a Product Manager and a Software Architect.
   Pays close attention to user needs, emphasizing practical solutions that enhance individual job satisfaction and increase company productivity. Applies broad and deep technical experience to select an appropriate mix of proven and cutting-edge technology.
2. for in-house projects, a hybrid of a Business Analyst and a System Architect. Bridges the gap between users and IT with previous success in both worlds.
Source: productarchitect.com

Sounds right on an ideal environment. The challenge comes when finances and bureaucracy get in the way. Trying to convince managers to adopt new technologies requires also some diplomacy.
Many are the times where you have to stand in the middle between the developers saying "we need the X version of software Y to be able to do this" and managers saying "X-1 Is the accepted version on the company" or "there is no budget to upgrade".  And here is where the architect needs to gain the credibility and the trust from managers and developers that his decisions are the right ones. Providing arguments that are business oriented to the managers for an upgrade or giving effective alternative solutions to developers on a technical level.

It is a really interesting job  where you have the opportunity to experiment with cutting-edge technology and real life problems and scenarios. Creating the link between the business and the technology that supports it.


Comments

Post a Comment

Popular posts from this blog

RabbitMQ first reactions

Image
As promised this is the first note about stuff we are working on our current project. Based on the nature of our system an asynchronous type of solution is needed. Having worked previously with some JMS solutions for example SonicMQ the words Messages and Queues was stuck on my mind right away when the project began.  OK, then if you remember my previous post I mentioned this is a "start-up" like project so we have to keep it cheap and OSS is the way to go. As consequence my first impression was hey! HornetQ its SUPER fast! 8.2Million messages per second. Lets try that!  So my colleague starts doing the first tests and after a while we begin realizing that its maybe too big of a rocket to shoot a fly and not so friendly to start with. Meanwhile I immerse myself in pages blogs and forums and the term Advanced Message Queuing Protocol (AMQP) pokes on my eyes together with RabbitMQ  which looks like the cool new kid on the messaging industry. So I do a few tests and wi
Read more

Start-up

After quite a few busy weeks I'm finally back to the blog. The reason for such absence was the change to a new job. And meant a more profound change than just switching jobs and let me explain what I mean with this by listing what has changed: From following to leading From guidelines to freeform From legacy to state-of-the-art From the consultancy world to the entrepreneur world And the last one pretty much sums it up... I recently left the consultancy world to join a "backed-up" start-up company on a moment where many may think it was a very risky moment to do so. Leaving from a established consultancy company to recently created one doesn't seem like something most people would do on times of financial crisis but to me it was worth the risk by believing that crisis times are those times where opportunities open to those few people who take it. It gives you the opportunity to reinvent yourself and to do something new or something better and to fill tha
Read more