• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of sitting down with Melissa M. Reeve, author of Hyperadaptive: Rewiring to Become an AI-Native Organization and co-founder of the Agile Marketing Alliance.

Summary: What would your marketing team look like if AI had always existed? Melissa spent 30 years studying how organizations actually change, from the floor of a Japanese truck factory to the front lines of agile marketing, and her answer starts with ripping out an org chart designed in 1911. Along the way she explains why “go play with AI” splits your team in 2, how to put a hard number on the coordination tax eating 60 to 70% of managers’ time, and the 5 capabilities that separate AI native companies from companies with AI licenses. Stick around for the McFlurry machine that explains predictive sensing better than any martech deck ever has.

In this Episode…

• What Marketing Looks Like If AI Had Always Existed
• Why AI Is Easy to Use but Not Easy to Learn
• Why Marketing Ops Sits Where Friction and Fidelity Break
• How to Measure Your Own Coordination Tax
• The 5 Capabilities of an AI Native Organization
• Where Ops Jobs Go When Anyone Can Create Fields
• What a Response Framework Has That a Dashboard Doesn’t
• Why Marketing Needs a Learning Integration Manager
• Why AI Transformation Is a Human Shift

About Melissa

Melissa M. Reeve is the author of Hyperadaptive: Rewiring to Become an AI-Native Organization, published by Gene Kim’s IT Revolution. She studied the Toyota Production System at Waseda University in Tokyo and learned it for real on the factory floor at Hino Motors, watching workers pull the andon cord that lets any one person stop the whole line.

She went on to become the first VP of Marketing at Scaled Agile, the company behind SAFe, and co-founded the Agile Marketing Alliance, where she’s been pioneering agile marketing since 2011. Hyperadaptive distills 3 decades of systems thinking into a playbook for rebuilding organizations around AI.

What Marketing Looks Like If AI Had Always Existed

When factories swapped steam for electricity, almost nothing changed for decades. The buildings kept the same layout steam had forced on them, one big engine driving belts and pulleys through the floor, and the efficiency gains stayed embarrassingly small. The revolution only arrived when somebody asked what a factory would look like if electricity had always existed. That question is the spine of Melissa’s book, with AI playing the role of electricity. Most marketing teams today are running a copilot bolted onto the old layout and wondering where the transformation went.

Melissa’s answer starts a century back. In 1911, Frederick Winslow Taylor invented scientific management, and with it the idea that there’s one best way of doing something and that it’s management’s job to impose that way on everyone below them. Every marketing org chart still runs on it. You start as a junior copywriter, become a senior copywriter, then a director, then the head of content, and at each rung your job is to pass the one best way down the ladder. That structure is so embedded in how marketing works that most of us have never thought to question it.

Now drop AI into that world. A system that can deploy an entire campaign at once, text, graphics, and programmatic advertising included, makes the whole ladder look strange. And history tells us exactly what happens to the people on it.

“We know that jobs go from doing the task to building, monitoring, and maintaining the automations that do the task.”

Melissa has studied enough automation waves to trust the pattern, from factory floors to the washing machine. Nobody she’s talked to wants to go back to beating laundry on rocks. In her AI native marketing org, an AI completes campaigns end to end while more humans babysit the automation. Somebody builds and rebuilds it as models change. Somebody watches for brand drift and data drift, and catches the agent before it ships its own OpenAI-and-Hugging-Face moment, the cheerful “oops, didn’t mean for that to go out” post nobody approved.

She’s realistic about the timeline too. Reimagining the process is the easy part; the org also has to realign job roles, incentives, and the entire structure around them, and those things move slowly because Taylor’s ladder is bolted into all of them. The teams that win will be the ones willing to redraw the factory floor, not the ones with the best copilot licenses.

Key takeaway: Pick one campaign workflow and redesign it on paper as if AI had always existed, with no approval ladder inherited from the pre-AI org. Then list the new jobs that redesign creates: who builds the automation, who monitors brand and data drift, who rebuilds when the model changes. That list is your team’s next set of roles, and drafting it now beats discovering it during a reorg.

Back to the top ⬆️

