SELECTED WORK / 02
INDEPENDENT CASE STUDY / CUSTOMER STRATEGY

One customer.
A connected experience.

An independent case study proposing how Adobe Experience Platform could connect customer data, personalized journeys, and marketing measurement for Bank of America.

ROLE
Independent analysis by Osayd Asif
FOCUS
Customer data & strategy
DELIVERABLE
12-slide case presentation
STATUS
Proposal · not client work
Connected.From fragmented signals to a more useful customer journey.
01Unify customer data02Activate relevant journeys03Measure and improve

An independently authored strategy exercise. It was not commissioned by Adobe or Bank of America. Financial benefits in the deck are modeled estimates and benchmark assumptions.

01 / THE PROBLEM

Personalization is only as connected as the data behind it.

The case frames three linked problems: customer information separated across retail, credit, and wealth; inconsistent personalization across channels; and difficulty attributing marketing activity to outcomes. Governance sits across all three.

A bank can have many interactions with one person without treating those interactions as one journey. The recommendation therefore starts with a shared customer-data foundation, rather than treating each campaign or channel as a separate optimization task.

“A unified data foundation enabling real-time personalization, governed insights, and measurable marketing ROI.”Original presentation · slide 4
02 / THE DECISIONS

The choices behind
the recommendation.

01

Build the foundation before promising the experience.

The recommendation uses Adobe Real-Time CDP to combine customer information into governed profiles. Those profiles would support contextual personalization across digital and human channels, while addressing the data fragmentation described in the case.

The quality and permitted use of source data remain prerequisites. A platform recommendation does not establish that integration or governance is complete.

02

Connect activation and measurement to the same journey.

Adobe Journey Optimizer is proposed for behavior-triggered journeys. Customer Journey Analytics is proposed to connect interactions across app, web, branch, and call center, creating a route from activation to attribution and optimization.

The proposed benefit is a more coherent operating model. The deck’s uplift and efficiency figures are assumptions and external benchmarks, not results produced for this bank.

03

Phase the rollout instead of treating it as a single launch.

The proposed 12-month roadmap progresses through foundation, activation, and optimization. Priority data sources and pilot personalization come first; automated journeys, campaign activation, analytics, and broader expansion follow through overlapping workstreams.

Phasing makes dependencies visible, but the roadmap still needs real delivery capacity, ownership, and pilot evidence before it can become a committed implementation plan.

The proposed Adobe solution framework. Benefit figures shown on this original slide are case assumptions and benchmarks, not delivered outcomes.
The proposed Adobe solution framework. Benefit figures shown on this original slide are case assumptions and benchmarks, not delivered outcomes.Open slide 4 ↗
The proposed 12-month roadmap separates foundation, activation, and optimization. It is an implementation recommendation, not a completed rollout.
The proposed 12-month roadmap separates foundation, activation, and optimization. It is an implementation recommendation, not a completed rollout.Open slide 6 ↗
03 / THE OUTCOME

A recommendation that connects the technology to the business problem.

The finished artifact is a 12-slide presentation with a problem assessment, platform recommendation, financial model, phased roadmap, and appendix. It makes the relationship between customer data, relevant engagement, and marketing measurement explicit.

The result is an independently authored case recommendation. No deployed Adobe integration, verified revenue uplift, cost saving, or live customer-experience improvement is claimed here. The financial section should be read as a scenario model to be challenged and validated.

What would turn the recommendation into evidence

  1. Confirm priority data sources, consent requirements, and who owns each dependency.
  2. Define a pilot journey with a baseline and a comparison group.
  3. Replace benchmark assumptions with pilot measurements before expanding the model.
04 / GO TO THE SOURCE

The full thinking,
in the original deck.

Explore the presentation behind this case, including the recommendation, supporting detail, and assumptions.

Read the original deck (PDF)
NEXT CASE / TEAM CASE COMPETITION / COMMERCIAL STRATEGY

G.R.O.W.