At the Worth & OPR Brand Stewardship Breakfast in Davosโ€”hosted with Loreal Lynch (Jasper) and Chris Foster (Omnicom Public Relations)โ€”the table wasnโ€™t doing โ€œAI hype.โ€ It was doing operations: whatโ€™s working, whatโ€™s breaking, and where the friction actually lives when you try to move from pilot projects to enterprise behavior.

The opening framing captured the mood shift from a year ago. As one host put it, โ€œLast year, I kind of felt like it was Groundhog Day around this AI brand. Trustโ€ฆโ€ The implication wasnโ€™t fatigueโ€”it was that the conversation had matured. The question is no longer whether AI belongs in marketing and communications; itโ€™s how you keep control of the work when the tooling moves faster than the org can absorb it.

A lot of the talk landed on governanceโ€”not in the abstract, but as an everyday constraint. One participant cut straight to the point: โ€œGetting around procurement and the AI governance councils within your organization. Itโ€™s brutal.โ€ That one line explains why so many โ€œtransformationsโ€ stall. Itโ€™s not that teams canโ€™t generate use cases. Itโ€™s that they canโ€™t get adoption, access, and permission at the speed the market now expects.

And speedโ€”specifically the impatience for resultsโ€”came up as a self-inflicted wound. One participant described the pattern: โ€œI think thereโ€™s this Need for Speed, and so people donโ€™t want to spend the time.โ€ The โ€œtimeโ€ here isnโ€™t implementation hours. Itโ€™s the foundational work: consolidating messaging, defining voice, building governance, and creating a usable knowledge base so AI systems donโ€™t just produce more contentโ€”they produce the right content.

That connects to a second thread: authenticity at scale. One person described the target state as less โ€œwrite a pieceโ€ and more โ€œbuild a system that can write in our voice without drifting.โ€ Another participant put the failure mode bluntly: โ€œHow do you have the guard rails โ€ฆ stay authentic as you scale so that itโ€™s not slop, you know.โ€ The word โ€œslopโ€ is doing a lot of work there. Everyone knows what it looks like: content thatโ€™s plausible, high-volume, and brand-toxic because it feels generic or miscalibrated.

Whatโ€™s interesting is that nobody framed this as a creative-versus-machine argument. It was closer to craft-versus-chaos. When the inputs are messyโ€”fragmented messaging, conflicting guidance, outdated languageโ€”AI will faithfully scale the mess. When the inputs are coherent, AI can become leveraged. There was real agreement that the blocking issue is โ€œcontext,โ€ not capability.

Another point that landed: the mental model has shifted from fear of replacement to pressure for re-architecture. One participant described their own evolution: โ€œThereโ€™s no way AI would not replace 20 to 25 of the jobs.โ€ But that line didnโ€™t hang in the room as doom. It landed as a reminder that the work is being re-bundled: fewer purely mechanical tasks, more oversight, more orchestration, more responsibility for outcomes.

The New Rules of Discoverability

The table also revealed a genuine tension around the open web and โ€œbeing found.โ€ Someone recalled a moment from last yearโ€™s breakfast that sounded outlandish then and feels less outlandish now: โ€œI wonder if I should stop investing and building my website and I should instead hire someone that can focus on getting us found in LLMsโ€ฆโ€ The immediate responseโ€”still in the transcriptโ€”was: โ€œYouโ€™re crazy.โ€ But the fact that this came up again (and wasnโ€™t dismissed as quickly) is the tell. The discoverability game is changing. CMOs and CCOs are being asked to fund new forms of visibility while still maintaining the legacy ones that boards, business units, and stakeholders understand.

If there was a throughline to the morning, it was this: AI isnโ€™t โ€œa toolโ€ in the way the last decadeโ€™s tools were. It behaves more like infrastructureโ€”something that touches workflow design, governance, reputation, and measurement simultaneously. Thatโ€™s why the discussion kept returning to systems questions: standardize or let โ€œa thousand flowers bloom,โ€ centralize or federate, lock things down or move fast and audit later.And itโ€™s why the most practical takeaway wasnโ€™t a platform recommendationโ€”it was an operating principle: if you want scale without brand drift, you have to do the unglamorous work first. Build the message foundation. Agree on guardrails. Make it possible for teams to move quickly and stay in bounds. Otherwise, you get speed, but not controlโ€”and youโ€™ll spend the year cleaning up things you didnโ€™t mean to say.