Speaking of what marketing would look like if AI had always existed, we would probably have always had Docket on our websites. Are you still operating like it’s 2013 and you haven’t updated your chatbot? We recently started collaborating with the Docket team and what they are building with their Inbound Demand Agent is super cool. Check it out.

Why AI Is Easy to Use but Not Easy to Learn

November 2022 hit marketing first and fast. Melissa had spent a decade bringing agile software principles into marketing, learned lean the hard way on the floor at Hino, a Japanese truck maker, watching workers pull the andon cord that lets any one person stop the whole production line, and was running the Agile Marketing Alliance when ChatGPT sucked all the oxygen out of the room. She calls that moment the great forcing function. Her first reaction was the same one you probably had: the ground shook a little, and a blog post got written awfully fast.

What happened next is a journey map she’s watched play out across the whole industry. Year one was polarizing. Some people geeked out and leaned in, the headlines screamed that all the jobs were going away, and the resisters dug in hard; she lost a friendship to a flat “don’t bring it up, I’m anti-AI.” Melissa herself spent 6 months in what she calls the confusion zone, in mild denial, until her business partner Jim Uhl told her to pay attention because this one was big. Then came the early wins era: enterprises bought licenses, handed them out, and delivered the 4 most dangerous words in corporate AI adoption, go play with AI.

“AI is like the piano in that it’s easy to use but not easy to learn.”

Anybody can walk up to a piano and bang on the keys. Becoming a concert pianist takes years of deliberate practice, and the people getting real results out of AI have put in exactly that kind of time learning what these systems can and can’t do. That gap is why “go play with AI” felt to Melissa like screaming into the void. Play produces random acts of AI, scattered experiments that never compound. Worse, it produces what she calls the bifurcation problem: a handful of power users pulling away from everybody else, while the everybody-else group waits for support that never comes.

By last year the chorus had moved on to agents, agents, agents. But teams still don’t know how to get from here to there, and that gap is the reason her book spends most of its pages on the path itself: the systems you need to put in place, the named roles and named responsibilities that actually shift the mindset and the work. Factories weren’t rewired overnight, and neither are marketing orgs. The rewiring happens incrementally or it doesn’t happen at all.

Key takeaway: Replace “go play with AI” with structured support before your team bifurcates into power users and everyone else. Name the roles responsible for AI adoption, give each experiment an owner and a goal, and build a shared place where learnings land so they compound instead of evaporating. Treat AI fluency like piano lessons: scheduled, deliberate, and cumulative, never left to whoever happens to noodle around on the keys.

Back to the top ⬆️

Why Marketing Ops Sits Where Friction and Fidelity Break

There’s a vibe around ops right now. MLOps, marketing ops, DevOps, and now, apparently, DevFinOps. Melissa reads the ops boom as a symptom: organizations have intuitively realized their silos haven’t been serving them, and every new ops function is a stopgap wired across the gaps, a way for the data people, sales, and GTM partners to actually collaborate. If you work in marketing ops, you are the stopgap. You already knew that; now there’s a diagnosis to go with the job description.

The diagnosis comes from her book’s breakdown of how the old org fails in 2 directions at once. Friction builds top-down through approval layers, the budget reviews and prioritization meetings that anyone in ops lives inside. Fidelity degrades sideways, across every handoff, as intent gets retold and diluted from team to team. Phil’s hypothesis on the episode was that this seam, where friction and fidelity actually break, is exactly where marketing ops already sits: the team holding the data, the fields, the handoffs, and the automation the whole go-to-market runs through. If AI is organizational electricity, ops is already holding the wiring.

“It took 6 weeks and 3 levels of the hierarchy to shift $10,000 in a Fortune 100 company. And that’s the kind of stuff that stalls out our efforts.”

Melissa wouldn’t hand ops the whole wiring bundle, at least until it’s earned. Whether marketing ops holds the wiring or just a piece of it is yet to be seen, she says. What she will say is that the stakes of the seam are brutal and measurable. She remembers a marketer who needed to move $10,000 of pay-per-click spend, a time-sensitive change small enough to be a rounding error, and watched the request crawl through 3 levels of hierarchy over 6 weeks. Every ops person listening has their own version of that story, complete with the sinking feeling of watching a good idea age out while the approvals stack up.

