Always Know Your #1

A few years back, I was in a weekly S-Team meeting. Every quarterly objective seemed to be making progress, but nothing was making it to the finish line.

There was one particular initiative that I thought would be the biggest game changer for us this quarter. It wasn’t going to be easy, but it was going to be insanely valuable. I remember pulling that leader aside to find out how he was thinking about it.

“What’s your top priority right now?” I asked.

He ticked off three things, all of them fairly important, one of which was that initiative.

But the answer was telling — he didn’t have a top priority. And he was spreading himself equally across three good things when completing one of them would unleash a massive impact on our business.

The Three #1s Problem

There’s something deeply satisfying about checking things off a list.

Our brains are wired to seek the dopamine hit of completion. So we gravitate toward tasks we can finish quickly — the emails we can clear, the small requests we can knock out, the meetings we can check off. We end up accomplishing a large quantity of tasks — while studiously avoiding the one really hard task that will actually change everything.

The result? We spend our days doing a bunch of B-level work instead of the A+ task that will move the business forward.

Peter Thiel was famous for enforcing a brutal discipline at PayPal and his later ventures: he would refuse to talk to you about anything except your #1. If you came to him with a question about your second or third priority, he’d redirect you back to the most important thing. “What’s your #1? Why aren’t you working on that right now?”

When you have three #1s, you really have zero.

I’ve come to believe this is one of the most powerful management disciplines that exists. Every person should have exactly one #1 priority. Not three. Not five. One.

And here’s the mindset shift that makes it work: when you look at a month or a quarter’s worth of objectives, I’d much rather achieve 100% of two objectives than 80% of five.

Allow me to explain.

How “Always Know Your #1” Works

After that conversation, we implemented a simple discipline across the organization: every person has a #1 priority, and everyone knows what it is.

Here’s how it works in practice.

One #1, visible to your team. Each person identifies their single most important priority. This isn’t a secret — it’s shared with their manager and visible to your team. We maintain a #1 list that shows every key person and the priority they own right now.

Your #1 wins tie-breakers. When you’re deciding between tasks, your #1 is the tiebreaker. If there’s something substantive you can do to push your #1 forward, you choose that over making progress on a lower priority. Every time.

The #1 list is a management tool. In our regular strategy reviews, we look at the #1 list and ask: are our resources aligned with what we actually need to achieve? If someone’s #1 doesn’t connect to our most critical objectives, we have a problem to solve.

This might sound rigid, but it’s actually liberating. Instead of constantly re-evaluating what deserves your attention, you’ve already decided. Your #1 is your #1 until it’s done or until circumstances force a change.

Why This Creates Speed

The real payoff isn’t just better prioritization — it’s speed.

Organizations that embrace “always know your #1” compress their cycle times dramatically. Here’s why.

Decision-making becomes trivial. When someone asks “should I work on X or Y today?”, the answer is obvious. Which one is your #1? Do that. The cognitive overhead of constantly re-prioritizing evaporates.

Context-switching drops. Every time you switch between projects, you pay a tax — the time it takes to reload context, remember where you left off, rebuild momentum. When your #1 is clear, you stay in flow longer and ship faster.

Alignment happens automatically. When the CEO knows each leader’s #1, and each leader knows their team’s #1s, misalignment becomes visible immediately. You don’t discover three months later that half your organization was rowing in the wrong direction.

The net result is that we can consistently accomplish 100% of two things rather than 80% of five things. And here’s what I’ve learned: 100% of the right two things beats 80% of five things every single time.

Speed isn’t about working faster. It’s about eliminating everything that slows you down.

When Your #1 Changes

Now, reality isn’t static. Sometimes your #1 has to change.

Maybe the market shifted. Maybe you learned something that changes the calculus entirely.

When that happens, don’t pretend your old #1 is still your #1. Update it. Tell your manager. Update your quarterly objectives if needed.

I’d rather have someone say “my #1 changed because of X, and here’s my new #1” than have them clinging to an outdated priority because it’s what they wrote down in January.

One practical tip: keep a parking lot. All those good ideas, interesting projects, and “we should really do this someday” items — write them down and put them aside. They’re not your #1 right now. That doesn’t mean they’re bad ideas. It means they’re not the most important thing. If you actually complete all 3–5 of your objectives this quarter as each one becomes your #1, you can always dig deeper from the parking lot.

The discipline isn’t about ignoring everything else. It’s about being ruthlessly honest with yourself about what matters most right now.

The Bottom Line

Here’s my challenge to you.

Can you name your #1 right now — without hesitating?

Can every person on your team name theirs?

If you asked your leadership team what their #1s are, would those answers align with the two or three things that will actually determine whether this quarter is a success?

If the answer to any of these is “no” or “I’m not sure,” you have work to do.

Sit down with your team. Force the conversation. Make everyone pick one. Write them down. Review them regularly. And watch what happens when an entire organization knows exactly what matters most.

That’s how you achieve 100% of the things that actually count.