Diagnose a 20 percent drop in activation for Creative Cloud

Problem Statement Description

Product context: Adobe is a creative, document, and marketing software company; its products include Creative Cloud, Photoshop, Illustrator, Acrobat, Adobe Express, Firefly, and Experience Cloud.

Adobe Creative Cloud has seen a 20% drop in activation among professional designers. In this interview, you are asked to diagnose what may be causing the decline and how you would structure the investigation. Treat “activation” as the point where a new or returning user successfully reaches meaningful first value in Creative Cloud, such as installing an app, opening a project, starting a creative workflow, or completing an onboarding milestone.

The product context includes a multi-app creative suite used by professional designers across individual, team, and enterprise plans. Activation can be affected by acquisition channel quality, account setup, payment or entitlement issues, installer performance, onboarding, app discovery, AI feature expectations, collaboration workflows, or competitive alternatives such as Canva, Figma, Microsoft tools, OpenAI-powered workflows, Autodesk, Google products, or CapCut.

Your task is not to immediately propose a fix, but to show how you would isolate the problem, validate whether the drop is real, identify where in the funnel it occurs, and determine the highest-confidence root cause before recommending action.

The experience should consider:

- How activation is defined, measured, and tied to user value for Creative Cloud users

- Whether the 20% decline is global or concentrated by region, plan type, device, operating system, acquisition channel, app, or user segment

- Instrumentation checks, event logging changes, dashboard issues, attribution changes, or data pipeline delays that could create a false signal

- Funnel steps from sign-up, authentication, plan entitlement, download, installation, launch, onboarding, and first meaningful creative action

- Differences between new users, returning users, trial users, students, freelancers, professional teams, and enterprise-managed accounts

- Potential external or product-driven hypotheses, including pricing, plan changes, installer reliability, app performance, AI feature rollout, competitive shifts, or marketing traffic quality

- Evidence needed to prioritize hypotheses, including cohort analysis, support tickets, user feedback, experiment logs, release history, and operational incidents

- Short-term mitigation, long-term prevention, monitoring, and communication if a root cause is confirmed

The goal is to demonstrate a clear RCA approach: frame the anomaly, verify the data, segment the impact, generate and test hypotheses, identify the likely root cause, and outline how Adobe should respond while protecting trust with professional creative users.