Adobe Summit 2026 · Field Notes
The best product intelligence at any conference does not come from the keynote. It comes from the bar. At the Adobe Workfront mixer during Adobe Summit in Las Vegas, I had a chance to speak at length with ambassadors, program managers, and everyday users who had no reason to stay on script. The conversations were candid, specific, and more revealing than any analyst briefing.
A $1.5 Billion Bet on Marketing Operations
Adobe acquired Workfront in December 2020 for $1.5 billion. The thesis was straightforward: Adobe had Creative Cloud and Experience Cloud but no system of record for the work that happened between creative brief and published asset. Workfront filled that gap. It brought intake management, resource allocation, approval chains, and project tracking into the Adobe stack. As I noted in earlier coverage of the Workday deployment case study, Workfront is doing the structural work most organizations skip: formalizing production sequencing so marketing and technology teams share visibility into what is actually moving through the pipeline.
The acquisition logic was sound. What the mixer confirmed is that the retention logic is equally sound, and that it comes from a different place than the product roadmap.
Delight Lives in the Details Most Vendors Overlook
One attendee lit up talking about a feature that would register as table stakes in most product reviews: Workfront notifies the right person the moment a ticket requires their action. That sounds obvious. The fact that it prompted genuine enthusiasm tells you something about how many enterprise tools still fail at basic workflow handoffs. When software removes the friction of chasing down the next person in a chain, the experience compounds across hundreds of small moments in a week. That is where loyalty is built, not in feature matrices.
Program Managers and End Users Want Different Things — Workfront Picks a Side
Enterprise work management tools sit in an inherent tension. The people who buy them want control, accountability, and on-time delivery. The people who use them daily often experience the same controls as friction. This is not a flaw in Workfront's design; it is the nature of any system that brings structure to creative and marketing workflows.
At the mixer, program managers were enthusiastic. The tool keeps projects on time and on target. End users who prefer more latitude had a more qualified view. That divide is not a warning sign. It tells you exactly who Workfront is designed to serve: the operational layer that needs visibility, not the individual contributor who would rather work without guardrails. Knowing which problem you are solving, and solving it well, is a more defensible position than trying to please everyone.
Four to Five Years of Retention Tells a Story
Most of the people I spoke with had been on the platform for four to five years. In enterprise software, where migration is painful and switching costs are real, that tenure is not surprising. But the absence of complaints about being locked in was notable. Nobody said they stayed because leaving was too hard. They stayed because the platform had earned its place in their workflow. Workfront is not inexpensive. For these teams, the investment had cleared whatever internal bar they set.
The Ambassador Program Is a Strategic Asset
Kristin Farwell runs the Workfront customer advocacy program and the mixer showed why that work matters. Ambassadors were given prominent placement, their stories displayed in high-resolution visuals across the screens at the venue, production quality that reflected Adobe's Creative Suite capabilities. They received custom team jerseys that gave the group a visible identity in a conference full of vendor messaging.
Each ambassador had a specific story. Not a testimonial, a story. That distinction is worth noting. A testimonial is a quote about how good the product is. A story is about the problem that existed before, what changed, and what is possible now. Customer advocacy programs that produce stories instead of testimonials create assets that do more work in more contexts. The mixer ran well because the content was real and the people telling it had earned the credibility to do so.
Running into David Smith in the elevator and discovering he had wandered into a selfie was a reminder that these events are also just people finding each other. Kim Kent and Sheila Dailey were good companyand it was thrill meeting them in person. Adobe Analyst Relations is one of the best in my opinion in adhereing to best practices and relationship building. The informal moments around a conference are often where the most honest conversations happen, and this mixer created the conditions for them.
Where Workfront Goes Beyond Marketing
Adobe positioned the acquisition primarily around marketing operations, and that is where the installed base is deepest. But Workfront's roots are broader. Before the acquisition, deployments spanned manufacturing, utilities, government, and professional services — environments where structured intake and approval workflows matter as much as they do in a 20-person marketing department. The question for Adobe is whether it extends that footprint or continues to prioritize the marketing and experience cloud use case. The architecture supports both. The go-to-market has not yet committed equally to both.
Workfront's marketing operations install base is deep and sticky. The real question is whether Adobe invests in extending the platform to non-marketing workflows, or whether it consolidates around the content supply chain use case and cedes the broader work management market to Smartsheet, Microsoft, and others. Which direction Adobe takes will determine whether Workfront grows into an enterprise-wide system of record or remains a premium tool for large marketing teams.I will ask for a briefing to get more insights if this is true or just my perspective
