Where Adobe may fit
Adobe may sit across several layers of a customer-technology architecture: experience data and profiles, content and assets, analysis, journey management, decisioning and channel activation. Its role must be defined against CRM, data-platform, consent, identity, commerce and channel systems so that overlapping products do not create competing sources of customer context or duplicated orchestration.
Decisions the architecture must make explicit
- 01
Which Adobe products are necessary for the target capabilities, and which needs should remain with existing platforms?
- 02
Where should customer identity, profile, event and consent data be mastered and governed?
- 03
How should content, decisioning, journey orchestration and channel execution responsibilities be divided?
- 04
What integration, migration and operating-model changes are required before implementation commitments are made?
- 05
How will the organisation test vendor and integrator proposals against an agreed architecture and decision log?
Where independent advice can help
- Frame a bounded Adobe platform decision or independently challenge a vendor recommendation before commitment.
- Map the intended role of Adobe capabilities against customer journeys, data flows, identity, consent, content and channel responsibilities.
- Assess platform overlap, architecture options, governance, operating-model implications and implementation readiness.
- Provide architecture assurance and decision challenge while internal teams or an appointed implementation partner deliver the solution.
Boundaries and non-fit
- Adobe product configuration, campaign operations or production support
- Detailed migration execution, software build or programme management
- Licence resale, formal procurement administration or vendor negotiation
- A predetermined recommendation that must favour Adobe