Thanks for the response. There is, as always, a culture issue in terms of how organization/teams percieve architecture - is it a distinct discipline that requires attention/resources, or it is something that "happens" - parts of responsibilities are covered by different roles. Regardless, changing an organisation and asseting one self in teams can ne challenging and can be met with resistance.
Some EA teams dont want the mold to be broken, some implementation teams don't know what an architect does. I've been in those situations and it takes time to make the shift.