Resolve a cross-functional conflict blocking Frame.io

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.

You are the PM responsible for a Frame.io initiative aimed at improving how enterprise marketing teams review, approve, and deliver campaign creative across video, design, and document assets. The work touches Adobe’s broader creative and marketing ecosystem, including creative production tools, stakeholder review workflows, permissions, asset governance, and enterprise readiness.

A cross-functional conflict is now blocking progress. Product, design, engineering, go-to-market, customer success, legal/security, and leadership stakeholders are not aligned on what should launch, when it should launch, and which customer commitments or risks should take priority. The conflict may involve scope, technical readiness, enterprise compliance, integration dependencies, or disagreement over whether the marketer-focused workflow is ready for release.

Your task is to explain how you would diagnose the conflict, align the teams, create an execution path, and move the initiative forward without compromising customer trust or launch quality. Focus on how you would operate as the PM in an Adobe/Frame.io environment serving professional marketing teams.

Your execution plan should consider:

- The specific teams and decision-makers involved, including product, engineering, design, sales, customer success, legal/security, and executive sponsors

- The root cause of the conflict, such as unclear ownership, competing launch goals, technical dependency risk, customer escalation, or misaligned success criteria

- How you would gather facts from users, customer-facing teams, technical owners, and business stakeholders before making trade-offs

- How you would define decision rights, escalation paths, owners, and timelines to unblock execution

- How you would sequence work across must-have launch requirements, deferred scope, integration dependencies, and enterprise safeguards

- Go/no-go criteria, rollback planning, risk mitigation, and communication expectations for internal and external stakeholders

- How you would maintain trust with marketing customers while balancing speed, quality, collaboration depth, and Adobe’s enterprise standards

The goal is to demonstrate how you would lead through ambiguity and cross-functional tension, create a clear operating plan, and unblock a Frame.io launch or milestone in a way that is practical, customer-aware, and aligned with Adobe’s product and business priorities.