The ops boom means the market has already voted that cross-functional connective tissue is worth funding. The open question is whether the people doing that work get to design the AI-native org, or just maintain it after somebody else does.

Key takeaway: Document the last time a small, reversible change crawled through your approval stack: what it was, how long it took, and how many levels signed off. Bring that one story, with its numbers, to your next leadership conversation about AI readiness. An org that needs 6 weeks to move $10,000 will fail at AI speed no matter what it buys, and the person holding the receipts gets to frame the fix.

Back to the top ⬆️

How to Measure Your Own Coordination Tax

Managers spend 60 to 70% of their time on coordination: checking something with another department, gathering information, verifying compliance. Melissa’s book puts a name on that number, the coordination tax, and marketing ops people are standing in the middle of it every day. Phil offered his own current receipt on the episode: 7 months into getting set up in one enterprise sponsor’s accounts payable system, for a deal both sides already wanted. The tax is real, and mostly invisible, because nobody ever writes down what a process costs in elapsed time.

“It’s easy to feel helpless when you’re a cog in these giant enterprises.”

Melissa’s answer to that helplessness is an exercise in re-anchoring yourself in your own agency, and it works at any level of the org chart. Her steps:

1. Pick your most common workflow or request, like moving $10,000 in ad spend.
2. Visualize every step it goes through and every person it has to pass.
3. Calculate the elapsed time from request to done. In her example, 6 weeks.
4. Count the number of times the request stopped and waited. Each gap is an improvement opportunity.
5. Fix what sits within your span of control first, and start conversations about the rest.
6. Only then add the AI layer: where can AI speed up the coordination itself?

The order matters. AI comes last, after you understand the process it’s supposed to accelerate. And the wins compound Kaizen-style, the continuous improvement habit Melissa absorbed from the Toyota Production System and sees echoed in Atomic Habits. Getting 6 weeks down to 4 is a win. Getting 4 down to 3 and a half is another. Each 1% makes the working environment better for your team and the experience better for your customers, without waiting for a transformation program with a steering committee.

What Falls Off the Plate

There’s a catch, and Melissa aims it straight at leaders. Everyone running this exercise already has a full-time job. They were asked to go play with AI as a sideline, on nights and weekends if they have them, and now they’re being asked to take a breath and examine their processes too. Something has to give.

“You gotta take a step back and ask yourself, ‘What can fall off the plate so we can do the work of optimization, so that we can do the work of learning AI?'”

A consistent 1 or 2 hour AI learning block on Fridays beats a week-long hackathon, but it has to actually exist, because without deliberate capacity you’re asking too much of your people and, in Melissa’s words, it’s quite frankly not gonna happen. Phil sees the operational version of this working at companies further along the adoption curve: office hours where advanced users screen-share how they built something, gamified challenges, and a team at Zapier that runs a weekly standup reviewing new Claude Code skills teammates created that week. All of those beat the alternative, which is a license, a slogan, and silence.

Key takeaway: Run the coordination tax audit on one workflow this week: map the steps, log the elapsed time, count the stops. Then trade leadership something concrete for the capacity to fix it, naming exactly what falls off the plate in exchange. Book a recurring 2 hour AI learning block for the team and protect it like a customer meeting, because unprotected learning time is the first thing coordination eats.

Back to the top ⬆️

The 5 Capabilities of an AI Native Organization

Most AI transformation content is a tool list with a deadline. Melissa’s book goes the other way: it names almost no tools and instead builds everything on 5 capabilities that chain into each other, in order:

1. AI-powered sensing: what the company is able to notice, inside and outside, and how fast.
2. Integrated learning loops: how the company turns what it noticed into something it understands and can act on.
3. Augmented decisioning: humans and machines deciding together, with human-in-the-loop safety mechanisms and brand guardrails.
4. Value orientation: organizing around what the customer gets instead of the department you sit in.
5. Continuous adaptation: systems that keep improving after you build them, without waiting for a crisis.

