
📋 5-3-1 — The leaders changing themselves before they change anything else
234 CEOs left their jobs in 2025, 21% above the eight year average, according to Russell Reynolds' Global CHRO Turnover Index. When a new one arrives, the CHRO is often next out the door within the year, not because they failed at the role, but because the role itself quietly got bigger: organisational design, operating model change, culture, and now the workforce implications of AI, all landing on one desk that didn't used to carry any of it. Whatever a culture change costs an organisation on paper, it costs the person driving it something closer and harder to put a number on.
This week is about five leaders making a version of that same bet right now, in public. One CEO stayed personally hands-on inside a company scaling past $100 billion, because she believes presence protects culture better than absence. One leadership team put its own name on the internal AI usage leaderboard before asking anyone else to touch the tools. One CEO has kept a hundred-year no-layoffs promise standing through the exact AI wave everyone else is using as cover to break theirs. One co-CEO has spent three decades treating leadership as an integration problem, not a balance one. And one company's 21,000 job cuts arrived by email at six in the morning with no warning at all, the clearest possible answer to what happens when you skip every step the other four took. Three Micro-Playbooks on why the people meant to protect a culture are leaving it fastest, what a 2026 workplace survey actually found when it measured belonging against AI use, and why convening always looks like the slower option right up until commanding blows up in your hands.
Jeremy Reeves is living the harder, closer-in version of this same question, from inside a single company rather than a single headline. As Chief Creative and Culture Officer at Creative Consortium, a company running 250 to 300 live creative projects at any given time, he calls his own job convening rather than commanding: getting the right people to a table, then making sure they can actually say what they need to say once they're there. He's also Co-Founder of GHOST Signal. He joins The Work Life Reporter Live this Tuesday to talk about what a culture shift actually asks of the leader personally, not just the organisation around them, a question that gets harder, not easier, as workplaces get faster and more technical.
Welcome to the thirteenth issue of The Work Life Reporter. This week you get:
5x Culture Plays, the leaders and companies changing themselves before they change anything else
3x Micro-Playbooks for people leaders
1x Leader Spotlight ft. Jeremy Reeves, Chief Creative and Culture Officer, Creative Consortium
Let’s get into it.

The Future of AI in Marketing. Your Shortcut to Smarter, Faster Marketing.

This guide distills 10 AI strategies from industry leaders that are transforming marketing.
Learn how HubSpot's engineering team achieved 15-20% productivity gains with AI
Learn how AI-driven emails achieved 94% higher conversion rates
Discover 7 ways to enhance your marketing strategy with AI.
Presented by HubSpot ![]() HubSpot’s Agentic Customer Platform brings your data, teams, and tech stack into one place — the same disconnect this issue keeps circling: the people who need to act sit in different rooms. Get started free → hubspot.com |
THE FIVE CULTURE PLAYS

Play 01
Torani's CEO Is Keeping a Hundred-Year No-Layoffs Promise Standing Through the Exact Wave Everyone Else Is Using as Cover

Torani, the 101-year-old flavoured syrup maker, has never laid off an employee, not through the Great Depression, the 2008 recession, Covid, or, as of this year, the AI-driven automation wave that's given plenty of other companies a ready-made excuse. Melanie Dulbecco has run the company for 35 years and led it through 20% average annual revenue growth over that period, without breaking the streak once. Asked directly by Fortune in September 2026 how AI changes the promise, she didn't hedge: "It is going to dramatically change things, and we're all going to live through this together, but our approach is going to be the same as it has been. How do we create great jobs through this for everyone?"
The insight is in what that promise actually buys the company operationally, not just morally. Dulbecco's own framing: "What we find is our team is more likely to embrace new technologies also because there's confidence and an openness to learning new things because they know we've got their backs and they've got ours." Torani calls its answer to displacement "career mixology": when a role changes shape, the person in it moves to a new one inside the company rather than out the door, the way a longtime procurement staffer named Carlos has moved through several roles as the business evolved. Job security isn't the reward for adopting new technology at Torani. It's the precondition that makes people willing to try it at all.
If you want people to actually adopt the technology you're rolling out, the fastest way to slow them down is to let them suspect it's the first step toward replacing them. Job security isn't a nice-to-have next to change management. It's the thing that makes change management work at all.
TEMPLATE: THE TRUST-BEFORE-TOOLS CHECK
| The Trust-Before-Tools Check 1. Before announcing any AI or automation rollout, ask plainly whether your team currently believes it puts their job at risk. If you don't know the answer, that's the first problem to fix. 2. State your position on job security explicitly and in writing, not as a vague reassurance in a town hall nobody can quote back later. 3. Build a real internal mobility path for anyone whose role changes shape, not just a severance policy for anyone whose role disappears. 4. Name one person, publicly, who has already moved through a role change successfully. A real example does more work than a policy document. 5. Track adoption speed against your own trust levels over time. If people are slow to use a new tool, check whether that's a training problem or a trust problem before you assume the former. |
Play 02
Airbnb's CEO Went Back to Being Hands-On, on Purpose, Once the Company Got Big Enough to Let Him Stop

