Is the Enterprise Architect's job about influencing?

Yet again the EA architect role has risen debate. Here is a
post on influencing from Chris Venable. To start with, the fact is that the current EA architect role does not typically have the authority to make decisions. As such, pundits have suggested that "influencing" is the way the EA architect should do the job. It would be much clearer though had the kind of decisions been illustrated. After all, there are too many kinds of EA architects out there (see ads), from infrastructure, applications, Java, SAP, BI... to strategy and business architects. In practice, EA work consists of solution reviews, integration and IT strategy, see
this. Even if the architect would have the mandate to make decisions, they would be limited to IT. There is little scope for business decisions making even if the architect would be qualified for that since the role more often than not reports to the Head of IT Strategy and Architecture which has limited authority anyway. For decisions making there is an organization and governance structure in place in which the EA architect does not really sit. Moreover, as EA trespasses so many domains that any attempt at influencing or unauthorised decision making would meet politics. More the EA role should only provide the information for decision making. The analysis and decisions are made by other bodies not the EA architect. Because of the knowledge span, the EA architect can be invited at the decision table, sometimes. Todd Biske assumed
here that the EA architect is a leader and then talked about leadership in general and politics of influencing rather than about the EA role in particular. In the current role the architect is not a leader. Moreover, leadership comes usually with authority. But I believe we all have to influence in our jobs. In general it's a time consuming and risky avenue to get somewhere. Petty politics can halt your good intentions and what's good for the Enterprise. What is the meaning of influencing though? I assume that it means convincing people through various methods, passion and professionalism, to take the decisions you could only suggest. What are the chances that influencing succeeds though? 50-50%? It depends on personal skills. Would the management leave the future of the company at the mercy of an architect's skills and meagre pay? If Enterprise Architecture is so important to a company why not empower the EA function to shape the Enterprise? The problem is that top managements do not really think that current EA architects and EA bring value. So it is not about the EA professional having to influence but about having to convince everybody else that EA returns business value which has not been too often the case. What the EA architect has to do is to sell the EA based on real achievements. If that is what is meant by "influencing" then I agree. But you still needs practical results. How many good EA blueprints have you seen today? Mike Rollings of Gartner wrote
at "An EA program typically requires a massive amount of influence and communication because it includes the implementation of organizational change. It includes changes to governance, changes to processes, new decision-making responsibilities, and a wide-range of other changes to how an organization does planning and implementation." In reality an Enterprise Transformation and change program, if any, would not not be lead by the EA architect but by Program Management as an Enterprise Project Portfolio, controlled by a high up governance body. The EA architect does not plan the change either. The EA architect only produces the architecture and I agree here, collaborates and with all key efforts in the Enterprise. The was also discussion about a hypothetical and idealised executive EA position that shapes the Enterprise; but this does not really exist, and it won't until there will be a proper body of knowledge to arm the EA architect with and guarantee the EA value return. This position sits much higher in the organization, is empowered and no longer an IT role alone. Here is an older
discussion on the topic with Jeff Scott of Forrester. Yours PS:
here is a novel reference business architecture in a single page newly designed I am soon going to post about.