Jimmy Parker is the Founder and Chief Transformation Officer of Peaq, where he helps companies create fast, lasting transformation at scale. A graduate of the U.S. Naval Academy who served 11 years as a Marine Corps helicopter pilot, Jimmy went on to earn a PhD in developmental psychology applied to organizational transformation from Fielding Graduate University. Before founding Peaq, he led organizational development at The Home Depot and Kaiser Permanente, where he spent the better part of two decades studying what actually changes on-the-job behavior, and just as importantly, what doesn’t.
Episode Description
What if almost everything we spend on training never makes it back to the job? That isn’t rhetorical. The research Jimmy Parker has been chasing for 20 years puts the application rate of traditional training somewhere between zero and nine percent. In this conversation, Jimmy traces the path from his frustration as a classroom trainer to a methodology he calls micro experiences, a way of changing behavior at scale by leading with doing rather than knowing.
Jimmy’s career arc is a study in contrasts. started in the Marine Corps as an attack helicopter pilot, then carried that low tolerance for theater into corporate L&D. He has studied behavior change wherever the lessons live, including habit science, marketing, addiction recovery, even religious conversion, and he has spent years pressure-testing what survives contact with a real organization. The result is a system designed around the gap between knowledge, behavior, and habit, and a specific format for closing it: a 45-minute action in the flow of work, paired with a reflection question, followed by a small-group conversation, repeated weekly for three to six months.
We get concrete in this episode. Jimmy walks through two micro-experiences he uses in the field: the “judo move” for product teams stuck in order-taker mode, and a decision audit for executives who say they want to grant autonomy but never quite manage to. We talk about why most OKR programs would score a D, why simple isn’t easy when you’re designing for behavior change, and why Jimmy ultimately frames this work as a question of equity, because the people who get the highest-quality development today are almost always the rare and privileged few.
Links and Resources
Guest Links
Peaq — Jimmy’s consulting practice
Email Jimmy directly: jimmy@peaq.co
Tools, Frameworks, and Concepts
Micro Experiences — Jimmy’s framework for behavior change at scale, structured as 45-minute on-the-job actions with reflection and small-group debrief
The Four-Step Weekly Cycle — adapt, do, reflect, discuss
Experiential Learning — the tradition of learning by doing and reflecting, traceable to John Dewey
Declarative vs. Implicit Knowledge — the distinction between what can be taught in a classroom and what can only be learned through doing
Unconscious Competence — the final stage in the progression from ignorance to habit
OKRs (Objectives and Key Results) — referenced as an example of how knowing the framework rarely translates to doing it well
People Referenced
John Dewey — the philosopher widely regarded as the father of experiential learning, often paraphrased: "We do not learn from experience, we learn from reflecting on experience.”
Topics Discussed
From the Cockpit to Behavior Change
Jimmy opens with the throughline of his career: a love of leadership picked up in the Marine Corps, sharpened by years of running leadership training programs, and ultimately reshaped by the uncomfortable realization that classroom training rarely changes what people actually do on the job. That frustration sent him on a 20-year hunt across disciplines for what really drives behavior change.
Key points:
The military taught Jimmy a low tolerance for things that don’t work, a standard he has carried into executive development
After running thousands of people through classrooms, Jimmy noticed the change rarely manifested on the job
His study took him well outside L&D, into habit science, addiction recovery, religious conversion, and consumer marketing, looking for what consistently moves behavior
The work eventually focused on executive behavior change, because the cultural barriers that block agile teams often exist above the team
Why Traditional Training Falls Short
Training is built on a single assumption: if people knew differently, they would do differently. That assumption holds for simple knowledge gaps and breaks down almost everywhere else. Jimmy is direct about the implications, including that the application rate for traditional training tops out at around 9%.
Key points:
Studies from Harvard, MIT and others put the percentage of training participants who properly apply what they learned between zero and nine percent
Knowledge transfer is the right move for simple gaps; for complex, contextual, or culturally rooted behaviors, it almost never gets you to adoption
Agile talk is the common tell: organizations describe themselves in agile terms while their actual norms, requirements flow, and decision rights tell a different story
Most OKR programs score a D or C when measured against best practice, even when the people running them teach OKRs for a living
Knowledge, Behavior, Habit
Jimmy keeps his definitions deliberately simple because the value is in the progression rather than the taxonomy. Knowing is what you can recall. Behavior is what you can be observed doing in a given moment, including how you speak. Habit is what you do consistently, without conscious thought, even when old patterns are pulling you backward.
Key points:
The path from ignorance to habit runs through a stage of effortful, high-cognitive-load doing before the new behavior becomes automatic
Most behavior change interventions stop at knowing and hope the rest takes care of itself
Speech counts as behavior, which is part of why team communication and conflict patterns are so hard to change
The endpoint is unconscious competence, and getting there takes deliberate reps over time
Experience as the Lead, Not Learning
When Dave and Jimmy were planning the episode, Jimmy specifically pushed back on using the word learning to describe his work. The reason matters. Leading with experience is a wager that doing first, then reflecting, gets you further on the hard problems than thinking your way to a new way of acting.
Key points:
Declarative knowledge can be taught; the tacit, contextual knowledge of when and how to adapt can really only be learned through reps and reflection
Jimmy borrows from Dewey: experience by itself isn’t enough; the learning lives in structured reflection on the experience
“Do we think ourselves into a new way of acting, or act ourselves into a new way of thinking?” Both work, but the second is consistently underused
For deeply rooted behaviors, especially with senior leaders, the experiential path tends to be the only one that lands
Anatomy of a Micro Experience
Jimmy walks through two real examples. The first is the “judo move,” a one-pager for product teams stuck in order-taker mode, offering a handful of responses to use when a stakeholder hands them features without context. The second is the decision audit, where executives track every decision they make for a week and score each on a one-to-five scale of whether someone else should have owned it.
Key points:
A micro experience has two non-negotiable components: micro, meaning it fits in 45 minutes or less, and experiential, meaning it happens in real work, not in a simulation or a classroom
Each micro experience runs on a four-step weekly cycle: adapt it to your context, do it, reflect using a designed question, then debrief with a small group of five or six peers
The decision audit consistently surfaces hidden patterns: leaders score their own decisions and realize how many they’re holding onto, and why
Designing micro experiences turns out to be much harder than it looks; Jimmy describes it as something close to a PhD-level design skill when the targets are seasoned executives or deeply rooted norms
Scaling Without Scaling Cost
The scalability claim for micro experiences isn’t about how long they run; it’s about how cheap they are to deliver and how small their administrative footprint stays. Jimmy has run programs of 30,000 people that needed just over one full-time person to administer.
Key points:
Programs run a minimum of three months and a maximum of six, with intentionality and engagement designed in from the start
The facilitator role is deliberately designed for moderately skilled coaches with about two hours of training, because certified agile coaches don’t scale to cross-functional transformations
Engagement design matters: opt-in versus opt-out, executive sponsorship, accountability mechanisms, and incentives all materially affect the 90% application rate Jimmy targets
Once an organization learns how to build these in-house, the cost runs around a tenth of traditional training
Democratizing Deep Development
The conversation closes on the purpose driving the work. Programs that consistently change behavior in lasting ways do exist, but they have historically been reserved for executives and high-potentials because they’re expensive. Jimmy frames the cost barrier as an equity problem, and micro experiences as one answer to it.
Key points:
The highest-quality development has historically been a privilege, available only to a small slice of any organization
Jimmy describes the goal as deep development at scale, getting the impact of high-touch executive programs to many more people
Anyone can start experimenting with the approach on their own; the real lift is in designing micro experiences well enough to drive sticky change
For organizations that want the full system, Peaq offers a multi-step certification path that ends with clients running their own programs under license
Hard Boiled Software is hosted by Dave Laribee.
