Each month, this series follows a fictional composite leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. I invented the names and companies. The failure modes, however, are real.

Nadia approved the AI expansion in February, during a quarterly business review where her demand gen results were the one bright spot in a flat pipeline quarter. Eight months earlier, she built an agentic AI system to handle prospecting sequences, content personalization, and pipeline qualification. The results held, and the team gained capacity. Her CEO asked where they could apply it to other use cases, and Nadia thought about customer renewal.

Her reasoning was defensible. The same personalization logic that interpreted buyer signals in demand gen, she reasoned, could do the same in retention. She moved forward, setting firm guardrails on volume and frequency. But she didn’t define what the agents should never be allowed to decide.

In week three of the new deployment, an agent generated a renewal sequence for three enterprise accounts in active contract renegotiations. The system generated the sequence on schedule. But the tone read like a script, completely misaligned with a delicate, multi-million dollar renewal. No one on Nadia’s team flagged those accounts as outside the agent’s mandate, because no such mandate existed. Two account executives received escalations from their contacts. One account went quiet.

Nadia was in a pipeline review when her VP of Sales texted her about the incident.

THE SITUATION

Eight months of results made the next decision feel inevitable

Nadia’s demand gen system didn’t fail once during the eight months it operated. That track record shaped the February decision more than the capability analysis. Consistent performance at one layer of the customer journey created a specific kind of confidence: that the agent understood the work as well as executed the task.

Nadia tightly governed the first deployment, with named KPIs, a defined scope, and human review at key points. The second deployment inherited the first one’s results, not its architecture.

The agents ran as designed. But the design was the problem.

WHY THIS MATTERS NOW

Agentic AI is scaling faster than the criteria to constrain it

Right now, B2B marketing leaders are operating under an intense executive directive to scale automation. According to BCG’s AI Radar 2026, roughly 90% of CEOs expect measurable ROI from AI agents this year, and companies dedicated nearly a third of their AI budgets to agentic deployments. CMOs aren’t expanding agent access in a vacuum; they are responding to massive top-down pressure. The conviction, however, is running ahead of the evidence.

McKinsey found that 62% of organizations are experimenting with AI agents, but only 39% report any impact on enterprise-level EBIT. A March 2026 BCG analysis found that 60% of companies have seen minimal or no business value from AI despite significant efforts, and nearly two-thirds report uncontrollable scaling expenses. Gartner projected in June 2025 that more than 40% of agentic AI projects will be canceled by the end of 2027, citing escalating costs, unclear business value, and inadequate risk controls. Gartner’s analyst named the root cause directly: most projects are “mostly driven by hype” and “often misapplied.” The mandate gap is where the failure lives.

The technology performed; the agent generated the renewal sequence exactly on schedule. The failure was operational. Because executive pressure demands fast deployment, leaders are scaling AI without building the governance architecture that defines where it should stop. The agents ran as designed. Nadia never built the constraint layer.

THE GAP

What she governed, and what she forgot to define

Her initial demand gen deployment succeeded because it had three structural pillars that the customer retention expansion did not: a tightly defined scope, a clear human owner for every automated action, and a mandatory review checkpoint before any text reached a live account.

Nadia didn’t actively strip these guardrails away for the second rollout. She assumed the governance structure had transferred.

But continuity is a dangerous assumption when changing customer motions.

Unlike cold prospecting, enterprise accounts live in a high-stakes relationship layer. Here, slight changes in timing, tone, and context carry massive revenue consequences. A conversion-optimized AI script simply isn’t equipped to read those nuances.

The three accounts currently in contract renegotiations went completely unflagged because the system lacked any concept of relationship states. Tracking a sensitive, ongoing negotiation requires human context and judgment, but Nadia had never designated anyone to feed that critical insight to the AI.

She wasn’t alone in this governance vacuum.

According to a 2026 industry survey by SmarterX, only 13% of organizations have all four foundational governance elements in place for AI deployment; nearly a third have none.

Nadia’s customer retention expansion fell into the latter camp. The incident report documented what the agents sent. Nadia never defined what should have been off-limits.

WHERE WE LEAVE NADIA

The incident report closed. The governing question stayed open.

Her VP of Sales spent three weeks in direct conversations to repair the damage and bring back the account that had gone quiet, conversations that a proper mandate would have prevented. They resolved the escalations, but the structural gap remained. Nadia acknowledged the mistake in a leadership meeting and committed to reviewing her AI expansion criteria.

The underlying problem was systemic: no one asked her what those criteria were before she approved the deployment. She hadn’t asked herself.

The question Nadia struggled to answer in that meeting is the one this series picks up: which decisions should an AI agent never make? She can document what the agents sent. The mandate that would have prevented it was never written.

This series, in four parts:

Part 1 — The Leadership Brief: The mandate that was never written (this post)

Part 2 — The Framework: The Agent Scope Map (paid)

Part 3 — Real-World Examples: Where strategic restraint held — and where it didn’t

Part 4 — The Debrief: What Nadia decided, and the question she’s still carrying

Sources

• BCG. “As AI Investments Surge, CEOs Take the Lead on Decision Making and Upskilling Themselves.” January 15, 2026. https://www.prnewswire.com/news-releases/as-ai-investments-surge-ceos-take-the-lead-on-decision-making-and-upskilling-themselves-302661849.html

• BCG. “How Leaders Build an AI-First Cost Advantage.” March 27, 2026. https://www.bcg.com/publications/2026/how-leaders-build-an-ai-first-cost-advantage

• McKinsey & Company. “The State of AI in 2025.” November 2025. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai

• Gartner. “Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027.” June 25, 2025. https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027

• SmarterX. “2026 State of AI for Business.” April 2026. [Industry survey — secondary reference]

About Kim

Kim Celestre is a strategic advisor and executive coach who helps marketing leaders navigate AI transformation without eroding judgment, trust, or human value. Her work is grounded in AIGP-certified responsible AI expertise, executive coaching, and 25 years of Silicon Valley marketing leadership, including 4 years as a Forrester industry analyst.

Each month, this series follows a fictional composite leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented, but the failure modes are not.

This is the final installment of our four-part series following Marisol, a composite B2B SaaS marketing executive, as she navigates the fallout of six months of operational decisions made without narration. While each post stands on its own, this week focuses on the reckoning: what she found when she finally asked, what she can’t undo, and the conversation she still owes.

WHAT CHANGED

The exercise she rewrote the morning of the meeting

Marisol did not run the session as planned. She originally prepared to walk her team through the Cultural Honesty Map herself, plot their collective position, and outline her forward-looking adjustments. Drawing inspiration from a Klarna case study she read the week prior, she intended to lead with a firm commitment: identify exactly which tasks she would never ask AI to take away from the team.

She abandoned that script the morning of the meeting. Instead, she handed out printed copies of the map and asked her team to complete three silent, solo tasks:

1. Locate yourself on the map.

2. Locate me on the map.

3. Write a single sentence describing the gap between those two points.

She gave them ten minutes. The room fell into an uncomfortable silence. When she asked her senior content strategist to share first, the strategist hesitated, then cut straight to the core: “You put yourself in Aligned. I put you in Exposed. That’s the gap.”

Marisol had walked into the session believing she was naming the change. Her team had walked in after six months of trying to decode the silent signals she didn’t realize she was sending. The mismatch wasn’t a minor communication hiccup; it was the chasm between a leader who believed her narrative was landing and a team left to write their own anxious version of reality.

The Cultural Honesty Map gave the meeting a forcing function that previous sessions lacked. Working through the axes together, Marisol explicitly defined what would end in the marketing function, what would evolve, and what would remain strictly human-led, no matter how advanced the tooling became. As the senior strategist documented these commitments in real time, a junior marketer asked the question the team had quietly carried for months:

“Which of these decisions did you already make without us?”

The true penalty of leadership silence isn’t what the leader mismanages; it’s what the team stops contributing while they wait for clarity.

WHAT SHE COULDN’T RECOVER

The six months her team spent waiting for a starting point

Marisol could fix the communication gap moving forward, but she couldn’t erase its history.

Two of her strongest contributors built private exit strategies. One took two exploratory coffee meetings with an outside recruiter; the other updated her resume the week before the all-hands. While both ultimately decided to stay, the baseline of trust they held in October—before the platform consolidation began—was severely depleted. They had spent half a year mentally detached, constructing a future where their work was no longer central. That defensive posture doesn’t unbuild itself just because a leader finally delivers the context she owed them months ago.

The cost manifested in smaller, compounding ways, too. A brilliant campaign concept that the content lead conceived in February surfaced in a brainstorm three weeks after the mapping exercise. When Marisol asked why it was held back for six months, the answer was telling: the lead didn’t think it was worth pitching in a department she assumed was being quietly dismantled. The idea was excellent, but it was six months late.

The true penalty of leadership silence isn’t what the leader mismanages; it’s what the team stops contributing while they wait for clarity. Marisol waited to perfect her strategy before sharing it, forgetting that her team wasn’t demanding perfection. They just needed a starting point.

WHAT REMAINS UNRESOLVED

The discipline she has not yet proven

By the end of May, the marketing team possessed a clearer sense of direction and a shared vocabulary for their evolving roles. The senior strategist who first identified the alignment led a session on maintaining cultural honesty with cross-functional partners. The retention risks stabilized. These were meaningful, rapid cultural corrections.

Yet a harder reality remained: Marisol had not yet faced the version of cultural honesty that actually tests a leader.

She had not had the conversation with her CMO. The CMO still believed the AI rollout was a textbook success. The baseline performance metrics looked healthy, and the original all-hands slide deck was still circulating in board updates as proof that marketing was adopting automation responsibly. That narrative wasn’t inherently false; it was simply incomplete. The CMO was operating from the exact same surface-level data Marisol had relied on back in March. The difference was that Marisol now knew the human cost behind those metrics.

Correcting the record upward meant vulnerability. It meant relitigating her own executive execution in front of the leader who approved her rollout strategy. It meant documenting that the all-hands presentation hadn’t landed well, despite what the congratulatory Slack threads suggested. It required owning a blind spot she only discovered because her team was brave enough to point it out.

Cultural honesty is not a conversation. It is a practice. The exercise Marisol ran with her team will be tested every time the pressure returns: the next board update, the next earnings cycle, the next time a campaign underperforms, and the easiest move is to soften what she tells the people above her and below her. Marisol had begun the practice. She had not yet proven she could sustain it.

That is where Discipline #4 reaches its limit. A diagnostic tool can map the gap between what a leader says and what a team hears, and running the exercise can bring that reality to light. But no framework can force a leader to manage upward with the same vulnerability she demands from her team.

June’s discipline begins where this one ends—with a leader facing a harder, more strategic question: Once you have named what is happening, what do you explicitly choose not to automate, even when you have the power to do so?

Thank you for following Marisol’s story through May. The EQ in Action series continues in June with Discipline #5: Exercise Strategic Restraint.

If this series has been useful, share it with a marketing leader navigating the same terrain.

About Kim

Kim Celestre is a strategic advisor and executive coach who helps B2B marketing leaders navigate AI transformation without eroding judgment, trust, or human value. Her work is grounded in AIGP-certified responsible AI expertise, executive coaching, and 25 years of Silicon Valley marketing leadership, including 4 years as a Forrester industry analyst.

Each month, this series follows a fictional leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented, but the failure modes are not. This month’s real-world examples — Google, Cloudflare, and Klarna — are drawn from documented public reporting.

Last week, Marisol ran the Cultural Honesty Map. The gap she found between what she said and what her team heard wasn’t hidden; it had been widening for six months while she focused on operational execution. She wasn’t alone. These organizations confronted the same question. Some answered it with deliberate design. One discovered the cost of leaving it unanswered.

THE PATTERN

What teams do when leaders are silent about AI

The failure mode in Marisol’s story was structural, not interpersonal. She didn’t withhold information from her team intentionally. She held it back because she believed her AI strategy wasn’t ready to share. During the six months she spent perfecting it, her team built their own version from what they could observe: a platform consolidation, a workflow integration, a hiring pattern that quietly shifted. By the time she presented the strategy at her all-hands, the version her team had written had already replaced the one she was about to deliver.

Every industry where AI is reshaping the work itself reveals this pattern. McKinsey’s January 2025 Superagency in the Workplace study surveyed 3,613 employees and 238 C-suite executives across six countries and found that employees use generative AI at work three times more than their leaders realize. C-suite executives estimated four percent of employees use AI for at least 30 percent of their daily work. Employees self-reported 13 percent. The same study found that 47 percent of employees believe AI will replace 30 percent of their work within a year, against only 20 percent of leaders who believe the same.

Those numbers describe a perception gap, but the gap itself is the diagnostic. When leaders are operating from one understanding of AI’s reach inside their organization, and employees are operating from another, the silence between the two is where the cultural honesty failure lives. Teams aren’t waiting for permission to use AI. They’re using it. What they’re waiting for is leadership to acknowledge what’s happening, what it means, and what comes next.

On the Cultural Honesty Map, this is the Inferred quadrant: leaders silent on the substance, teams already in motion. The team is constructing the future their leader has not yet named, from the operational signals available to them. The team writes the strategy. The leader is no longer the author of it.

THE BREAKDOWN

How silence reveals major decisions

Google signed a contract with the Pentagon to provide cloud and AI infrastructure for military operations. Employees learned about it through media reports. According to internal accounts published by Fortune in May 2026, the company never clearly communicated to employees that it was negotiating the contract or that it had signed one. Leadership’s closest response to the resulting concern was an internal memo about responsible AI and military partnerships that did not explicitly acknowledge the agreement.

