What information does EA need from a new project?

A project does not need to produce a huge architecture document before engaging with EA.

Useful initial information includes:

• What problem are we trying to solve?
• What business outcome is expected?
• Who are the users or customers?
• What capabilities are affected?
• What data is involved?
• What systems need to change?
• What integrations are required?
• What security or regulatory requirements exist?
• What technology is being considered?
• What other initiatives depend on this work?

This allows the architecture discussion to focus on outcomes rather than paperwork.