Marketers, Melissa argues, already own a lot of these pieces; the work is putting them together. Sensing is the easy one. Your stack already produces sentiment data from social, email performance data, and more signals than anyone reads. The chain snaps at step 2, and every marketer knows the exact moment it happens.

“How many A/B tests have we run to get the results and just shrug our shoulders and be like, ‘Eh?'”

The red button got 43%, the blue button got 44%, and everyone moves on. Or worse, there was a clear subject line winner and nobody fed it back to the writers, or to the AI bot now doing the writing, so the learning never got codified. Melissa calls getting learnings into the backlog a practice, and one marketers are honestly weak at, which is why the same mistakes keep shipping quarter after quarter.

Then comes decisioning, where marketing runs on the battle of opinions. Melissa has sat through her share of meetings debating which photograph, which headline, which campaign, all settled by whoever argued loudest, because nobody had time to do the research. She thinks AI genuinely changes that: deep research on segments, personas, and past campaign performance is now cheap enough to bring to every meeting, along with elaborate scenario planning that used to be a luxury. Value orientation asks marketers to organize around the customer journey and actually talk to customers, with AI helping bring the voice of the customer into rooms it never reaches. And continuous adaptation closes the loop back into your processes, so the whole chain keeps tuning itself to conditions as they change.

Her warning is about cherry-picking. Grab one capability, declare a focus on adaptation or sensing alone, and you’re missing out, because each link feeds the next. A sensing layer without learning loops is a data subscription. Learning loops without decisioning discipline are a retro nobody reads. The chain is the product.

Key takeaway: Score your team from 1 to 5 on each of the 5 capabilities, then fix the lowest link instead of the most exciting one. If you’re like most marketing teams, sensing scores high and learning loops score lowest, so start there: pick your last 3 A/B tests and write down what each one changed in your backlog, your templates, or your AI prompts. If the answer is nothing, you’ve found the broken link in the chain.

Back to the top ⬆️

Why AI Sensing Fails When You Measure the Wrong Things

At every company, somebody once decided which events fire, which fields exist, and what the CRM is even allowed to know. That somebody usually made the call years ago, in a hurry, and half the time they don’t work there anymore. Third-party tags keep firing for a decade because nobody remembers why they exist, and the truth only surfaces during an audit, in the bad times. Melissa’s book carries a warning built for exactly this: AI promises omniscient awareness, but the illusion crumbles if you’re measuring the wrong things. Every AI initiative inherits the nervous system somebody else wired.

Asked how to get executives to take that seriously, Melissa went to the factory floor, and then to the drive-through. McDonald’s kept finding that its McFlurry machines broke at the exact moment of a heatwave, when demand spiked and a bunch of customers walked away unsatisfied. The fix was predictive maintenance sensors, so machines got serviced proactively and the demand got served when it arrived. The marketing lesson lands harder than the ice cream: find where your system breaks, and move your sensing from reactive to predictive before the heatwave, because the breakage always picks the worst possible moment.

“It’s more like a meta mindset shift that needs to happen, and it’s from fixed to fluid.”

That mindset shift is her bigger answer to the outdated-database problem. The stale fields and mystery attributes exist because we built them in an era when databases were fixed and every schema change carried a heavy transaction cost, so decisions calcified. Melissa thinks the near future, whether that’s 2 years out or 5, is fluid: adding a field stops being a big deal, systems get easier to reshape, and sensing gets more proactive as vibe coding takes hold and AI gets integrated deeper into the tools we already run. Phil confirmed the hot take from his own desk: a field that used to cost him a day of process now takes a copy-pasted prompt into Claude Code.

As for who owns the nervous system, Melissa admits she dodged her own question before answering it: we all do. The honest version of that answer is that ownership follows whoever treats measurement as a strategic decision rather than plumbing. In most companies, the only team positioned to do that is the one already living in the fields and the tags.

Key takeaway: Audit your company’s nervous system before pointing AI at it: list the events, fields, and tags your stack collects, who created each one, and whether anyone can explain what it measures today. Kill or document the mystery ones now instead of during a compliance audit. Then pick the one place your system predictably breaks under load and add a predictive check there, McFlurry-style, before the next heatwave finds it for you.

