When I was hired by the NYC LGBT Community Center to fix Cycle for the Cause, the mandate was not subtle. Fix this, or we kill it.
The ride was a massive AIDS-fundraising event, a multi-day bike ride from Boston to New York, and it had stalled. These rides are brutally expensive to put on, in money and in time. Staff take days off work to run them. They only make sense as fundraisers if they raise a metric ton of money, because the cost of putting one on is so high. This one had stopped clearing that bar, and the organization had reached the end of its patience. Make it work, or it's done.
That's the kind of pressure that makes people act fast. When someone hands you a "fix it or we kill it" mandate, every instinct says come in guns blazing, show them you're decisive, start changing things on day one so everyone can see you're earning your keep. I've watched a lot of people respond to that pressure exactly that way.
I did the opposite. I spent the first few months changing nothing at all.
I was hired only a couple of weeks before that year's ride, so the first thing I did was go on it. Not on a bike. I drove from rest stop to rest stop and I watched. How were people using the rest stops? What were they doing, what were they ignoring, how were they interacting with each other and with the event around them? I interviewed dozens of riders while they were out there in it. What was missing. What they wished existed. Whether they did other rides, and what those rides did better. I wasn't there to fix anything that weekend. I was there to see the thing running in its natural state.
Then I went into the data, and I stayed there for three months. I pulled the last ten years of rides and took them apart. Rider retention. Fundraising cohorts. I broke fundraising down by age, by gender, by employment status, by location, by the time of year someone registered. I wanted to know things nobody had thought to ask. If a rider registered earlier in the year, did they end up raising more? If they worked at one of the big New York finance firms, did their numbers run higher? Where were the clusters, the pockets of riders who were all connected to each other?
That last question turned out to matter enormously. Buried in the data were clusters: a group from Goldman Sachs, a group from JP Morgan, riders from the gay bars in Chelsea, a couple of people from Pepsi, a group from Google. These weren't random individuals. They were champions, natural hubs, people I could build official company and community teams around and turn into engines of recruitment and fundraising. Nobody had ever seen them, because nobody had ever gone looking at the data this way.
I became, frankly, a little obsessed. I'd take the analysis home on the subway and sit there scribbling in a notepad like a crazy person, because I'd just spotted a connection between two numbers that nobody had ever put next to each other. When I finally shipped the strategic plan to the Chief Development Officer, he texted me before work the next morning. I am obsessed with this document, Michael. The more I read, the more obsessed I become.
Then we executed. A full rebrand. The community engagement work. I went out and pitched those companies I'd found in the data, I presented in the amphitheaters at Goldman Sachs headquarters and Google's New York office, building official teams and new fundraising incentives. We coordinated with the NYC LGBT Community Center's communications team on social content to keep people engaged and excited all year long, not just on ride weekend. Ridership exploded. Fundraising exploded. The first ride under the new model tripled the revenue of any previous ride. It was the most successful the event had been since the nineties.
And here's the part that still matters most to me: I had built revenue projections for all of it, and when the numbers came in, I was accurate down to the dollar. We're talking about revenue in the millions, and I was off by maybe a fraction of a percent. Not because I'm clairvoyant. Because I had spent months understanding the actual mechanics of the thing before I touched it.
That accuracy is the whole argument for diagnosing before you plan, and it comes down to something close to physics.
There's a principle in quantum mechanics that the act of observing a system changes it. You can't measure certain things without your measurement itself altering the result. Operating inside a company works the same way. The moment you start changing an operation, you can no longer see what it actually was. Your own interventions become part of the data. You contaminate the very thing you're trying to understand.
So if you walk in with a mandate and immediately start moving pieces, you've blinded yourself before you ever got a clean look. You're now studying a system you've already disturbed, and you'll mistake the noise you introduced for signal. The only way to see an operation in its true state is to stand still at the beginning and let it run unobserved, the way it ran before you got there. Watch it flow. Ask questions. Gather. Resist, hard, the urge to fix.
My actual superpower isn't a playbook. It's pattern recognition, the ability to see connections in behavior and revenue and operations that the people living inside them are too close to notice. But that only works if I let the patterns reveal themselves. If I come in with preconceptions, or worse, with a mandate I start executing on day one, I'll see the patterns I expected to see instead of the ones that are actually there. Standing still isn't passivity. It's the only way to get data that isn't already bent by my own hands.
There's a second reason to diagnose first, and almost nobody talks about it, because it has nothing to do with the analysis.
It's the people.
I could have walked into Cycle for the Cause and started issuing changes. I had the mandate to do it. But I didn't, and because I didn't, something happened that turned out to be as valuable as the plan itself. I spent months listening, to the riders, to the staff who'd been running this thing for years and understood its mechanics better than I ever would, to the whole community around the event. I honored what they knew before I proposed a single thing.
So by the time we started executing, I wasn't a stranger imposing a plan on people who hadn't been asked. I had a mountain of stakeholders who were invested in my success, because I'd made them part of how the plan got built. The people who could have quietly resisted every change instead wanted the change to work. That buy-in didn't come from charisma or a good kickoff meeting. It came from the diagnostic itself. The months of listening weren't just how I found the answer. They were how I earned the right to lead the people who'd have to live with it.
This is the thing the "move fast and show them you're decisive" instinct gets exactly backwards. Coming in guns blazing doesn't just produce a worse plan, built from preconceptions instead of evidence. It also produces a plan that nobody around you is bought into, which means even a good plan dies in the execution. Slowing down at the start does the opposite on both fronts. Better answer, and an organization that wants you to win.
If you're under pressure to fix something, the hardest discipline in the world is to not immediately start fixing it. Every nerve says do something visible, fast, so people know you're working. Resist it.
The plan you build in your first week, from your assumptions and your mandate and your need to look decisive, is almost always wrong. And it's wrong in a way you can't even see yet, because you haven't watched the thing run clean. Stand still first. Watch it in its natural state. Talk to the people who've been living inside it. Let the patterns show themselves before you decide what they mean.
The plan comes second. It's supposed to. The diagnostic is what makes it any good, and the diagnostic is also what makes the people around you want it to work. Do that part right and the plan almost writes itself, down to the dollar.