Author: Alexis

  • Why You Need to Start Being “Lazy” at Work

    Why You Need to Start Being “Lazy” at Work

    Most of us are addicted to over-delivering. We think adding more features, more slides, more planning, and more process makes our projects safer and our leadership more effective. We were taught in school that doing more gets you the A+.

    But what if your obsession with doing “more” is actually the exact thing holding your team back?

    The Source: Jon Kern on Le Podcast on Emerging Leadership

    In the latest episode of our podcast, I sat down with Jon Kern, an aerospace engineer turned software architect and one of the original co-authors of the Agile Manifesto.

    Jon didn’t help create Agile because he loved corporate frameworks. He helped create it as a pragmatic, lightweight defense mechanism against bureaucratic lunacy. Early in his career testing jet engines for the Defense Department, he realized that rigid, heavyweight processes (like trying to predict a year of R&D in advance) were worse than useless: they were actively destructive.

    The Reframe: The Strategic Value of “Laziness”

    We typically view laziness as apathy or a lack of drive. But Jon advocates for a different kind of laziness: Strategic Laziness.

    In development and leadership, being “lazy” means finding the smartest, smallest possible thing to build (or do) to get immediate feedback. It is a rebellion against doing too much work, too far in advance.

    When we over-prepare, we usually do it out of anxiety. We build massive plans to soothe our fear of the unknown. The signal hidden inside the urge to over-engineer is that we are afraid to test our assumptions against reality. Strategic laziness forces you to stop hiding behind bloated plans and start treating your requirements as hypotheses.

    The Leadership Application: Purpose vs. Process

    You cannot ask your team to be “lazy” and agile if they don’t know what they are actually trying to achieve.

    If a team doesn’t understand their core business purpose, they become mere order-takers. And order-takers will just blindly build every feature, tick every box, and follow every process, no matter how bloated it gets.

    Jon’s rule is simple: Start with a clear, 25-word purpose.

    When your team has a razor-sharp flag in the distance, they are empowered to exercise micro-judgments. They can look at a massive project requirement and say, “To achieve our purpose, we don’t actually need to build all of this yet. Let’s just do this tiny piece and see what the customer thinks.”

    Even in the modern frontier of AI and “Vibe Coding”, which Jon actively uses to automate rigorous testing and compliance, this discipline holds true. You can use AI to do the heavy lifting, but you still must “coerce” the tools into following sound engineering fundamentals. Agility requires a clear purpose and relentless consistency.

    The Practical Takeaway

    Mantra: “I can out-small anyone.”

    Whenever you are faced with a massive, ambiguous project, do not ask, “How do we get all of this done?” Ask, “What is the smallest, embarrassingly tiny piece of value we can deliver right now to get real-world feedback?”

    The Coaching Prompt

    Grab a notebook or bring these to your next 1:1. Answer honestly:

    • The 25-Word Test: Can you clearly articulate your team or project’s core purpose in 25 words or less?
    • The Bloat Audit: Where are you currently doing too much work, to too great a depth, too far in advance of actual feedback?
    • The Next Small Step: What is the tiniest, smartest thing you could test or build this week to prove (or disprove) a major assumption?

  • Agile, AI, and Engineering Pragmatism with Jon Kern

    Agile, AI, and Engineering Pragmatism with Jon Kern

    In this episode of Le Podcast on Emerging Leadership, I sat down with Jon Kern, aerospace engineer turned software architect and co-author of the Agile Manifesto.

    Jon shares his fascinating journey from testing jet engines for the Defense Department to pushing back against heavyweight, bureaucratic software processes.

    We explore the original intent behind the Agile Manifesto, the misconceptions that led to overly rigid frameworks, and how leaders can embrace the concept of “being lazy” to deliver true business value.

    Finally, Jon dives into the frontier of “Vibe Coding,” sharing how he uses AI to automate rigorous testing, compliance, and architecture without losing the foundational discipline of software engineering.

    🔑 Key Takeaways:

    • The Origins of Agile: Jon’s contribution to the Agile Manifesto stemmed from a deep frustration with one-size-fits-all, heavyweight processes (like MIL-STD-2167) that hindered research and development. The manifesto was born out of a desire for a pragmatic, lightweight defense mechanism against bureaucratic lunacy.
    • The Biggest Agile Misconception: Agile is not a recipe or a simple step-by-step framework. Jon warns against the industry’s reliance on rigid frameworks, emphasizing that true agility must be experienced and tailored to a team’s specific context, rather than simply memorized for a certification.
    • The Power of “Being Lazy”: In software development, being “lazy” means finding the smartest, smallest possible thing to build to get immediate feedback. It is a rebellion against doing too much work, too far in advance, and instead treating requirements as hypotheses to be tested with actual customers.
    • Purpose is Paramount: If a team doesn’t understand their core business purpose, they become mere order-takers. Starting with a clear, 25-word purpose allows everyone on the team to exercise micro-judgments, empowering them to propose smaller, faster, and cheaper ways to deliver value.
    • Leading in the Age of AI (Vibe Coding): AI is a game-changer for software development, but it requires strict engineering discipline. Jon shares how he uses AI platforms like Replit to build applications, but notes that developers must learn to “coerce” AI into following best practices like Behavior-Driven Development (BDD) rather than letting it write unchecked code.
    • Agile is Necessary, But Not Sufficient: To build great products, an agile mindset must be paired with solid engineering fundamentals: a clear purpose, a shared domain language, sound architecture, and relentless consistency.

    References

    Transcript

    Alexis: This is Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. Today, I’m joined by Jon Kern, an aerospace engineer turned software architect and a co-author of the Agile Manifesto. Jon is currently an agile consultant at The Adaptavist Group How do you introduce yourself to someone you just met?

    Jon Kern (Adaptavist): Like in a, let’s say formal busi- like a business setting or at a party at a friend’s house?

    Alexis: Let’s say, let’s say in a business setting

    Jon Kern (Adaptavist): Okay. Typically, like I was just in Nuremberg at the Business Agility Conference last week, could probably ask people there. I generally [00:01:00] Introduce myself probably as just a guy, just a developer, software engineer. Love to help build awesome products, help teams build awesome products. So probably mostly as a, just a guy, an engineer. I try… I will only reluctantly mention that I’m a co-author of the manifesto. If there’s a, some sort of pressing, I don’t have time to be in my humble, I have to, like I have to im- which is pretty ra- rare that I have to impress, impress somebody.

    Yeah I, tend to be just, I, ’cause I really am just another, person the good fights, [00:02:00] working, trying to help people. all

    Alexis: I, love that. And yeah, I, agree. I’m I, met, I met you a few years back at the Agile conference in in Dallas, I believe. And yeah, it felt like a, a normal interaction then. And I, I know a lot of people knew who you were, but that, that felt completely completely normal and completely cool.

    And and I felt you were very curious about what other people had in their, had in their mind. So that was very interesting to me. So you mentioned the Agile Manifesto. W- can you tell us what led to your contribution to the Agile Manifesto?

    Jon Kern (Adaptavist): I think my experiences [00:03:00] having a really a blessed career starting with Defense Department jet engine testing, working in, a job that some wonderful mentors. I still get together with Rich Thaler and every, pretty much every year. One of my first mentors, I would say. And also some really interesting, what you might call signposts of… I’m early 20s, right? So, you know, somebody in their 40s I’m, I remember thinking, “Yeah, don’t wanna be like this person that far into my career,” not liking my… So I had these great, wonderful opportunities to, see mentored and to see things I didn’t wanna [00:04:00] do, to be able to grow from there as an engineer. So I, four or five years of jet engine, cruise missile engine testing and, discovering a- the awesomeness of software to help do a job a three-hour job down to a few minutes I was bitten by the bug early on. And then went with another one of my former bosses, moved to a Defense Department contractor comp- company, and then I started a whole another that was about a 10-year career there with flight simulation and, again, heavyweight MIL- Standard-2167. So I started to get brush up against these heavyweight processes that made no sense with the kind of work we were doing. They might make sense for other types of work, but it was a one-size-fits-all big heavyweight process. So that led me down the path of [00:05:00] my personality is the kind where If it’s stupid, I don’t wanna do it. I think many times I probably should have been fired from some companies, including being a dishwasher and a pot washer and doing some things that I shouldn’t have. But somehow I learned better to forgiveness than ask permission. I was creating a lighter weight method, trying to…

    I’m a taxpayer too. Why should I just do this stupid process for a process sake? So it was an interesting journey that kinda led me to creating my own, what I would call, like a lightweight process to combat the lunacy of pretending you could estimate a year-long project for a research and development that was purposefully going to wander and learn, and that’s the whole point. a lot of things led me to be [00:06:00] very let’s say, vocal at the, at Snowbird about experience with heavyweight process. I also was working My a good… Yeah I, created my own company. My… I started working with Peter Coad. He was an o- became an object-oriented mentor, and then basically hired me away from my own company to help found another company, Togethersoft, together in the, late ’90s, early 2000s. We had a way of working there, feature-driven development, and a mantra, frequent tangible working results.

    So you could really looking back, ’cause the event itself was just, hey, it was fun. It was like drinking beer, you

    Alexis: Spectacular.

    Jon Kern (Adaptavist): And, writing a few things down and meeting people that I only read in books and magazines. Like, I was the, a younger person there. [00:07:00] maybe Adi and, I might have been the young the two youngsters. So, know, looking back it’s, easy to see why, know, people, process, and tools, which is kinda like the first value, it was something we… was a mantra we used at And then how I built my own lightweight defense mechanism process against the world that I was in for the government contracting. You can see the last the, three bullets. I learned contracts don’t help you. Better to get a good rapport with the customer. I learned a- as, as, good as you might be with a project plan, ’cause that’s… Back then as an engineer, I used Microsoft Project until I realized that was foolish on soft.

    So all those things l- you know, speaking of what led me to to the manifesto and the ideas that came out, it certainly feels like it was [00:08:00] tailor-made a, as a way to at least a lot of the learning that I had in my… I would say I was, like, halfway through my career, so to speak. So yeah, it was a amazing opportunity to somehow get all that, kind of a resonant frequency with others in the room, that these things, y- were across many of the other folks were the co-authors.

    Alexis: Yeah. Excellent. So now we are roughly 25 years later what are some of the mi- misconceptions about Agile you encountered over time?

    Jon Kern (Adaptavist): Yeah, I think the, blessing and the curse of the manifesto looking back is [00:09:00] It’s an extremely, what I might now call po- a post-conventional way to make your meaning about how to do software development. And, I say that because one of my good friends Daniel Markham, at one point said, “Imagine being a fresh out from college, being like on a software team, being told to go read the manifesto.” Especially the, first just the values page. The principles might get a little simpler in some… yeah, what do what are, you supposed to do with that? Wh- where do I start? Oh, good question, right? That’s that’s definitely a blessing and a curse that it’s, super powerful if you it and understand it, but super [00:10:00] ambiguous and unclear if you don’t. Which was a, pretty good eye-opener for me that, because I didn’t have to memorize it. I, lived it. I do… And that’s, the experience you have, so to speak if you work with me on a team, I like to think you get to experience Agile. ‘Cause y- I say you almost have to experience Agile.

    It’s not a recipe. It’s not a it’s not a st- a step-by-step process, and I think that’s the biggest… I don’t know if it’s a misconception or just human nature to want an easier way. Okay, that’s really hard. What’s an easier way? Things like frameworks- Scrum, or God forbid, SAFe or something like that, which reminds me of back in the day, things we were fighting called Rational Unified Process. but I think [00:11:00] what happened over time, ’cause I literally checked out near… checked out of the Agile community as I saw the- The penchant for trying to simplify and assume you can just learn this framework and get a, certification in a couple of days and somehow be agile. I was like, nah, not interested in this. Goodbye. I’m just gonna go work with teams and have fun and help help explain through action and involvement how, what I think agility is.”

    And I still do that at, Adaptivists we, happily work with teams to help experience what agility might be. And so yeah, I think that’s [00:12:00] the biggest misconception is people fell for… I don’t know, I’m not gonna say it’s snake oil. In the right hands, any almost any process will work and, especially if you make sure you tailor it to your world. But making it seem like you just have to follow these five steps and you’re good I think sold a lot of management and executives and businesses down a river of that it’s… No it’s really that simple. Even though, Agile, you can kinda consider it to be simple if you get it, doesn’t mean it’s easy. So I, think probably the biggest misconception that led to a bit of a backlash. And ano- another thing happened while I was away from, the [00:13:00] community. I kinda got brought, back in to the Agile Alliance maybe one, one gathering before the Dallas one or, a couple.

    I went to a few ’cause they invited me. but I remember one of the first ones I went back to, I was like, “What happened? What- why is there nothing technical in this conference?”

    Alexis: Ooh.

    Jon Kern (Adaptavist): whatever happened to, don’t know, testing, visit or the whole XP. I said I’m, an engineer by training, so all of a sudden it was all about coaches and all this. Yeah, you need to care about the soft skills, and you need to care about that, sort of thing, but it was suddenly what happened to the real- the main thing? The ma- the main thing is trying to produce value and put smiles on customers’ face in exchange for helping to pay my salary, and that all seemed to go away.

    I was kinda like, “How come there’s no technical sessions? Why?” But or at least [00:14:00] very f- few

    Alexis: Yeah. Yeah, and it, I, I feel that the first sentence of, of the manifesto was the very important one about we are uncovering better ways of developing software by doing it and helping others do it. I, I have the feeling that that one was very important. It could be only that one even.

    Jon Kern (Adaptavist): Yeah, I, it’s funny when I look back because nobody knew this was gonna take off. It’s we’re just just passed the 250th anniversary of the founding of our country and Declaration of Independence and the f- the, amazing thing that happened when a relatively few number of people farmers and lawyers and doctors came together and created a document in hindsight is amazing. And in a very, [00:15:00] extremely humble way I, feel the same thing happened there. It was this magical cauldron that produced a pretty small set of words when you, get right down to it. And so now when I take that first page, the values page as we come, I’ve come to call it, I point out the preamble, and I point out, look at the humility in there. To your point it’s active voice ’cause I still– I’m still trying to figure out, like with the advent of AI I’m a, wholly addicted to vibe coding and I just did a pretty fun workshop in Nuremberg. It’s, a whole game changer, but you better have a good solid understanding of not only engineering practices and principles, but also what does it mean what does agility mean?

    What does it… but that preamble [00:16:00] is so true that we’re still uncovering. And how do we do it? Not by reading about it, by doing it and experiencing it, having enough humility and ability to have… I think part of it is the it, depending on how you make your meaning as a human the, kind of vertical development of the side of the brain, not the skills horizontal.

    But you may or may not be able to absorb even experiencing it, to have the perspectives, be able to step back to see what are we learning, what’s going on. I’m following the process. Why is it different? I guess we need to predict better or plan more, right? When the whole aspect of that simple, humble phrase is you’re right a really important one.

    And I would say the f- the very first value, the [00:17:00] people people and process over tools, but it’s individuals and interactions over process and tools. So that also, you could say, just that in and of itself is almost sufficient. ‘Cause the other three it’s details, so to speak. But if you had, the first one individuals and collaboration over a contract or you, could make over a project Gantt chart. You you could, also make the case there that the preamble, like we’re still doing it, you’re never done. Sorry it’s it’s it’s the hardest Way to practice because you’re constantly have to be on the vigil. A little bit like lean, where two-second lean. I wonder if I can get this process just two seconds faster, right? It’s that same kind of never– seemingly never-ending quest for the ability to, [00:18:00] improve and get better and do it more effectively. So yeah, it’s, I’ll also say the other thing that the, I don’t know what you call the thing at the bottom, the postamble, preamble, the values, and then the the whole bit about the left over the versus the right. That’s also a big dose of humility ’cause

    Alexis: Yeah

    Jon Kern (Adaptavist): Doesn’t say… I’m a documentation nut.

    I love I I’m, always forcing people to take their knowledge that they post in Slack or on WhatsApp or on a Google Doc, and, “Nope, let’s get it into our knowledge base in Confluence or something like that.” I’m always forcing because what we do is a lot more complex than, I think people understand. So yeah it’s important to notice those two things, I think to your point

    Alexis: Yeah. Yeah, I have [00:19:00] the feeling that those are polarities. And at the time it was written, the, the pendulum was really tilting towards one side. And and the goal was not necessarily to pull the pendulum completely on the other side, but to say, “Hey, hey, let’s find let’s find the right balance,

    Between those things.”

    That’s,

    Jon Kern (Adaptavist): a great way that’s a great way to visualize it cause it’s the right balance for your context and it’s gonna change and that’s the point is you have to intentionally the i the of the things that the manifesto can do is bring attention to different things you may or may not think about All of those values are attention to these things And then to your point about where do we dial it for this project for this customer for this Even down to the feature so that’s a great way to visualize it is it’s really is like sliders And super highly regulated environment I might [00:20:00] bake in ways to actually capture more documentation and screenshot Who knows Because y it’s gonna be a more effective way to deal with something that’s super heavyweight but it just has to be All right how can I make it cost less and suck less it’s kinda One of my other mantras is be lazy

    Alexis: That’s, that’s an interesting one. G- give me an example of being lazy that is effective

    Jon Kern (Adaptavist): Yeah even what I was just making up in my mind right there about I I remember way back in the day 95 to 98 cutting my teeth and architecting IBM’s manufacturing execution system as an outside consultant in a company that we got the contract to do it was discrete manufacturing and one of my buddies from the I left my DoD company that time and formed my own company and did [00:21:00] this big IBM project my other buddies had left my the DoD company and was working in pharma and similarly manuf manufacturing but that wasn’t discrete It wasn’t making computers it was the more challenging aspect of making medicines and drugs and things that had batches almost like hamburgers right You got a batch of meat you have to be able to All kinds of weird stuff And he said even have to track exactly did the screen look like how was it designed when something was being manufactured versioning out the wazoo So being lazy to me is what’s maybe a clever use of technology to make that suck less to put it bluntly like how do you do that like we’re gonna have the quality assurance people take [00:22:00] screenshots and document Ah screw that Now let me build a was actually just doing that just this weekend with a crazy thing that produced different images and I was like really to cut those out you know being lazy is I get a faster more effective cheaper way to do something that I would consider as mundane and tedious And it’s that sort of an attitude Also lazy is don’t so much work ahead of time Don’t most offensive offenses that teams make is doing far too much work to too great a depth of detail too far in advance of the need I’m talking about like re big requirements or ex excessive UX design or crazy stuff like you need to do just enough to get the frame [00:23:00] So that’s another aspect of no be lazy but the problem is that fights against everything we’ve been taught since children in school doing more is better And you know how I got five 100s in a row on the quizzes in algebra Woo I’m really good that is such disservice to an agile way of working you have to fight it And I often say I can outsmall anybody that has to do with what’s the tiniest thing that you can think of to build you might call it lazy no I don’t wanna build all that A cause I don’t believe it I don’t We don’t know as much as we think Let’s treat it as a hypothesis get some feedback sooner right All kinds of great things to that in my mind make perfect sense of why I’m being lazy so yeah I often try to tell people think of the smallest possible thing you could [00:24:00] to get feedback and then make it slightly smaller until you’re uncomfortable your level of uncomfortableness won’t be mine I I’m okay being embarrassed delivering something embarrassingly small Anyway it’s the point is to get skilled at getting less and less because it’s quite simply the truth that you can always add more if it was If you missed the mark You can never take back time you spent and energy you spent and you’ll never know if it was too much So that’s a to me the lazy But it’s also being smart But it’s a bit of a joke but not really It’s you hire somebody to do a specific very narrow job guess what you’re gonna get eight hours a day Eight hours of UX or eight hours I learned this in the DoD days Eight hours and what does a specification writer do Super tedious like mindnumbing words about how [00:25:00] is this ram air turbine supposed to be work just the spec writers were notoriously tedious and slow but anyway yeah that’s my

    Alexis: And it’s hard. I, I, can feel how

    hard it is, But the number of examples I had in mind when you,

    you talked about it, it’s wow. You, you mentioned business value because it was all about it, putting a smile on, on your users. How do you help teams to stay focused on that

    Jon Kern (Adaptavist): another great question So it’s a such an important topic that whenever working with teams [00:26:00] Especially trying to center it along something they’re trying to achieve Whether it was four groups that we were working with one of my good buddies at Adaptavist he’s on his own now but Jon Turley and I and another friend Tony Camacho we went to Florida last September run a multiday workshop with the Special Operations Command special ops Nothing secret just some software teams like four teams And each But after we did what I would call like a toy project to warm up to my very opinionated way of delivering software we did project that they brought So the In both cases you have to have a really good understanding of what are we trying to do And in Nuremberg in my AI two twohour AI workshop [00:27:00] Vibe Coding now that particular product that we wanted to build was an agile buzzword bingo game but in all those cases or if I’m working with a team delivering a benefits package for employee healthcare in the US case what’s the very first after we say hi and learn about each other but the first actual meaningful exercise is in 25 words or less what is your business purpose or your system purpose However you wanna think And teams we coach internally in Adaptavist what why are you here It’s a the funny movie Office Space the the Bob and Bob efficiency experts right what is it that you do here It’s humorous but it’s also so critical cause if and I’ll explain why Number one if you don’t know why you’re here what are we trying to do [00:28:00] a recursive I love learning a few things that apply whether it’s the full product idea that we have like buzzword agile buzzword bingo or a feature or an epic anything The point is understanding what we’re after what the outcome is what the I can’t say it raison d’être or whatever the reason for existence without that You might just be an order taker and you And anything will do A list of requirements will be huge You So the whole point is how do I get my entire team cause we all have brains many times the brains are better than mine I want everybody to participate in the being humble and being lazy because we have a flag in the distance We know what we’re trying to do again whether it’s a feature [00:29:00] set or the whole product that you can exercise micro judgments I got smart people I don’t wanna have to think it all up myself I said I wanna just put out there this is what we’re trying to do and be surprised and elated when an engineer might come and or a UX person and anybody can now come and offer up the smallest possible thing to get the most value Maybe I can’t do it all but maybe all isn’t necessary right Isn’t that what you say Jon That we shouldn’t We should treat the requirements as hypotheses that someone might want this So it’s this weird really holistic way of learning how to do just enough And I think sim You can see how much your little tiny question that’s the whole point is that little tiny what is the purpose fans into the whole thing that we’re doing I won’t need to architect that yet I don’t [00:30:00] need to build this yet I don’t need the UX I don’t need the f driven scenarios yet for those things that we might not So it’s all about giving us the chance to deliver more sooner and for less cost and get feedback right So it’s a strange selfreinforcing loop that without that you’re an order taker You don’t have nearly the chance You might have to invent it in your head and wonder why they’re asking for this I don’t know I’m just a coder you will be replaced by me and Replit I will replace you if I can’t if you’re not gonna use your brain andor you’re not allowed then you need to replace the process cause you need to ask that question right from the start in everything you do So that’s a brilliant question

    Alexis: Just enough to get feedback to deliver some value

    In[00:31:00]

    Jon Kern (Adaptavist): And as much as possible have customers in the room when you get some something to validate with them even if it’s early look over their shoulder I might have a little I’m not sure the UI feels right come look All of that is just shortening the Often say mind the gap in time between doing something and getting feedback So yeah it’s all it’s really s in my mind really simple It just appears to be really hard for a lot of teams to get there or think it can really be that simple Or it is harder to try to get customers to talk to but the simplistic secret Is yeah involve your customers

    Alexis: Yeah. So you mentioned AI twice, so I, I need to ask about it. How should leaders consider AI

    in their organization?[00:32:00]

    Jon Kern (Adaptavist): I’ll just narrow it down to the way that I’m thinking about in the context of building software there are I’ve seen There was a cool exercise I w I spoke in in Belgrade Serbia at a Agile conference maybe two years ago and there was a pretty cool little workshop that he ran with kind of AI at the front end and requirements And I’m a behaviordriven development I will write my Jira issue I’ll put in there Gherkin given when then Cause it’s a super awesome fast and concise way to write a requirement To say what are the preconditions What’s the person doing What do they expect Cool Versus big paragraphs and So couple that with some maybe some domain models as necessary depending on where you’re at and some U UI [00:33:00] designs maybe I saw how rapidly that w I forget the tools that he he had us work in some teams and probably download something on our phone or the computer I don’t remember But some kind of a you know bot the AI thing that produced driven BDD It seemed a little excessive That was my takeaway was okay I’m thinking in my head Is that good It’s a lot of volume I wonder how much editing I have to do versus what if I just do it like I do now do it myself So that was my first experience with kind of a front end part of the process recently I’m working with a team actually just a [00:34:00] guy and it was funny He wanted something that he obviously asked AI to produce the requirements and it was a fairly interesting technical aspect around solidifying how can you produce something like a certification that’s unique and protected and u uniquely identifiable nobody can copy it and cheat and pretend Like he It’s oh that’s pretty cool But I could he used some AI tool and built out and then he dumped it into Jira epics and issues oh my g now you’re really getting on my nerves right And s and so this is another interesting facet was Part of the process of taking an idea that you need to build out is working with [00:35:00] it So just cause I can get a tool to spit all this stuff out including BDD including the specs including use this API or whatever this I felt that was taking learning opportunity for me to dive into that So I basically didn’t r didn’t overreact just pushed it aside took the real requirement which is just what a customer might ask and then as an engineer figured it out And sure largely the AI is not wrong in terms of things to do it completely missed the whole part of the learning process if you just took it face value care what it said or didn’t understand it So that was another interesting factor of I’m not so sure that’s I know that’s not that good Another funny [00:36:00] I was speaking in Poland in Gdansk with Anita from Network Perspective who does deve you know developer experience surveys and what was funny is we were preparing one of her slides cause when you do a DevX survey you can get anonymous you get anonymous feedback you get comments and she tau taught me long ago cause we used the DevX stuff at Adaptivist taught me long ago that comments are gold when people are like Err Okay I got something to say

    Alexis: Hmm.

    Jon Kern (Adaptavist): And this guy w- was hilarious. He was complaining about just what I told you about yeah, we get the the architecture team s- weighs in on something, and then dumps this giant thing on top of us, and they don’t have to do it.

    They’re just sitting in a corner and pontificating.” he was basically expressing the same kind of frustration that I had receiving that. [00:37:00] In answering your question so far the, things that I’ve seen on the front, eh- I’m on the fence about because it’s, I think, more important that more about where the lines need to be drawn in terms of what are you trying to do to elicit requirements from, users, to express them, how far sh-should you go into the sort of what I would consider the, details of writing some specs, so to speak BDD. And then certainly the architecture, how deep should you go into producing that? ‘Cause the team’s basically the ones responsible and that’s l- maybe work with them, let… Anyway, that, there’s that. So now to the vibe coding part. Yeah. This is the most wild thing. learned about it [00:38:00] when I was flying to Special Operations Command in September My normal mode was I have a Git repo, download this little toy project, get yourself set up. That’s basically a BDD, TDD kind of an environment. But still, was like, “Ah it’s 2025. There’s ways to do development in the web without having to download anything.” So I’m like, ah, I know I bookmarked some things, ’cause I always bookmark more than I ever seem to find time to read. but I’m like, oh, I know, what was it? And I stumbled on Replit replit.com. and lo and behold, just maybe two weeks prior to that, they had released Agent 3. So I’m like… I watched a couple videos that were on an older agent. I was like, “Eh,” and then I thought, “I’ll try it.” Sure enough, there’s an environment that’s in the web it’s in your browser, and you can ask it to build stuff. [00:39:00] So by the time I landed I’d already built a little app that it’s basically Conway’s Game of Life, so it’s a funny cellular automata game. But I I’d learned that I could build that and this tool was gonna work, that it took away all the, they have to install things. Now I just needed to coerce it, ’cause it’s a little…

    This, is something I’ve learned over the, ensuing months, that it will happily go f- speaking of do the tiniest thing that you can or maybe slightly less, that it’s not how, not how it operates. It’s “Whoa, Nelly, what are you doing?” It’s ah. I had to learn how to actually coerce it to do BDD.

    It was pretty funny. I don’t I don’t know how much time your podcast has. We’re probably turning this into two podcasts. But it was really funny to learn [00:40:00] how hard it was to get it to stop to write a failing test. And I’ve, I’m now able to do that pretty successfully, it was not easy because it’s just too eager, so I’ve learned also how to get it to be curious and how to get it to s- maybe supply some options. But you can drive it, like what I did with the Vibe Coding workshop in Nuremberg, was be very BDD. Write a failing test, write a BDD. They, I took them through the normal Jon Kern opinionated way to to from a fuzzy idea to something out the door, and we actually produced something and you can run it, and it’s funny. But yeah the, idea is that the calculations about things that I can now do because of Vibe Coding has completely changed my approach in terms of I will create amazing [00:41:00] things that I never would do if I had to write them hand. I for many years, I’ve had a, for almost probably two decades, for fighter- firefighters and emergency whether it’s for y- small rural departments or our biggest one is Arlington, Texas, which is 17 stations, so it’s pretty huge. or big pharma companies and universities, stuff like that. So it’s a it’s a no joke way to try to protect lives and property. And so I’m, I used it to migrate from up- update the Rails app from the current production to the new version using Replit. And I learned I [00:42:00] could do things like web penetration testing security audits, GDPR compliance, SOC 2, name it. was able to, i- instead of just doing it off to the side, I actually built essentially security audit control panel with a Kanban board and the findings. And then over time started knocking down the findings as I was making the staging before we got to production. never have done that ’cause it was al- when I’ve done it in the past, it’s been manual. might have a spreadsheet, you might record it and do some things. And anyway, I could automate the penetration testing. I could automate much of this, could even have Replit refer to, “Hey, all right, let’s tackle finding number 13.” Or “Tell me about your infrastructure in the context of these, compliance regulations.” So that kind [00:43:00] of thing is wild. I have code quality built in with RuboCop the ability to also show the quality metrics for super admins. Don’t get to see it, but the super admins do. And I, often expose the end-to-end testing, the BDD, to super admins as well, so you can actually see the test results gr- it’s all green or not. I’ve built synthetic testing to run every so often and to holler if something’s… all kinds of insane things that have long built up in my repertoire.

    Some of these things I did with teams in, the past ’cause I could. But so it’s, an amazing world that in the context of what you might need in your product teams, can do an amazing amount of rigor [00:44:00] if you need to, and automate it. So again, that’s the being lazy. don’t wanna have to do this by hand.

    So I don’t know. That’s a lot of answer to a s- pretty simple question, but I think this is a brave new world. It’s unbelievable what you can do you, need to know. blessed with having a long career and knowing the hard way to do things. So I know what architecture looks…

    I know the things that I should worry about. With other, teams you can, now take some of those non-functional requirements and turn them into things that maybe we can bake into the product to satisfy some of those needs. And at, the touch of a button, if a new client, like a major ele-elevator company that’s hosted in Europe wants to use this firefighting app, and they want to do a a [00:45:00] security audit type thing, “Oh check this out.”

    Alexis: And it’s-

    it, it’s funny because I hear also things you said before about quality by design and solid architecture in your answer

    about how to use AI in, in an effective way.

    So it’s it’s very interesting

    Jon Kern (Adaptavist): Yeah. It’s it’s a brave new world. It’s exciting.

    Alexis: Excellent. What is one question I should have asked you that I did not?

    Jon Kern (Adaptavist): Oh. No th-those are fascinating, really good questions. And I I think it it allowed me to touch on quite a bit. One of the, [00:46:00] one of the details that maybe you could’ve asked was is the manifesto, you know the, phrase about n- necessary but not sufficient? I would say that’s a good way to put it ’cause it’s, In the age of AI, I think it’s so important to really understand what it means to act with agility and have that that, different way of thinking. and it’s not sufficient, Scrum’s not sufficient or safe or anything. My engineering background can’t help but have constantly bled through my my whole career in that, my holistic approach is a lot about six fundamental aspects that you gotta have going on. [00:47:00] touch on some the, purpose and just enough requirements and what I would consider the domain.

    What is the language of the world that is the problem we’re trying to solve? Let’s, not invent it, let’s use it and make that another… It’s another lazy approach even though it looks like I’m doing excess. Man, why are you drawing some of these funny squares with names? Because I want everybody to use the right terminology and to more quickly speed up our ability to make sure the thought bubble’s above our head when the customer says something, or the architect, or the database person or the UX. It’s the same, it’s the same concept, right? That’s lazy, but also being effective. And then the, what architecture we’re gonna use, what sort of patterns, and then doing it in a very consistent freq- fre- I’d rather you be consistently poor ’cause you can fix that, right? I… [00:48:00] Like my BlazeMAR version two, so to speak, done in MongoDB and Rails 4.2, cons- really consistent, covered with tests, and it makes it easy to move it into the more modern Rails 8 and the more mo- I, switched to PostgreSQL, but the, consistency is a savior because it’s not like it looks like three different teams built it.

    I’ve worked on systems like that. Oh, they’re… Why are these same looking things done differently? Oh, man, it’s a long story. So that, and then plus run it with an agile mindset. So I think, is also often missing the, art of engineering behind the systems you’re building in an agile way. So there, now I’ve said it.

    Alexis: Excellent. Thank you. Thank you very much for joining the podcast.

    Jon Kern (Adaptavist): Oh, my pleasure.

    Alexis Monville-2: Thank you for listening this episode of Le [00:49:00] Podcast on Emerging Leadership. I hope you found today’s conversation as insightful and inspiring as I did. If you want to dive deeper into the topics we discussed today, you can find the full episode transcript and all the references we mentioned by visiting alexis.monville.com.

    Leadership is a continuous journey and is one best shared with others. If you took away something valuable from today’s episode, please take a moment to share it with a friend or two who might also benefit from these insights as they navigate their own leadership path. Until next time, keep learning, keep adapting, and keep leading. I’m Alexis Monville, and this has been Le Podcast on Emerging Leadership.

  • The Empathy Trap and the Responsibility Myth

    The Empathy Trap and the Responsibility Myth

    I was on stage in Lyon last week at the Tech’Work conference, talking about a concept that radically shifts how we build teams.

    We were discussing the “Above the Line / Below the Line” framework. When we are below the line, we are in survival mode: defensive, closed, and committed to being right. This is biology, not a character flaw. It’s normal. But when we pause, breathe, and step above the line, we choose a conscious response: open, curious, and committed to learning.

    The audience was highly engaged, mapping out the behaviors of both states. But during the interactive session, two brutally honest comments from the audience hit the floor like lead weights:

    1. “Too much empathy is bad because you just end up doing all the work in place of other people.”
    2. “Some people just don’t want to take responsibility.”

    You can practically hear the exhaustion and resentment dripping from those statements. If you’ve ever led a team, you’ve probably felt both. We are told to be “empathetic” and “empowering,” but the reality often feels like we are just babysitting.

    So, what is the signal hidden in this frustration?

    The Source: The Drama Triangle and Unconscious Commitments

    To unpack this, we need to look at two heavy-hitting psychological models.

    First is the Karpman Drama Triangle. When we drop below the line, we often fall into three roles: the Victim (powerless), the Persecutor (blaming), or the Rescuer (saving the day).

    Second is the concept of Unconscious Commitments from the Conscious Leadership Group. Often, the outcomes we complain about the most are the exact outcomes our hidden behaviors are perfectly designed to create.

    The Reframe: Friction as a Signal

    When we complain about empathy and responsibility, we are misdiagnosing the problem. Here is the reframe:

    The Empathy Trap is actually a Boundary Problem. When the leader in Lyon said, “Too much empathy means I do all the work,” they were describing the Rescuer role, not empathy. Empathy is understanding someone’s struggle. Rescuing is doing their work for them to alleviate your own discomfort with their struggle. Over-functioning for your team isn’t a surplus of caring; it is a deficit of boundaries.

    The Responsibility Myth is actually a Mirror. When we declare, “Some people just don’t want to take responsibility,” we have slipped into the Victim role. We are blaming their character rather than looking at the system. The hard, transformative truth is recognizing our own unconscious commitment to the dynamic. If your team isn’t stepping up, what is the payoff for you? Often, it’s the ego-boost of being the “indispensable fixer.”

    Leadership Application: Evolving the System

    Leadership is a property of the system, not a personality trait. If people aren’t exhibiting leadership, the system is actively preventing it.

    To create the conditions for leadership to emerge, you have to stop playing the Rescuer. Yes, some individuals, bruised by previous micromanagers or toxic cultures, will need time to trust that taking a risk won’t get them fired. They need proof.

    But you cannot provide that proof if you keep doing their work. You have to step back, establish firm boundaries, and allow them to feel the natural friction of their role. You must accept that an old version of your leadership, the one that swooped in to save the day, is no longer useful. It got you here, but it is actively sabotaging your team’s growth for the future.

    A Practical Takeaway

    Empathy without boundaries is just enabling. You cannot rescue someone into taking responsibility.

    The Coaching Prompt

    Grab a notebook or open a blank document, and ask yourself these questions about your current team dynamics:

    • Where am I confusing empathy with doing the work for someone else?
    • If I am complaining that my team won’t take ownership, what is my unconscious commitment to being the “fixer”?
    • What is the “payoff” I get from a team that constantly needs my help?
    • What is one clear boundary I can set today to shift the system from enabling to empowering?
  • The 3.5% Rule: Why “Burning Platforms” Are Burning Your Best People

    The 3.5% Rule: Why “Burning Platforms” Are Burning Your Best People

    “Get on the bus or get left behind.”

    “We need to build a burning platform.”

    “If they don’t like the new direction, they know where the door is.”

    How many times have you heard these phrases tossed around during a corporate restructuring, a messy pivot, or a sudden round of layoffs? We’ve been conditioned to believe that driving organizational change requires a kind of executive shock-and-awe. We issue top-down mandates, weaponize performance metrics, and use the unspoken anxiety of the next economic downturn to force compliance.

    We call it “driving alignment.” Let’s call it what it actually is: corporate coercion.

    We use these heavy-handed tactics because we assume force is the most efficient way to get results. But modern history, human psychology, and data tell a completely different story.

    The Source: 100 Years of Uprisings

    On a recent episode of the Hidden Brain podcast, political scientist Erica Chenoweth dropped a data-backed bomb on our collective assumptions about power. Chenoweth studied over a century of global revolutions and insurrections to determine what actually forces a system to change.

    Her research revealed two staggering facts:

    • Non-violent movements are twice as likely to succeed as violent ones.
    • The 3.5% Rule: No government or regime in her data set failed to change once 3.5% of the population became actively, visibly engaged in the movement.

    Chenoweth also uncovered a dark tactical truth. Authoritarian regimes intentionally use violence and intimidation not just to hurt their active opponents, but to terrify the “neutral middle” of the population. The goal is to make joining the movement look so dangerous that the average citizen decides to stay home and stay quiet.

    When we use coercive language, tight ultimatums, and fear-based pressure in business, we are running the exact same autocratic playbook. And it backfires beautifully.

    The Reframe: The “Neutral Middle” is Your Bedrock

    When a new initiative drops, leaders tend to divide the company into two camps: the enthusiastic early adopters and the “resisters.” Anyone who doesn’t immediately drink the Kool-Aid is viewed as passive, checked out, or a barrier to progress.

    That is a short-sighted leadership blind spot.

    Let’s reframe the emotional signal of the “neutral middle.” These employees aren’t lazy, and they don’t hate growth. They are corporate survivors.

    They have deep institutional memory. They’ve watched three different “transformations” come and go under different leaders. Their neutrality isn’t a lack of commitment. It is a healthy mechanism of self-protection. They are trying to shield their energy, their focus, and their daily output from a chaotic management wave so they can actually do the work.

    The neutral middle has good intentions. They are the essential bedrock holding the business together while executives play with new frameworks. If you treat their caution as a threat, you will push them directly into active resistance.

    Leadership Application: How to Activate Your 3.5%

    If you want real, sustainable evolution in your organization, you have to stop trying to force 100% compliance through fear. Instead, you need to attract a critical mass.

    • Ditch the Coercive Language: Eliminate phrases that imply people are disposable if they don’t instantly fall in line. Fear produces superficial compliance, but it utterly destroys the psychological safety required for actual innovation.
    • Build a Cross-Functional 3.5% Coalition: Your critical mass shouldn’t just be the executive team or a specialized squad of “change champions” who look like corporate cheerleaders. Your 3.5% must be a micro-coalition across all levels and roles. Find the informal culture carriers: the quiet senior engineers, the respected front-line managers, the operations experts. If they buy in, the system shifts organically.
    • Lower the Cost of Entry: Dictators hate humor and flexibility because it strips away their power. In organizations, instead of high-stakes mandates, use what Chenoweth calls “dilemma actions”—lightweight, low-friction experiments. Invite teams to try a new process for just two weeks as a trial. Keep it conversational, flexible, and iterative.

    When you make the change safe, low-risk, and genuinely collaborative, the neutral middle will naturally lean in. You don’t need to drag them onto the bus. They will walk over to see why it’s worth riding.

    A Practical Takeaway

    Mantra for the week:

    “Compliance can be forced; commitment must be attracted. Stop hunting for resisters, and start building your 3.5%.”

    The Coaching Prompt

    Ask yourself or your leadership team these questions this week:

    1. Look at your current top-priority initiative. What coercive language or fear-based pressure (implicit or explicit) are you using to drive it forward?
    2. Who are the informal, trusted influencers in your organization, outside of the executive team, who need to be part of your critical 3.5%?
    3. How can you reframe the skepticism of your neutral team members? What valuable thing are they currently trying to protect?
  • Why your brain freezes when the spotlight hits

    Why your brain freezes when the spotlight hits

    “Hey, what are your thoughts?”

    It happens in almost every meeting. You are sitting there, minding your own business, when a colleague or executive throws a conversational hand grenade your way.

    Suddenly, the spotlight is on you. Your heart rate spikes. Your brain frantically scrolls through every piece of data you’ve ever acquired, trying to find the “perfect” thing to say. And when you finally open your mouth, what comes out feels less like a strategic insight and more like a word salad.

    We look at people who are effortlessly articulate in these moments and assume they possess a rare, genetic gift. We tell ourselves, “I’m just not good on my feet.” But that panic isn’t a sign of incompetence. It’s a structural failure.

    The Source: Why Your Brain Freezes

    In his book Think Faster, Talk Smarter, Stanford communication expert Matt Abrahams highlights the real culprit behind our impromptu speaking anxiety: Cognitive Load.

    When you are put on the spot, your brain is suddenly forced to do two incredibly difficult things at the exact same time:

    1. Listing: Generating the raw content (the facts, the ideas, the data).
    2. Sequencing: Deciding the order in which to say them.

    It’s the mental equivalent of trying to bake a cake while simultaneously writing the recipe from scratch. Your mental RAM maxes out, your internal system crashes, and you resort to “umms,” “ahhs,” and rambling.

    The Reframe: Structure is Freedom

    Here is the shift: Stop trying to think of what to say, and start choosing how to say it.

    That sudden spike of adrenaline you feel when put on the spot isn’t a bug; it’s a feature. It is raw energy looking for a container. If you don’t give that energy a boundary, it turns into anxiety. But if you give it a framework, it turns into focus.

    As Abrahams notes, structure sets you free. When you choose a structural map before you start speaking, you automate the sequencing part of your brain. This frees up 50% of your cognitive capacity to focus entirely on your message. You don’t need a silver tongue; you just need a track to run on.

    The Leadership Playbook: 3 Frameworks to Lean On

    The next time you are caught off guard, do not just start talking. Take a breath, silently pick one of these three structural blueprints, and fill in the blanks:

    1. The Everyday Anchor: What? So What? Now What?

    This is the undisputed heavyweight champion of impromptu speaking. It works for project updates, giving feedback, or answering a sudden question from a client.

    • What: State the cold, hard facts or the current situation.
    • So What: Explain why this matters. What is the impact on the team, the budget, or the timeline?
    • Now What: Define the immediate next step or call to action.

    2. The High-Stakes Pivot: Challenge – Opportunity – Resolution

    When things go wrong and everyone looks to you for answers, use this to reframe a crisis into a strategic moment.

    • Challenge: Acknowledge the problem or obstacle directly without sugarcoating it.
    • Opportunity: Pivot to what can be learned, or what new door this challenge opens.
    • Resolution: Propose the definitive action step to move forward.

    3. The Vision Builder: Past – Present – Future

    Perfect for milestones, kicking off unexpected initiatives, or when you need to align a team that has lost its bearings.

    • Past: Where did we start? What is the context?
    • Present: Where are we standing right now? What is the immediate reality?
    • Future: Where are we going? What does success look like?

    The Practical Takeaway

    The One-Second Blueprint: The moment you are put on the spot, pause for one full second. In that silence, whisper a mantra to yourself: “I am doing a ‘What, So What, Now What’.” Deciding the structure before you open your mouth is the difference between wandering aimlessly and leading with authority.

    The Coaching Prompt

    Bring these questions to your next reflection session, or use them to coach a team member who struggles with visibility in meetings:

    1. Where do I ramble most? In which specific scenarios (e.g., upward management, peer debates, client pushback) do I feel my cognitive load redlining?
    2. What is my default defense mechanism when caught off guard? Do I over-explain with data, shut down and say too little, or pass the mic to someone else?
    3. How can we build a “structure-first” culture on our team? How can we use frameworks like What? So What? Now What? in our async updates or daily standups to save everyone’s mental RAM?
  • How to escape the mental maze of rumination

    How to escape the mental maze of rumination

    Let’s talk about the lie we tell ourselves when we’re stressed:

    “If I just think about this problem for another three hours, I’ll finally solve it.”

    We replay past conversations like we’re a director trying to edit a bad movie, or we project into the future, convinced that worrying is just “proactive preparation.” We convince ourselves that this mental gymnastics is useful.

    Spoiler alert: It’s not. It’s a maze. And the deeper you run into it, the harder it is to find the exit.

    The Source: Thoughts are Weather, Not the Sky

    In her book Just a Thought, Dr. Amy Johnson introduces a liberating paradigm shift about how our brains actually function.

    As human beings, we are evolutionary marvels wired for survival. Your thinking mind isn’t trying to torture you when it loops on a mistake you made in a meeting last Tuesday; it’s simply trying to keep you safe.

    The problem is that your brain doesn’t know the difference between a physical predator and a difficult client email. It treats both as existential threats, flooding your system with thoughts designed to “fix” the danger.

    The Reframe: The Suggestion Box

    Here is the twist: Rumination isn’t a sign that you are broken; it’s a sign that your survival brain is working perfectly. The loop of worry is just an emotional signal. It’s your brain saying, “Hey, I care about this outcome, and I feel unsafe right now.” But just because your mind hands you a thought doesn’t mean you have to buy into it. Your brain is a suggestion box, not a dictator. Thoughts are not solid objects; they are transient energy. They only become a maze when we grab onto them, unpack our bags, and decide to live there.

    Nothing external can lift you out of that maze. No new strategy, no extra data, and no amount of reassurance. The exit is entirely internal: it’s realizing that a thought is just a thought, and you have the power to let it pass.

    Leadership Application: Stop Time-Traveling

    In leadership, staying stuck in the maze is a quiet productivity killer. When we ruminate, we aren’t leading; we are time-traveling.

    • We are either in the past, trying to manage a reality that has already occurred.
    • Or we are in the future, trying to control a reality that doesn’t exist yet.

    When you are trapped in the past or the future, you are completely unavailable to the people you are leading in the present.

    Letting go of the thought loop and returning to the room takes practice. It feels counter-intuitive because your brain tells you that dropping the worry means you’re being irresponsible. But true human-centric leadership requires the discipline to say, “Thank you, mind, for trying to protect me. But I am choosing to be right here, right now.”

    A Practical Takeaway

    The Leader’s Mantra: “It’s just a thought. It doesn’t need a meeting.”

    The tl;dr: You cannot stop your brain from producing thoughts any more than you can stop the sky from producing clouds. But you can stop mistaking the clouds for the sky. Drop the debate with your own mind and anchor back into the present moment.

    The Coaching Prompt

    Ask yourself, or your team, during your next 1-on-1, these four questions to break the cycle of rumination:

    1. What is the actual data here, and what is just the “survival story” my mind is spinning about it?
    2. Am I actually preparing for the future right now, or am I just using worry to feel like I’m doing something?
    3. If I chose not to believe this specific thought today, what action would I take right now?
    4. What does my team need from me in this exact moment that I am currently missing?
  • Why AI Doing 90% of Your Coaching is the Best Thing to Happen to Leadership

    Why AI Doing 90% of Your Coaching is the Best Thing to Happen to Leadership

    Anxiety is creeping into leadership circles. A late-2025 study by The Conference Board suggests that AI can now handle up to 90% of routine career coaching tasks.

    I’ll be honest: the knee-jerk fear of obsolescence was exactly my response recently. A client told me she was looking into AI to scale coaching across her organization. In her company, coaching has historically been locked behind a velvet rope, available only to those who reach a certain hierarchical level. She wanted to democratize it.

    I was skeptical, but I investigated. And frankly, I was blown away. I found a platform that is incredibly effective if you want your people to practice soft skills, like navigating a difficult conversation with a colleague, or nailing a sales pitch, rather than practicing on actual prospects and customers.

    My initial fear quickly gave way to a counterintuitive observation: AI isn’t here to kill human coaching or leadership; it’s here to save us from our own transactional mediocrity. The algorithm is forcing a brutal but necessary question: If a machine can do my job, was I operating like a machine?

    The Framework

    The Integral Institute offers a brilliant framework for navigating this shift. They divide our development needs into two distinct lanes:

    • Top-of-Funnel (How do I think about this problem?): The realm of performative, cognitive coaching.
    • Bottom-of-Funnel (Who am I becoming as a leader?): The realm of existential, transformational coaching.

    Researcher Tatiana Bachkirova (HEC Paris) draws the absolute dividing line at “embodied empathy.” AI possesses flawless syntactic empathy: It knows exactly what words to string together to validate an emotion. But it has never lived through anything. It doesn’t know risk, loss, or mortality.

    The Reframe: The Signal Behind the Threat

    The fear of being replaced isn’t a bug; it’s a signal. It tells us we’ve spent way too much time in the “performative” zone: optimizing skills, running role-plays, and offering cognitive behavioral tweaks. AI excels here. It treats symptoms, optimizes metrics, and operates 24/7 without burning out.

    The positive side of this “threat” is liberation. By offloading habit tracking and cognitive prep to an algorithm, human leaders and coaches are forced to step up and do their actual jobs: navigating the messy reality of human identity. An AI can give you ten perfectly structured frameworks for delegating tasks, but it cannot help you when your nervous system is terrified of losing control.

    Leadership Application: The Hybrid Model

    In organizational life, this demands a shift in how we build and support our teams. The future belongs to a tiered, hybrid model:

    • Phase 1: AI as the Pre-Coach (Performative). The tool is used for onboarding, baseline skill assessments, and goal-tracking. It handles the “presenting problem.”
    • Phase 2: The Human as the Alchemist (Transformational). This is where you step in. You use the AI’s data as a baseline, but focus entirely on the human. You read the shifting energy in a room, spot systemic power dynamics that an algorithm is blind to, and possess the courage to sit in the discomfort of silence to force a real breakthrough.
    • Phase 3: AI as the Accountability Partner (Continuous). Post-breakthrough, the AI steps back in to provide the daily nudges and micro-learning needed to turn a transformational epiphany into a sustained habit.

    The Takeaway (TL;DR)

    If coaching and leadership are just about giving advice and tracking KPIs, the algorithm wins. If they are interpretive, embodied, relational practices meant to reinvent how a human operates in the world, you are irreplaceable.

    Leave the tasks to the bots; keep the identity for the humans.

    The Coaching Prompt: The Impact Audit

    Take five minutes before your next 1:1 or team meeting and ask yourself:

    1. Looking at my meetings last week, which ones were just information transfer or checklist tracking (things an AI could easily do)?
    2. When a team member struggles, do I rush to hand them a “solution framework” (bot mode), or am I capable of sitting in the discomfort and listening for the “unsaid”?
    3. Am I trying to optimize this person’s symptoms, or am I trying to help them transform their professional identity?

    P.S. If you are curious about the AI simulation tool I mentioned earlier—the one that blew me away for safe, scalable soft-skill practice—just reply to this email. I will gladly introduce you to the people behind the solution. Ironically enough, they are fantastic and very human.

    P.P.S. Speaking of doing the deep, human work: if you haven’t yet taken the Emerging Leadership Navigator from last week’s newsletter for a spin, consider this your gentle nudge. It’s designed specifically to help you map out your own leadership bottlenecks and identity shifts: exactly the kind of “bottom-of-funnel” inner work an algorithm can’t do for you.

  • Where are you hiding in your leadership?

    Where are you hiding in your leadership?

    We all have a default setting. When the pressure dials up at work, we unconsciously retreat into the tasks that feel safe. The visionary strategist ignores the operational messy work; the relentless executor ignores team morale; the empathetic people-pleaser avoids hard business metrics.

    We usually dress this up as “playing to our strengths.” But if we are being honest, it is often just a sophisticated way of neglecting the parts of our role that make us uncomfortable. The friction, exhaustion, or stagnation you might be feeling right now isn’t a sign that you are failing, it’s a signal that a critical dimension of your work is being starved of your attention.

    The Source

    More than a decade ago, I was working with a team that was hitting a wall. They were talented, but they were deeply misaligned on where their energy should be going. To help them map out their blind spots, I built a tool to force reflection on the neglected aspects of their roles.

    Over the years, I’ve refined this framework through individual coaching and team sessions. It works just as well for Individual Contributors as it does for Managers. I call it the Emerging Leadership Navigator.

    As you can see in the profile map below, it breaks your role down into four distinct compass points:

    • Business: The strategy, the market, and the value you are delivering.
    • People: The relationships, the culture, and the emotional intelligence required to lead.
    • Execution: The delivery, the grind, and getting things across the finish line.
    • System: The processes, the structures, and how things scale.

    The Reframe

    When you look at a radar chart like the one above, the instinct is to judge the gaps between where you are (Self-Perception) and what the role requires (Importance).

    But let’s reframe that gap. That negative space isn’t a character flaw or a permanent weakness. It is pure signal. If you are feeling overwhelmed, the gap is showing you exactly where the bottleneck is. The anxiety of feeling “behind” is simply the emotional signal that you have outgrown your current default setting and it’s time to intentionally step into a new quadrant.

    Leadership Application

    Leadership does not emerge by being perfect at all four dimensions simultaneously. That’s a recipe for burnout. Leadership emerges when you create the conditions for awareness.

    When you map your role using the Navigator, you suddenly make the invisible visible. You might realize that as an IC, you’ve been over-indexing on Execution while entirely neglecting the System that could make your life easier. Or as a manager, you might realize you are focusing so heavily on the Business that the People dimension is eroding. Recognizing this misalignment is the first step to correcting it.

    I recently decided to make this tool accessible to everyone by creating a simplified online version. You can read more about the philosophy behind it ​here​, and you can start your inquiry right here: The Emerging Leadership Navigator

    Note: I would love to hear your feedback on the tool itself, or simply hear how it made you reflect on your role differently. Hit reply and let me know.

    A Practical Takeaway

    TL;DR: You can’t navigate out of a rut if you don’t know where you are on the map. Mantra: “The friction I feel is the exact dimension of leadership I am avoiding.”

    The Coaching Prompt

    Before you click into the tool, ask yourself (or your team) these three questions this week:

    1. Of the four dimensions (Business, People, Execution, System), which one do I naturally retreat to when I am stressed?
    2. Which dimension am I currently avoiding because it makes me feel incompetent or uncomfortable?
    3. If I shifted just 10% of my energy this week into my most neglected dimension, what specific problem would it solve?
  • Why the coworker you can’t stand is your greatest teacher

    Why the coworker you can’t stand is your greatest teacher

    We’ve all got that one colleague. The one who sends our blood pressure spiking the second they open their mouth in a meeting. Our default response? We label them as difficult, passive, or overly rigid, and we vent about it to our work bestie later.

    But what if your intense frustration with them isn’t about their incompetence, but a massive flashing signal pointing toward your untapped potential?

    The Source: Daniel Ofman’s Core Quadrant

    Dutch management expert Daniel Ofman developed a remarkably intuitive framework called the Core Quadrant. In studying human behavior, Ofman noticed that our greatest interpersonal clashes don’t happen because we are fundamentally broken, but because we misunderstand the nature of our own innate strengths.

    As ​Ofman explains in this video​, we are all born with effortless core qualities, things like determination, flexibility, or caring. But as he says, “There is no light without shadow.”

    The Reframe: The “Too Much of Something Beautiful” Principle

    When we look at our frustrations through Ofman’s lens, the emotional signal changes completely. Let’s break down the anatomy of a conflict using a common leadership trait: Determination.

    • The Core Quality: You are naturally driven. Pushing projects across the finish line is effortless for you.
    • The Pitfall (Too much of a good thing): Under stress, your determination tips over into your shadow side. You become Pushy or Demanding.
    • The Challenge (The Antidote): To balance your pitfall, you need to develop its positive opposite. The antidote to being pushy is developing Patience. If you can be “patiently determined,” you become unstoppable.
    • The Allergy (What you despise in others): Here is where the magic happens. What happens when someone takes Patience too far? They become Passive. This is your Allergy. Passive people drive you absolutely insane.

    Here is the quote from Ofman that completely shifts this paradigm:

    “If people would only realize that whenever you see something in another person that you don’t like, by definition it is always too much of something beautiful, it would change the world.”

    That colleague who drives you crazy because they are “too passive”? They are just over-expressing the exact trait (patience) that you desperately need to develop.

    The Leadership Application

    In organizational life, we unconsciously look for our “Challenge” in others. The visionary founder partners with the methodical operator. The fiercely determined director hires the exceptionally patient manager.

    This complementarity is incredibly powerful… until the pressure hits.

    When stress enters the system, we retreat into our extremes. Suddenly, the determined leader views their patient partner as “lazy,” and the patient partner views the determined leader as a “bully.” You are allergic to their pitfall, and they are allergic to yours. It’s a predictable script that plays out in boardrooms every single day.

    The goal of human-centric leadership isn’t to eradicate the people who annoy you. The goal is to stop judging your allergy and start mining it for the underlying “beautiful” trait. You don’t need to become passive, but you do need to learn the patience that lives underneath it.

    A Practical Takeaway

    Your intense emotional reactions to others are rarely about them; they are a diagnostic tool for your own imbalances.

    Mantra: “My greatest frustrations are pointing to my greatest areas for growth.”

    The Coaching Prompt

    Grab a notebook and take 3 minutes to map this out before your next team interaction:

    1. Identify the Trigger: Who is the one person at work who consistently triggers your “allergy” (frustration, anger, eye-rolls)?
    2. Name the Label: What specific negative label have you placed on their behavior (e.g., passive, chaotic, overly rigid, wishy-washy)?
    3. Find the Beauty: What is the positive, “beautiful” core quality hidden beneath that annoying behavior? (e.g., If they are “wishy-washy,” the core quality is “flexibility”).
    4. The Integration: How can you integrate 10% more of that positive quality into your own leadership style this week?
  • The Rise of the Micro-Squad

    The Rise of the Micro-Squad

    We need to talk about process fatigue.

    If you’ve spent any time in modern corporate software or product development, you know the feeling. The endless sprint planning sessions. The two-week agile cycles that feel like a relentless treadmill. The daily stand-ups where a dozen people justify their existence to a Jira board.

    We often view this bureaucratic friction as an annoying “bug” of scaling a company. But what if it’s an emotional signal? That feeling of drowning in meetings and coordination isn’t a sign that you need a better Scrum Master. It is a signal that your teams are too big, your boundaries are too weak, and you are trying to manage uncertainty through surveillance rather than trust.

    Shape Up

    What if the approach developed by the team at Basecamp, and detailed by Ryan Singer in the book Shape Up, is the exact answer we need? While traditional Agile often relies on large, multidisciplinary teams (Product Managers, Scrum Masters, UX, UI, Front-end, Back-end, QA) passing tickets back and forth, Shape Up advocates for a radically autonomous, micro-squad: one designer and one or two engineers.

    Relevance in the Age of AI

    Why is this incredibly relevant right now? Because we have entered the era of AI. With AI coding agents handling more and more software development tasks, a two-person squad today has the output capacity of a larger team from five years ago. Bloated multidisciplinary teams don’t make you faster anymore; they just multiply your communication tax.

    The Reframe: Fixing the Time, Freeing the Humans

    Traditional frameworks try to eliminate the anxiety of the unknown by breaking work into tiny pieces and asking: “How long will this take?”

    Shape Up flips the script. You don’t ask for an estimate; you declare an appetite (e.g., “We are willing to spend six weeks on this problem, no more”).

    By fixing the time constraint, you liberate the small team to creatively negotiate the scope. You give them a safe, strict container, and then you get out of their way.

    The Shape Up Playbook: A Leadership Guide

    This isn’t about blindly installing a new framework; it’s about drawing inspiration to fundamentally rethink how your organization delivers software. Here is the interconnected language of Shape Up, decoded for your context:

    1. Preparing the Work (The Act of Shaping)

    • Shaped versus unshaped work: You cannot hand a micro-team a vague, unshaped idea (“fix onboarding”) and expect success. You must define the boundaries, the problem, and the guardrails before you delegate.
    • Designing at the right level of abstraction: When shaping, you don’t provide pixel-perfect wireframes—that stifles the team’s autonomy. You provide constraints.
    • Concepting with breadboards and fat marker sketches: You sketch the flow and the logic of the solution using thick markers (to prevent getting bogged down in UI details) or text-based “breadboards.”
    • Setting appetites instead of estimates: You declare what the problem is worth to the business in time (usually 2 or 6 weeks), rather than asking the team to predict the future.

    2. The Commitment (The Contract)

    • Choosing the right cycle length: Basecamp uses a six-week cycle. It’s long enough to build something meaningful from start to finish, but short enough that the end is always looming, forcing tough decisions.
    • Making bets with a capped downside: You don’t “plan” a project; you make a bet on a 6-week appetite. The “capped downside” is the circuit breaker: if the project isn’t done in six weeks, it dies. No extensions. It forces the team to ship.
    • Honoring uninterrupted time: Once the bet is made, leadership steps back. No daily stand-ups. No checking in. You give the team total focus.
    A Hill Chart diagram. It looks like a wide bell curve, with a vertical dotted line down the middle. The far left edge is labeled: Start, and the far right edge labeled: Finish. The left slope going up is labeled: Figuring out what to do. The right slope going down is labeld: Getting it done. A dot is drawn about two-thirds of the way up the left side of the hill. Light-colored arrows suggest the dot originated at the left side, moved up to its current position, and later moves over the hill and down the right to the finish.
    Uphill and Dowhill work (illustration from the book)

    3. Executing the Work (The Team’s Ownership)

    • Breaking projects apart into scopes: Instead of organizing work by technical layers (e.g., “build the database”), the team organizes work by user flows or “scopes” that can be built, clicked through, and evaluated independently.
    • Downhill versus uphill work: This is brilliant emotional vocabulary. “Uphill” work is full of unknowns, it’s the anxiety of figuring out how to solve the problem. “Downhill” work is just execution. Teams use this language to communicate their confidence levels to leadership without needing a status meeting.
    • Scope hammering: To hit the immovable 6-week circuit breaker, the team must ruthlessly separate the “must-haves” from the “nice-to-haves.” They hammer the scope down to fit the time box.

    4. The Reset

    • A cool-down period: After a 6-week cycle, you mandate a two-week cool-down. No scheduled projects. The team fixes bugs, explores new tech, and breathes. You cannot run human beings at 100% capacity indefinitely.

    The Practical Takeaway

    AI has given us the tools to keep teams incredibly lean, but lean teams require high trust and clear boundaries. Stop feeding people unshaped work and demanding estimates. Give a small team a shaped problem, a fixed time appetite, and the autonomy to hammer the scope.

    (And remember, this is just a primer. There is a wealth of tactical depth to learn in the actual book, I highly recommend reading it in full to rethink how your team builds.)

    The Coaching Prompt

    Bring these questions to your next planning session or your own weekly review:

    1. Am I tossing “unshaped” work over the fence?(Where am I causing team anxiety by delegating vague ideas instead of bounded problems?)
    2. Where are we suffering from communication tax?(Could a specific initiative be handled faster by isolating 1 designer and 1 engineer and leaving them alone for 6 weeks?)
    3. Are we managing risk through surveillance or boundaries?(Do we rely on daily stand-ups to feel safe, or do we rely on a strict “circuit breaker” that caps our downside risk?)
    4. What is currently “uphill” work for my team?(Where are they carrying the emotional weight of unknowns, and how can I help them push it over the hill into execution?)
  • Stop Trying to Outrun Your Shadow: The First Lie We Were Told About Leadership

    Stop Trying to Outrun Your Shadow: The First Lie We Were Told About Leadership

    We’ve all heard it. Maybe it was on the playground after a scraped knee, or at the dinner table after a frustrating day at school:

    “Don’t cry.”

    “Be a big girl/boy.”

    “Don’t get angry. It’s not a big deal.”

    From the time we can walk, we are taught that “strength” is synonymous with “silence.” We are coached to treat our emotions like unruly pets that need to be locked in the basement so the “productive” version of us can go to work.

    But as Andy Puddicombe, the co-founder of Headspace, famously put it:

    “Trying to outrun our emotions is as effective as trying to outrun our shadow in the sun.”

    When the sun is high and things are easy, the shadow is small. But as the day goes on and the pressure mounts, that shadow stretches out behind you, looming over every decision you make. If you don’t learn to turn around and look at it, you’ll eventually trip over it.

    The Source: Emotional Agility vs. The “Be Strong” Script

    Psychologist Susan David, author of Emotional Agility, argues that modern culture often promotes a “tyranny of positivity.” We’ve been conditioned to treat difficult emotions as problems to fix rather than experiences to understand.

    When we tell a child—or a direct report—not to feel what they are feeling, we aren’t teaching resilience. We are teaching suppression. And suppression is costly. Research shows that when people push emotions down, they don’t disappear. They tend to increase internal stress and often resurface later as disengagement, chronic stress, or emotional outbursts.

    The Reframe: Emotions as Bio-Data

    We need to stop viewing emotions as “weaknesses” and start viewing them as biological data points.

    “Problemo resoluto” Madagascar

    If you were driving a car and the “Low Oil” light came on, you wouldn’t put a piece of tape over it and say, “I’m a strong driver, I don’t need oil.” Yet, that’s exactly what we do when we tell ourselves to “power through” anxiety or “ignore” resentment.

    • The Old Way: “Stop crying/getting angry. Get back to work.” (Repression).
    • The New Way: “I feel tension in my chest. My body is noticing a threat. What is the signal?” (Literacy).

    Leadership Application: The Stone-Faced Leader

    The “Be Strong” narrative creates leaders who are emotionally stunted. If you can’t acknowledge your own fear, you will react with frustration when your team expresses theirs.

    Unexamined emotions always “leak”:

    • An unacknowledged fear of failure manifests as micromanagement.
    • An unexpressed feeling of being undervalued manifests as passive-aggression.
    • The “Don’t Cry” kid grows up to be the “Don’t Complain” boss who wonders why their turnover is so high.

    True human-centric leadership requires us to stop being “policemen” of our feelings and start being “detectives.”

    A Practical Takeaway: The “Data Scan”

    Next time you feel a “negative” emotion, don’t try to outrun it. Stand still and name it. Use the “Physical Anchor” tool:

    1. Locate it: Where is it in your body? (Tight jaw, heavy chest, knotted stomach?)
    2. Label it: Use the Emotion Wheel. Start at the center (e.g., “Sad”) and move outward until you find the specific word (e.g., “Abandoned” or “Empty”).
    3. The Mantra:“I don’t have to like this feeling to listen to the data it’s giving me.”

    The Coaching Prompt

    Try these questions to break the “Be Strong” cycle with yourself or your team:

    • The Legacy: What was the “rule” about expressing emotions in my house growing up? How is that rule affecting my leadership today?
    • The Signal: If this physical tension in my body had a voice, what is the one sentence it would say right now?
    • The Shift: Instead of trying to “get over” this feeling, what would happen if I just sat with it for 90 seconds without judging it?

    Header picture by Martino Pietropoli

  • The most dangerous four-word sentence in your office is: “What do we do now?”

    The most dangerous four-word sentence in your office is: “What do we do now?”

    I watched a new TV show last weekend, and there it was again. The line that, once you notice it, ruins almost every script it touches.

    “What do we do now?”

    I want you to watch this short clip of Reese Witherspoon explaining exactly why this four-word sentence is so toxic. It is a masterclass in identifying the subtle ways we give away our power.

    Before I heard Reese talk about this, I never truly “heard” the line. It was just background noise. I never considered it a problem, let alone a symptom of something deeper.

    This is the definition of a blind spot.

    We don’t know what we don’t know. Often, the things we are missing are the very things that would make the most difference in our growth. In movies, this line strips a character of their agency. In the workplace, it does something even worse. It turns high-performing professionals into passengers who are simply waiting for a driver.

    Once you see this pattern, you cannot unsee it. You start to notice it in meetings, in emails, and in the way teams lean on their leaders. It is the sound of potential stalling out.

    We usually think of blind spots as embarrassing or dangerous. We treat them like bugs in our software that need to be patched immediately.

    But here is the reframe: The moment you identify a blind spot, you have found your next level of performance. The “What do we do now?” feeling is a signal. It isn’t a sign that you are failing: it is a sign that you have reached the edge of your current “map.” When you feel that urge to ask for directions, you aren’t actually lost. You are just standing at the frontier of your own agency.

    The discomfort you feel when you realize you’ve been “scripted” is actually the birth of a new leadership capacity. It is the transition from a Fixed Mindset (waiting for the right answer) to a Growth Mindset (creating the answer).

    Once you realize that “What do we do now?” is a signal of a blind spot, you have to decide how to respond to it in real-time. Whether the words are coming out of your mouth or someone else’s, the goal is the same: move from Passive Waiting to Active Intent.

    When you hear yourself saying it

    It usually happens when you’re tired, overwhelmed, or facing a problem you haven’t seen before. Your brain wants to offload the cognitive load to someone else.

    The Pivot: Catch the question before it leaves your lips. If it does slip out, immediately follow it with: “Wait, let me rephrase that. Based on what I see, I think our best move is X. What am I missing?”

    The “I Intend To” Rule: Practice the habit of never presenting a problem without a proposed next step. Even if you are 90% sure your idea is wrong, stating an intent forces your brain back into the driver’s seat. It changes your posture from a passenger to a navigator.

    Intent is not “The Answer”: This isn’t about being a lone genius. Stating an intent can be as simple as saying, “I intend to pull the team together this afternoon to analyze our options.” By doing this, you aren’t waiting for a boss to tell you when to collaborate. You are designing the conditions for the solution to emerge. You are owning the process, even if you don’t own the final answer yet.

    When you hear your team saying it

    This is the “Answering Machine” trap. When a report or a coworker asks you what to do, your ego wants to provide the answer. It feels good to be the expert. But every time you provide the “fix,” you are accidentally training them to remain in the blind spot.

    Create the Container: Instead of giving the answer, hold the space for theirs. Use what David Marquet calls “The Ladder of Leadership.”

    The Reflection Technique: When they ask “What do we do now?”, respond with: “That’s a critical question. Before I share my perspective, I want to hear yours. If you were in total control here, what would your first move be and why?”

    Adjust and Decide Together: This isn’t about leaving them stranded. It’s about collaborative adjustment. Once they share their intent, you can say: “I like that logic. Let’s tweak this one part to account for X, and then let’s run with it.” You are no longer giving orders: you are refining their leadership.

    Banish the “Answering Machine” response. Next time you or your team feels stuck, remember that the goal isn’t to be right. The goal is to be active. Replace “What do we do now?” with “I intend to…” even if that intent is just to gather the right people to solve it together.

    The Coaching Prompt

    Grab a notebook or bring these to your next 1-on-1:

    1. The Reaction Audit: The last time a team member suggested a “wrong” course of action, did you shut it down or did you explore their logic?
    2. The Safety Check: Does my team know what “safe to fail” looks like in this project? Or do they feel they only have one shot to be right?
    3. The “I Intend To” Challenge: How can I encourage my team to start their updates with the phrase “I intend to” this week?

    Thank you for reading the Emerging Leadership Newsletter Each edition explores one idea that helps leaders create organizations where people take responsibility and deliver impact. If this resonates with you, feel free to share it with a colleague or start a conversation in your team.


    You can also listen to new conversations on Le Podcast on Emerging Leadership. You will find references and transcripts for each episode, along with past newsletters, on ​alexis.monville.com​.

    You can listen wherever you already get your podcasts. Just pick your favorite platform and hit “subscribe” so you won’t miss any new episodes:

    And if your favorite platform isn’t on the list, just let me know, I’ll be glad to add it.

    I’d love for you to join me there! See you in your earbuds!