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.

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.

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

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

Before you read this, take a big, deep breath. You did it. You survived 2025!

I hope you found time this month to pause and look back on the year before the January sprint begins. If you’re still racing to close out the month, it’s not too late!

Over the past three weeks, we explored the hidden costs of rushing through AI adoption, the framework for resetting how your team works, and the five ongoing practices that turn your reset into sustained change.

If you missed any part of the series or read them all but want synthesized takeaways, I’ve summarized what matters most as you head into 2026.

This debrief includes lessons on leading through a major transformation when the pressure is to move fast, and the cost of moving in the wrong direction is your team’s trust, confidence, and performance.

Here are the 5 key learnings that will shape how you lead in 2026.

Learning #1: Your Team’s Silence Is the Crisis

From Week 1: “Your Team Is Quietly Cracking”

The most dangerous problems accumulate quietly:

• Your senior designer is redoing every AI-generated mockup from scratch but telling no one

• Your content lead can’t articulate why AI outputs feel “off-brand” and is losing sleep over it

• Your best people are questioning why they’re still employed if AI can do their work

The research that matters:
Manager engagement dropped from 30% to 27% in 2024, and Gallup explicitly attributed this to leaders feeling unprepared for AI-era challenges.

What this means for you:
Stop waiting for your team to tell you they’re struggling. They won’t. Create structured opportunities (like 15 minute weekly check-ins) where problems can surface while they’re still small and before they compound into quiet quitting or project failures.

The shift: From reactive firefighting to proactive problem-surfacing

Learning #2: You Can’t Build New Systems on Old Assumptions

From Week 2: “The Reset Framework”

Most teams adopted AI without resetting how they work. They bolted new capabilities onto old workflows, old role definitions, old ways of making decisions.

That’s why AI usage metrics look good on paper while team anxiety builds in the background.

The pattern we see:
Teams using AI tools don’t equate to teams working effectively with AI. To achieve the latter, leaders need to provide clarity about what’s changed:

• What work should humans still own vs. what AI should handle?

• How do we evaluate AI output quality?

• Who owns decisions about which tools to use and when?

• What does “good work” look like in an AI-native workflow?

What this means for you:
Before you optimize for speed, optimize for clarity. Your team needs to know: What’s our new operating system? How do we work together when AI is in the mix? What are we each responsible for?

The shift: From tool adoption to workflow redesign

Learning #3: Reflection Without Action Is Pointless

From Week 3: “5 Practices That Keep You Moving”

Insight without implementation doesn’t drive change. Most leaders do the reset—they reflect, they identify what needs to change—and then other priorities take over and nothing changes. Your team will think that the reset was just another item on your to-do list and quietly vent about wasting valuable time they could have spent completing their to-do list.

The truth about transformation:
It doesn’t happen through willpower. It happens through rhythm. Practices you run on repeat turn one-time insights into ongoing behavior. It takes time to build a habit, but once you do, this will be ingrained in your team and become effortless.

The five practices that sustain momentum:

1. The Huddle - Surface problems early

2. The Review - Create accountability without micromanaging

3. The Retrospective - Zoom out to strategy

4. The Learning Drop - Build shared knowledge

5. The Leadership Mirror - Keep yourself honest

What this means for you:
Don’t treat the reset as a one-time event in December. Build it into your operating rhythm for 2026. The teams that thrive are the ones who continuously recalibrate.

The shift: From a one-time event to an ongoing system

Get Weekly AI Leadership Insights

Learning #4: AI Literacy is More Than Training

The common thread:

One-time AI training has a very short shelf-life. Two-day workshops don’t create sustained behavioral change. What works is continuous, practice-based learning where teams capture what they’re discovering through trial and error.

The research that backs this up:
92% of marketing leaders believe AI literacy will be a must-have skill in the next 2-4 years. But AI literacy isn’t about knowing how to use tools, it’s about understanding when to use them, why they work (or don’t), and where human judgment remains essential.

What creates real AI literacy:

• Regular debriefs where teams share what they learned

• Peer-to-peer knowledge sharing that scales

• Permission to experiment, fail, and surface challenges without penalty

• Frameworks that evolve based on what the team discovers

What this means for you:
Stop sending your team to more AI training. Instead, create the conditions where they teach themselves, and each other, through doing, reflecting, and sharing.

The shift: From training workshops to practice-based learning

Learning #5: The Same Behaviors That Drive Engagement Enable AI Adoption

The common thread:

This is the insight that connects everything: The leadership behaviors that drive team engagement (acknowledgment, recognition, clarity, reflection, modeling) are exactly the same behaviors that enable effective AI adoption.

Why this matters:
To successfully guide your team through AI transformation, you need to do what good leaders have always done—just more intentionally, more consistently, and with more urgency.

The behaviors that matter most:

• Acknowledgment: See the struggle, name it, don’t minimize it

• Clarity: Define what success looks like, what’s changing, what stays the same

• Reflection: Create space to pause and assess, not just execute

• Modeling: Show your own learning process, don’t pretend you have it figured out

• Psychological safety: Make it safe to say “I don’t know” and “this isn’t working”

What this means for you:
If your team is struggling with AI adoption, the fix isn’t better tools or more training, it’s better leadership. It’s creating the conditions where people can learn, experiment, fail, and surface problems without fear.

The shift: From managing AI tools to leading humans through transformation

What This Means for January 2026

December was about reflection. January is about action.

You’ve done the work of identifying what needs to change. Now comes the harder part: sustaining that change when urgency builds, when deadlines hit, when it feels easier to slip back into old patterns.

Here’s what you know:

• Your team’s silence is dangerous. Create structured ways to surface problems.

• You can’t build new systems on old assumptions. You must redesign workflows, not just adopt tools.

• Reflection without action is pointless. Build ongoing practices, not one-time events.

• AI literacy comes from doing. Create conditions for continuous learning.

• Good leadership is good leadership. The fundamentals haven’t changed, just the context

The question for January:
Will you build the rhythm to sustain your reset? Or will you let your busy calendar erase the clarity you just created?

A Special Invitation

In January, I’m shifting from reflection to implementation. I’ll be sharing the frameworks, playbooks, and EQ-driven approaches I use with clients to redesign how they lead through AI transformation in 2026. And for the first time, I’m opening a small group of coaching spots for leaders who want hands-on support making these changes stick.

If you want to be among the first to know when spots open, reply to this email with “Interested.”

Until then: take what you learned in December and turn it into practice in January.

Your team is watching to see if the reset was real, or if it was just another good idea that faded when work got busy.

Next week: We kick off January with “The Leadership Transition: From AI User to AI Leader”—exploring what changes when you shift from learning to use AI yourself to leading a team that uses it.