One part of an information strategy is how to classify information used in and by the organization and external parties, but it’s not as easy as thought of at first sight.

Enterprise architecture is about strategy and guidelines, but in the end you need to have an implemented process with tools to get business rolling.

This is a variant of Lyndon Johnson’s iron law of politics: that successful politicians must learn how to count.

You need to find enough of stakeholders that will accept your Architecture design. One way of doing this is to present a hypothesis to them and see how they react. 

As Enterprise Architect in an organisation, you don’t have any formal decision power, and you don’t have any P&L responsibilities.

Do I need to know privacy regulations as an enterprise architect? 

Normally as an EA, those requirements were managed by the legal department, but with #GDPR and Privacy by Design, this is something you need to take into account when designing architectures.