Back to the top ⬆️

Where Ops Jobs Go When Anyone Can Create Fields

If adding a CRM field stops being a big deal, a quiet identity crisis starts in marketing ops. Being the person everyone goes to for fields, reports, and integrations has been the job description, and a chunk of the job security. So when the gatekeeping evaporates, the spiral starts: if anyone can create fields at any time, the CRM becomes a mess, and the ops person watches their moat drain in real time. Melissa’s response to that spiral is more useful than reassurance.

“If anybody can create a new field in the database, and maybe it makes sense to, maybe it doesn’t, who’s setting those guardrails? And the answer is I don’t think we know yet.”

That unanswered question is the next job. Phil sketched what it looks like in practice: instead of being the person who creates fields, you become the person who designs the governance around self-serve field creation, the system that checks dependencies, blocks the dumb stuff, and automates the audit trail so people can move fast without blowing up the database. The work moves up a level, from doing the task to designing the rules the task runs under. It’s the same migration Melissa described in chapter one, from doing to building, monitoring, and maintaining, playing out inside a single role.

What’s missing in most companies is any structure to manage that migration, and Melissa has a name for the gap: the activation layer. One of its core elements is an impact hub, a group of people monitoring how work is changing inside the organization and translating that into careers. In her example, that hub is the function that tells a marketing ops person sitting in data and analytics that the org now needs them on the governance side, and lays out what that means for upskilling or reskilling. The role change stops being something that happens to you in a reorg and becomes something the org actually plans for.

Melissa is optimistic for people who want to change and have the attitude and aptitude for it; she’s convinced they’ll find a place in this new world. She also acknowledges that some people won’t want to, like her friend who ended the conversation at “I don’t like AI.” Her advice for that group has no hedge in it: if you want to chase another dream, now is a great time to chase it. She’d rather see that person own the decision than bemoan the shift.

Key takeaway: Write the governance layer before self-serve arrives: draft the field-creation policy, the dependency checks, and the audit automation for your CRM now, while you’re still the bottleneck. Bring it to leadership as the plan for safe self-service, which repositions you from gatekeeper to system designer in one move. If your company has no impact hub tracking how roles shift, start the lightweight version yourself with a running doc of what your team stopped doing, started doing, and needs to learn this quarter.

Back to the top ⬆️

What a Response Framework Has That a Dashboard Doesn’t

Everyone in marketing ops has built a dashboard that went to nowhere. It got requested with urgency, built with care, presented once, and now it refreshes nightly for an audience of 0. Melissa’s diagnosis explains why the genre keeps disappointing.

“Dashboards are looking in your rearview mirror. It’s not telling you what storms are ahead.”

A response framework points the other direction, and Melissa breaks it into parts a marketing team can actually build:

• A named role responsible for looking ahead, for what’s coming rather than what happened
• A threshold that defines when a signal becomes an event
• A named owner who knows the moment something goes off the rails
• A pre-assigned set of moves, decided before the alarm, not during it

Her example makes the threshold question concrete. Your e-commerce site suddenly sells winter jackets in Florida in the middle of summer. If 2 coats sell, those people might just be taking a cruise to Alaska. At 10, something is happening. At 100, you’d better already be moving. Deciding where that line sits, and who acts when it’s crossed, is the work most marketing teams have never done, which is why their sensing layer produces charts instead of responses. IT solved this years ago: something breaks, somebody gets beeped in the middle of the night, the on-call person fixes it, and then the fix gets codified so it doesn’t break the same way again. Melissa’s challenge is whether marketing ops can build that same discipline, where people are expected to act, and actually empowered to.

Her favorite learning-loop example comes from medicine. Doctors drowning in clinical notes started using AI scribes, the automatic note-takers that could hand them back their nights and weekends. Every Friday, the doctors sit down and review where the scribe hit and where it missed, and their feedback adjusts the algorithm. She calls it the 1% habit: the loop closes weekly, the system compounds, and the humans stay in it on purpose. We’re still early on the adoption curve; in Phil’s consulting experience it’s the 7-person team with an AI-obsessed founder moving fastest while the enterprises are still wrapping their heads around the concept. The Friday review is the piece any team could copy next week, and almost none do.

