Flow

Why tracking your approaches makes you better at them

5 min read

Memory is a bad scorekeeper. After a night out, you'll remember the one rejection that stung and forget the three conversations that went fine. A week later, your gut will tell you "I'm not getting anywhere," even if you've been steadily improving. Writing things down fixes that, because a log doesn't care which moment felt worst.

Why your memory lies to you

Psychologists have a name for the tendency to weigh bad experiences more heavily than good ones: negativity bias. A widely cited 2001 review by Roy Baumeister and colleagues, titled "Bad Is Stronger Than Good," pulled together evidence that negative events tend to have a bigger and longer-lasting effect on people than positive ones of similar size.

You don't need the research to recognize it. One awkward no can color an entire evening. That's a problem when you're trying to judge whether you're making progress, because your memory hands you a highlight reel of the worst parts.

A log gives you the boring, accurate version. Six approaches. Two good conversations, one number, three nos. That's a decent night, even if the drive home felt otherwise.

What tracking actually does for you

It shows progress you'd otherwise miss. The difference between your first month and your third is hard to feel from the inside. It's obvious on paper.

It separates effort from outcome. You control whether you approach. You don't control whether the other person is interested. Counting approaches, not just results, rewards the part you control.

It surfaces patterns. Maybe your approaches in coffee shops go better than the ones in bars. Maybe you do well early in the night and fade after an hour. You can't spot that from a handful of memories.

It keeps you consistent. A visible streak or a weekly total is a small nudge to go out when you'd rather stay home. Small nudges add up.

What to log

You don't need much. The minimum is useful on its own, and the extras make it more useful.

The minimum

Define "success" for yourself before you start and stick to it. For some people, it's getting a number. For others, it's any conversation where the other person was clearly enjoying it. Either works. Changing the definition halfway through makes the numbers meaningless.

Useful extras

That last one is the most valuable. A single line like "waited too long to ask for her number" is more useful than a page of reflection. If you want to go deeper on a particular night, a full field report is the next step up.

What not to log

Don't write down personal details about the people you talk to. Leave out full names, what they looked like, photos, and anything else that could identify them. You're tracking your own actions and choices. They didn't agree to be in your notes, and a log that reads like a collection of people is the wrong mindset entirely. Keep it about you.

How to read your numbers

Look at volume first

Early on, the most important number is how many approaches you're doing. Success rate is noisy when the sample is small. Going from 1 out of 3 to 2 out of 3 looks like a huge jump, but it's one conversation.

Get your volume up and steady before you pay much attention to anything else.

Calculate success rate honestly

A sensible way to calculate success rate is successes divided by successes plus rejections. Leave out anything that didn't clearly resolve either way. That keeps the number tied to real attempts.

Don't optimize for success rate

This is the big trap. If you start caring a lot about your success rate, the easiest way to improve it is to only approach people when it feels like a sure thing. That makes the number look better while making you worse at the actual skill. A lower success rate with more approaches is usually a sign of more courage, not less ability.

One bad night means nothing. Look at weeks and months. Is your volume stable or growing? Are conversations lasting longer? Are more numbers turning into dates? Those trends are where the real information is.

A weekly review

Once a week, take ten minutes and look back. A few questions to ask:

Keep the answers short. The goal is a small adjustment, not a full self-assessment.

Pitfalls

Lying to the log. Skipping the bad nights, inflating outcomes, or counting near-misses as approaches. A log you don't trust is useless.

Obsessing over it. If you're checking your stats more often than you're going out, the tracking has become the hobby. It should take a minute after each approach and ten minutes a week.

Treating rejections as failures. They're attempts. In a well-designed log, a rejection counts toward your total just like a success does. If rejections are hitting you hard, how to handle rejection has practical ways to deal with them.

Turning people into numbers. The numbers are about you. The people you meet are people. If you notice yourself thinking of anyone as a "stat," step back.

Where tracking fits

Tracking is a tool, not the goal. It's most useful when you're actively trying to build a habit, like during the 100 approaches challenge, or when you feel stuck and want to figure out why. It's also a quiet confidence builder. Scrolling back through months of approaches is a concrete reminder that you've done this many times and survived every one. That's a big part of building real confidence.

Flow is built around this. You log each approach as Success, Rejected, or Pass from the home screen, and only successes and rejections count toward your totals and success rate. Stats shows your streaks, success rate, and an outcome funnel from number to dating, and Sessions let you group a night out so you can see how a whole evening went. Logging works offline, too, so you can log right after an approach and it'll sync later.