A Forrester study commissioned by Adobe found that organizations often have solutions like Adobe Customer Journey Analytics (CJA) already in place, yet training and adoption move slowly because teams lack the bandwidth to coach colleagues on best practices. Because of this, teams often fall back on legacy tools and stay siloed, and the investment never delivers the value it was supposed to.
That gap, between go-live and confident everyday use, is where most Customer Journey Analytics investments either pay off or stall out. Here's why I believe implementation and enablement need to be treated as two separate goals, and what a real post-training enablement plan looks like.
A Customer Journey Analytics implementation represents a real investment of time, money, and people. Budgets get approved, requirements get gathered over months, and many different teams all pitch in along the way to plan, test, validate, and finally launch the new environment. By the time it goes live, an organization has often put in hundreds, sometimes thousands, of hours to get it right.
The trouble is, most organizations are measuring the wrong questions once they get there. Post go-live, variations of the same handful of questions circulate, such as:
Those are all fair questions, and they matter. But they're also all about the technology. The questions that predict whether the investment pays off tend to go unasked:
Organizations that plan for that second set of questions, rather than treating go-live as the finish line, are the ones who end up capturing the full value of their Customer Journey Analytics investment. Getting there starts with understanding just how much daily work changes once teams move into the platform.
Once teams are working inside Customer Journey Analytics, the shift is bigger than a new login. People are learning new terminology, building calculated metrics and curated components for the first time, and getting comfortable with person-based attribution instead of the device-level numbers they're used to. Even strong, capable teams tend to fall back on old habits when something feels unfamiliar.
A solid training program gives everyone the same starting point: shared vocabulary, a working understanding of data views and how they're modeled, and a sense of what the solution can do.
But knowing something conceptually and being able to apply it in practice aren't the same skill. Think about learning to drive. Nobody walks out of driver's ed and immediately merges onto the highway as a confident driver. Confidence is built from actual time spent behind the wheel, encountering real situations outside of a classroom.
Adopting Customer Journey Analytics works the same way. Training builds the foundation, but the real learning happens once people are back at their desks, working with their own data and business questions.
Post-training enablement usually takes a few different forms, and most organizations get more value from combining them than picking just one.
Office hours create a dedicated space where users bring real questions, analyses, and business challenges. Someone might come in stuck on why a calculated metric in Analysis Workspace isn't returning the numbers they expect, or unsure how to structure a curated component for a new stakeholder request. Over time, these sessions reinforce what training introduced and build confidence in a low-pressure setting.
Co-creation sessions go a step further and focus on building together. Instead of just answering questions, enablement leads work side by side with teams to solve a specific business problem, build out a new analysis, or set a best practice for how a data view gets used across departments. These sessions give teams hands-on experience while producing something the business needs, and they build independence at the same time.
Champion networks address a different problem: neither office hours nor co-creation scales well on their own once a platform rolls out to more teams. Identifying a handful of engaged early users, often the ones already showing up to office hours or asking sharp questions in co-creation sessions, and giving them a bit of extra support turns them into a built-in source of peer coaching that instills confidence. They troubleshoot the everyday questions before those questions ever reach a formal support channel. Champions also facilitate company-wide buy-in and act as intermediaries, bridging the gap between the technical parts of the implementation and practical daily use.
Used together, these three approaches move enablement from something that happens to teams into something teams start doing for each other.
Adoption is less a milestone than a curve. It builds as teams spend real time in Analysis Workspace, as stakeholders start trusting person-based attribution over the device-level numbers they're used to, and as analysts get comfortable answering business questions without waiting on a specialist. Reporting consistency across data views tends to follow the same pattern, improving gradually as more teams settle into shared habits rather than all at once.
The payoff for sticking with it shows up in the numbers. In the Forrester Total Economic Impact study on Adobe Ultimate Success, interviewees who set up desk-side coaching and workshop sessions alongside training got their teams to full proficiency about 30% faster, in nine months instead of twelve.
That kind of gain is the return on treating adoption as an ongoing process instead of a single go-live date. It's also what a long-term commitment to enablement can look like in practice, as it did for Cedars-Sinai, where an ongoing Customer Journey Analytics partnership helped the team build a durable, privacy-first analytics strategy over time rather than a one-time deployment.
Because adoption builds gradually, it needs its own way of being tracked, separate from the technical milestones that mark an implementation as complete. Technical milestones might include data view deployment, data collection validation, or system integrations working as designed. Enablement milestones should look at adoption and business impact instead:
A successful implementation creates capability, while a successful enablement strategy creates adoption. Organizations often spend heavily on building an advanced Customer Journey Analytics environment, but don't put the same effort into helping people use it well. But the organizations getting the most value from Customer Journey Analytics are investing just as much in helping teams understand, use, and get comfortable working in the platform over time.
If your organization has invested in Customer Journey Analytics and is still working to build adoption across teams, our team would love to talk through what a post-training enablement plan could look like for you. And if you're earlier in the process, our change management blueprint for Adobe Customer Journey Analytics covers how to set teams up before you ever reach go-live.