A Google researcher quoted in the Fortune piece described the lack of transparency as “pretty indicting” and said the deal felt as if it had been done “in the dark.” The internal pushback that historically defined Google’s response to military contracts, most notably the 2018 employee revolt that killed Project Maven, was largely absent this time. The absence wasn’t agreement. It was the simpler fact that the company never gave employees the option to push back against the decision.

The breakdown wasn’t the contract itself. The breakdown was the company’s choice to let employees discover a consequential decision through external reporting, and to respond with adjacent language instead of direct acknowledgment. The cultural honesty failure was not that Google made a controversial decision. It was that leadership treated the decision as something communicated through absence, which is the most expensive form of silence a leader can choose.

When leaders communicate a consequential AI decision through implication rather than direct statement, it does not stay implicit. It becomes the dominant narrative. By the time leadership decides to address it directly, employees have already accepted a version of the decision that the leader did not write and cannot easily revise.

THE NAMED MODEL

Two companies, two cultural honesty moves

In May 2026, Cloudflare announced a workforce reduction of more than 1,100 employees. The announcement came as a blog post from co-founders Matthew Prince and Michelle Zatlyn, titled “Building for the Future,” published the same day every affected employee received a personal email from one of the two founders.

The post was specific in three ways that mattered. It named the cause: Cloudflare’s internal AI usage had increased by more than 600 percent in the prior three months, with employees across functions running thousands of AI agent sessions daily, and the company’s existing organizational structure no longer aligned with how employees actually did the work. It named the responsibility: Prince and Zatlyn wrote that the decision was theirs to own as founders, not something managers should communicate. It named the protection: severance packages that included full base pay through the end of the year, healthcare coverage through year-end for US employees, and equity vesting extended through August.

Clarity did not ease the transition. Cloudflare faced criticism in industry coverage for the timing of the announcement, which came alongside a strong earnings report. But the cultural honesty move held. Employees who were leaving knew why. Employees who were staying knew what had changed. The story was the company’s to tell, not the press’s.

Klarna made a different cultural honesty move, in a different format. In February 2026, CEO Sebastian Siemiatkowski spoke openly on the 20VC podcast about expecting Klarna’s workforce to shrink from 3,000 to under 2,000 employees by 2030, driven by AI absorbing white-collar work. He named the direction. Then he named what was not changing: the roles built on human connection.

“I have people in Portland talking to Nike. I have people in China talking to Shein. I have people in Amsterdam talking to Adyen,” Siemiatkowski said. “I’m still gonna argue that it’s going to be vital to offer a human connection there.” He opened the same conversation by saying “I want to be honest about the fact that I do think there’s going to be a very big shift.” Cultural honesty was not subtext. It was the move he named first.

Cloudflare and Klarna landed on different sides of the Cultural Honesty Map. Cloudflare made a moment legible through specificity and ownership. Klarna made a direction legible by naming what stayed human even as the headcount shrank. Both moves are versions of the same discipline: leaders making the transition visible while there is still time for the team to be part of it.

For marketing leaders, the equivalent moves are not theoretical. They are: naming the AI shift inside the marketing function before the workflow has fully changed; attaching a specific human owner to the consequences when AI-assisted work fails; and saying out loud what work will remain uniquely human regardless of how fast the tooling improves. These are not policy statements. They are structural decisions about who carries the weight of the transition.

WHERE WE LEAVE MARISOL

The conversation she scheduled for the following week

Marisol brought the Cultural Honesty Map to her team the following Tuesday. Rather than presenting her findings, she asked each person to locate themselves on the map first, in writing, before anyone spoke.

The room came back with answers Marisol had not expected. Most of her team did not place her where she had placed herself. The conversation that followed was the first honest one her team had about what the AI rollout had meant to them. Not the metrics. Not the workflow. The version of the future they had been carrying without language for it.

That is where the discipline of cultural honesty begins: not in the announcement, but in the conversation the silence has already shaped. That conversation is what Part 4 examines.

Here’s what’s coming in May:

Part 1: Marisol’s all-hands and the six months her team had been writing a different story. Published.

Part 2: The Cultural Honesty Map. A diagnostic for locating the gap between what you’ve said and what your team has heard. Published.

Part 3 (this post): What three organizations did with the same cultural honesty question, and what their choices revealed.

Part 4 (next week): Marisol revisits the all-hands with new information. What she’d say differently. What she cannot recover. The one question she cannot yet resolve.

About Kim

Kim Celestre is a strategic advisor and executive coach who helps B2B marketing leaders navigate AI transformation without eroding judgment, trust, or human value. Her work is grounded in AIGP-certified responsible AI expertise, executive coaching, and 25 years of Silicon Valley marketing leadership, including 4 years as a Forrester industry analyst.

Sources

• McKinsey & Company: Superagency in the Workplace: Empowering People to Unlock AI’s Full Potential, Mayer, Yee, Chui, & Roberts (January 28, 2025).

• Fortune: Google’s AI deal with the Pentagon has sparked employee backlash. But don’t expect a repeat of Project Maven, Beatrice Nolan (May 4, 2026).

• Cloudflare: Building for the Future, Matthew Prince and Michelle Zatlyn (May 7, 2026).

• Fortune: Klarna’s CEO agrees with Dario Amodei. He thinks his white-collar workforce will shrink by a third by 2030, (February 17, 2026).

The morning after

The day after the all-hands, Marisol opened her laptop and pulled up six months of meeting transcripts. She searched for the words she thought she had said. What she found was the language she used to talk about the AI rollout — adoption rates, platform consolidation, workflow integration, Q1 numbers — without ever saying, out loud, what any of it meant for the people doing the work.

Her team spent the same six months searching for the missing words. By the time Marisol stood in front of them with her AI-Forward vision deck, they weren’t interpreting what she said. They were interpreting what she still was not saying. The gap between those two things is what the Cultural Honesty Map is designed to measure.

The Cultural Honesty Map

Cultural honesty is the discipline of being transparent about how AI decisions are made, where accountability sits when AI is wrong, and what happens when systems fail. It is also the discipline of making the emotional transition visible; naming what is ending, what is evolving, and what remains uniquely human.

Most leaders frame cultural honesty as a communication strategy. They think the work is finding the right words, the right cadence, and the right venue. The Cultural Honesty Map starts from a different premise. The work is not what a leader says in any one meeting. The work is the cumulative meaning a team is building from everything a leader has said and everything a leader has not.

The map locates a leader and her team on two dimensions: what the leader said about the AI transition, and what the team heard. The gap between them is where most cultural honesty failures live.

Read more

The deck her team waited for

Marisol opened the all-hands with the slide she had labored over most. A single line, centered in the brand’s deep purple, read:

Where Marketing Goes Next: Our AI-Forward Operating Model.

She had built the deck over four weekends, working in the quiet hours while her organization, forty-three people at a Series D B2B SaaS company, waited for a signal. She had waited for the right moment: strong Q1 numbers and a CFO who was finally using the phrase compounding returns.

She presented for thirty-eight minutes. She thought she was being responsible. While she was solving for the business by waiting for perfect data, her team was solving for safety by assuming the worst. When she finally opened the floor, the questions hit the nerves:

• Does AI-Forward mean Human-Optional?

• Is efficiency a proxy for headcount reduction?

• Whose judgment is being replaced first?

Marisol leaned on her talking points. She said no decisions had been made. In her mind, she was being factually accurate. In the vacuum of her six-month silence, accuracy felt like an exit strategy.

By the next morning, a senior manager Marisol had been quietly developing for a director role requested a private fifteen minutes. His opening sentence reflected her intuition about how the presentation landed:

I want to understand what I should be telling my team, because right now they think the all-hands was the warning before the layoff.

The strategy she finally shared, and the version her team wrote without her.

Marisol hadn’t been hiding the strategy; she had simply been waiting until it was ready. The platform consolidation came first, in October. The workflow integrations came second, through January and February. The vision deck was the third, designed to explain why the first two had happened. She built it carefully because she believed her team deserved a fully formed version, not a half-formed one she would have to walk back later.

She did not account for the six months between move two and move three. In that silence, her team did what people do when their leader goes quiet during a major change. They built their own theory of the case from the only signal available: the operational patterns Marisol kept executing without explaining.

By the time she stood in front of them with the vision deck, her team had already set the theory. The platform consolidation was the prelude. The workflow automation was the rehearsal. The all-hands was the announcement they had been bracing for since the consolidation went live. Marisol’s deck did not introduce a strategy to the team; it confirmed the one they had already written: that the company was preparing to reduce the marketing org and that the AI-forward operating model was the framework that would justify it.

The cost of the honesty gap

The pattern Marisol walked into is documented. Edelman’s 2025 Trust Barometer found that employees who feel secure in their jobs because of AI are twice as likely to embrace its growing use, at fifty percent, than employees who feel their job security is decreasing, at twenty-one percent. By staying silent to avoid alarmist talk, Marisol triggered the resistance she was trying to prevent.

The silence has a second cost: leaders lose visibility into what their teams are actually doing. McKinsey’s January 2025 Superagency in the Workplace study surveyed 3,613 employees and 238 C-suite executives and found that employees use generative AI three times more than their leaders realize. C-suite leaders estimated that four percent of employees use AI for thirty percent or more of their daily work. Employees self-reported thirteen percent. The same study found employees were twice as likely as their leaders to believe AI would replace at least thirty percent of their work within the next year. Marisol’s team had been making decisions about their own future inside that gap. The all-hands did not close it.

Why a polished strategy cannot undo six months of inferred ones

The failure was not the all-hands; that was simply where the failure showed its face. The actual failure was the six months of operational decisions Marisol made without narration, each one defensible on its own, but indistinguishable from a layoff plan when viewed from the outside.

She consolidated four tools into one. She integrated workflows. She tracked adoption metrics weekly. What she did not do, in any of the venues available to her, was explain out loud what this meant for the work itself. She didn’t name what was ending. She didn’t name what was changing shape. Crucially, she didn’t name what she would never ask AI to do for them.

Two years in the role had given her something dangerous: operational confidence. She had quietly removed certain conversations from her calendar because she trusted her team to follow her. She stopped explaining her reasoning. She stopped checking in on the unspoken because she assumed nothing was unspoken between them. That trust became an assumption, and the assumption absorbed the questions her team needed her to answer in language they could repeat to each other in the Slack channels she did not see.

Morale had thinned over the prior six weeks, slowly enough that it did not show up in the engagement survey that closed in March. Output had not dropped, but the energy underneath the output had. Two strong contributors had stopped volunteering for cross-functional projects. One had quietly started interviewing. The senior manager had held the information back because he did not know how to bring it up without sounding alarmist. The all-hands gave him the opening to say it.

Where we leave Marisol

The polish of the deck made the gap worse, not better. A leader who waits six months to present a strategy, and then arrives with a fully built operating model, communicates something her team will read whether she intends it or not: that she has already made the decisions, set the pillars, and mapped the roles without them.

A draft strategy invites input. A finished strategy, presented this late in a transformation, reads like the announcement her team had already been bracing for.

Marisol ends her week sitting with a question her confidence kept off her calendar: How do you lead a team that has already moved on without you?

She doesn’t have a framework for seeing that yet.

She will by the end of the month.

Coming in May:

Part 2: The diagnostic tool Marisol needs before her next all-hands. Paid subscribers receive the full one-pager.

Part 3: Stories from marketing leaders who navigated the same silence differently, and what each choice cost or protected.

Part 4: Marisol revisits the all-hands. What she would say differently. What she cannot recover.

Sources:

• Edelman (2025). 2025 Trust Barometer Flash Poll: Trust and Artificial Intelligence at a Crossroads. Edelman Trust Institute. edelman.com

• Mayer, H., Yee, L., Chui, M., & Roberts, R. (2025). Superagency in the Workplace: Empowering people to unlock AI’s full potential. McKinsey & Company. January 28, 2025. mckinsey.com

Recently, Reuters and CNBC reported that Meta is capturing employee keystrokes and mouse clicks across hundreds of websites, including Google, LinkedIn, Slack, and GitHub. This “Model Capability Initiative” aims to gather training data for the agentic AI systems—software capable of autonomous reasoning—that Meta is racing to build. Simultaneously, Fortune reported that the company is preparing to cut up to 20% of its workforce, with layoffs potentially starting in May. Both announcements arrived in the same quarter.

Employees described the program as “dystopian.” Whether that description is fair matters less than the speed of the reaction. The Meta workforce didn’t wait for leadership to provide context; they connected the dots themselves and ran with the most alarming conclusion.

The interpretation

When a company announces a consequential decision without providing context, the workforce doesn’t pause; it interprets. These interpretations compound, circulate, and settle into a shared narrative that becomes nearly impossible to unwind. At Meta, two facts became public within the same news cycle: The company is collecting granular workflow data from its employees, and it is preparing to cut roughly one in five of them. The official framing addressed the data collection. The employees connected the dots.

The interpretation spreading inside and outside Meta is that this isn’t a productivity initiative or a generic training effort. It is an extraction of knowledge. Employees suspect the company is capturing how senior engineers debug and how researchers navigate tradeoffs because that is the content AI cannot yet reproduce. The implication is that the people whose judgment is being captured are the same people the company is preparing to let go. The company hasn’t confirmed or refuted the plan. The workforce is reading the silence.

This is a cultural honesty failure, not a communications failure. Cultural honesty exists when a company’s story and its actions match so closely that employees don’t have to choose what to believe. When a gap opens, the workforce fills in the blanks. Like a game of Mad Libs, the version they write is almost always worse than reality. Once employees write this “missing half” of the story, it becomes the actual narrative. No subsequent clarification from leadership can easily overwrite a version that has already spread through the ranks.

The warning for marketing leaders