Airbnb now runs with AI writing roughly 60% of its new code and AI-powered support resolving 45% of customer inquiries without a human, changes that have compressed the company's concept-to-launch timelines by as much as 60% this year. On the company's August 2026 earnings call, CEO Brian Chesky called AI "the best thing to ever happen to Airbnb." What's less obvious is what he says winning that shift actually requires of him personally: "The winners of AI are going to be the companies that embrace transformation. You might call it founder mode, not manager mode."
Chesky isn't describing a return to micromanagement. His own account of the company's early days, "I was in the details. I knew everything going on. I was the chief product officer," gave way, as Airbnb scaled to roughly 8,200 employees, to a deliberate sequence rather than a permanent handoff: "We should start in the details, develop trust, develop muscle memory, and then let go." The AI moment pulled him back toward the start of that sequence on purpose, personally reviewing token usage and AI output alongside his teams rather than only setting a target and waiting for a report. His own summary of why: "Great leadership is presence, not absence."
Delegating further as a company scales isn't automatically the mature move. When the ground shifts fast enough, the leader who stays present in the details isn't failing to let go, they're recognising that this is exactly the moment letting go costs the most.
TEMPLATE: THE PRESENCE AUDIT
| The Presence Audit 1. Identify the one capability or shift in your business moving fast enough that nobody below you has built full muscle memory in it yet. 2. Get personally back into the details on that one thing specifically, not everything at once. Presence that's spread everywhere reads as micromanagement, not leadership. 3. Set a visible marker of your own involvement, a metric you personally review, a session you personally show up to, so your presence is legible to the team, not just felt. 4. Agree explicitly with yourself and your leadership team when you'll step back out again, tied to a capability milestone, not a calendar date. 5. Watch for the moment "letting go" quietly becomes "checked out." The difference is whether you can still answer a detailed question about the thing without asking someone else first. |
Play 03
Shopify's Leadership Put Its Own Name on the AI Leaderboard Before Asking Anyone Else to Use the Tools

When Shopify CEO Tobi Lutke told staff in an April 2025 memo that using AI effectively was now a "baseline expectation" and that teams should show why a task genuinely required a human before asking for more headcount, the memo alone didn't do the cultural work. What actually moved adoption, according to internal accounts of how the mandate spread, was that Shopify's own senior leaders showed up on the company's internal AI usage leaderboard, including CTO Mikhail Parakhin appearing among the top token spenders, and that engineering leadership paired directly with individual engineers to show their own workflow rather than delegate that down. VP of Engineering Farhan Thawar's own description of it: "I have a tab open for ChatGPT and in practice, will show how I'm pairing with AI all the time."
The insight is the order of operations. A mandate that starts with "prove you can't do this with AI before you ask for headcount" reads as a threat if the only visible AI users are the people it applies to. It reads as a genuine expectation once the people issuing it are visibly, personally near the top of the same leaderboard everyone else is being measured against. Thawar's coaching to a product lead captures the standard leadership held itself to alongside everyone else: "There are an infinite number of bad solutions and probably 10,000 good ones. Your job is to find the best one."
A behaviour mandate from leadership lands as commanding right up until leadership's own name shows up on the same scoreboard everyone else has to answer to. That's the exact moment it starts reading as convening instead.
TEMPLATE: THE LEADERBOARD-FIRST ROLLOUT
| The Leaderboard-First Rollout 1. Before issuing any new behavioural expectation to your team, put a visible tracking mechanism in place that includes your own name and your direct reports' names, not just the team you're asking to change. 2. Get your own numbers on that leaderboard first, publicly, before the policy takes effect for anyone else. 3. Have a senior leader personally demonstrate the new behaviour to a small group, one on one or in a small session, rather than only announcing it company-wide. 4. Write the mandate as a standard applied to leadership first and the wider team second, in that explicit order, not as a flat announcement to everyone at once. 5. Revisit the leaderboard's top names every quarter. If leadership quietly drops off it once the initial push is over, the team will notice before you do. |
Play 04
EO Products' Co-CEO Has Spent Three Decades Treating Leadership as an Integration Problem, Not a Balance One

