Curating an enterprise architecture map

We might have satisfied Kinley in production, but we’re not done appeasing our other internal stakeholders just yet. Dalbert in marketing needs our Experience Cloud data to plug into his marketing technology (MarTech) stack, and Maggie in finance needs data from franchisee sales and end-consumer purchases to connect to our Enterprise Resource Planning (ERP) finance system. We also can’t forget Anna in quality, who needs the user experience to cleanly connect behind the scenes to internal IT systems such as single sign-on (SSO), our data lake, or any other middleware.

Let’s tackle the potential tech stacks around each of our stakeholders as we begin to design our enterprise architecture map. Every organization is different, and this Architecture Map is intended as an example to inspire you; it is not intended to be seen as gospel or as the sole way to do it.

Marketing technologies

Marketing automation tools have become...