Meta is the visible case because of its scale, but this pattern isn’t unique. Any company that deploys automated AI tools while cutting staff or squeezing margins creates a similar silence. I have watched smaller versions of this play out in executive conversations over the past several months. In every case, the company shared facts but failed to explain what those facts meant.

The cost of this silence is high. Senior contributors stop speaking in meetings, Slack channels go quiet, and honest feedback vanishes. People replace candor with safe, performative work. The very human judgment that AI was supposed to augment disappears instead.

The warning is loud. When a company layers AI into operational decisions, transparency is no longer a luxury. It is the only thing that stops employees from reaching conclusions the company will eventually have to live with. Companies that cannot name what they are doing, why they are doing it, and what it means for their people are borrowing trust they cannot pay back.

Sources

• Reuters / CNBC, April 22, 2026. “Meta tracks employee usage on Google, LinkedIn AI training project.” cnbc.com

• Fortune, April 21, 2026. “Meta will start tracking employees’ screens and keystrokes to train AI tools.” fortune.com

• Gartner press release, October 23, 2023. “Gartner Survey Finds 83% of HR Leaders Are Expected to Do More Now Compared to Three Years Ago.” gartner.com

• Harvard Business Review, February 20, 2024. “Surveilling Employees Erodes Trust, and Puts Managers in a Bind.” Thiel, McClean, Harvey, and Prince. hbr.org

Each month, this series follows a fictional composite leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented, but the failure modes are not.

This is the final post in a four-part series following Lena, a composite VP of Marketing at a publicly traded healthcare SaaS company, through the consequences of a restructuring decision that looked right on every metric available. Each post stands on its own. This week: what she changed, what she couldn’t recover, and the conversation she’s been avoiding.

WHAT CHANGED

The session that reframed the work

Lena didn’t open the workshop with the assessment tool. She opened it with a question: What makes this team irreplaceable?

The room was quiet for a moment. Then her content lead said, “buyer fluency”. Her campaign manager said, “the ability to read a healthcare audience’s skepticism”. A junior marketer said she wasn’t sure she’d developed enough expertise to answer the question. That last response stayed with Lena.

The conversation that followed was the first honest one the team had about what AI changed in their day-to-day work, not operationally, but in terms of what they were being asked to learn. Lena brought on the new junior hires for content production. But they didn’t build the domain understanding that made production meaningful.

Lena used the Human Strengths Protection Map to give the conversation structure. The team worked through the eight capabilities together, identifying where expertise existed, where it thinned, and where the restructuring impacted its development. By the end of the session, each person named one strength they wanted to build and one way Lena could support their development.

This visual is drawn from the Five Disciplines framework. Paid subscribers receive the full Human Strengths Protection Map — a one-page assessment tool for identifying which capabilities your team needs to protect and develop before AI reshapes the work.

The session delivered something more durable than a governance process: a team that understood what it was trying to protect, and a leader who made visible commitments about how she would help them do it.

Two weeks later, one of the junior marketers flagged a case study draft before it reached final review. The positioning implied a clinical outcome that the product couldn’t deliver. The marketer caught it because she knew the question mattered, not because anyone told her it did.

WHAT SHE COULDN’T RECOVER

The cost of rebuilding from scratch

In March, Lena brought in a fractional healthcare content specialist for a three-month engagement. The scope was deliberate: not production support, but knowledge transfer. The specialist sat in on buyer conversations, debriefed the junior team afterward, and documented the judgment calls the original specialist made but didn’t record.

It was the right structural decision. It was also slower and more expensive than retaining the specialist who was laid off during the restructure. Lena struggled to explain this to her CFO without sounding like she was relitigating a closed decision.

The three enterprise deals that stalled in Q1 were still in motion. Two moved deeper into the evaluation stage. Lena’s team remained in contention, but she had no way to measure whether the relationship was genuinely recoverable or whether the competitor being evaluated had already established the trust that would eventually close the deal. Her pipeline reports tracked stage and deal velocity, but there was no metric to track a buyer’s confidence in the team’s expertise.

That was the cost of restructuring for efficiency. Now she had to rebuild her team from the outside in.

WHAT REMAINS UNRESOLVED

The conversation she’s been avoiding

By the end of April, the team had a clearer sense of what they were trying to develop and a structural path for doing it. The fractional specialist was three weeks into the engagement. The junior marketer who flagged the case study started asking pointed questions in sprint planning. These were big changes, and they happened faster than Lena expected.

What hadn’t changed was what Lena said out loud about the decision that made all of this necessary.

She hadn’t told her team that the October restructuring was optimized for efficiency at the cost of lost domain expertise. She hadn’t shared that with her CFO, who approved the layoffs. She hadn’t shared it with her CMO, who assumed all was well based on the performance metrics.

She knew what the restructuring cost. The team knew it too, through the daily friction of doing work without the deep expertise to do it well. But neither side addressed this in the same room at the same time.

That is where Discipline #3 reaches its limit. The Human Strengths Protection Map gives a leader the language to see what’s at risk. Running the session gives a team the structure to name the strengths they need. But these actions don’t require a leader to stand in front of the people who absorbed the consequences of a bad decision and say what she would have done differently.

Lena knows what the restructuring cost her team. She has yet to say this out loud, to them or to the leadership that approved her decision.

May’s discipline starts with a different leader facing the same question: what does it cost to say the truth out loud?

Thank you for following Lena’s story through April. The EQ in Action series continues in May with Discipline #4: Lead with Cultural Honesty.

If this series has been useful, share it with a marketing leader navigating the same terrain.

Each month, this series follows a fictional leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented, but the failure modes are not. This month’s real-world examples — the University of Bath research, Deloitte Australia, and Morgan Stanley — are drawn from documented public reporting and peer-reviewed research.

Last week, Lena ran the Human Strengths Protection Map. The gaps she found weren’t hidden; they were just unnamed. She wasn’t alone in needing that clarity. These organizations confronted the same gaps, some by deliberate design and some after a consequence made it visible.

THE PATTERN

What breaks before anyone names it

The failure mode in Lena’s story was quiet by design. No single decision triggered it. No alarm went off when the senior specialist left with eight years of domain knowledge. The marketing engine looked healthy, even after the intuition that powered it was unplugged. The gap between what the team produced and what the team understood grew slowly, invisibly, until a buyer conversation and a stalled deal made it visible.

This pattern is not unique to Lena’s healthcare SaaS company. It’s common across every industry where AI efficiency models are applied to knowledge work. What made it difficult to catch was that the knowledge loss wasn’t visible in the metrics leaders tracked. It lived in the judgment calls that happened before content shipped, the ones no workflow captured and no dashboard measured.

Research published in the Human Resource Management Journal in February 2026 named this pattern precisely. A team at the University of Bath School of Management identified three forms of knowledge that AI is fundamentally incompatible with: embodied knowledge, developed through hands-on practice and real-world experience; encultured knowledge, the understanding of organizational culture and unwritten norms built through proximity and observation; and embrained knowledge, the analytical judgment and problem-solving capacity developed through years of applied expertise. “If people begin outsourcing thinking, decision-making, or interpretation to AI systems,” the researchers warned, “These critical forms of knowledge wither over time and create a dangerous dependency that could possibly compromise an organization or a company’s profitability.”

On the Human Strengths Protection Map, we identify the specific manifestation of this: Contextual Judgment. This is the hard-won wisdom required to decide when a situation is truly novel, and the existing data is dangerously incomplete.

This is what Lena lost — not output volume, but the contextual judgment her specialist carried, and the judgment that shaped every message before it went out.

THE BREAKDOWN

When claims oversight disappeared from the workflow

Australia’s Department of Employment and Workplace Relations commissioned Deloitte to conduct an independent audit of a government welfare compliance system, a contract valued at AU$440,000. When the 237-page report was published on the department’s website in July 2025, it did not disclose that Azure OpenAI GPT-4o was used to produce parts of it.

A University of Sydney health law researcher, Dr. Chris Rudge, reviewed the published report and flagged more than 20 errors. References pointed to academic papers that didn’t exist, and a quote attributed to a federal court judge had been fabricated. When Deloitte investigated, the firm confirmed that the footnotes and references were incorrect, issued a corrected version of the report, and refunded the final installment of the payment to the government. This consequence became a matter of public record.

The incident revealed that the technology failure was secondary to a more fundamental breakdown in claims oversight. The organization asserted claims in a document that would influence public policy, yet no human owner assumed accountability for their accuracy before the report was finalized. AI produced content that appeared superficially credible, but it was published without being vetted by anyone with the contextual judgment required to spot the fabrications.

For marketing leaders, this isn't just a cautionary tale about government audits; it’s a preview of the accountability gap. When AI-assisted volume outpaces human verification, the claims oversight muscle begins to atrophy. This capability—one of eight on the Human Strengths Protection Map—is the organizational habit of taking responsibility for every word published under the company’s name. In Deloitte’s case, a researcher caught the failure; in a marketing organization, the gap is usually discovered by a buyer or a competitor only after the damage is done.

THE AUGMENTATION MODEL

How Morgan Stanley kept humans as the judgment owners

Morgan Stanley’s deployment of AskResearchGPT offered a design model built around the opposite assumption: that the most valuable human strengths are worth protecting explicitly, not accidentally.

AskResearchGPT accelerated the retrieval and summarization of Morgan Stanley’s internal research library. Analysts surfaced relevant prior work faster, synthesized across larger bodies of research, and reduced the time spent searching for information that already existed inside the organization. The efficiency gain was real and documented.

This system reduced friction in the research process while humans retained the expertise required to apply that research with sound judgment. Human analysts remained accountable for the judgment calls: the interpretation, the client guidance, and the narrative that translated research into an actionable recommendation for a client.

The design decision Morgan Stanley made was the same one Lena’s team needed before the restructuring: a conscious determination about where AI would assist and where humans would own the outcome. It wasn’t a policy statement; it was a structural choice baked into the workflow long before deployment.

For marketing leaders, the equivalent scenario is a content operation where AI accelerates the production layer — first drafts, structural outlines, content variants — while humans retain explicit ownership of the judgment layer: positioning decisions, claims accountability, competitive framing, and the interpretation of what market intelligence means for a specific buyer in a specific moment. That separation requires the same deliberate design Morgan Stanley applied before the workflow was deployed, not negotiated after a mistake surfaced.

WHERE WE LEAVE LENA

The session Lena runs the following week

Lena brought the Human Strengths Protection Map to her team on a Thursday afternoon. Rather than presenting her results, she asked each team member to run through the assessment themselves.

The conversation that followed was the first honest one her team had about the real cost of the restructuring. Not the headcount. Not the output metrics. The human strength underneath both.

Two truths emerged in the room. For months, the team watched their contextual judgment erode in real-time, but they lacked two essential tools: a vocabulary to name the loss and the psychological safety to report it.

That is where the discipline of protecting human strengths begins: not in the assessment, but in the conversation the assessment makes possible.

That conversation is what Part 4 examines.

Here’s what’s coming in April:

Part 1: Lena’s situation and the human capability gap hiding inside her efficiency model. Published.

Part 2: The Human Strengths Protection Map — the assessment tool for identifying which marketing capabilities require active protection from AI displacement. Published.

Part 3 (this post): What the research reveals about AI and expertise erosion, and what the organizations that got the design right built instead.

Part 4 (next week): Lena revisits the restructuring decision with new information. What she’d change, what she can’t recover, and the one question still unresolved.

Sources

• University of Bath School of Management / Human Resource Management Journal: “On the Dangers of Large-Language Model Mediated Learning for Human Capital,” Professor Dirk Lindebaum et al. (February 2026)

• The Guardian / Fortune: Deloitte Australia government report — AI-generated errors, partial refund (October 2025)

• Morgan Stanley: AskResearchGPT press release

Most marketing leaders don’t deliberately eliminate human strengths. They optimize for efficiency, adopt AI tools, and make headcount decisions that look sound across all metrics. The human strengths erode quietly. The cost surfaces later: in a stalled deal, a positioning drift, a buyer conversation nobody on the team can hold.

This is the assessment Lena needed before she restructured her team. It works for any marketing leader navigating AI transformation, whether or not a restructuring is planned.

Each month, this series follows a fictional composite leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented. The failure modes are not.

THE FRAMEWORK

The map she needed before the audit

Lena’s channel audit measured the right things: reach, engagement, content volume, and channel distribution. It told her everything was working. What it couldn’t measure was the human capability underneath the workflow: the judgment, the fluency, the relational intelligence that made the content credible when a buyer pushed back.

That’s the gap the Human Strengths Protection Map is designed to close.

The map works as a pre-decision assessment. A marketing leader runs each of their team’s core capabilities through three columns: what the capability requires from a human, whether AI adoption has begun eroding it, and what a concrete protection action looks like. The output is not a score. It is a prioritized list of what to protect, reskill, or redesign before anything changes.

One thing this tool is not: a layoff planning guide. Most leaders who need it aren’t planning to cut anyone. They are adopting AI tools, accelerating workflows, and watching their teams produce more than ever. What is quietly eroding underneath stays invisible until a business consequence names it. The Human Strengths Protection Map is a reskilling and redesign tool. Use it before something changes, not after.

THE ASSESSMENT

Eight capabilities. Three questions each.

The map covers eight human strengths AI adoption puts at risk in any B2B marketing team. For each one, ask whether your team currently has the capability, whether AI has begun displacing it, and what you will do to protect it.

Here is a preview of the first three capabilities.

Buyer fluency

The empathy to understand how buyers think, feel, and decide — not only what they need. This is the capability Lena’s specialist carried and the junior hires hadn’t yet developed. It doesn’t live in a content brief or a persona document. It lives in the accumulated experience of sitting across from buyers and learning how they process risk, evaluate vendors, and decide who they trust.