Susan Griffin-Black has co-run EO Products, the organic bath and body care company she co-founded, for over 30 years. Her explicit rejection of one of the most common frameworks in leadership, work-life balance, isn't a branding line, it's how she describes actually running the company: "There's an ongoing conversation about work life balance which I believe is a set up for women to be unsuccessful. It's not as much about balance, it's presence." Her stated model for leadership borrows directly from parenting rather than management theory: "the job is to lead from an integrated place, to bring your whole self to work," pointing to consistency, mindfulness, and bringing people together as the traits the two roles share.
The insight is what "integrated" rules out as much as what it allows. Griffin-Black is explicit that bringing your whole self to work isn't a licence for boundarylessness: "That doesn't mean it's boundaryless, or you're leaking too much information all over the place, but it's a much more curious, open and collaborative process." She's also candid that three decades in, the work isn't finished: "Even though we've been a B Corp, and even though I've been aspiring to do this for 30 years, there's still such a long way to go." That combination, a firm personal model plus an explicit admission it's still incomplete, is a harder thing for a leader to say out loud than either a confident framework or a vague aspiration on its own.
Balance treats work and the rest of your life as two things in competition for the same fixed hours. Integration treats them as one identity that has to hold together under both. The second one is harder to model and impossible to fake for three decades if it isn't actually true.
TEMPLATE: THE INTEGRATION, NOT BALANCE, SELF-CHECK
| The Integration, Not Balance, Self-Check 1. Notice the next time you or someone senior describes work life "balance." Ask what specifically is being traded off against what, and whether that framing is even accurate to how the work actually gets done. 2. Define what "bringing your whole self" would concretely mean and rule out in your own team, before using the phrase publicly. Vague versions of it read as licence for oversharing or under-delivering. 3. Model one specific boundary alongside the openness, out loud, so people see the "curious and collaborative" half paired with the "not boundaryless" half in the same sentence. 4. Say explicitly, on the record, where your own culture work is still incomplete. A leader who claims the work is done is less credible than one who names the gap. 5. Revisit this yearly. A model of integrated leadership that hasn't visibly evolved in years probably isn't being lived, it's being recited. |
Play 05
Oracle's 21,000 Job Cuts Arrived by Email at Six in the Morning, the Clearest Answer to What Happens When You Skip Every Step Above

Oracle eliminated roughly 21,000 roles, 13% of its workforce, over the year to June 2026, funding a $156 billion infrastructure commitment that is, in the reporting's own phrase, "replacing approximately 30,000 human workers with servers, networking equipment, and AI accelerators." The company booked a $2.1 billion restructuring charge and raised $50 billion in new debt to fund it. None of that is unusual for a company repositioning around AI infrastructure at scale. What made it a story about culture rather than just balance sheets was how it landed: termination notices went out by email at approximately 6:00am Eastern on 31 March 2026, simultaneously across the US, India, Canada, Mexico and Uruguay, with no advance warning, reading in part "today is your last working day."
The insight is the gap between the decision and the delivery. A workforce reduction tied to a real, defensible infrastructure strategy is a business decision leadership is entitled to make. A 6am email with zero notice, landing the same way across five countries at once, is a communication decision, and it's the one employees actually experience. LinkedIn filled with posts from affected staff "expressing shock at the lack of advance notice," and the reporting describes remaining employees living in "a climate of fear and uncertainty, with remaining staff unsure whether additional rounds of layoffs are coming." Every leader in this issue's other four Plays chose presence, visible personal involvement, or an explicit promise, before asking their people to absorb a hard change. This is what it looks like when a company skips straight to the outcome instead.
The decision to restructure and the decision about how people find out are two separate choices, and leadership only gets credit for handling one of them well if it visibly owns both. A 6am email doesn't just deliver bad news badly, it tells everyone who's still there exactly how much warning they can expect next time.
TEMPLATE: THE DELIVERY AUDIT, BEFORE YOU ANNOUNCE ANYTHING HARD
| The Delivery Audit, Before You Announce Anything Hard 1. Separate the business decision from the communication plan explicitly. Approving the first is not the same as approving the second, and both need a named owner. 2. Ask how much advance notice is operationally possible, not just legally required, and default to more rather than the regulatory minimum. 3. Never deliver a termination as the entire content of a message with no context, and never let it be the employee's first signal that a decision was even being considered. 4. Decide deliberately whether the news lands the same way everywhere at once or in a staggered sequence, and be able to explain that choice afterward. 5. Assume every remaining employee will read your delivery method as a preview of how the next one will go. Because they will. |
THREE MICRO-PLAYBOOKS

Playbook 01
The People Protecting the Culture Are Leaving It Fastest
In 2025, 155 CHROs were appointed at public companies globally, up from 124 the year before, and still below the five-year average, according to Russell Reynolds' Global CHRO Turnover Index. Separately, HR Dive's H1 2026 data puts CHRO turnover above the eight-year average, with 95 appointments in the first half of the year alone. Around 60% of new CHROs are first-timers in the seat. The average tenure of a departing CHRO is now 5.2 years, and a meaningful share of that turnover tracks directly behind CEO transitions: 234 CEOs left their roles in 2025, 21% above the eight-year average, and a new CEO very often wants a different CHRO within the year.
The reason given for why isn't performance, it's scope. Analysts increasingly describe the CHRO's job as now covering "organisational design, operating model change, culture, and the workforce implications of AI," a remit that barely resembles the role a decade ago. That's the exact same expansion Jeremy Reeves is describing from inside his own job this week, a role that used to be about protecting culture and is now also about holding that culture together while everything else moves faster underneath it.
If you're a CPO or CHRO reading this, the data isn't abstract, it's describing your own actual risk of burnout and exit, not a trend happening to someone else. If you're the CEO or board member this person reports to, the honest question isn't why CHRO tenure keeps shortening, it's whether you've actually resourced the job for the scope you've quietly expanded it to.
Playbook 02
What a 2026 Survey Actually Found When It Measured AI Use Against Belonging
Jeremy Reeves' own question going into this week's conversation, whether AI-accelerated pace puts workplace belonging at risk, has a real answer as of this year, and it isn't the one most people assume. Gensler's 2026 Global Workplace Survey, built from over 16,400 office workers across 16 countries, found that employees it classifies as "AI Power Users," the 30% who use AI tools regularly in both professional and personal contexts, report stronger team connection than late adopters, not weaker. AI Power Users spend 37% of their workweek working alone, against 42% for late adopters, meaning they're actually alone less, not more. They also report 12% of their time on learning against 8% for late adopters, and 11% socialising against 9%.
Janet Pogue McLaurin, Gensler's Global Director of Workplace Research, put the finding plainly: "The employees most embedded in AI workflows are also the ones most engaged in learning and have better team relationships." The mechanism isn't mysterious once you sit with it: AI is freeing up time inside the workweek, and the people using it well appear to be reinvesting a meaningful share of that freed time into exactly the human parts of work, learning together and connecting with colleagues, rather than only into more output.
That doesn't make Jeremy's question naive, it makes it the right question asked one step too early. The real risk isn't AI's pace itself, it's what a leader does with the time it frees up. AI adoption alone doesn't erode belonging. A leader who takes the hours AI frees up and fills every one of them with more output, rather than any of them with more connection, is the actual mechanism to watch.
Playbook 03
Convening Costs More Than Commanding, At First
Every leader in this issue's five Plays made a choice about which was cheaper: convening people into a decision, or commanding it down to them. Torani, Airbnb, Shopify and EO Products all chose some version of convening, staying personally present, modelling the behaviour themselves, holding a promise steady under pressure, and every one of those choices cost more time and personal exposure up front than simply issuing an instruction would have. Oracle chose the fastest available version of commanding, a decision and a departure delivered in the same six-word email, and it was faster to execute by every measure except the one that actually matters afterward: whether anyone left still trusts what happens next.
This is the trap in judging convening against commanding on speed alone. Commanding wins every short-term productivity comparison, right up until the moment trust becomes the constraint instead of task completion, and by then the cost has already compounded past the point a single town hall or apology memo can undo it. Convening looks slower on a Tuesday and looks like the only option that was ever actually available in retrospect, once the alternative has visibly failed somewhere else.
Jeremy Reeves' own description of his job, convening rather than commanding, getting the right people to a table and then making sure they can actually say what they need to say, isn't a soft alternative to real leadership. Based on what this issue's five Plays actually show, it's the expensive, slower-looking option that's also the only one that was ever going to hold.
LEADER SPOTLIGHT
THIS WEEK'S SPOTLIGHT, FIRST APPEARANCE
Jeremy Reeves calls his own job convening, not commanding, and he's about to explain what that costs him personally.

