The Back Row (When Only the Enthusiasts Stand Up)
The Problem
Your instinct is to start with the enthusiasts. Of course it is. They're already building. The AI channel has a few dozen people posting every day. Gather them in a room, give them more tools and let the energy spread. It doesn't spread. A room full of enthusiasts being enthusiastic looks, to everyone else, like the AI people being into AI. Your best builder has been doing remarkable work in a corner by the window for a year, and nobody has noticed. Meanwhile, the senior person everyone listens to has sent their team a two-line email: do the training, and don't put any real data into these tools.
The Principle
It moves from the front row. When someone people watch stands up, the room follows. John Miller and Scott Page call it the standing ovation problem. Whether the whole room stands depends on where the first person is sitting. In the back row, almost nobody notices. In the front row, everyone does. Same performance, different seat. So before you plan a session, ask one question about the person you're counting on: when they stand up, will enough people see it? Often the best person to invite is a respected skeptic, asked personally and honestly. People listen to you, and you won't fake being impressed. Let your enthusiasts be the helpers in the room, and don't script anybody.
4 Steps to Take Action
- 1
Find your front row
List the five people others in your company watch. Not by title: the person everyone asks, the one whose opinion travels.
- 2
Invite a skeptic personally
A call or a coffee, never a mass email. Be honest about why. Expect a polite no at least once.
- 3
Make the enthusiasts helpers
One helper for every six to eight people, with one rule: never grab the keyboard.
- 4
Don't script the stand-up
End with each person saying what they actually did. If someone in the front row stands up, let them.
💡 Inspired By
Chapter 4 of The Second Factory, "The Front Row." And two ideas about how movements start: the standing ovation problem from John Miller and Scott Page, and Derek Sivers' talk on the first follower.
This is what Analytics Pitfalls & Principles is about: people helping people.
In Practice
Nora Berg had her first invitation half written. Theo, who'd been building his own campaign tools in a corner for a year. Marisol, whose shared document had halved three colleagues' response times. Rita, whose forty-two-row checklist was the best in the company. All wonderful. All in the back row. She deleted it and went to see Rachel, the VP of Finance, whose two-line email telling her team not to put financial data into the tools had done more to slow adoption than anything else in the company. "Because you're the most skeptical senior person in the building," Nora told her. "If it doesn't work for you, it doesn't work. And if it does, people will listen." "Three hours," Rachel said. "And I'm sitting in the front." Fifteen minutes into the hands-on part, Rachel found a reconciliation her team had spent months on. Then she stood up, picked up her laptop and walked to the next table, where one of her own analysts was making a chart. "I know what I said. I was wrong about how to think about it. Come and look." Theo had been building for a year, and nobody had noticed. Rachel had been at it for fifteen minutes, and the whole room was on its feet.
