In an era when AI, volatility, and organizational complexity are rewriting the rules of leadership, author and Ferrazzi Greenlight founder Keith Ferrazzi argues that the most dangerous mistake a leader can make is trying to lead alone.
In his new book, Never Lead Alone: 10 Shifts from Leadership to Teamship, and in our recent Tech Whisperers podcast conversation, Ferrazzi unpacks why traditional top-down leadership models are breaking down under the weight of AI-driven speed, scale, and interdependence, and what must replace them.
As AI moves from “bright and shiny” to simply how work gets done, Ferrazzi explains that leadership must evolve from directing work to architecting environments where trust, candor, and shared accountability accelerate decision-making and innovation. The social contracts, collaborative behaviors, and peer-to-peer accountability systems that exist across the team are the real differentiators in this environment.
Rather than waiting for the leader to set the pace, the best teams coach one another, challenge one another, co-elevate one another, and move faster, because they and their leaders have built cultures where candor is a shared responsibility. For CIOs navigating the messy middle of AI, modernization, and talent transformation, this shift from leadership to what Ferrazzi calls “teamship” may be the most important upgrade of all.
In a conversation after the podcast wrapped, Ferrazzi spent more time discussing the mindsets, practices, and habits CIOs must cultivate to shift from leadership to teamship — and to architect high-performing, AI-enabled organizations. What follows is that conversation, edited for length and clarity.
Dan Roberts: You’ve said that great teams need less leadership. Can you talk a bit about how technology leaders need to think differently about their role?
Keith Ferrazzi: The No. 1 shift is to move from leadership to teamship. That means stop thinking of leadership as a hub and spoke. Don’t think aboutwhat you need to give feedback on, how you need to hold people accountable, how you need to do this or that. Instead, think about, how do you get your team to step up and meet each other, to give each other feedback, to hold each other’s energy up. Get out of the center and expect your team to step up.
I was working with the executive team of a global company that was rolling out AI across engineering, product, and operations. The CEO was exhausted. Every meeting was about people waiting for him to weigh in on priorities, on tradeoffs, on conflicts.
We ran a simple experiment. In their weekly leadership meeting, we took the CEO out of the middle. He could listen, but he couldn’t decide anything unless the team explicitly asked. At first it was awkward. People kept looking at him. But after about 15 minutes, something shifted. The product leader challenged engineering directly. Operations called out a risk nobody wanted to surface. The CFO pushed back on a roadmap that wasn’t grounded in reality. The quality of the conversation went up, not down, when the ‘leader’ stepped out of the center.
That’s teamship. Leadership doesn’t disappear. It moves into designing the conditions where the team holds itself accountable.
Most leaders intellectually agree with the idea of teamship but struggle to operationalize it. How can leaders start building a culture that supports the shift?
The most important thing leaders need to do is build a challenge culture. As an example, the book [Never Lead Alone] talks about stress testing, a practice that replaces the stale, passive report-outs at meetings. Think about all the meetings you’ve been in where someone’s clicking through an endless PowerPoint deck about their project’s status. How many people are tuned out, checking their emails and texts, or, let’s face it, struggling to stay awake? Especially if the project isn’t directly related to something they’re working on or could impact them in some way, most people will just be sitting there waiting for the presentation to be over.
This is a huge lost opportunity. Because the practice itself is unengaging, you’re missing out on the candid discussion and opinions of the entire team. That’s rich conversation that could elevate the project, help surface previously overlooked risks or challenges, and introduce innovations and ideas. There may even be team members who can step up to support the project in new ways. This is what stress testing does. A form of engaged peer feedback, it’s the superfood of a high-performing team, and it’s rooted in a culture of challenge, curiosity, bold innovation, and support.
To be effective, stress testing needs to be positioned as a service to the person who’s giving the project update. We’re not trying to make them look bad or catch them in what they’re doing wrong. The feedback should be offered and received as data, with no presumption that they have to act on it. By reducing the emotional charge that often comes with feedback, this opens up more honest and productive discussions.
You also want to make sure everyone knows in advance that they have a responsibility to be engaged and attentive. This isn’t about sitting back passively. It’s about being prepared and leaned-in so you’re ready to comment, because immediately following the presentation, you’ll be working in small breakout groups to write down challenges, risks, ideas, innovations, and offers of help.
Stress testing also demands a new kind of presentation. Instead of a 20-page report, the project point person is now putting together a deliberate, purposeful one-page summary of what’s been achieved, what they’re struggling with, and what’s next. They will have the opportunity at the end to reflect and share with the others ‘yes, no, maybe’ responses to their suggestions and ideas.
This is an example of how structured processes help drive culture change and establish a challenge culture. As these practices are repeated, they become new habits.
How do you build psychological safety so that people have the comfort to challenge each other?
That’s the relationship layer. Here’s a really simple practice leaders can use as a personal and professional check-in. I often open meetings by asking, ‘What’s really going on for you? Where might you be struggling, personally and professionally?’
As this is intended to reveal struggles, it can and often does elicit deeper responses. When leaders go first and answer honestly, it creates instant permission for others to do the same, and that’s where psychological safety begins.
There’s another simple practice that our research shows increases psychological safety by 85%: ‘The Power of Three.’ When you have a dozen people in a virtual meeting, split them up into breakout rooms of three people per room. Let them engage in the small group first. Not only do team members feel safe and heard, you’ll also find that better ideas will arise this way.
The shift from leadership to teamship is a big mental and operational shift. What are some practical strategies CIOs can apply to make that transformation?
The first step is to think about, how do we redefine ‘team’? How do we stop thinking of team as the org chart and start thinking about team as: Who do you need to get the job done? One way to frame it is to say, let’s wake up and start collaborating like the kids out of Stanford do, which is not in meetings. The world’s best teams operate under a fundamentally different social contract, one built on peer-to-peer accountability and co-elevation rather than hierarchy. So then the question is, how do we build a culture where team members are open about what they think and committed to pushing each other to greater heights? And then, how do we collaborate more broadly? How do we start doing asynchronous collaboration more effectively?
That’s really about some simple practices like meeting shifting, using asynchronous collaboration, and collaborating with tools more than you collaborate in meetings. Instead of sitting in meetings, people can work on projects and problems individually while posting updates and having more thoughtful, less rushed debates and conversations on shared platforms like Teams, Slack, and the multitude of other options available to us now. These modern collaboration practices and tools ultimately enable bolder innovation and faster decision-making.
One of the biggest objections leaders raise to shared leadership is, ‘If everyone owns it, no one owns it.’ How do you prevent teamship from becoming a lack of accountability?
That fear is rooted in a misunderstanding of how high-performing teams actually work. In traditional leadership models, accountability flows upward: People worry about what the boss will think. In teamship, accountability flows sideways: People worry about letting their peers down.
Our research shows that when teams adopt co-elevation behaviors and peer-to-peer commitments, accountability actually increases dramatically. Why? Because you’re no longer hiding behind hierarchy. Your teammates see what you’re doing every day.
This is especially critical in an AI-enabled organization, where work moves too fast and too broadly for any one leader to supervise it all. If peers don’t hold each other accountable in real-time, you lose speed, quality, and innovation.
As work becomes more distributed, adaptive, and human-machine integrated, no single leader can see enough, know enough, or move fast enough alone. As Ferrazzi shows us, the most successful, disruptive organizations will be those that intentionally design high-performing teams where peers challenge peers, feedback flows freely, and accountability travels laterally, not just vertically. For more from Ferrazzi on what CIOs must do to make the essential shift from leadership to teamship, tune in to Tech Whisperers podcast.
See also:
Read More from This Article: Rethinking IT leadership to unlock the agility of ‘teamship’
Source: News