Risk signal: Direct buyer conversations have decreased since AI tools entered the workflow.

Protection action: Conduct at least one unassisted buyer conversation per quarter per senior team member.

Competitive discernment

The discernment to position against competitors with confidence and without creating brand or legal exposure. AI can generate competitive comparisons faster than any human team. It cannot read the competitive landscape, assess partner sensitivities, or judge whether a positioning move will hold up when a buyer pushes back in a late-stage conversation.

Risk signal: Competitive positioning is generated by AI and enters workflows without a human review checkpoint.

Protection action: Require human sign-off on all competitive positioning before it moves downstream.

Claims oversight

Being accountable for what the organization asserts in the market. In a high-volume AI content operation, claims proliferate faster than anyone can track them. The human capability at risk here is the organizational habit of taking responsibility for what goes out under the company’s name.

Risk signal: AI-generated content publishes without a human verifying the underlying claim.

Protection action: Designate a named owner to review claims in every content type that touches product, legal, or compliance territory.

Read more

Each month, this series follows a fictional composite leader through a real professional challenge. The situations are composites drawn from patterns I observe across B2B marketing teams in AI transformation. The names and companies are invented. The failure modes are not.

The audit came back clean. The problem didn’t.

Lena inherited a marketing team built for a different era.

Nine months into her role as VP of Marketing at a mid-size, publicly traded healthcare SaaS company, she was still calibrating what she had taken on. The headcount model was designed before AI-assisted workflows existed. Two people were dedicated almost entirely to content volume, drafting, editing, and versioning messaging across a complex buyer landscape that included provider organizations, health systems, and value-based care networks.

The team delivered meticulous work. By every efficiency metric her CFO tracked, it was also expensive.

So Lena restructured.

She consolidated two roles into one, eliminated the senior healthcare content specialist position, and hired two junior marketers who could operate an AI-assisted workflow at pace. She’d run this math before, at a high-growth B2B tech company where AI-accelerated content delivered a genuine competitive advantage. She built a solid business case, and the CFO approved it in a week.

Output volume stabilized within six weeks. The dashboard looked fine for five months.

Then her sales leader put a single slide in front of her at the quarterly business review: three enterprise deals in the same provider vertical, all stalled at the solution overview stage. Buyers had gone quiet after the initial engagement. A smaller competitor consistently outperformed Lena’s team in late-stage conversations. Not on features. Not on pricing. On fluency.

Lena commissioned a channel audit. It came back clean.

THE SITUATION

The expertise that never made it into the workflow

The senior healthcare content specialist Lena eliminated spent eight years learning how provider organizations evaluate workflow change, where the language of clinical operations diverges from the language of enterprise software, and which claims create friction in a room full of compliance-aware buyers. None of that knowledge was documented. It lived in the judgment calls she made every time she shaped a message, softened a framing, or pushed back on positioning that would land wrong with a risk-averse healthcare buyer.

The junior marketers who replaced her were capable and fast. They learned the AI workflow quickly. No one remained to teach them the domain underneath the workflow.

That shortcoming doesn’t appear on a productivity dashboard — it appears in a sales call.

WHY THIS MATTERS NOW

The capability AI efficiency models quietly erase

The pattern Lena walked into is documented and accelerating. In October 2025, Gartner predicted that by 2030, half of enterprises will face irreversible skill shortages in critical roles due to GenAI skills erosion. Organizations are losing more than output quality. They are losing the conditions under which expertise gets built and transferred.

Gartner’s follow-on prediction sharpens that insight: through 2026, atrophy of critical-thinking skills due to GenAI use will push 50% of global organizations to require AI-free skills assessments. The concern is not that AI produces weak output. The concern is that sustained AI use, without deliberate protection of the human judgment underneath it, erodes the expertise that made the output credible in the first place.

Lena hadn’t reduced output — she restructured away the conditions that made it trustworthy to a healthcare buyer.

The AHA’s 2026 Health Care Workforce Scan identifies this dynamic explicitly in the healthcare context. As AI tools are embedded into healthcare workflows, organizations that fail to protect mentorship structures and redesigned education pathways remove the scaffolding where domain expertise becomes transferable. What holds true for clinical teams holds equally true for the marketing teams selling to them.

THE GAP

The competitive edge her dashboard couldn’t see

The channel audit told Lena nothing was wrong with her distribution. What it couldn’t measure was her team’s eroding domain fluency.

Forrester’s 2026 Buyer Insights research across 22 industries found that buyers in regulated sectors, including healthcare, rank expertise and trust above operational efficiency and price as purchase drivers — a pattern distinct from buyers in less regulated markets. Healthcare buyers don’t evaluate vendor content in isolation. They evaluate it against what they know about their own environment, and they notice when a vendor’s team doesn’t share that knowledge. That recognition rarely surfaces in a feedback form. It surfaces in a deal that quietly loses momentum.

Lena’s competitor ran a smaller content operation whose team could go deeper than the content when the room required it.

PwC’s 2026 health industries board survey found that nearly half of healthcare industry directors say management provides inadequate information on the risks associated with AI use inside their organizations. The board pressure pushing Lena toward efficiency was real. What the board wasn’t getting was the risk profile of an efficiency model that treated domain expertise as overhead. Lena hadn’t surfaced it.

WHERE WE LEAVE LENA

The question she still hasn’t asked herself

Lena has a clean audit, a stalled pipeline, and a structural question she hasn’t fully asked herself yet: not where the content is going, but what domain fluency her team lost when she restructured.

She restructured for efficiency, and she got it. What she optimized away was the institutional knowledge her buyers were looking for at exactly the moment the deal was in play.

She doesn’t have a framework for seeing that yet.

She will by the end of the month.

Here’s what’s coming in April:

Part 1 (this post): Lena’s situation and the human capability gap hiding inside her efficiency model.

Part 2: The tool Lena needs before she restructures again — the Human Strengths Protection Map, a framework for identifying which marketing capabilities require active protection from AI displacement. Paid subscribers receive the full downloadable one-pager.

Part 3: What other marketing leaders learned when they tried to protect human strengths — and what broke before they got it right.

Part 4: Lena revisits the restructuring decision with new information. What she’d change, what she can’t recover, and the one question still unresolved.

Sources

• Gartner: AI Revolution and Cost Pressures Drive Top Talent Acquisition Trends for 2026 (October 2025) — gartner.com/en/newsroom/press-releases/2025-10-07-gartner-says-ai-revolution-and-cost-pressures-are-two-forces-driving-the-top-four-trends-for-talent-acquisition-in-2026

• Gartner: Top Predictions for IT Organizations and Users in 2026 and Beyond (October 2025) — gartner.com/en/newsroom/press-releases/2025-10-21-gartner-unveils-top-predictions-for-it-organizations-and-users-in-2026-and-beyond

• Forrester: 2026 Buyer Insights: Industries (December 2025) — forrester.com/report/2026-buyer-insights-industries/RES186880

• AHA: 2026 Health Care Workforce Scan Executive Summary (December 2025) — aha.org/system/files/media/file/2025/12/2026-Health-Care-Workforce-Scan-Executive-Summary.pdf

• PwC: 2026 Corporate Governance Trends in Health Industries (February 2026) — pwc.com/us/en/services/governance-insights-center/library/annual-corporate-directors-survey/health-industries.html

Intelligently Human publishes every Tuesday, Wednesday, and Thursday. Subscribe to follow Lena's story through April — and get the Human Strengths Protection Map when it drops next week.

This is the final post in a four-part series following Maya, a composite VP of Marketing, navigating governance failures that arise when AI content workflows scale faster than judgment boundaries. Each post stands on its own. This week: what changed after she drew the line.

Three weeks after the competitor’s response to inaccurate competitive comparison content slowed a late-stage deal, Maya noticed a change in how work moved through her team.

The workflow itself remained largely intact; Campaign timelines stayed on track, and performance dashboards continued to indicate stability. The noticeable change appeared in the rhythm of decision-making. Questions surfaced earlier in the content production process. Legal partners reviewed claims before messaging reached final approval. Sales leaders began asking how marketing classified competitive positioning before using it in active buyer conversations.

The underlying system stayed the same, but visibility sharpened. Decision authority, once embedded quietly inside production steps, became an explicit leadership concern.

What Changed

After applying the Judgment Boundary Matrix, Maya introduced a classification checkpoint at the start of every externally facing content initiative.

Her team began evaluating messaging through two practical considerations: 1) the consequences of an inaccurate claim and 2) the degree of contextual judgment required to assess risk. They immediately moved competitive comparison content into a category requiring human approval. AI systems continued to support drafting content, but leaders assumed responsibility for publication judgment calls.

The team documented approval thresholds, clarified escalation ownership, and distinguished between permissions for drafting and permissions for distributing content externally. None of these adjustments required new technology. They required agreement about who would carry accountability as exposure increased.

This realignment altered how responsibility manifested in existing workflows.

What Became Harder

The first impact of establishing judgment boundaries appeared in production speed. Content that had previously cruised from draft to publication within hours now paused at each stage for deliberation. Teams now debated classification boundaries, occasionally escalating decisions that later proved routine. Managers recalibrated their tolerance for uncertainty while sales leaders continued to push for rapid responses when live deals were at stake. The team struggled with the slower pace.

Workflows that once felt efficient now felt heavier. Individual contributors questioned whether leadership overcorrected, and managers struggled to distinguish high-impact messaging from routine execution. Governance clarity introduced decision fatigue before it produced confidence.

These tensions reflected a transition from implicit judgment to explicit oversight, forcing the organization to confront trade-offs previously hidden.

What Became Easier

Over time, positive effects emerged. Public corrections became less frequent, and discussions about messaging gained depth. Cross-functional conversations pivoted from reactive problem-solving to earlier anticipation of potential consequences. Legal partners engaged more constructively, intervening before vulnerabilities reached the market rather than after.

Accountability also became easier to trace. When teams questioned a claim or positioning choice, they could quickly identify who had made the call and under what assumptions. Escalation processes felt more purposeful and less political. Exposure didn’t disappear, but leaders recognized it sooner and responded with greater coordination.

The organization began to treat governance less as a constraint and more as a mechanism to improve decision quality.

Operational Integration

As Maya continued refining governance in competitive messaging workflows, she noticed similar ambiguity in other areas of marketing execution. Customer segmentation models operated with limited human oversight. Campaign systems reallocated budgets and influenced buyer perception without a human in the loop. Meanwhile, automated partner outreach raised questions about authorization boundaries that had never been formally defined.

Addressing one area of vulnerability revealed others that had previously remained invisible.

Rather than launching a comprehensive governance initiative, Maya focused on targeted adjustments. Her leadership team began defining specific publication risk triggers, clarifying escalation ownership in customer-facing communication, and reviewing selected AI-enabled workflows with legal and compliance partners. These actions did not eliminate uncertainty, but they improved the organization’s ability to recognize emerging consequences before they escalated.

Governance maturity developed gradually through operational practice rather than policy declarations.

What Remains Unresolved

Consequences from the original incident continued to surface. Buyers raised credibility concerns in conversations with sales, and internal confidence remained low. Market perception shifted slowly, reminding leadership that reputational effects often outlast process improvements.

At the same time, governance clarity exposed new tensions. As decision authority became more explicit in competitive content workflows, leaders began questioning how much oversight other automated systems required. Each improvement revealed additional areas where judgment boundaries remained undefined.

For Maya, the experience reinforced a difficult but practical realization. Establishing judgment boundaries did not remove exposure. It reshaped how the organization recognized and managed it.

Greater clarity improved decision quality. It also increased leadership responsibility for the outcomes that followed.

This is the third post in a four-part series on judgment boundaries in AI-assisted marketing. Each post stands on its own. In Week 1, Maya’s competitive comparison content surfaced on LinkedIn before her team knew it was live. In Week 2, the Judgment Boundary Matrix identified the governance gap that enabled it. This week: four incidents from other industries that show the same structural failure at different scales.

The competitor’s response to the inaccurate content went viral — first publicly, then internally. Sales leaders began forwarding screenshots. A late-stage pipeline conversation halted. What had felt like routine execution was now a reputational conversation unfolding in real time.

Maya’s team had built an AI-assisted workflow for competitive comparison content, and it was working brilliantly. The workflow shortened drafting cycles, speeding publishing cadence. This automated process they deployed felt operational rather than strategic. Maya assumed the risk of using it was minimal.

She was wrong. The market quickly reacted to the published content. And not in Maya’s favor.

Working through the Judgment Boundary Matrix last week reframed the incident. The issue was not only content accuracy. It was also decision ownership. The workflow treated competitive comparison content as low-stakes production. In practice, it carried brand, legal, and revenue exposure. A high-impact decision had moved through a low-friction system. undetected.

This week, Maya isn’t trying to resolve the incident. She is trying to understand what allowed it to happen.

Across industries, similar failures are emerging in marketing-adjacent workflows. Contexts differ. Consequences vary. The structural gap across these failures is consistent. Automation increases output, but it can also make decision authority harder to see.

When drafting quietly becomes acting

In November 2025, Zoho CEO Sridhar Vembu received an acquisition pitch from an unnamed startup founder. The email included more than a pitch. It disclosed that another company was already in negotiations and revealed the competing price.

Moments later, a second email arrived, but not from the founder. It came from the founder’s browser AI agent, which had identified the error and transmitted an unsolicited apology to Vembu without the founder’s knowledge or approval.

The governance question this incident raised wasn’t about the original disclosure, which could be attributed to the founder’s judgment. The question was why an AI system held authority to transmit external communications in a negotiation context without a human review gate. The agent had drafting and sending access. No boundary distinguished the two.

