Enterprise Architecture can become very personal. A platform choice can protect a team we trust. A roadmap can preserve a budget we fought for. A standard can make our past recommendation look wise. None of this is unusual, but it is dangerous when private interest becomes louder than enterprise need.

The deeper issue is not whether we visit the enterprise concern for a meeting. It is whether we remain with it long enough for our own preference to stop steering the answer.

Good architecture asks a quiet but difficult question: what would I recommend if my reputation, favourite method, preferred vendor, and local success were not being defended?

When self-interest gets quiet, the real work becomes easier to see. Data ownership may matter more than the dashboard. Operating model clarity may matter more than the new tool. Commercial discipline may matter more than pleasing one sponsor. The architect’s job is not to win the design argument. It is to help the organization see what serves the whole enterprise over time.

Today, stay with the real enterprise question long enough for private interest to lose its grip.

Reflection:

Where might my recommendation be shaped by self-protection, team loyalty, method loyalty, or a past decision I do not want challenged?

Practice:

Before one architecture conversation, write two columns: “what I prefer” and “what the enterprise needs.” Do not proceed until you can explain the difference.