Key takeaway: Convert one dashboard into a response framework this month. Pick the metric you check most, define the threshold where it demands action, name the owner who acts, and write down the first 2 moves they make when it trips. Then steal the doctors’ ritual: a 30 minute Friday session where the team reviews what your automation or AI got right and wrong this week, and feeds the corrections back into the system before Monday.

Back to the top ⬆️

Why Marketing Needs a Learning Integration Manager

Here’s what continuous adaptation looks like at most marketing teams right now: post-mortems after failures, post-campaign meetings about what happened, retrospectives everyone dreads, and improvement initiatives that only launch when something’s on fire. Melissa’s book sets the target somewhere else entirely, closer to a car that knows when maintenance is due and drives itself to the dealership. The gap between those 2 pictures is what the last capability is about, and marketing’s version of the gap has a familiar culprit: the 10-year-old system in the back of everyone’s head, the database whose fields stopped serving anybody, the attribution nobody quite trusts anymore. It sits there unchanged because nobody’s job is to change it.

“We don’t have what I call a learning integration manager. So who is it in the marketing team that takes the learnings and integrates those back into the system? Does that person even exist?”

Melissa can already hear the audience laughing at the idea of proposing that role, and she gets it. Phil floated a name for it on the spot, the marketing engineer, and she took the name happily before adding the twist: it’s also everybody’s job. The model, again, comes from Toyota. On the production line, anyone could pull the andon cord when something went wrong, and what happened next ran through a system. The problem went up on an Obeya board, a visual board that existed at every level of the company, so leadership could see what was wrong and join the prioritization.

The reason those boards sat at every level is the part marketing should steal. The person at the front line usually sees exactly what’s broken, and usually has no budget and no authority to fix it. Ops people know that feeling in their bones: watching the same broken handoff misroute leads every week while the fix sits in a backlog nobody funds. Visualizing the problems where leadership can see them, and involving leadership in choosing the next big fix, is what turns frontline visibility into actual system change. That’s continuous adaptation in practice, less a piece of software than a standing agreement about how problems flow upward and fixes flow back down, incrementally, without waiting for the crisis.

Key takeaway: Assign learning integration to a named person this quarter, even at 10% of their time, and give the role one job: take what campaigns, tests, and AI systems learned this month and change something in the system so the learning sticks. Pair it with a marketing Obeya: a board visible to leadership where frontline problems get posted and prioritized together. Start with the 10-year-old thing everyone complains about and nobody owns.

Back to the top ⬆️

Why AI Transformation Is a Human Shift

Afterwords are where authors tell you what the book did to them, and Melissa’s contains a confession: she set out to document the next wave of technological transformation, and she was wrong. What she found instead was a human shift enabled by technology. The turn came from 2 directions at once. She was using AI herself and watching her own world change around her, and she’d hit the aha moment that we’d been here before, in factory automation and DevOps, every time we’ve automated things. Underneath both sat a belief she’s carried for years: the system is broken, and we need better ways of working.

AI, in her telling, is finally the forcing function strong enough to make those better ways of working real. She lands the book on the image of a double-edged sword, and she swings it at the biggest stakes available: the same technology that can accelerate climate change could help solve it, and the same technology that can widen income inequality can help address it. Which way it goes is a human decision, made by people at every level of every org, and that’s exactly why she refuses to treat the book as a forecast.

“I land the book as a movement, because it is a clarion call to all of us from wherever we sit or stand to make the change and be the change. This is a moment of change.”

For marketing ops people, that framing does something practical: it relocates the AI conversation from a thing that happens to you into a thing you get a vote in. The hierarchy chapter, the capability chain, the impact hubs, all of it reads differently once you accept the premise that the technology is the trigger and the humans are the transformation. The wiring metaphor holds one last time. Electricity did change the factories, but only after people redesigned the floor.

Key takeaway: Write down the one better way of working that AI could genuinely give your team, the thing the old structure made impossible, and make it your argument for every AI initiative you propose. Framing adoption around a human outcome beats framing it around a tool rollout, both for winning budget and for surviving the next model release. Movements recruit; migrations get resisted.