Jeremy Reeves is Chief Creative and Culture Officer at Creative Consortium, a role he's held since January 2026 after previously serving as the company's Creative Strategist. He's also Co-Founder of GHOST Signal, based in Colorado Springs, Colorado.
Since taking on the Chief Creative and Culture Officer seat, Jeremy has held two roles inside one job that don't usually sit in the same person, pushing the creative work forward across 250 to 300 live projects at any given time, and protecting the human culture underneath that same team. He's built his own working definition of leadership as convening rather than commanding, getting the right people to the table and then making sure they can actually say what they need to say once they're there, developed a real two-question diagnostic he uses before assuming someone can't deliver on a request, and run the twice-weekly project reviews that keep Creative Consortium's work moving, using them as his own real-time read on where culture is actually made or lost. He's also raised his own unprompted question about whether AI-accelerated pace puts workplace belonging at risk, the same question this issue's second Micro-Playbook takes on directly.
"The change a culture shift actually asks of the leader personally, not just the organisation, gets harder, not easier, as workplaces get faster and more technical." That's Jeremy's own framing for the conversation he pitched to this show himself.
In this week's Leader Spotlight, we look ahead to sitting down with Jeremy to unpack what leadership as convening actually looks like day to day, what a stalled answer in a room really tells you, and what changing a culture has cost him personally that never makes it into a culture deck. A note on what follows: Tuesday's conversation hasn't happened yet as this issue goes out, so instead of five direct quotes, here are five threads from his own guest brief worth bookmarking ahead of it.

FIVE THREADS WORTH BOOKMARKING AHEAD OF THE CONVERSATION
1. Leadership as convening, not commanding
Jeremy's own definition of the job: get the right voices to the table, then make people feel safe enough to actually use them. Worth watching for what he says happens in the room when that safety isn't there yet.
2. The two questions Jeremy asks before assuming someone can't deliver
A stalled answer usually means one of two things, and only one of them is actually a performance problem. Worth watching for what the other one is, and how he tells the difference in the moment.
3. What changing a culture actually costs the leader
The part Jeremy says never makes it into a culture deck: the personal shift a leader has to make before anyone else does. Worth watching for what he names as his own cost, specifically.
4. Running culture at volume
Two standing review meetings a week, across 250 to 300 live projects, are Jeremy's real-time window into where culture is actually made or lost. Worth watching for what those meetings have taught him that a survey never could.
5. Human-centred work in an increasingly tech-heavy workplace
Jeremy's own question going in: whether faster tools and AI-driven pace put belonging at risk, and what a creative leader can actually do about it. Worth watching for his answer against this issue's own Micro-Playbook on the same question.
Thank you in advance, Jeremy, see you Tuesday!
![]() | ||
The Interior Job: What Leading Culture Change Actually Costs the Leader, Not Just the Organisation A weekly LinkedIn live series where we take the most interesting conversation from the newsletter into a real room, with guests, debate, and the questions the newsletter doesn’t have space to answer. Episode 12 Tuesday, 15 September 2026 at 6:00pm UK / 11:00am Mountain Guest: Jeremy Reeves, Chief Creative and Culture Officer, Creative Consortium, Co-Founder, GHOST Signal Real conversation, no script, 25 minutes, off by 6:25pm UK / 11:25am Mountain at the latest. No questions sent in advance, no rehearsal. Nothing is being sold, it's a conversation. Via Restream Studio. Reserve Your Place → |
Hire anyone, anywhere — compliant in under 3 days
Found the right hire, but no entity in their country? Remote becomes the legal employer — with contracts, benefits, and tax setup handled, plus direct access to the same in-house team that runs payroll locally.
In Partnership With Remote ![]() Global hiring solves contracts and tax. It doesn’t solve the harder problem: making someone three time zones away feel like part of the room — the same test this week’s Leader Spotlight keeps circling back to. See how it works → remote.com |
And that's a wrap for Issue 013. Something land? Hit reply and tell us which section you're taking back to your team.
Follow The Work Life Reporter on LinkedIn for what we share between issues, and join us live on Tuesday for Jeremy Reeves' first appearance. Visit theworklifereporter.com for more.
PS. Know someone who leads people and would find this useful? Forward it on. Ten seconds to share, a lot longer to write.
PPS. Got a story, a leader, or a topic you'd like us to dig into? Reply with your ideas.