Marketing leaders encounter this pressure point more often than they expect, through partner outreach, analyst briefings, and executive ghostwritten content. When AI systems execute inside these workflows, decision authority is easy to overlook. Once an organization transmits a message, it no longer shapes intent internally. It shifts to managing external perception.

That distinction belongs in the workflow before the message goes out, not after.

When a missing review step becomes a vulnerability

In December 2025, Unit 42, Palo Alto Networks’ threat intelligence team, documented a real-world attack designed to exploit an AI-based ad review system. Attackers embedded hidden instructions inside a deceptive advertorial page, tricking the AI reviewer into approving content it would otherwise have rejected.

The attack succeeded because of a governance gap, not a technology failure. The AI system held final decision authority. Human escalation protocols existed but had no defined triggers. There was no threshold for unfamiliar domains, unusual claim patterns, or new advertiser identities that would route a submission to human review.

A human in the approval chain, with a clear escalation trigger, would have caught it.

This is the “it can happen to you” case for marketing leaders managing AI-assisted media or content review. The attack vector was external. The governance gap was internal. When AI holds final authority in brand safety, content review, or media placement, accountability for the outcome must live somewhere. If leadership hasn’t explicitly assigned it to a person, it defaults to the model. And models can be manipulated.

Publication permission is a leadership decision. Wherever that permission lives in the workflow, authority lives there too.

When AI states policy it has no authority to state

In April 2025, a developer contacted Cursor’s customer support after being repeatedly logged out when switching between devices. The response came from an AI agent named Sam, which informed the user that Cursor allowed only one active device per subscription, a core security feature.

No such policy existed.

The fabricated limitation spread across developer communities within hours. Subscription cancellations followed before Cursor’s leadership could intervene. The co-founder eventually apologized on Hacker News, confirmed the user had been refunded, and acknowledged the error.

What the incident exposed was not a model performance failure alone. It was a boundary failure. Cursor’s support system held customer-facing authority over policy communication without a defined limit on what it could assert as fact. The model filled the gap the way models do: confidently, and incorrectly.

Customer-facing authority carries disproportionate consequences in marketing terms. Trust erosion that begins in support interactions surfaces later in retention metrics, campaign response rates, and brand advocacy signals. Recovery extends beyond corrective action into reputational rebuilding.

One boundary — “AI may surface verified policy, not interpret or state it” — would have changed the outcome.

When user permission is treated as platform authorization

In March 2026, a federal judge granted Amazon a preliminary injunction blocking Perplexity’s Comet browser from accessing password-protected sections of Amazon on behalf of users.

Perplexity designed Comet to extend user convenience; Amazon’s platform read it as an unauthorized access violation. The court found that user permission and platform authorization are distinct, and that operating inside a third-party system without platform consent is not a user-rights question; it’s an access question.

Marketing consequences followed quickly. Claims about ecosystem compatibility required revision. Growth narratives tied to distribution partnerships required recalibration. Leadership attention shifted from expansion to defensibility.

For marketing leaders operating in partner-dependent environments, the authorization boundary is worth examining before the workflow is built. It is not only what a user permits. It is what each platform in the distribution chain explicitly authorizes. When AI agents operate inside those systems without that clarity, the exposure is not a performance risk. It is a permission risk.

Where judgment boundaries actually break

Reviewing these incidents side by side, Maya noticed that the public consequences appeared too late for the organizations to correct course. Authority had moved gradually from human judgment to workflow assumption. The market response revealed what had already shifted internally.

Each scenario began with efficiency gains. Workflow friction decreased, output increased, and decision ownership became less visible. Leadership attention stayed anchored to performance indicators while governance assumptions went untested.

Maya’s situation was smaller in scale. It involved a competitive comparison asset, a reactive LinkedIn thread, and a weekend workflow audit. But the architecture of the failure was the same. A workflow had been designed for production efficiency. Decision authority had not been assigned. When the content went live, the process performed exactly as designed.

These incidents are not cautionary tales about AI going rogue. They document what happens when governance assumptions go untested at the point where automation meets external consequence.

What mature marketing teams do before the incident

Teams that avoid similar failures tend to define escalation triggers before automation expands: specific content types, claim categories, or relationship contexts that require human classification before entering the workflow.

They separate drafting from execution in external-facing communication. An AI system that can draft can only draft. One that can send requires a human approval gate for outbound action.

They restrict customer-facing AI to verified information retrieval. Interpretation, policy assertion, and judgment calls stay with the people who hold accountability for the answer.

They treat publication and transmission as leadership decisions at Judgment Boundary Q2 and above, not workflow outcomes.

None of these practices prevents every error. What they do is make accountability visible before errors reach the market.

For Maya, reviewing these incidents reframed her original decision. The workflow had not malfunctioned. It had performed exactly as designed. The design itself lacked a clear authority boundary. Recognizing that distinction is uncomfortable. It is also actionable.

Next week: Maya revisits the decision she made after reclassifying competitive comparison content as a human-authority call. Some risks became easier to manage. Others became more visible. Clarity moves leadership forward. It does not eliminate cost.

Sources

Zoho CEO Sridhar Vembu on X, November 28, 2025 — an unnamed startup founder’s browser AI agent disclosed confidential acquisition details and autonomously sent an apology without the founder’s knowledge. Reported by The Hans India and Business Today.

Unit 42, Palo Alto Networks (December 2025): Real-world indirect prompt injection attack designed to bypass an AI-based ad review system — unit42.paloaltonetworks.com/ai-agent-prompt-injection/

Cursor / Anysphere (April 2025): AI support agent fabricated a one-device subscription policy, triggering cancellations and a public apology from the co-founder. Reported by Fortune, The Register, and CX Today.

Amazon v. Perplexity, U.S. District Court, Northern District of California (March 9, 2026): Preliminary injunction blocking Perplexity’s Comet browser from accessing password-protected Amazon accounts — cnbc.com/2026/03/10/amazon-wins-court-order-to-block-perplexitys-ai-shopping-agent.html

The audit

Maya spent the weekend after the LinkedIn thread doing what most VPs of Marketing do after a public failure: auditing backwards. She pulled every AI-assisted workflow her team ran. Twelve of them.

At first glance, the competitive comparison workflow looked like the others. It had a review step and a quality check, which meant that on paper, the process worked. Several members of her team had already pointed this out in the initial conversations. The system did what it was designed to do.

That explanation held up until Maya looked more closely at what the review step was actually supposed to accomplish.

She realized the workflow included a review step, but it lacked a standard for what review meant for that content category. Her team treated it as a quality check when the situation called for a judgment call. The AI workflow never distinguished between those two things.

The question her workflow never asked

Most AI content workflows ask two questions before they publish: is the content accurate, and is it on brand?

For routine content, those are the right questions. For content that carries brand, legal, or competitive risk, they are incomplete.

The question missing from Maya’s workflow was: Does this decision belong to AI, or to a human?

Without that question, every piece of content moved through the same gate regardless of what was at stake if it was wrong. A blog outline and a competitive positioning claim require very different levels of human oversight. Maya’s process treated them identically.

What her team needed was a way to classify those decisions before the workflow began.

Classification has to happen before review. The review step existed, but the classification standard did not. That distinction turned out to be the difference between a functioning process and one that quietly allowed risk through the system.

A framework for drawing the line

Maya’s team had already built a review step into the workflow. What the process lacked was a classification standard that defined which decisions required human judgment before the content entered the review stage.

The Judgment Boundary Matrix is designed to solve that problem.

The framework gives marketing teams a repeatable way to classify AI-assisted content decisions before they enter the review process. It maps decisions across two factors: how much is at stake if the content is wrong, and how much contextual judgment the decision requires. The intersection of those two dimensions determines who owns the decision.

Use the matrix to classify the decision before the workflow reaches the review stage.

Each quadrant defines a different level of human authority in the workflow.

Read more

By the time Maya saw the LinkedIn thread, the post had 200 reactions and a tagged competitor.

Her CMO sent the screenshot with a single question:

“Did we approve this?”

The CMO’s question arrived with a LinkedIn screenshot attached: a competitive comparison Maya’s team had published through their AI content workflow, now live in a thread with 200 reactions and a tagged competitor.

The claims had been accurate when the workflow was built. They were not accurate when the content was published; No one flagged them for re-review because no one owned that decision.

What her CMO was really asking was whether Maya had a system for knowing which decisions needed a human. And she didn’t have a clear answer.

THE SITUATION

What was working and what it was hiding

Maya is VP of Marketing at a 200-person B2B SaaS company, 18 months into an AI transformation championed by her CMO. She assumed all was well. Her team delivered. Adoption metrics were strong. Workflow documentation was complete. AI usage across content, campaigns, and competitive intelligence became routine.

Maya’s team ran twelve AI-assisted workflows, and competitive-comparison content was among them. The asset had cleared the standard review process. No one questioned it because the AI workflow said it had cleared review, and clearing review had always been enough. That’s what made it a structural problem, not a human one.

WHY THIS MATTERS NOW

Adoption moved fast. Governance didn’t follow.

The pattern Maya walked into isn’t unusual. In a May–June 2025 Gartner survey of 360 IT leaders involved in generative AI rollouts, only 23% reported being very confident in their organization’s ability to manage security and governance when deploying GenAI tools. Over 70% cited regulatory compliance as a top-three challenge.

Adoption outpaced governance. That gap is where the exposure lives.

Gartner projects that by 2028, enterprises will spend more than $30 billion battling misinformation and disinformation, cannibalizing 10% of marketing and cybersecurity budgets combined. That figure reflects what happens when internal content governance doesn’t keep pace with the volume of content. Bad actors are part of the equation. Ungoverned internal workflows are too.

The accountability gap is documented: when AI-generated content causes legal or reputational damage, the liability belongs to the humans and organizations that published it. The tool doesn’t get sued, and the vendor doesn’t answer to the board. The marketing team does.

THE GAP

Designed to fail

Maya’s team didn’t make a careless mistake; They followed the process. What the process didn’t include was a defined point at which a human had to step in and own the judgment call. Research on human-AI decision-making published in Scientific Reports in early 2026 identifies this failure mode. When AI workflows lack explicit intervention triggers, humans shift from active control to passive monitoring and systematically fail to intervene when systems err. The team wasn’t negligent. They were operating exactly as humans do inside workflows that never told them when to stop and decide.

Competitive positioning. Claims about named competitors. Content that could attract legal scrutiny or go viral for the wrong reasons.

These are decisions, not tasks.

Maya’s workflow treated them as tasks.

The boundary was never defined, so no one crossed it. It simply didn’t exist.

WHERE WE LEAVE MAYA

The unanswered question

Maya knows the asset was wrong. She knows how it got published.

What she doesn’t have is a system for knowing where judgment belongs inside the twelve AI workflows her team runs.

Her CMO asked, “Did we approve this?”

Maya doesn’t have that answer yet.

She will by the end of the month.

This month I’m experimenting with a serialized format. One situation, explored over four weeks.

Here’s what you can expect:

Chapter 1 (this post): The protagonist’s situation (Maya) and the judgment boundary failure that created it.

Chapter 2: The tool Maya uses to drive change: the Judgment Boundary Matrix, a framework for mapping decisions by impact severity and context complexity, with the downloadable decision tool (for paid subscribers).

Chapter 3: What Maya learns from other marketing leaders who are drawing judgment boundaries and what they got wrong before they got it right.

Chapter 4: Maya revisits her solution. What shifted, what she’d do differently, and the one boundary she and her CMO still disagree on.

I’d love to hear your feedback on this new format. Share it in a comment!

Leave a comment

SOURCES

Gartner (May–June 2025 survey of 360 IT leaders): AI Regulatory Violations Will Result in a 30% Increase in Legal Disputes for Tech Companies by 2028 — gartner.com/en/newsroom/press-releases/2025-10-06-gartner-predicts-ai-regulatory-violations-will-result-in-a-30-percent-increase-in-legal-disputes-for-tech-companies-by-2028

Gartner: Enterprise Spending on Battling Misinformation Will Surpass $30 Billion by 2028 (October 2025) — gartner.com/en/newsroom/press-releases/2025-10-21-gartner-predicts-enterprise-spending-on-battling-misinformation-and-disinformation-will-surpass-30-billion-dollars-by-2028

Gartner: 50% of Enterprises Will Invest in Disinformation Security and TrustOps by 2027 (November 2025) — gartner.com/en/newsroom/press-releases/2025-11-20-gartner-predicts-50-percent-of-enterprises-will-invest-in-disinformation-security-and-trustops-by-2027

Cummings & Cummings Law: Legal Issues in Using AI-Generated Content for Business Marketing (January 2026) — cummings.law/legal-issues-in-using-ai-generated-content-for-business-marketing/

Scientific Reports / Nature (2026): Examining human reliance on artificial intelligence in decision making — nature.com/articles/s41598-026-34983-y

February was about making trust operational instead of aspirational:

• We named the Trust Tax: the cost of treating trust as a value statement.

• We built the Trust Stack, four layers that replace invisible workarounds with clear systems.

• We walked through four real-world cases where missing one trust layer changed the outcome.

In this article, I highlight what matters from everything I covered and how you can apply it to your work. I’ll also preview what’s coming in March when we tackle Judgment Boundaries.

What we covered this month

The Trust Tax

The biggest lesson: invisible workarounds cost more than visible failures. Teams are quietly compensating by adding extra review passes, redoing AI outputs manually, and creating private quality standards. Leaders saw high adoption numbers and assumed trust was building. What was actually building was operational debt.

The Trust Stack

The realization: trust doesn’t scale through culture or communication alone. It scales through systems. Four specific layers—Verification, Accountability, Transparency, Recovery—answers one question teams must answer before moving forward.They provide operational clarity that removes the reasons to hesitate.