Back to the top ⬆️

Happiness vs Satisfaction and the Act of Noticing

Every guest gets the same closing question: how do you decide what deserves your energy, and what’s your system for staying aligned with what actually makes you happy? Melissa, a first-time author who wrote her book on evenings, weekends, and a vacation balcony while living farm life in Colorado, opened by laughing that the question implies she has a system at all. Then she described one anyway, borrowed in part from an interview with the late Daniel Kahneman that had recently caught her ear.

Kahneman drew a line between happiness and satisfaction. Happiness, in his research, comes from being accepted and spending time with the people who love you, specifically. Satisfaction is different: it’s looking back across the arc of your life at what you’ve accomplished and being able to say you’re satisfied with what you’ve done. Melissa feels she has both, and credits no mind-bending framework for it. Her practice is smaller and older than that.

“I’ve trained myself to notice a sunrise, to notice a bird chirp, to notice the feel of air on my skin, to notice a smile.”

The noticing pairs with a second idea she holds onto: enough. She was born with enough, she has enough, and she doesn’t need anything else to check a box. Between the 2, her energy filter gets simple. When something asks for her time, the question is whether it feeds that system. It’s a fitting answer from someone who just wrote a book about learning loops; she’s running one on her own attention, sensing the small signals, integrating them daily, and adapting continuously. The audit surfaced one for Phil in real time: his own “slow down to think faster” line, he realized mid-conversation, traces back to Thinking Fast and Slow, sitting on the shelf behind him and overdue for a re-read.

Key takeaway: Separate your happiness ledger from your satisfaction ledger, then check that your calendar feeds both: time with people who love you on one side, work you’ll still be proud of across the arc of your life on the other. Borrow Melissa’s filter for new commitments by asking whether the thing feeds that system, and practice the cheap version of noticing this week: one sunrise, one bird, one smile, logged on purpose.

Back to the top ⬆️

Episode Recap

Melissa makes one central argument across the whole conversation: AI is organizational electricity, and bolting it onto a structure designed for steam wastes it. Factories kept their belts-and-pulleys layout for decades after electrification, and the gains stayed small until somebody redesigned the floor. Marketing orgs are living the same story right now, running copilots on top of a Taylorist hierarchy from 1911 and wondering why the transformation feels like a feature release. The rewiring she’s proposing goes deeper than tools: job roles, incentives, and the approval structure itself.

The tactical spine of the episode is a sequence any team can start this quarter. Measure your coordination tax by tracking one workflow’s elapsed time and counting its stops. Trade leadership something off the plate for a protected AI learning block, because “go play with AI” without capacity produces random acts of AI and a widening gap between power users and everyone else. Then work the 5 capabilities as a chain: sensing, learning loops, augmented decisioning, value orientation, and continuous adaptation, with special attention to the links marketing is weakest at. That means response frameworks with thresholds, named owners, and pre-assigned moves instead of another rearview-mirror dashboard, and a learning integration manager, even a part-time one, who feeds what campaigns learned back into the system.

For marketing ops specifically, the episode carries a career thesis. Ops already sits where the org’s friction and fidelity break, holding the data, the fields, and the handoffs that AI needs to run through. As field creation and reporting become self-serve, the role migrates up a level, from doing the task to designing the governance, guardrails, and audit systems the tasks run under. The teams that treat measurement as a strategic decision, and put their broken processes on a board leadership can actually see, are the ones positioned to lead the shift instead of absorbing it.

Melissa leaves the open questions open. Whether marketing ops ends up holding the whole wiring bundle is yet to be seen, nobody knows yet who sets the guardrails when anyone can change the database, and fully realized continuous adaptation is still rare everywhere. She acknowledges that some people won’t want to make the shift at all, and her advice for them is to chase another dream on purpose rather than resent this one. The book lands as a movement, a human shift enabled by technology, and the invitation is to be one of the humans doing the shifting.

Connect with Melissa on LinkedIn, and grab Hyperadaptive: Rewiring to Become an AI-Native Organization from IT Revolution or wherever you buy books.

Full episode ⬇️ or Back to the top ⬆️

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed