Dave Zaron
The short answer
Delegation & operations

The 30-Second Decision That Put $1 Billion on Our Leaderboard: Leading Under Pressure

The short answer

Under pressure, the instinct is to push harder: ask for updates, demand timelines, hover over the people doing the work. That usually makes the fix slower. The leader's job in a crisis is to set the priority, get the right people what they need, and then get out of their way. And the decisions you make in calm moments, like what to fix before launch, are what set up the crisis in the first place.

One billion dollars. That was the number on the leaderboard two hours after we went live.

But it wasn't real money.

Someone had found a way to get around our payment system and make the leaderboard show any number they wanted. Then they posted how to do it online, so now anybody could.

How did it get there?

Let me back up twenty-three days.

My company was hired to build the entire technical infrastructure for #TeamSeas, MrBeast and Mark Rober's $30 million ocean cleanup campaign. The website, the donation system and the leaderboard. All of it.

When you're building at that speed, every decision matters, including what gets built now and what gets pushed. Their previous campaign had gone down for 24 hours on launch day, so uptime was the top priority.

We accepted donations through Stripe, crypto and PayPal. Stripe and crypto had solid verification, so every transaction was confirmed on our end before anything posted. PayPal was different. The confirmation happened on the donor's side, in their browser, which meant someone could theoretically skip PayPal entirely and just tell our system a donation had come through for whatever amount they wanted.

We knew the gap was there. Closing it meant coordinating access we didn't have, getting several organizations on the phone, and working through a process that was going to eat time we couldn't afford, less than a week from launch.

So I made the call. We'd handle it after launch. The odds of someone finding it were low.

That decision took about thirty seconds.

The Next Level Sprint

Five sessions. Real fixes. A clear next move.

One on one, within ten days. $500.

Start the Sprint

$500. Full refund if the first session isn't for you.

Two hours after launch

My phone rang. It was the co-founder. "Why is there a billion dollars on the leaderboard?"

I was staring at a live system processing hundreds of thousands of dollars in real donations every hour, with an inflated leaderboard in front of millions of people.

In my head, I was running through every step at once. Stop the bleeding. Build the verification. Coordinate with the client. Validate every donation.

I got my lead engineer on the phone. How are we looking? Are we close? I need a timeline. Over and over, in his ear.

Until he said, "HEY. You need to chill out. I can't fix this with you bitching at me."

I stopped

I took a breath, and I didn't say another word until he spoke again.

It took more than two hours to stop the bleeding and build the proper solution. And we still weren't done.

Next I had to get the nonprofit's CFO on the phone. PayPal could send a notification every time a real payment came through. We just needed him to set it up on their account.

I called him, walked him through what we needed and sent him the address for the notifications. Simple enough. Except now I had to stay on the line while he logged in and clicked through screen after screen, reading carefully and not quite sure what he was looking at.

I could feel the same impulse building. Push him. Speed this up.

But I caught it. I heard my engineer's voice telling me to chill out, so I held it, took a few breaths, and waited. About fifteen minutes later he said he thought he was in the right place, and then the notifications started popping off like fireworks on the Fourth of July.

Afterward, I was sure my engineer was already updating his resume.

Four hours from that first phone call, it was handled. The site never went down. The leaderboard was accurate. And the campaign raised $30 million by January 1st.

Club Solo

Solo. Not Alone.

Software, creative support, and education to help service-based business owners turn interest into trust and bookings.

See Club Solo

What did it teach me about leading under pressure?

This wasn't my first high-stakes campaign. But it was the first time I had to face the fact that under pressure, I wasn't the leader I thought I was.

I had built my company brick by brick, and I'd gotten so used to carrying everything that I treated a crisis the same way. More pressure, more questions, more hovering. I called it being in control. What it actually did was slow down the one person who could fix the problem.

I called it confidence. What it actually looked like was a man carrying everything alone.

The lesson wasn't just about staying calm. It was about knowing what my job actually was in that moment. And stopping, it turns out, is a practice. You can't borrow someone else's reps.

What does this mean for your business?

You may never have a fake billion dollars on your leaderboard. But you'll have your version of that phone call. A system goes down during your busiest week, a key client is furious, or a mistake goes out to your whole list.

When it happens, there are two decisions that matter.

The one you make before the crisis. My thirty-second call to fix the gap later is what set the whole thing up. When you decide to push something off, be honest about what happens if the unlikely thing happens, and who will be on the hook for it.

The one you make during it. Set the priority, make sure the person fixing it has what they need, and then get out of their way. Asking for a timeline every five minutes doesn't make the fix faster. It just adds you to the list of problems.

Read next

Why Your Team Stops Following Process: The Friday Rule That Took Down 94 Websites

6 min read

Frequently asked questions

How do you stay calm as a leader in a crisis?

Focus on what's actually yours to do: set the priority, remove obstacles and make the decisions only you can make. Then step back and let the people doing the work do it.

Why does micromanaging make a crisis worse?

Constant check-ins pull the person fixing the problem away from the work. Every update you ask for is time they're not spending on the fix.

How do you decide what to fix before a launch?

Ask what happens if the unlikely problem actually happens, how bad the damage would be, and who'd have to handle it. If the answer is serious, fix it before you launch.

Scroll to read