The Trust Stack in Action

The pattern: organizations that got one layer wrong paid for it publicly. Coca-Cola (Verification). A fintech (Accountability). Air Canada (Recovery). And one that got it right: Klarna (Transparency). What separated success from failure wasn’t the presence of AI. It was the presence of clear systems before they were needed.

The data that drove this month’s conversation

The research we highlighted showed why trust can’t stay aspirational. 69% of employees and 66% of consumers say companies should disclose AI governance frameworks. Only 5% of marketing leaders using generative AI report significant business gains. McDonald’s Netherlands discovered what happens when customer perception shifts—customers assumed AI-generated burgers meant lower quality, even without evidence.

The pattern was clear: AI adoption is rising, but confidence in how organizations use it isn’t keeping pace. Teams compensate with invisible rework. Customers ask harder questions. High performers hesitate before putting their names on AI-assisted work.

February was about turning those invisible costs into operational systems.

What’s resonating (and what readers are asking)

The most common question: “Which layer do I start with?”

Here’s what I learned from reader responses: most leaders already know which layer they’re missing. The hesitation comes from feeling like they need executive alignment, cross-functional buy-in, or a formal project plan before they can act.

You don’t.

Start small. Pick the one layer causing visible friction on your team right now. Build it for one workflow, one output type, one use case. Let the team see it work. Then expand.

The leaders making progress are the ones who defined “good enough” for one content type, mapped decision rights for one AI-assisted process, or wrote down three consistent answers to the questions customers actually ask.

Operational trust builds through use, not through perfect documentation.

Which layer are you starting with?

I’m hearing from readers tackling everything from verification standards to recovery protocols. Hit reply and let me know which layer is causing the most friction on your team right now. I read every response.

How to put this into practice

Pick one layer. The one causing the most friction in your team right now.

If you’re starting with Verification:

Identify three output types your team produces regularly with AI assistance (campaign briefs, social posts, customer emails, whatever yours are).

For each output type, answer these three questions:

1. What’s the quality bar for “draft complete”?

2. What’s the quality bar for “ready to publish”?

3. What triggers a review before it goes out?

Write it down. Share it with your team. Watch the second-guessing drop.

If you’re starting with Accountability:

Map one workflow where AI-assisted content currently moves through your team.

Identify four decision points: who creates, who reviews, who approves, who publishes.

Name people or roles. Not “the team” or “marketing.” Actual names.

Make it visible. Pin it in Slack. Reference it in your next 1:1. Turn invisible assumptions into explicit agreements.

If you’re starting with Transparency:

Write down the three most common questions you get about AI use from customers, partners, or stakeholders.

Draft consistent answers. Not marketing language. Clear, simple explanations.

Share those answers with marketing, customer success, and leadership. Make sure everyone uses the same language.

Inconsistent disclosure erodes trust faster than no disclosure at all.

If you’re starting with Recovery:

Define three severity levels for AI-related incidents: minor (internal correction), moderate (customer-facing issue), major (legal or reputational risk).

For each level, answer:

• Who gets notified first?

• Who decides the response?

• What’s the communication protocol?

You don’t need a 20-page playbook. You need clarity before pressure hits.

The pattern across all four layers

Every layer follows the same logic: define the standard before you need it, not after.

Quality thresholds work when they’re explicit before work goes out, not improvised during a second review pass.

Decision rights work when they’re clear before approval is needed, not negotiated in the moment.

Disclosure standards work when they’re consistent before questions arrive, not invented per conversation.

Recovery protocols work when they’re defined before incidents occur, not created under crisis pressure.

Trust becomes operational when the system exists before the friction surfaces.

What didn’t work (and what I’m adjusting)

The Trust Stack framework landed well. The case studies clarified it. But I heard from several readers who wanted more guidance on implementation, specifically, how to socialize these systems with teams who are already overwhelmed.

Fair feedback.

Here’s what I’m learning: frameworks help leaders see the problem clearly. But getting teams to actually use the system requires a different skill set. It requires noticing when people are going through the motions instead of trusting the process. It requires reading the signals that say “this policy sounds good but doesn’t feel safe to follow.”

The gap between system design and system adoption lives in the emotional intelligence layer.

March’s theme, Judgment Boundaries, will address this more directly. It’s the first of the Five Disciplines, and it’s about knowing where human judgment is non-negotiable even when AI can technically handle the work.

Looking ahead: March focuses on Judgment Boundaries

Here’s the tension we’re tackling in March:

AI can draft the campaign brief. AI can generate the social post. AI can write the customer response. Capability is no longer the question. The question is: “Should a human make this call anyway?”

Judgment Boundaries is about defining where human decision-making is required, not because AI isn’t capable, but because the stakes, context, or consequences demand a person in the loop.

It’s the discipline that protects what matters when speed becomes the default.

What to expect in March:

The Leadership Brief on why boundaries matter more as AI gets better, not less.

The Judgment Boundary Framework—how to map where human oversight is non-negotiable in your workflows.

A case study showing what happens when boundaries aren’t clear and teams assume AI can handle more than it should.

The March Debrief, plus a preview of April’s theme (Lead with Cultural Honesty).

And daily Notes that will help you boost your own AI literacy.

Bottom line

Trust doesn’t build itself. But it becomes scalable when it’s operational instead of aspirational.

February gave you the framework. March will show you how to protect the decisions that matter most.

See you next week.

Sources

• BCG, “Only 5% of Marketing Leaders Using Generative AI Report Significant Business Gains,” 2026

• Edelman Trust Barometer, “Employee and Consumer Expectations for AI Governance Disclosure,” 2026 (69% of employees and 66% of consumers)

• McDonald’s Netherlands AI Burger Perception Study, 2026

• Reuters, “Air Canada Chatbot Misinformation Case,” Moffatt v. Air Canada, British Columbia Civil Resolution Tribunal, 2024

• Reuters, “Coca-Cola AI-Generated Creative Backlash,” March 2024

• Reuters and Financial Times, “Klarna AI Assistant Deployment and Course Correction,” February 2024 - May 2025

Last week, I shared the Trust Stack—four layers that replace hidden coping mechanisms with operational clarity. Today, I want to show you what those layers look like when they’re tested.

Here are four cases for each layer. Three are public and well-documented. One is a composite drawn from governance patterns that I consistently observe across regulated B2B environments. Each one reveals a different kind of trust failure and what it actually costs when the system isn’t in place.

Layer 1: Verification

Coca-Cola: when brand standards aren’t enough

Coca-Cola integrated generative AI into high-visibility creative campaigns, including its holiday advertising and the Coca-Cola Create platform. Coverage in Reuters, AdAge, and Forbes documented both the company’s formal AI adoption and the public reaction that followed.

The response was mixed and revealing.

Audiences described some of the AI-generated creative as inauthentic, wrapped in“AI-sheen,” and inconsistent with the brand’s visual legacy. Critics called out the gap between what audiences expected from Coca-Cola’s creative and what the outputs delivered.

For a brand built on emotional resonance, that gap was visible almost immediately.

What this reveals about Verification: Coca-Cola has some of the most recognized brand standards in the world. But even extensive brand guidelines don’t automatically translate into AI quality thresholds. When a team knows what the brand looks like but doesn’t define what AI-generated work for that brand must look like—what constitutes “draft complete” versus “publish ready”—quality drift is the predictable result.

You can’t blame AI for the rework and the backlash. But you can blame absence of explicit verification standards for AI-generated creative.

The question Verification answers: What does “good enough” look like for this output type, at this risk level, for this audience?

When that’s defined—and aligned— teams catch quality gaps before the work goes public.

Read more

When teams spend hours reworking AI outputs, when high performers hesitate before hitting send, when customer confidence erodes despite faster responses—that’s the cost of treating trust as a value statement instead of an operational system.

Last week, I referred to this cost as the Trust Tax.

Right now, your team is inventing their own coping mechanisms. They’re creating stealth quality checks, informal approval chains, and private standards for “good enough.” These workarounds feel necessary because the formal systems don’t exist yet.

The Trust Stack replaces those invisible mechanisms with clear operational layers. It’s not a maturity model. It’s not a governance document. It’s the operating system that lets teams move fast with confidence instead of moving fast with anxiety.

The Four-Layer Trust Stack

Each layer of the Trust Stack addresses a specific trust breakdown from last week. The stacks aren’t sequential. They reinforce each other. You don’t need all four to start, but you need to know which one you’re missing.

The full breakdown of all four layers—plus the one-page framework download—is below for paid subscribers.

Upgrade to paid

Read more

AI was supposed to make your team faster. Instead, caution has replaced speed, and that shift carries a hidden cost.

As AI takes on more customer-facing and internal work, trust failures are becoming a hidden operating cost. Employees and customers increasingly want to know how AI is governed. When trust isn’t built into workflows, teams quietly redo AI’s work, question decisions, and absorb risk.

This leads to a “Trust Tax” that will only increase as companies build out their AI workforce. And the last thing you need is another tax.

This is why I have designated February’s theme as “operationalizing trust”. It’s easier said than done, but modern marketing leaders must prioritize this in 2026. The success of your AI-human workforce depends on it.

Mind the gap

Across marketing, customer experience, and brand leadership, a pattern is emerging: when expectations around AI use are unclear, humans compensate. They rewrite outputs they don’t feel confident defending. They hesitate before sending automated responses. They add manual checks that were never planned. Over time, this creates a growing gap between reported adoption and real confidence.

This gap has a cost: a steady drain on time, energy, and credibility. This is the Trust Tax: what organizations pay when trust remains aspirational rather than operational.

The data behind the Trust Tax

The pattern shows up across industries:

69% of employees and 66% of consumers say companies should disclose their AI governance frameworks, signaling that trust expectations now include oversight and accountability.

Only 5% of marketing leaders using generative AI report significant business gains, suggesting that adoption alone doesn’t equal value when confidence in outputs is low.

58% of consumers say companies still don’t understand their needs, despite more data and automation than ever before.

The message is consistent: AI use is increasing, but trust in how it’s applied is not keeping pace.

The paradox: AI promises efficiency, but creates trust debt

AI accelerates production. Trust depends on judgment.

When organizations move quickly without defining standards, decision rights, or review expectations, individuals are left to manage the risk on their own. The result is caution. Work slows because people don’t know what “good” looks like anymore.

This is how trust debt accumulates: quietly, invisibly, and across thousands of small decisions.

Dont' miss out! Become a subscriber.

Three trust gaps cost leaders more than they realize

1. The customer trust gap

“Does this content prioritize my needs over speed?”

Customers are increasingly sensitive to whether AI-driven interactions feel attentive or dismissive. In late 2025, McDonald’s Netherlands pulled an AI-generated holiday campaign after viewers criticized it as emotionally hollow and visually disturbing. The public backlash centered on one question: did anyone with judgment review this before it went out?

McDonald’s defense, ”we had a huge team working day and night for seven weeks,” missed the point entirely. Effort doesn’t replace judgment. The trust gap appeared when customers sensed that speed and efficiency drove the decision, while quality control and emotional resonance got deprioritized.

For B2B leaders, the equivalent shows up in automated messaging, support responses, or content that technically answers the question but misses context entirely—creating doubt instead of reassurance.

2. The team trust gap

“I can’t put my name on this without redoing it.”

Inside organizations, low trust manifests as invisible rework. High performers quietly revise AI outputs before sharing them upward or outward because they don’t feel safe defending them as-is.

A VP of Marketing at a fintech company recently told me her team had 85% AI tool adoption. Impressive metrics. But when she dug deeper, she discovered her team was spending hours “reviewing and revising” what AI produced in 10 minutes. They weren’t resisting the technology; they were protecting themselves. Without clear standards for when AI outputs were “good enough” and who was accountable if something went wrong, they defaulted to redoing the work rather than risking their credibility.

This isn’t isolated. When Coca-Cola faced criticism for AI-heavy holiday creative in 2025, the underlying issue was similar: teams may have used AI tools, but the outputs felt under-considered. When judgment doesn’t clearly live somewhere in the workflow, teams learn that speed gets rewarded publicly while caution is required privately. That tension erodes performance over time.

3. The organizational trust gap

“Are we using AI responsibly, and who is accountable?”

At the organizational level, trust gaps surface as unanswered questions: Who approves AI-generated work? What requires disclosure? What happens when something goes wrong? Who decides what’s off-limits?

In professional services and consulting, this gap is becoming acute. Firms are using AI to accelerate research, draft client deliverables, and analyze data, but without clear policies on disclosure, verification standards, or accountability when AI produces flawed analysis. One consulting firm discovered a junior team had used AI to generate competitive analysis for a major client pitch, but no one had verified the data sources or checked for hallucinations. The analysis included fabricated market statistics. The pitch failed, but worse: the client questioned whether they could trust any future work.

The organizational trust gap widens when companies can’t answer basic questions: How do we know this is accurate? Who owns this decision? What’s our policy on AI use in client-facing work? When those answers don’t exist, teams either move too cautiously (slowing everything down) or too quickly (creating risk no one can manage).

The Trust Tax, defined

The Trust Tax shows up in three places:

Time — hours spent reworking AI outputs people don’t feel confident defending

Relationships — customer and partner confidence weakened by inconsistent or impersonal experiences

Opportunity — delayed decisions, stalled deals, and cautious teams waiting for clarity

Most organizations never calculate these costs. They just feel slower and more exposed than expected.

Why CMOs must lead this

CMOs sit at the intersection of technology, brand, customers, and teams. That makes marketing leaders the natural owners of trust operationalization, even when the implications extend beyond marketing.

