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

Popular posts from this blog

RabbitMQ first reactions

Start-up

6 Years later