What a 2012 Management Book Taught Our AI-Era Team
written by Stefan Christoph
The Workshop That Surprised Me
Lencioni’s six questions that create organizational clarity.
A few weeks ago, our leadership team spent a day in a workshop. No slides about AI strategy. No architecture reviews. No customer deep dives. Instead, we worked through six questions from a book published in 2012.
The book was Patrick Lencioni’s “The Advantage: Why Organizational Health Trumps Everything Else in Business” [1]. The questions were deceptively simple:
- Why do we exist?
- How do we behave?
- What do we do?
- How will we succeed?
- What is most important right now?
- Who must do what?
By the end of the day, we had more clarity about our team’s identity than months of strategy documents had produced.
Smart vs Healthy
Lencioni’s core argument is that organizations obsess over being smart (better strategy, better technology, better financial models) while neglecting being healthy: strong culture, clear communication, genuine trust, low politics.
His claim: organizational health trumps everything else. A healthy organization with a mediocre strategy will outperform a brilliant but dysfunctional one. Because healthy organizations learn faster, adapt quicker, and retain better people.
In an industry that worships technical excellence, this felt almost heretical. We spend enormous energy evaluating AI models, optimizing architectures, and debating technology choices. But the biggest friction in our work isn’t technical. It’s alignment. Who owns what. What we prioritize. How we make decisions when we disagree.
Sound familiar? The DX study on AI coding productivity found the same pattern: AI tools deliver only ~10% productivity gains because writing code was never the bottleneck [2]. Planning, alignment, scoping, code review, and handoffs (the human coordination parts) are where the time goes. Lencioni would nod.
The Four Disciplines
The book organizes around four disciplines:
Build a Cohesive Leadership Team. A small team (3-10 people) that trusts each other enough to be vulnerable. Not “I trust you to do your job” trust, but “I trust you enough to admit I was wrong” trust. Lencioni calls this vulnerability-based trust, and it’s the foundation everything else rests on.
Create Clarity. Answer the six questions above. Not in a 50-page strategy document. In simple, memorable statements that everyone on the team can repeat. If your team members give different answers to “What is most important right now?”, you don’t have clarity.
Over-Communicate Clarity. Leaders need to repeat the core messages far more than feels comfortable. Lencioni’s rule: by the time you’re sick of saying it, your team is just starting to hear it.
Reinforce Clarity. Every process (hiring, performance reviews, meetings, decisions) should reinforce the answers to the six questions. If your values say “we prioritize customer outcomes” but your promotion criteria reward internal visibility, you have a reinforcement gap.
What We Did
In our workshop, we worked through the six questions as a team. Not as an exercise in corporate wordsmithing, but as an honest conversation about what we actually believe and how we actually work.
The hardest question was #2: How do we behave? Not aspirational values, but actual behavioral norms. What do we do when we disagree? How do we handle a team member who’s struggling? What does “good enough” look like when we’re under time pressure?
The most useful question was #5: What is most important right now? Not the five strategic priorities. Not the ten OKRs. One thing. The single most important focus for the next period. Getting a team of strong-minded people to agree on one thing is harder than it sounds. And more valuable than any strategy deck. To be clear: this doesn’t mean you only work on one thing. It means you have a tiebreaker, when two priorities conflict, this is the one that wins.
The Connection to AI-Era Leadership
There’s an irony in using a 2012 book to build a team in 2026. But the timing is actually perfect.
AI is amplifying individual capability fast. A single person with the right tools can now do research, write content, build prototypes, and analyze data that would have required a team of five a few years ago. The bottleneck is shifting from “can we do the work?” to “are we working on the right things?”
This is what Lencioni’s framework addresses. When individual productivity is high but organizational clarity is low, you get a lot of fast movement in different directions. The Advantage argues that alignment (knowing why you exist, how you behave, and what matters most right now) is the multiplier that turns individual capability into team impact.
Or as Lencioni puts it: “An organization that is healthy will inevitably get smarter over time. But a smart organization that is unhealthy will eventually regress.”
What I’d Recommend
If you lead a team, especially a technical team in the AI era, read this book. Not for the management theory, but for the practical framework. The six questions are a workshop you can run in a day. The four disciplines are a checklist you can audit quarterly.
The book is deliberately simple. Lencioni acknowledges this: the concepts aren’t new or complex. The advantage comes from actually doing them, which most organizations don’t, because they’re too busy being smart. The workshop is a day. The real work is the six months after, over-communicating and reinforcing until the answers are embedded in how the team actually operates. That’s where most teams quietly drop it.
Full disclosure: our workshop was recent, and the real test is whether we sustain it. Ask me in six months whether we kept it up. But the clarity it produced in a single day was enough to convince me the framework is worth sharing now.
💬 How does your team create clarity? Do you have a shared answer to “What is most important right now?”
Sources
[1] Patrick Lencioni — “The Advantage: Why Organizational Health Trumps Everything Else in Business” (2012): https://www.goodreads.com/book/show/12975375-the-advantage
[2] DX — “AI productivity gains are 10%, not 10x” (March 2026): https://newsletter.getdx.com/p/ai-productivity-gains-are-10-not
[3] My earlier post on AI coding productivity — “AI Coding Productivity: 10%, Not 10x”: https://schristoph.online/blog/ai-productivity-10-percent-not-10x/
About the Author
Stefan Christoph is a Principal Solutions Architect at AWS, focused on agentic AI, media & entertainment, and helping builders move from demo to production. He writes about AI architecture, developer productivity, and the future of software.
This is a personal blog. Opinions expressed here are my own and do not represent the views or positions of my employer.