When trust is clearly designed into workflows, teams move faster with confidence. When it isn’t, marketing absorbs the consequences first: brand risk, internal friction, and skeptical buyers.

This is leadership work, not messaging work.

This month: From trust debt to trust systems

February is about moving trust out of slide decks and into daily practice.

This week: Naming the Trust Tax and why it’s growing

Next week (paid): The Trust Stack: a four-layer operating system for AI confidence

Following week (paid): How leaders use EQ to surface and fix hidden trust breakdowns

Final week: What leaders are learning as they operationalize trust in real teams

Trust is no longer something you assert. It’s something you build.

Bottom line

In 2026, organizations won’t lose trust because they adopted AI. They’ll lose it because they failed to support human judgment as AI took on more responsibility.

The paid posts this month include governance templates, decision matrices, and trust-building systems: foundational assets to help you operationalize trust—and avoid the dreaded Trust Tax.

What We Covered This Month

January was about naming what’s changing, and why the old playbook isn’t just insufficient, it’s getting in the way.

We started with The 2026 Leadership Inflection Point: the recognition that four forces are converging to make this year fundamentally different:

1. AI capability surpassing human comprehension.

2. Job displacement anxiety hitting new highs.

3. A widening gap between what AI can do and the value organizations capture.

4. Complexity that’s outpacing our capacity to manage it

Then we gave you The Discipline of Staying Human framework: five interconnected practices that redefine what leadership looks like when decisions are increasingly shared between humans and systems:

1. Establish judgment boundaries

2. Lead with cultural honesty

3. Protect human strengths

4. Operationalize trust

5. Exercise strategic restraint

And we closed with a case study showing what happens when a B2B SaaS CMO discovered that 87% AI adoption meant nothing if no one actually trusted the output. Her team was complying: using the agents, generating content, hitting the metrics. But they were redoing everything manually because they were terrified to rely on recommendations they couldn’t defend.

The breakthrough came when she stopped optimizing for adoption metrics and started building trust systems. She:

• Set boundaries that made it clear when AI leads and when humans decide.

• Practiced cultural honesty that named the fear instead of spinning past it.

• Built trust that became operational, not aspirational.

What’s Landing with You

I’ve been reading your comments, DMs, and emails. Here’s what’s resonating:

“I thought it was just me.”

Multiple marketing leaders have told me they’re seeing the same pattern Alysa saw: high adoption rates masking low confidence, and teams performing AI adoption for dashboards while working the old way behind the scenes.

One VP of Marketing wrote: “I’ve been celebrating our ‘AI-first’ metrics in team meetings while employees are silently burning out from AI adoption. Reading the case study felt like someone finally named what I’ve been too afraid to admit.”

You’re not alone. This is the pattern everywhere right now.

“The ambiguity is killing us.”

The biggest pain point isn’t the technology. It’s the uncertainty about accountability.

When AI recommends something, and you approve it, and it fails—who’s responsible? The person who approved it? The person who didn’t catch the flaw? The system? Your team doesn’t know, so they treat every decision as high-stakes, creating paralysis.

Several of you asked: “How do I draw those boundaries when I don’t even know what AI can reliably do yet?”

Fair question. Here’s what I’m seeing work: Start by defining what’s too risky to get wrong (customer promises, proprietary content, brand positioning). Those are human-owned, full stop. Then work backward from there.

“My team thinks I’m chasing AI for the sake of AI.”

This one hit hard.

One comment: “I thought my best people were resistant to change. After reading the case study, I realize they think I don’t value their expertise anymore.”

Strategic restraint—Practice 5—is the action that changes this: saying no to automation that adds complexity without value, pausing use cases that erode confidence, and keeping humans in loops where judgment matters most.

When you demonstrate discernment (not just enthusiasm), your team starts trusting that you understand what they actually do.

What I’m Hearing You Struggle With

A few themes keep coming up in conversations:

1. “I can’t get executive buy-in to slow down.”

You’re framing it wrong.

Don’t ask for permission to slow down. Ask for permission to build a trust infrastructure that accelerates sustainable adoption.

Show them the cost of the compliance charade: teams working double time, high performers disengaging, decisions taking longer despite “high adoption,” and retention risk among key people.

Then show them what operationalized trust looks like: clear boundaries, explicit accountability, and escalation paths that remove ambiguity. That’s not slowing down. That’s removing the invisible drag.

2. “My team wants more certainty than I can give them.”

Good. That means they’re being honest about the uncertainty.

The mistake leaders make is thinking they need to provide certainty. You don’t. You need to make it safe to operate under uncertainty.

That’s what cultural honesty does (Practice 2). You name the uncertainty openly. You make three commitments explicit: raising concerns isn’t resistance, mistakes surfaced early are learning, and silence is riskier than slowing down.

You’re making uncertainty manageable.

3. “How do I protect human strengths when I don’t know what AI will be capable of next year?”

You need to name what’s irreplaceable right now in your business context.

Not generic “creativity” or “strategic thinking.” Specific capabilities:

• Understanding the anxiety a CFO feels when evaluating a $300K decision during a budget freeze

• Sensing hesitation in a customer’s voice when they ask about your product roadmap

• Making ethical calls in gray areas where the data doesn’t tell you what’s right

• Translating between what Product built and what Sales needs to message

Those capabilities aren’t going anywhere. And your team needs to hear you name them specifically.

Where We’re Going in February

Next month, we’re deep-diving into Practice 4: Operationalize Trust.

Why start with #4? Because this is where most AI transformations stall. Leaders talk about trust like it’s a feeling to cultivate. It’s not. It’s a system to build.

Here’s what we’ll cover:

Week 1: The Four Trust Pillars diagnostic

• Competence Trust: Can we rely on this without risking credibility?

• Integrity Trust: Are the rules clear and fair?

• Agency Trust: Are we in control, or are we being replaced?

• Care Trust: Does leadership have our backs?

Week 2: Building trust systems (not trust vibes)

• Templates for AI policies that actually answer the questions your team is afraid to ask

• Ownership models that make accountability explicit

• Escalation paths that remove the guessing

Week 3: A new case study

• How multiple marketing leaders operationalized trust in different contexts

• What works across B2B SaaS, and what’s industry-specific

• The artifacts they built (and you can adapt)

Week 4: Trust at scale

• How trust infrastructure evolves as AI capability increases

• When to revisit boundaries

• How to know if trust is eroding before it shows up in retention data

Your Turn: What’s Your Biggest Question Right Now?

I want to make sure February’s content addresses what you’re actually wrestling with.

Reply in the comments or hit reply to this email:

• What’s your biggest challenge with building trust around AI right now?

• Which of the Four Trust Pillars (Competence, Integrity, Agency, Care) feels most fragile in your organization?

• What would make the February content immediately useful for you?

One Last Thing

Several of you have asked if I offer coaching or advisory work.

I do both. I work with marketing executives (CMOs, VPs of Marketing, Founders) navigating AI transformation—particularly in B2B SaaS contexts where trust, long sales cycles, and brand credibility make “move fast and break things” a challenging strategy.

If you’re interested in exploring that, reply to this email.

And stay tuned for an upcoming announcement about quarterly group coaching calls that will be free for my paid subscribers.

See You Thursday

Next week: The Leadership Brief— the latest research, stats, and trends that inform how marketing leaders are currently building trust systems, and how they will evolve in 2026. This will kick off our February focus: Operationalizing Trust.

Until then,

Kim

The campaign review that changed everything

The senior marketer presenting had clearly done her homework.

Alysa, the CMO, was reviewing an AI-informed recommendation for their annual user conference campaign—a six-figure investment targeting enterprise IT decision-makers. The AI agent had analyzed three years of behavioral data and identified a new account segmentation pattern: companies experiencing rapid headcount growth showed 3x higher likelihood to register, regardless of industry vertical.

The analysis looked solid. The data was clean. The logic was sound.

Alysa asked her team, “What do you think? Should we reallocate budget toward this segment?”

The room went quiet.

The senior marketer—someone Alysa had personally recruited, someone who’d run enterprise campaigns for over a decade—said:

“The recommendation makes sense. The data supports it. But I’m not confident enough to defend it to the sales team if it underperforms.”

That admission cracked everything open.

AI was working. But the team couldn’t rely on it when they couldn’t fully explain how it got to its recommendations.

What she saw beneath the surface

Alysa is the CMO of a mid-sized B2B SaaS company selling infrastructure software to enterprises. Think 12-18 month sales cycles, $200K+ ACV, buying committees of 6-8 people, and deals that live or die on trust.

By early 2026, her team had AI agents embedded across:

• Content operations: Drafting solution briefs, case studies, and technical documentation for different buyer personas

• Campaign orchestration: Managing account-based campaigns across multiple stakeholders

• Analytics: Analyzing pipeline influence and content engagement across long buying journeys

• Customer communications: Personalizing onboarding sequences, expansion plays, and renewal campaigns

The technical work was done. AI agents were activated. Training was complete. Her dashboard said 87% adoption.

But in that campaign review, she finally saw what 87% adoption actually meant.

In our coaching session after the meeting, Alysa asked me: “How do I know if they’re actually using the agents’ outputs, or just using the tools to meet our adoption goals?”

“Walk me through what you’re seeing,” I said.

“People are activating the tools. Training completion is high. Content volume is up. But when I dig into how decisions are actually being made, I get evasive answers. ‘The tools are helpful.’ ‘We’re learning.’ ‘The agents give us good options.’ Then they change the subject.”

Me: “What does that tell you?”

Alysa: “That they’re complying. Not trusting.”

She was right.

What 87% adoption actually meant

Over the next few weeks, I talked to Alysa’s leadership team which included directors, senior managers, content leads, and campaign managers. What I heard wasn’t resistance to AI. It was something more concerning.

They were using the agents—then redoing the work manually.

A content director told me:

“I run the agent to generate a technical whitepaper for CISOs. Then I rewrite 80% of it after hours because I can’t tell if it’s positioning our differentiation correctly. What if a prospect shares it with their evaluation team and it sounds generic?”

A campaign manager:

“The agent recommends shifting the budget from our CFO nurture campaigns to our CIO campaigns based on engagement patterns. The logic makes sense. But I don’t know how to defend that to the sales team if the pipeline from CFOs drops. So I just...don’t do it.”

A senior marketer:

“I activated the agent. I generate content with it. I just never ship anything without completely reworking it first. The agent is fast, but I’m the one who has to answer to the VP of Sales when a campaign doesn’t generate qualified pipeline.”

A customer marketing lead:

“We’re using agents to personalize renewal campaigns. But every email gets manually reviewed by me and our CS leader because one wrong message to a $500K customer could kill the renewal. The agent saves time on drafts. It doesn’t save me from accountability.”

This is what 87% adoption looked like beneath the surface: people performing AI adoption for the dashboard while doing the actual work the old way—or double the work.

The team was adopting AI, but with zero confidence. They were terrified to rely on it.

The three questions no one could answer

Alysa’s team understood AI. The problem was that they were being asked to make decisions they couldn’t defend.

In B2B SaaS marketing, you’re accountable to Sales when the campaign pipeline is weak, to Product when positioning doesn’t resonate in competitive deals, to the executive team when a repositioning effort doesn’t move win rates, and to Customer Success when expansion messaging falls flat.

Your judgment is constantly scrutinized. Every campaign decision gets interrogated in pipeline reviews. Every positioning choice gets stress-tested in deal debriefs. And the teams you support start believing they can do marketing better than you—the seasoned marketing expert.

Now add AI agents into that equation, and suddenly you’re approving decisions shaped by systems you don’t fully control—decisions you’ll need to defend in rooms where “the AI said so” isn’t an acceptable answer.

Alysa’s directors kept circling back to three anxiety-inducing questions:

“Do I trust this recommendation, or should I pressure-test it?”

An agent analyzes three years of pipeline data and recommends deprioritizing the healthcare vertical in favor of financial services companies with recent M&A activity. The pattern makes sense statistically. But your sales leader has relationships in healthcare. Your last three case studies are healthcare logos. Do you:

• Trust the data and reallocate budget (and own the outcome if healthcare deals dry up)?

• Second-guess the recommendation and keep the current strategy (and become the AI bottleneck)?

• Spend three days validating the agent’s work (and slow everything down)?

“Is this something I approve, or do I escalate?”

An agent suggests updating your homepage messaging from “enterprise-grade infrastructure” to “infrastructure that scales with enterprise growth” based on A/B test performance and win/loss interview analysis. It’s a small change. But repositioning is strategic. The line between “you have autonomy on this” and “you should have flagged this” is invisible. So every decision feels high-stakes.

“If this underperforms, is that on me or the model?”

An agent-generated ABM campaign targets accounts based on behavioral signals (product usage patterns from trial users) rather than traditional firmographics (company size, industry). It performs 30% better in early metrics. But three months later, only 20% of those accounts convert to sales conversations, and Sales is frustrated because the accounts “don’t fit our ICP.”

Who’s accountable? The marketer who approved the targeting? The person who didn’t catch that the agent was optimizing for engagement, not conversion? The data science team that trained the model?

When those questions don’t have clear answers, hesitation becomes the rational choice.

What Alysa had to change

Alysa had done what strong leaders do during transformation:

• Set a clear direction

• Communicated urgency

• Projected confidence

But her confidence in the AI strategy was being interpreted as finality, not support.

One of her directors later told me: “It felt like her expectation was acceptance, not open discussion about when to trust (and not to trust) AI outputs. I didn’t want to be the one slowing things down.”

Alysa realized she’d optimized for speed. What her team actually needed was clarity about what happens when things go off the rails.

She’d confidently communicated the strategy. But they needed to know she had their backs.

The shift:

From: “Here’s the AI roadmap—now execute it”

To: “Here’s how we make judgment under uncertainty safe”

Practice 1: She drew the lines

Alysa’s first move was to stop saying “use your judgment” and start defining where judgment lived.

She spent a week mapping every major marketing workflow and putting each decision into one of three categories:

Agent-led, human-approved:

• Draft content (whitepapers, solution briefs, technical docs, case study first drafts)

• A/B test recommendations (subject lines, CTA copy, email send times)

• Performance reporting (campaign dashboards, pipeline attribution, content engagement)

• SEO optimization (keyword recommendations, meta descriptions, blog outlines)

Agent-generated, human-validated:

• Segmentation hypotheses (new ICP patterns, propensity models, account scoring)

• Budget reallocation suggestions (channel mix, campaign investment, spend optimization)

• Campaign optimization plays (messaging variants, audience targeting adjustments, bid strategies)

• Content repurposing recommendations (turn webinar into blog series, extract social snippets)

Human-owned:

• Positioning and messaging strategy (differentiation claims, value propositions, category positioning)

• Customer promises and product claims (ROI statements, capability assertions, competitive comparisons)

• Brand narrative decisions (company story, executive thought leadership, crisis communications)

• Strategic partnership messaging (co-marketing campaigns, joint value propositions)

• High-value account personalization (enterprise deal-specific campaigns, executive outreach)

She published it as a one-page guide: “When AI Leads, When Humans Decide.”

What she expected: Pushback. “This will slow us down. This is too restrictive.”

The reality: Relief.

“I’ve been guessing for three months where I had discretion and where I didn’t. I was spending 10 hours a week revalidating agent recommendations because I didn’t want to make the wrong call. Thank you for just telling me.”

- Campaign Manager

Her content director: “Now I know the agent owns first drafts and research, and I own differentiation and voice for enterprise buyers. That’s clear. I can move faster now.”

Once Alysa’s team knew exactly where they were accountable and where AI was accountable, decisions sped up. They weren’t carrying the weight of every decision alone.

Practice 2: She named what everyone feared

Early on, Alysa’s messaging was all about momentum: “AI is transforming how we work. We’re moving fast. This is the future.”

What she wasn’t saying: some of them were scared.

In her next leadership meeting, she changed her approach.

“We’re introducing systems that will sometimes be wrong. What matters isn’t perfection, it’s how we surface problems and learn from them.”

Then she made three commitments:

1. Raising concerns won’t be seen as resistance.

If you think an agent recommendation is off, say so. That’s judgment, not obstruction.

2. Mistakes surfaced early will be treated as learning.

We’re not penalizing people for catching AI errors. We’re rewarding it.

3. Silence is riskier than slowing down.

If you’re not sure, ask. If something feels wrong, flag it. Don’t wait.

The team’s attitude shifted.

One director who’d been quiet for weeks asked: “What happens if I override an agent’s recommendation and I’m wrong?”

Alysa: “Then we figure out why your judgment differed and whether we need to better understand how the agent came to that recommendation. You’re not wrong for exercising judgment. That’s your job.”

Naming the fear made it manageable.

Practice 3: She told them what AI can’t do

As agents took on more execution, Alysa noticed something troubling: her team was starting to defer judgment, not just tasks.

In a messaging review, someone presented an agent-generated value proposition for their new product module. When Alysa asked about the positioning choice, the marketer said: “The agent recommended this framing based on competitive analysis and win/loss data, so I went with it.”

Not: “The agent suggested this, and here’s why I think it resonates with enterprise infrastructure buyers.”

Alysa realized she’d accidentally sent a signal that AI outputs were answers instead of inputs. She course-corrected fast.

In her next all-hands, she said:

“AI can draft a technical whitepaper in two hours instead of two weeks. It can analyze three years of pipeline data across 50 variables to find patterns we’d miss. It can generate a hundred messaging variations and predict which will perform better based on historical engagement.

But it can’t understand the anxiety a CFO feels when evaluating a $300K infrastructure decision during a budget freeze. It can’t make the call about whether our messaging is technically accurate but misses the emotional reality of our buyers’ risk aversion. It can’t tell when we’re optimizing for this quarter’s pipeline metrics at the expense of long-term brand positioning that wins seven-figure enterprise deals.

It can’t sit in a sales call and hear the hesitation in a CIO’s voice when they ask about our roadmap. It can’t read the room when a champion goes quiet because their internal initiative lost executive sponsorship.

That’s your expertise. And it’s more valuable now, not less.”

Then she changed how her team reviewed work.

Old way: “Here are the results from the agent.”

New way: “Here’s what the agent recommended, here’s my reasoning for accepting or adjusting it based on what I know about enterprise buying behavior, and here’s the outcome.”

She made judgment visible again. Required it in campaign reviews, content approvals, and strategy presentations.

Her team stopped seeing AI as a replacement and started seeing it as a tool that amplified the judgment they were hired for.

Her senior demand gen lead told her later: “I thought AI meant my expertise mattered less. You helped me see it means my expertise matters more, because now I can focus it on the decisions that actually drive enterprise pipeline, not on generating the 47th draft of a nurture email.”

Practice 4: She made trust a system, not a vibe

Alysa realized early on that “trust me” wasn’t a scalable strategy.

Her team didn’t doubt her intentions. They doubted the system would protect them when something went wrong. So she stopped talking about trust and started building it.

She created a one-page AI policy that answered:

• What can agents do without approval?

• What requires human signoff?

• What data is off-limits for prompting?

• Who’s accountable when outputs fail?

She assigned ownership:

Every AI agent got assigned a human “owner”—the person responsible for its outputs.

Example:

Content Generation Agent
Owner: Senior Content Manager
Can: Draft blogs, social posts, email copy
Cannot: Publish without review, make product claims, access customer data
Escalate to: Content Director (brand questions), Legal (compliance questions)

She built escalation paths:

“If the agent is confident but you’re not, escalate to [specific person]. You won’t be penalized for raising concerns. You’ll be rewarded for catching issues early.”

The shift was immediate.

People stopped wondering if they could question an AI recommendation. They knew exactly how to escalate and who would back them up.

Trust became operational. And once it was operational, it scaled.

Practice 5: She learned when to say no

The board loved Alysa’s AI momentum. They wanted more.

“Can we automate approval workflows for low-stakes content?”

Alysa said no.

“We’re keeping humans in the approval loop, even for routine work. The moment we remove human judgment entirely, we’ve told the team their expertise doesn’t matter. In B2B, where trust and nuance drive buying decisions, that’s not a trade I’m willing to make.”

She also paused several agent use cases that looked innovative but didn’t demonstrate clear value:

• An agent that “optimized” email subject lines but actually just made them more generic

• A campaign orchestration feature that added complexity without improving outcomes

• A content repurposing tool that saved time but stripped strategic context

The impact:

Her team noticed. They started trusting the remaining initiatives more, because Alysa had demonstrated discernment, not just enthusiasm.

One director told me: “When she said no to that automation, I realized she actually understands what we do. She’s not just chasing AI for the sake of AI.”

Strategic restraint became a signal of mature leadership.

What changed

Within 90 days, Alysa’s team looked different.

Trust indicators increased:

• “Is this allowed?” questions dropped by 65%

• Directors brought her judgment calls, not permission requests

• Team members started voluntarily sharing “what I learned from the agent today” in weekly standups

• Override rates stabilized at 15-20%, reflecting healthy skepticism, not fear

• Escalations increased 40% (in a good way). People felt safe raising concerns early

Performance outcomes improved:

• Content output increased 40% without quality degradation

• Campaign cycle time from concept to launch reduced by 30%

• Enterprise deal content (case studies, ROI calculators, technical documentation) shipped 2x faster

• Pipeline influence attribution became 50% more accurate (agents analyzing multi-touch across long sales cycles)

• Engagement metrics improved across all buyer personas (personalization was finally working)

• Compliance incidents with AI-generated content: zero

Team dynamics shifted:

• The directors who’d been quiet in meetings started pushing back again with strategic challenges

• Manager effectiveness scores increased 25%

• Retention stabilized—two key people who’d been exploring external opportunities stayed

• Cross-functional tension with Sales decreased (clearer communication about why certain accounts were targeted in campaigns)

“I thought I had to choose between speed and trust. I was wrong. Once I built trust, speed followed naturally. My team wasn’t slowing me down with questions—they were paralyzed by ambiguity. The boundaries freed them to move faster than they ever had, because they knew exactly where they owned decisions and where they could rely on agents.”

— Alysa, CMO

Why B2B SaaS Makes This Harder

Here’s what Alysa learned that most CMOs don’t talk about:

In B2B SaaS, the cost of broken trust is catastrophic.

When you’re selling enterprise infrastructure software with 12-18 month sales cycles and six-figure deals, marketing isn’t just generating leads. It’s building credibility across an entire buying committee.

One generic-sounding whitepaper that doesn’t speak to a CISO’s actual concerns can kill a deal three months into the evaluation.

One poorly personalized email to a champion can make you look like you don’t understand their business.

One messaging shift that sales can’t explain to prospects creates friction that slows the entire pipeline.

Your buyers are few. Your sales cycles are long. Your brand is your primary asset.

Every piece of content, every campaign, every message carries weight. There’s no “move fast and break things” in enterprise SaaS marketing. There’s “get it right because you only get a few at-bats with each account.”

Leadership hesitation in B2B SaaS isn’t bureaucracy. It’s risk management in an environment where trust takes months to build and seconds to break.

And when that hesitation isn’t addressed explicitly with clear boundaries and operational trust systems, it spreads across the team and stalls everything.

“I kept thinking my team was being too cautious. But they weren’t. They were being appropriately careful in a context where mistakes are expensive and visible. My job wasn’t to make them less careful—it was to give them the systems that made it safe to move fast.”

— Alysa, CMO

What This Means for You

If you’re leading AI transformation in B2B SaaS marketing, these are the questions that will tell you whether you’re building for adoption metrics or building for trust:

Are you measuring adoption or confidence?

High activation rates might just mean people are afraid to say no. Look for behavioral signals: Are people acting on agent recommendations, or generating outputs they never use? Are decisions speeding up, or slowing down despite “high adoption”?

Can your team explain your AI rules in 60 seconds?

If not, they’re guessing—and protecting themselves through shadow work. Ask three people on your team right now: “What requires human approval vs. what can an agent handle autonomously?” If you get three different answers, you have an ambiguity problem. Ambiguity equals risk.

Do your best people feel safe to override AI recommendations?

If not, you’ve accidentally told them their judgment doesn’t matter. Watch who’s going quiet in meetings. Those are often your strongest performers realizing their expertise feels devalued.

What happens when AI fails, and who’s accountable?

If that’s not explicit, your team is carrying that uncertainty alone. Every agent recommendation becomes high-stakes because no one knows what happens if they approve something that fails.

Have you named what AI can’t replace?

If not, your team is wondering if they still matter. Be specific. Don’t say “your creativity is important.” Say “AI can’t read a CIO’s hesitation in a sales call. You can. That’s why you’re here.”

Alysa’s transformation started when she stopped optimizing for dashboard metrics and started designing for human trust in a high-stakes B2B environment.

Is Your Team Trusting AI? The 5-Question Diagnostic

To design AI leadership for human trust, you first need to know where your team stands. Download this assessment to learn how to get you—and your team—on a healthy path.

Get the Full Assessment

The Real Bottom Line

In 2026, AI agents will become table stakes in B2B SaaS marketing. The tools will work. The technology will be proven. The integrations will be solid. The question won’t be whether to adopt AI.

The question will be whether your team trusts you enough to rely on AI when the stakes are enterprise deals, long sales cycles, and brand credibility.

Alysa learned this the hard way: You can’t outsource trust to a dashboard, you can’t automate psychological safety, and you can’t generate confidence with a training deck.

AI adoption stalls when leadership hasn’t made judgment under uncertainty safe.

The five practices Alysa applied—establishing boundaries, leading with honesty, protecting human strengths, operationalizing trust, and exercising restraint—aren’t about AI strategy.

They’re about human-centric leadership design in an environment where:

• A single generic whitepaper can kill a six-month enterprise deal

• Sales needs to defend every campaign decision in pipeline reviews

• Your brand is your primary competitive asset

• Buyers evaluate you across committees of 6-8 people over 12-18 months

In B2B SaaS, leadership design isn’t a nice-to-have. It’s the difference between AI that accelerates your business and AI that creates a compliance charade that exhausts your team.

The technology is ready.

The question is: Are you?

A Note on This Case

This case study is a composite drawn from multiple B2B marketing leaders I’ve coached through AI and technology transformation. Details have been modified to protect confidentiality, but the patterns, tensions, and breakthroughs are real.

The five practices referenced throughout come from The Discipline of Staying Human: AI Leadership Framework for 2026, which you can download here.

Next month, we’ll deep-dive into Practice 4: Operationalize Trust—including diagnostic tools, templates for building trust systems, and a complete playbook you can adapt for your organization.

For now, chime in: Which practice resonates most with where you are right now?

Sources Referenced

The patterns described in this case align with emerging research on AI adoption challenges:

• McKinsey, The State of AI (2025): AI adoption often plateaus at decision rights, not deployment

• Harvard Business Review, Executives Overestimate AI Readiness (Nov 2025): Executives consistently overestimate employee enthusiasm and underestimate trust gaps

• UK Parliament POST, Artificial Intelligence and Employment (Dec 2025): Psychological safety is critical to surfacing errors in automated systems

• KPMG, AI Quarterly Pulse (2025): Trust increases when accountability and recourse are explicit

• Deloitte, Tech Trends: Agentic AI (2025): Strategic restraint is emerging as a maturity signal in enterprise AI